This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: dg-error vs. i18n?

On Oct 24 10:54, Corinna Vinschen wrote:
> On Oct 24 06:47, Andy Koppe wrote:
> > 2009/10/24 Charles Wilson:
> > > [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 ').
> > 
> > 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.
> Oh boy.  That's not just an easy one liner patch.
> Can I get a STC which shows the aforementioned problem?

Somehow I don't understand how a test application running in the "C"
locale could emit characters outside the ASCII range at all and another
part of the test expects the emitted character to be in the ASCII range.
How did that happen?


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]