MIME-Version: 1.0
In-Reply-To: <20090928161626.GC8378@calimero.vinschen.de>
References: <20090921103758.GE20981@calimero.vinschen.de> 	 <3f0ad08d0909240003j435818e7h6f7cde2e26188f7e@mail.gmail.com> 	 <20090924073441.GA30267@calimero.vinschen.de> 	 <3f0ad08d0909240237s518de248jee409b731711404a@mail.gmail.com> 	 <20090924095701.GC30851@calimero.vinschen.de> 	 <20090924100006.GD30851@calimero.vinschen.de> 	 <20090926091504.GA7275@calimero.vinschen.de> 	 <3f0ad08d0909262021u5fe79873r65850865166ce40f@mail.gmail.com> 	 <3f0ad08d0909280903t5caaf611ie4049a73beb93f06@mail.gmail.com> 	 <20090928161626.GC8378@calimero.vinschen.de>
Date: Tue, 29 Sep 2009 05:27:29 +0100
Message-ID: <416096c60909282127h775c674n89fa9b0a6d55d221@mail.gmail.com>
Subject: Re: The C locale
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

2009/9/28 Corinna Vinschen
>> My conclusion is as follows as a result of hearing other Japanese
>> people's opinion:
>>
>> LANG=3Dja -> UTF-8
>> LANG=3Dja_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. =C2=A0"C", "ja" or "en_US"
> would all default to UTF-8.

Hmm, there's much to be said for that.

> 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. =C2=A0Right 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. =C2=A0With your solution, that wouldn't be possible anym=
ore
> and the user would have to figure out the default ANSI codepage on the
> system before being able to use it.

How about an explicit "ANSI" charset that maps to GetACP()? And "OEM"
for GetOEMCP()? Those would make easy replacements for the
CYGWIN=3Dcodepage:[ansi|oem] option.

Andy

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