From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: cygwin started speaking German today
Date: Sat, 17 Sep 2011 22:50:00 -0000 [thread overview]
Message-ID: <4E751602.8070201@cornell.edu> (raw)
In-Reply-To: <20110917204041.GC28100@jethro.local.lan>
On 9/17/2011 4:40 PM, David Sastre wrote:
> On Tue, Sep 13, 2011 at 09:45:37AM -0600, Eric Blake wrote:
>> On 09/09/2011 08:59 AM, Corinna Vinschen wrote:
>>> On Sep 9 13:33, Andy Koppe wrote:
>>>> The 'C.UTF-8' default locale is not a bug, it was a deliberate design decision.
>>>
>>> Exactly. And it has been discussed a lot on the cygwin-apps mailing
>>> list.
>>>
>>> And above all, there *is* an official way for the user to align the
>>> Cygwin locale with the Windows locale, see the -s and -u options
>>> of the locale(1) command:
>>>
>>> http://cygwin.com/cygwin-ug-net/using-utils.html#locale
>>
>> On 09/09/2011 09:09 AM, Corinna Vinschen wrote:
>>>> OK, then the following four facilities are needed in Cygwin.
>>>>
>>>> 1) We need the name of the locale which is in effect when the user has
>>>> not specified environment variables.
>>>
>>> In Fedora, for instance, the fallback is what is set as system default
>>> in /etc/sysconfig/i18n.
>>>
>>> In Cygwin the fallback is the system default set in
>> /etc/profile.d/lang.sh
>>> or /etc/profile.d/lang.csh.
>>>
>>> Why should libintl use anything else on Cygwin, but not on Linux?
>>>
>>
>> Given this, I think the bug is in cygwin for having base files
>> /etc/profile.d/lang.{sh,csh} which hardcode LANG to C.UTF-8 instead
>> of using locale -s -u to default LANG to the preferred Windows
>> settings. Libintl should NOT be second-guessing an explicit setting
>> of LANG, but cygwin should NOT be explicitly setting LANG to C.UTF-8
>> in its default startup scripts without any regards to the Windows
>> settings. Whether setlocale(LC_ALL,"") returns C.UTF-8 or a
>> Windows-appropriate string _when LANG is undefined_ is still worth
>> solving, but right now, an out-of-the-box cygwin installation
>> _always has LANG defined_ by the default startup scripts. So our
>> first focus should be to get that setting of LANG fixed to honor
>> Windows, and to teach libintl that when LANG is set we really meant
>> it.
>
> WRT the base-files package, would it be acceptable/does it make sense to set:
>
> test -z "${LC_ALL:-${LC_CTYPE:-$LANG}}"&& export LANG=${locale -sU}
>
> in /etc/profile.d/lang.sh and
>
> if ( $?LC_ALL == 0&& $?LC_CTYPE == 0&& $?LANG == 0 ) setenv LANG = `locale -sU`
>
> in /etc/profile.d/lang.csh, both as proposed, _and_ a (possibly) commented-out
>
> test -z "${LC_ALL:-${LC_CTYPE:-$LANG}}"&& export LANG=${locale -uU}
>
> in the skeletal .bash_profile and .profile (i.e. both system-wide and
> user defined settings)?
If you want the user-defined setting to take effect, wouldn't you have
to omit the `test -z ...'? LANG will already be set when .bash_profile
is processed.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-09-17 21:50 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 10:18 Voelker, Bernhard
2011-08-30 11:28 ` Charles Wilson
2011-09-08 2:31 ` Charles Wilson
2011-09-08 10:46 ` Bruno Haible
2011-09-08 10:55 ` Voelker, Bernhard
2011-09-08 11:06 ` Eric Blake
2011-09-08 12:05 ` Charles Wilson
2011-09-08 12:48 ` Andy Koppe
2011-09-08 13:13 ` Eric Blake
2011-09-08 12:51 ` Andy Koppe
2011-09-08 21:58 ` Bruno Haible
[not found] ` <201109082344.55506.bruno@clisp.org>
2011-09-09 9:18 ` Charles Wilson
2011-09-09 12:33 ` Andy Koppe
2011-09-09 15:00 ` Corinna Vinschen
2011-09-10 11:36 ` Thorsten Kampe
2011-09-13 18:39 ` Eric Blake
2011-09-17 21:50 ` David Sastre
2011-09-17 22:50 ` Ken Brown [this message]
2011-09-18 3:19 ` David Sastre
2011-10-04 12:29 ` Corinna Vinschen
2011-10-04 12:46 ` Charles Wilson
2011-10-04 14:30 ` Corinna Vinschen
2011-10-04 18:04 ` Erwin Waterlander
2011-10-04 18:21 ` Corinna Vinschen
2011-10-05 16:04 ` Erwin Waterlander
2011-10-05 16:28 ` Corinna Vinschen
2011-10-05 16:52 ` Erwin Waterlander
2011-10-05 17:32 ` Charles Wilson
2011-10-05 18:24 ` Ken Brown
2011-10-05 18:29 ` Corinna Vinschen
2011-10-05 18:44 ` Erwin Waterlander
2011-10-05 18:50 ` Yaakov (Cygwin/X)
2011-10-05 18:58 ` Christopher Faylor
2011-10-10 17:24 ` Corinna Vinschen
2011-10-11 15:41 ` Erwin Waterlander
2011-10-11 16:54 ` Charles Wilson
2011-10-11 17:29 ` Christopher Faylor
2011-10-16 18:42 ` Charles Wilson
2011-10-17 6:59 ` Corinna Vinschen
2011-10-17 13:17 ` Charles Wilson
2011-10-17 13:52 ` Corinna Vinschen
2011-10-17 13:58 ` Corinna Vinschen
2011-10-05 18:29 ` Corinna Vinschen
2011-10-06 1:35 ` [OT] " Andrey Repin
2011-10-05 12:08 ` Ken Brown
2011-09-09 15:13 ` Charles Wilson
2011-09-09 20:08 ` Andy Koppe
2011-09-08 13:45 ` Corinna Vinschen
2011-09-08 13:51 ` Corinna Vinschen
2011-09-08 20:57 ` Bruno Haible
2011-09-09 15:09 ` Corinna Vinschen
2011-09-09 15:58 ` Andy Koppe
2011-09-10 11:45 ` Thorsten Kampe
2011-09-10 13:50 ` Christopher Faylor
2011-09-10 16:10 ` Thorsten Kampe
2011-09-10 17:11 ` Christopher Faylor
2011-08-31 8:39 Voelker, Bernhard
2011-08-31 14:01 ` Charles Wilson
2011-08-31 15:19 ` Charles Wilson
2011-09-01 5:30 Voelker, Bernhard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E751602.8070201@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).