This is the mail archive of the
mailing list for the Cygwin project.
- From: Andy Koppe <andy dot koppe at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 9 Oct 2011 17:29:10 +0100
- Subject: Re: locale
- References: <4E917965.firstname.lastname@example.org>
On 9 October 2011 11:37, Jan Kolar wrote:
> Re: /cygwin-patches/ Add locale.exe option for querying Windows UI languages
>> Corinna Vinschen-2 wrote in
>> h t t p : old nabble com
>> Therefore, afaics, it would be better if we change locale to use the
>> GetFooDefaultUILanguage functions by default, and we add a modifier
>> (-r/--region?) to switch to LOCALE_FOO_DEFAULT.
> Please, could locale follow what is standard and/or usual, that is "
> write information about the current locale environment Â "
> how a cygwin-native a program sees it. ÂCygwin-native =
> " Â Â Â When invoked without arguments, locale summarizes the current
> locale environment for each locale category defined Âby the LC_*
> environment variables.
> " (man locale Âon ÂLinux)
> I use
> Â ENVIR=value Â locale
> (on Unixes) to find out what locale setting will recieve-and-use any
> Program if I call it with
> Â ENVIR=value Â Program
> That is, I expect Âlocale.exe (without options) to show how standard
> libraries interpret current LOCALE(7) setting, that is what setting is
> obtained from current settings in environment and files.
> For example
> $ uname
> $ locale
> LC_COLLATE="en_US" ...
> # I am not happy now
> $ export LC_ALL=cs_CZ
> $ Âlocale
> LC_COLLATE="cs_CZ" ...
It already does that. This thread is about additional Cygwin-specific
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple