This is the mail archive of the
mailing list for the Cygwin project.
Re: suggestion (was Re: 1.7.7: Localization does not follow the language of the OS)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 12 Jan 2011 22:11:45 +0100
- Subject: Re: suggestion (was Re: 1.7.7: Localization does not follow the language of the OS)
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
On Jan 12 18:47, firstname.lastname@example.org wrote:
> > The official way to set the locale is to use the locale(1) tool, see the
> > User's Guide http://cygwin.com/cygwin-ug-net/using-utils.html#locale
> > export LANG=`locale -u` setenv LANG `locale -u`
> > export LANG=`locale -s` setenv LANG `locale -s`
> > or better
> > export LANG=`locale -uU` setenv LANG `locale -uU`
> > export LANG=`locale -sU setenv LANG `locale -sU`
> Thanks for this suggestion. I tested the locale command, and it does
> what you describe.
> Unfortunately, the people who download my application usually don't have
> Cygwin, so I'll have to distribute locale.exe with my application. Also,
> this trick will add extra complexity to my software, which is (AFAIK) not
> necessary on other UNIX platforms.
> Despite these disadvantages, I think this is a useful solution for me.
> locale.exe is only 18kB; I'll just check the license again to see if this
> distributing is OK.
locale.exe is Cygwin licensed, and it's a Cygwin application, so you
would have to distribute the Cygwin DLL as well. Plus the Cygwin source
codes (which include the locale.exe source codes), to adhere with the GPL.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple