X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW,SARE_SUB_ENC_UTF8,TW_RX X-Spam-Check-By: sourceware.org Message-ID: <4C69670A.5090405@cwilson.fastmail.fm> Date: Mon, 16 Aug 2010 12:27:54 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: "cygwin@cygwin.com" Subject: Re: UTF-8 breaks 'ascii' References: <1271259908.18480.1369934327@webmail.messagingengine.com> In-Reply-To: <1271259908.18480.1369934327@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 4/14/2010 11:45 AM, 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. Originally, 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. It was a quick way to tell that "yes, > those line art characters are present at the appropriate char values". Andy Koppe wrote: > 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? Done, for 1.4.6: I added a new option '--extended'. -- Chuck -- 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