This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: "C" character set (again)
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Thu, 7 Jan 2010 13:57:10 -0500
- Subject: Re: "C" character set (again)
- References: <416096c60912282254r7230cbaeiad6b3432f7c15257@mail.gmail.com> <4B3A0379.1090508@byu.net> <416096c60912290611y1a946525r4af6b2727b3725a7@mail.gmail.com> <20100107100611.GA23972@calimero.vinschen.de> <4B461D6B.10503@gmail.com>
- Reply-to: cygwin-developers at cygwin dot com
On Thu, Jan 07, 2010 at 05:44:11PM +0000, Dave Korn wrote:
>Corinna Vinschen wrote:
>>
>> First of all, Happy New Year to all of you!
>
> :) Likewise
>
>>> Trouble is, Cygwin currently is the only significant platform where
>>> plain "C" implies UTF-8, as far as I know anyway.
>
>> I'm still not convinced that C == C.ASCII is really such a good idea for
>> us. What other conversion problems are waiting right around the bend?
>> Shouldn't we rather try to fix some of the issues which show up on the
>> list?
>
> Yeah. I'm for WJM here. Takeup of i18n is years behind where it should be.
> If it's ever going to be anything but a joke, we're going to have to switch
>it on always everywhere by default and go through the pain sooner or later.
>Same goes for all the big linux distros; some of them are just starting to
>dabble their toes in the water, they're running up against similar problems.
>Might be kind of nice for Cygwin to be leading the pack amongst *[iu]x distros
>for a change instead of lagging some way behind!
Except that we're not supposed to be a leader in this regard since we
are supposed to be emulating not innovating.
cgf