bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#6546: win32 grep/shell utf-8 encoding


From: Laimonas Vėbra
Subject: bug#6546: win32 grep/shell utf-8 encoding
Date: Fri, 23 Jul 2010 22:07:16 +0300
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100504 SeaMonkey/2.0.5

Eli Zaretskii wrote:
Date: Fri, 23 Jul 2010 18:50:54 +0300
From: Laimonas Vėbra<address@hidden>
CC: address@hidden

Eli Zaretskii wrote:

You cannot easily change the locale of a Windows system by specifying
some environment variable.  You need to actually switch it
system-wide.  As long as we use ANSI APIs on Windows, we can only

I am talking about LANG env settings, which we can freely change for the
cygwin apps to act differently (as we need).

You are talking about Cygwin programs, while I'm talking about the
native w32 build of Emacs.  The effect of LANG and the way to change
the locale is different for each one of these two.

I am talking about LANG setting restrictions, that Emacs implies. I think -- it shouldn't.


You can't, sorry.

You can. That example was supposed to show, that you can freely change
LANG variable and cygwin utils, which relies on it, acts appropriately.

Again, I was not talking about Cygwin, I was talking about the native
w32 build of Emacs.  It doesn't use the Unicode (UTF-16) APIs, so it
can only support the current codepage when it invokes programs through
the Windows APIs.

It *can* (try mingw example, that i posted) pass utf-8 encoded (and in other encodings) arguments when it invokes external programs and for that it doesn't need to use UTF-16 API _everywhere_. Like i said -- now it (perfectly) works with native/mingw apps without any change.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]