1.7.1 release date?
Andy Koppe
andy.koppe@gmail.com
Wed Dec 2 09:49:00 GMT 2009
2009/12/2 Corinna Vinschen:
> On Dec 1 23:53, Thomas Wolff wrote:
>> Corinna Vinschen schrieb:
>> >On Dec 1 18:44, Thomas Wolff wrote:
>> >> * What about the Cygwin.bat LANG setting? The last comment on this
>> >> was Andy voting for LANG rather than LC_CTYPE, which I can agree
>> >> with; several Linux distributions set LANG by default.
>> >I'm still not really convinced that it's necessary. It would be a
>> >simple change to setup.exe, but the content of cygwin.bat is hardcoded
>> >into setup and I don't like the idea to set the language in the
>> >installer tool.
>> Not the language, only the encoding. The common proposal was
>> LANG=C.UTF-8, so just manifesting explicitly what is the internal
>> default anyway. I don't think it can be harmful and even if it may
>> not be necessary for many applications, it may be helpful for some
>> and thus avoid trouble; also it's the usual thing to do by Linuces
>> that use UTF-8 as a default.
>
> Yeah, but they don't have it hardcoded in the installer. As discussed,
> we should move the creation of cygwin.bat out of setup.exe soon, and then
> we can set LANG.
>
> Even then I would prefer if some package (base-files probably) would
> two files:
>
> /etc/profile.d/lang.sh:
> export LANG=C.UTF-8
>
> /etc/profile.d/lang.csh:
> setenv LANG C.UTF-8
These need to be guarded so as not to override an existing LANG setting.
For example with 'LANG=C.ASCII xterm -l', you'd get xterm using ASCII,
whereas the programs running inside it would use UTF-8. Same with
mintty's locale setting in the options dialog.
Andy
More information about the Cygwin-developers
mailing list