X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4AE2C97A.3080608@gmail.com>
References: <4AE235E4 DOT 2060005 AT gmail DOT com> 	 <84fc9c000910231559y194a9ccfyfb9414f8ed04a361 AT mail DOT gmail DOT com> 	 <Pine DOT LNX DOT 4 DOT 64 DOT 0910232305540 DOT 30905 AT digraph DOT polyomino DOT org DOT uk> 	 <4AE24BE4 DOT 8020207 AT gmail DOT com> <4AE281BC DOT 1040200 AT cwilson DOT fastmail DOT fm> 	 <416096c60910232247tb0ed351l2d542125bf566d7e AT mail DOT gmail DOT com> 	 <20091024085445 DOT GW16678 AT calimero DOT vinschen DOT de> 	 <20091024090651 DOT GX16678 AT calimero DOT vinschen DOT de> 	 <4AE2C97A DOT 3080608 AT gmail DOT com>
Date: Sat, 24 Oct 2009 19:44:44 +0100
Message-ID: <416096c60910241144u58db0c27m8e4ccad852fb9beb@mail.gmail.com>
Subject: Re: dg-error vs. i18n?
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

2009/10/24 Dave Korn:
> =C2=A0BTW, I don't see why this is anything other than a gcc testsuite pr=
oblem; if
> we want to use UTF-8 as the default encoding in the C locale, who's to sa=
y we
> shouldn't?

POSIX certainly allows it, but glibc's behaviour has to be taken into
account as well. If there was a de-facto standard of C meaning ASCII
that people rely on, Cygwin would be better off going with that.

> which it was for most systems until
> fairly recently, but now it's not just us but some of the linux distros a=
re
> moving to UTF-8 by default as well and they have the same problem.

You mean they're switching the unadorned "C" locale to UTF-8? That
would be great. Have you got examples?

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