X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4AE2C97A.3080608@gmail.com> Date: Sat, 24 Oct 2009 10:31:38 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: 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> <4AE24BE4 DOT 8020207 AT gmail DOT com> <4AE281BC DOT 1040200 AT cwilson DOT fastmail DOT fm> <416096c60910232247tb0ed351l2d542125bf566d7e AT mail DOT gmail DOT com> <20091024085445 DOT GW16678 AT calimero DOT vinschen DOT de> <20091024090651 DOT GX16678 AT calimero DOT vinschen DOT de> In-Reply-To: <20091024090651.GX16678@calimero.vinschen.de> 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: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Corinna Vinschen wrote: >> Can I get a STC which shows the aforementioned problem? BTW, I don't see why this is anything other than a gcc testsuite problem; if we want to use UTF-8 as the default encoding in the C locale, who's to say we shouldn't? I think it's just up to the testsuite to set the right flags for the known target platform, isn't it? The only thing I think we might benefit from is a "US-ASCII" alias for CP437, perhaps. > 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? The test was written long before GCC was updated to internationalise and unicode-aware its error messages. Once it started doing fancy output, rather than update the testsuite to allow all the different forms of quotes etc., it was simplest to just force the C locale to suppress the generation of utf-whatever fancy quotes. That worked only as long as the default encoding in the C locale happened to be ASCII... which it was for most systems until fairly recently, but now it's not just us but some of the linux distros are moving to UTF-8 by default as well and they have the same problem. cheers, DaveK -- 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