This is the mail archive of the
mailing list for the Cygwin project.
Re: dg-error vs. i18n?
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- 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>
- Date: Sat, 24 Oct 2009 00:25:32 -0400
- Subject: Re: dg-error vs. i18n?
- References: <4AE235E4.firstname.lastname@example.org> <email@example.com> <Pine.LNX.firstname.lastname@example.org> <4AE24BE4.email@example.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
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?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple