X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 24 Oct 2009 11:48:16 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: dg-error vs. i18n?
Message-ID: <20091024094816.GY16678@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> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AE2C97A.3080608@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 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?


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