Thanks alister. Turning tracing on was a great idea.

I was able to get around my previous issue by finding an alternative to piping. However, I have another spot where I am also using a pipeline and I am seeing the same issue.

Code:

tail -n +$license_start $0 | head -n $length | uudecode -o /dev/stdout

(I am using a combination of head and tail to get encoded data between two line numbers and then piping that into uudecode. There is probably a better way to do this but for now id like to solve this piping issue.)

Alister, I took your advice and turned tracing on.
In en_US or C for the locale I get this:

Code:

+ tail -n +46382 ./install.sh
+ head -n 2217
+ uudecode -o /dev/stdout

(and then the decoded file)

In other locales like cs_CZ i get this:

Code:

+ tail -n +46382 ./install.sh | head -n 2217 | uudecode -o /dev/stdout

as if it is all one command...


I am very new to shells, encoding etc. Sorry, i do not know exactly which sh I am using.

However, I noticed that when I change the locale from cs_CZ to cs_CZ.UTF-8 piping works. Is this just an encoding problem?