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: <4AE2E830.9040106@gmail.com>
Date: Sat, 24 Oct 2009 12:42:40 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
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> <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> <20091024085445 DOT GW16678 AT calimero DOT vinschen DOT de> <20091024090651 DOT GX16678 AT calimero DOT vinschen DOT de> <4AE2C97A DOT 3080608 AT gmail DOT com> <20091024094816 DOT GY16678 AT calimero DOT vinschen DOT de>
In-Reply-To: <20091024094816.GY16678@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: <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

Corinna Vinschen wrote:
> On Oct 24 10:31, Dave Korn wrote:
>> 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.
> 
> Erm... *iff* we add US-ASCII encoding it should be an equivalent
> to "ASCII", shouldn't it?

  Don't ask me, I don't understand any of this stuff.  I mean, yes, probably
so, I just thought US-ASCII might be something different from ASCII and that
the difference might be that it implied the US code page.  I guess I should
have said 'a "US-ASCII" alias, standing for whatever it ought to stand for.'

    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