X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4AE281BC.1040200@cwilson.fastmail.fm>
Date: Sat, 24 Oct 2009 00:25:32 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
CC: "Joseph S. Myers" <joseph AT codesourcery DOT com>,
   Richard Guenther <richard DOT guenther AT gmail DOT com>,
   "gcc AT gcc DOT gnu DOT org" <gcc AT gcc DOT gnu DOT org>,
   Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject: Re: dg-error vs. i18n?
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>
In-Reply-To: <4AE24BE4.8020207@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

[cross-posted to cygwin list]

Background for cygwin list: Dave discovered a problem running some of
the gcc tests.  The 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 ').

Dave Korn wrote:
> Thanks, that was it.  Had to use "C.CP437" in the end, apparently we have
> charset encoding names for lots of OEM code pages but none for plain vanilla
> ASCII.

That's interesting. I had thought "ascii" was a fairly common encoding
name; I know I've seen both 'encoding="ascii"' and 'encoding="us-ascii"'
in XML documents.  Maybe we (cygwin) should add an explicit
plain-old-ascii encoding name?

--
Chuck

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