X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.9 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: <4AE281BC.1040200@cwilson.fastmail.fm>
References: <4AE235E4.2060005@gmail.com> 	 <84fc9c000910231559y194a9ccfyfb9414f8ed04a361@mail.gmail.com> 	 <Pine.LNX.4.64.0910232305540.30905@digraph.polyomino.org.uk> 	 <4AE24BE4.8020207@gmail.com> <4AE281BC.1040200@cwilson.fastmail.fm>
Date: Sat, 24 Oct 2009 06:47:43 +0100
Message-ID: <416096c60910232247tb0ed351l2d542125bf566d7e@mail.gmail.com>
Subject: Re: dg-error vs. i18n?
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

2009/10/24 Charles Wilson:
> [cross-posted to cygwin list]
>
> Background for cygwin list: Dave discovered a problem running some of
> the gcc tests. =C2=A0The tests were run in the "C" locale, but in so doing
> they assumed an ascii encoding (specifically, that "'" would match ' in
> test patterns -- but the program actually emitted those fancy curled
> quotes which did not match ').

Do you mean they explicitly set the "C" locale?

Hmm. Now that we've got the "C.UTF-8" default, "C" could actually go
back to mean ASCII. With no locale variables set, the console and
filesystem would use UTF-8 anyway, as would applications that call
setlocale(,""). Only applications that don't call setlocale() would be
using the "C" locale and hence ASCII, as but that'd be fine as either
they don't care about it or they actually expect to be using ASCII.

> Dave Korn wrote:
>> Thanks, that was it. =C2=A0Had to use "C.CP437" in the end, apparently w=
e have
>> charset encoding names for lots of OEM code pages but none for plain van=
illa
>> ASCII.

Actually, we do: "C.ASCII". Except it's 8-bit rather than 7-bit as
elsewhere, making it practically the same as "C.ISO-8859-1".

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

