On 4/11/11 1:10 AM, Allan McRae wrote:
> I am seeing what appears to be some sort of UTF-8 conversion issue in
> bash-4.2. I do not see this in bash 4.1. I think the easiest way to
> describe this is:
>
>
>> bash41 --version
> GNU bash, version 4.1.9(2)-release (i686-pc-linux-gnu)
>
>> LC_ALL=ru_RU.UTF-8 bash41 -c привет
> bash: привет: command not found
>
>
>> bash42 --version
> GNU bash, version 4.2.8(2)-release (i686-pc-linux-gnu)
>
>> LC_ALL=ru_RU.UTF-8 bash42 -c привет
> bash: $'\320\277\321\200\320\270\320\262\320\265\321\202': команда не найдена
>
>> LC_ALL=ru_RU.KOI8-R bash42 -c привет
> bash: привет: ������� �� ������
>
>
> I'm not sure what further information is needed here, so let me know if you
> need anything else to replicate this.
There is a change in bash-4.2 that prints characters in error messages
using ANSI-C escapes if isprint() fails for any character in the string.
It's intended to make things like \r in filenames visible. It came in
from cygwin, but is generally useful.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
