X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Tue, 4 Oct 2011 16:29:20 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygwin started speaking German today
Message-ID: <20111004142920.GA15757@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <7856072A9D04C24B82DFE2B1112FE38A0C27492B56@MCHP058A.global-ad.net> <201109081246.23238.bruno@clisp.org> <4E68AF35.9030002@cwilson.fastmail.fm> <201109082344.55506.bruno@clisp.org> <4E69D9EA.2050004@cwilson.fastmail.fm> <CAHWeT-bQ=Qm7qyWzb9s-=Lfgwjh-vHrEk2BvYQS6X6707+EWMg@mail.gmail.com> <20110909145921.GA27289@calimero.vinschen.de> <4E6F7AA1.4090808@redhat.com> <20111004122837.GA27229@calimero.vinschen.de> <4E8B0007.5020500@cwilson.fastmail.fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4E8B0007.5020500@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Oct  4 08:45, Charles Wilson wrote:
> On 10/4/2011 8:28 AM, Corinna Vinschen wrote:
> > On Sep 13 09:45, Eric Blake wrote:
> >> 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.
> > 
> > Bug?  Didn't we choose C.UTF-8 after a long discussion?  Are the points
> > raised in this discussion invalid or outdated now?  Why?  I don't object
> > against using `locale -sU' in lang.sh/lang.csh, but we should not do
> > this without a discussion of the pros and cons.
> 
> IIRC, that discussion occurred before the 'locale' application (was
> written|got smarter).  Sure, I think C.UTF-8 should be the "default
> default" but the arguments in favor of respecting the users' own Windows
> i18n settings make sense.

Does it?  Even if I'm running a german OS, I absolutely hate to see
german diagnostic output from gcc, and I absolutely hate certain
programs using non-ASCII chars in output.  (In)famous examples are
Unicode quoting chars rather than ' or ", or using the Unicode hyphen
character rather than -.  But that's just me.

> However, one issue is that windows basically will always have SOME
> setting -- even if just "English".  Which would cause locale to report
> 'en_US' or something.  So you'd never actually SEE the "default default"
> of C.UTF-8 take effect.  Also, would locale append '.UTF-8' (or would
> lang.{sh,csh} do so?).

That's what the -U option is for.  See `locale --help'.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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

