From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 814 invoked by alias); 8 Sep 2009 19:35:15 -0000 Received: (qmail 772 invoked by uid 22791); 8 Sep 2009 19:35:14 -0000 X-Spam-Check-By: sourceware.org Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 08 Sep 2009 19:35:07 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 9E1D36D55B9; Tue, 8 Sep 2009 21:34:56 +0200 (CEST) Date: Tue, 08 Sep 2009 19:35:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: The C locale Message-ID: <20090908193456.GC17515@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <416096c60908300959i1e0084b1xc8f6e65e792b035d@mail.gmail.com> <20090831005258.GG2068@ednor.casa.cgf.cx> <416096c60909012329l2f25e735yc07145b8d6698cda@mail.gmail.com> <3f0ad08d0909020656v7d9fce6ft4afea63ed363b9a9@mail.gmail.com> <416096c60909071308qc5ff057sbe9cb1dbc270554f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <416096c60909071308qc5ff057sbe9cb1dbc270554f@mail.gmail.com> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2009-09/txt/msg00184.txt.bz2 On Sep 7 21:08, Andy Koppe wrote: > Which leaves one apparently good solution for the "C" locale: > >> - Use the default Windows codepage for filenames, console, and > >> multibyte functions. This is what happens already if you specifiy a > >> locale with a language but no charset, e.g. "en". Maximum 1.5 > >> compatibility. UTF-8 has been chosen because it has the advantage that every UTF-16 Windows filename will result in a valid multibyte string. Every choice has its advantage and its trade-offs. Maximum 1.5 compatibility (what for and how long?) vs. maximum default usability in the long run (at least I hope so). > On a closely related note, Debian are introducing a "C.UTF-8" locale > as a language-neutral locale with a UTF-8 character set. This is > useful for choosing UTF-8 without picking up language-specific stuff > like sorting rules. See here: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522776. It's a rather > lengthy thread, but in the end they did decide to go for it. Doesn't just setting LC_CTYPE=fo_ba.UTF-8 has the same result? > Cygwin 1.7, through newlib, already has "C-UTF-8", as well as the > likes of "C-ISO-8859-1" or "C-SJIS". So how about replacing the "C-" > with "C." in those, considering that Cygwin has no backward > compatibility requirement regarding those? No, but newlib has. That was the only reason to keep these specifiers. 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