X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 24 Oct 2009 10:54:45 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: dg-error vs. i18n?
Message-ID: <20091024085445.GW16678@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT 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>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <416096c60910232247tb0ed351l2d542125bf566d7e@mail.gmail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
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

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?


Corinna

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

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