X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 28 Sep 2009 18:16:26 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: The C locale Message-ID: <20090928161626.GC8378@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090921103758 DOT GE20981 AT calimero DOT vinschen DOT de> <416096c60909211420g4ac8ea93l80fc1f00dcd5c0f3 AT mail DOT gmail DOT com> <3f0ad08d0909240003j435818e7h6f7cde2e26188f7e AT mail DOT gmail DOT com> <20090924073441 DOT GA30267 AT calimero DOT vinschen DOT de> <3f0ad08d0909240237s518de248jee409b731711404a AT mail DOT gmail DOT com> <20090924095701 DOT GC30851 AT calimero DOT vinschen DOT de> <20090924100006 DOT GD30851 AT calimero DOT vinschen DOT de> <20090926091504 DOT GA7275 AT calimero DOT vinschen DOT de> <3f0ad08d0909262021u5fe79873r65850865166ce40f AT mail DOT gmail DOT com> <3f0ad08d0909280903t5caaf611ie4049a73beb93f06 AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3f0ad08d0909280903t5caaf611ie4049a73beb93f06@mail.gmail.com> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Sep 29 01:03, IWAMURO Motonori wrote: > 2009/9/27 IWAMURO Motonori : > >> LANG="ja" -> EUCJP > >> LANG="ja_JP" -> EUCJP > > > > Hmmm, It is a difficult problem. > > > > I think selecting UTF-8 is good because eucJP is legacy. > > > > But, for interoperability with other UNIX-like system(*), I don't > > think selecting UTF-8 is good. > > > > * Solaris: ja, ja_JP -> eucJP > > * Linux (Debian): ja -> Unknown, ja_JP -> eucJP > > > > I need to think more... > > My conclusion is as follows as a result of hearing other Japanese > people's opinion: > > LANG=ja -> UTF-8 > LANG=ja_JP -> UTF-8 > > Because, we specify "eucJP" explicitly when we need it. Hmm. That's an interesting point. In theory this sounds like a good idea to be used for all locales which don't specify the charset explicitely, because that results in using the same charset, "UTF-8", for all such locales. "C", "ja" or "en_US" would all default to UTF-8. The downside is that a user, who needs to work under the default ANSI codepage for some reason, has to know the name of the default ANSI codepage. Right now any user who needs the default ANSI codepage can simply set LANG to some language code and go ahead, without having to know the number. With your solution, that wouldn't be possible anymore and the user would have to figure out the default ANSI codepage on the system before being able to use it. I honestly don't know if that's really a problem, though. But I don't want to take that feature away for now. Anybody having a strong opinion on this issue? 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