X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.3 required=5.0 tests=BAYES_50,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW,SARE_SUB_ENC_UTF8,TW_RX X-Spam-Check-By: sourceware.org Message-Id: <1271259908.18480.1369934327@webmail.messagingengine.com> From: "Charles Wilson" To: "cygwin AT cygwin DOT com" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" Subject: Re: UTF-8 breaks 'ascii' Date: Wed, 14 Apr 2010 11:45:08 -0400 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 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". This is less of a concern now -- because (a) rxvt is, if not deprecated, at least discouraged, and (b) other terminals like rxvt-unicode, xterm, and mintty have different and better mechanisms to support such line art. And cygwin-in-cmd.exe "just works" too, thanks to improvements in cygwin's terminal handling code. So...yeah, I'll remove those in the next release. -- 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