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
