|
From: | Laimonas Vėbra |
Subject: | bug#6546: win32 grep/shell utf-8 encoding |
Date: | Fri, 23 Jul 2010 15:54:34 +0300 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6 |
Eli Zaretskii wrote:
Date: Fri, 23 Jul 2010 00:48:28 +0300 From: Laimonas Vėbra<laimonas.vebra@gmail.com> CC: 6546@debbugs.gnu.orgDid you try to add a suitably-valued LANG variable to process-environment? That would at least force Cygwin executables to work in the Windows codepage.The only way it works is when i set LANG process-environment variable to the current windows locale codepage and 'coding-system-for-write' to the encoding/charset in which i'd like to grep.That's the only way it's _supposed_ to work.
Then i suppose it's wrong/incorrect way of what is supposed to operate like that.
Why? Because for the correct behaviour we (external app, Emacs) shouldn't require to set locale to some fixed setting; it should be freely changed as many cygwin apps relies on that. For example, how do you sort data with improper locale settings (which are required to be fixed)? Will seek for another workaround?
Example: echo -e "-ĔĿİ-\n_ĔĿİ_\nELI\nĔĿİ" > file.txt $ export LANG=lt_LT.cp1257 $ cat file.txt -Ä”ÄæÄ°- _Ä”ÄæÄ°_ ELI Ä”ÄæÄ° $ cat file.txt | sort _Ä”ÄæÄ°_ Ä”ÄæÄ° -Ä”ÄæÄ°- ELI $ export LANG=lt_LT.utf-8 $ cat file.txt -ĔĿİ- _ĔĿİ_ ELI ĔĿİ $ cat file.txt | sort _ĔĿİ_ ELI ĔĿİ -ĔĿİ-
Yes, this is the only setup that is supposed to work.
Maybe it is/was suppose to work (at all) like that in the sense of workaround, but i doubt if it was/is supposed to be correct.
[Prev in Thread] | Current Thread | [Next in Thread] |