On Sun, May 01, 2005 at 05:42:05AM -0400, Larry W. Virden wrote:
> From: Henry Nelson <[EMAIL PROTECTED]>
> > Thus, even if I have
> > Lynx display the raw UTF8, the terminal emulator has no way to present it.
>
> Even with no way to present it, the data should not be corrupted.
Sorry, I shouldn't have spoken since I was talking about the rendering
aspect, i.e., someone sees weird characters so _assumes_ that the input
was corrupted when it really wasn't. (I've never used UTF for input
since I have no way to do it. All I can say is that just reading it is
a pain with character-cell applications, e.g., Lynx and Mutt, over a
terminal emulator that can only use fixed-width fonts. UTF is fine
when the charset range is covered by the font, but it doesn't work at
all for characters that don't have a glyph.)
Just curious, but how does this work for you unix purists? How do
XWindows terminal emulators get around the fixed-width font problem
we Windoze people suffer when using PuTTY or TeraTerm?
__Henry
"Using Lynx is like wearing a really good pair of shades: cuts out
the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
-- me, March 1999
_______________________________________________
Lynx-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lynx-dev
