MIME-Version: 1.0
In-Reply-To: <1271259908.18480.1369934327@webmail.messagingengine.com>
References: <1271259908.18480.1369934327@webmail.messagingengine.com>
Date: Wed, 14 Apr 2010 18:59:18 +0100
Message-ID: <o2k416096c61004141059z85efba04le3465c6675cba59b@mail.gmail.com>
Subject: Re: UTF-8 breaks 'ascii'
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Charles Wilson wrote:
> Kenneth wrote:
>> Maybe it shouldn't attempt to display code points 128..255
>> since they aren't really ascii.
>
> You're probably right. =C2=A0Originally, ascii didn't display those code
> points; I added it back when a big concern was getting the "correct"
> fonts for rxvt-windows and cmd.exe so that line graphics (pstree -G,
> etc) would display properly. =C2=A0It was a quick way to tell that "yes,
> those line art characters are present at the appropriate char values".

I still find it useful for much the same reason, when testing the
plethora of supported charsets. How about disabling the extended code
points by default and having an option for enabling them?

Andy

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