>> Heck, I don't know what text encoding I'd have >> to change this Terminal window to to make sure the chars showed up the
> Well, this topic is not really specific to the lynx-dev mailing list, > and > only involves Lynx in relation to the display character set. When you > say "Terminal window," do you mean X on some Unix, Microsoft Windows or > something else? If X, why not UTF-8? Under X, UTF-8 is certainly the best way. Anyone can go to Thomas's page and grab the newest xterm-16x (http://dickey.his.com/xterm). If Unix one's using doesn't support UTF-8 locale, just run it with '-u8' option with some free iso10646-1 X11 fonts. display-charset of Lynx can be set to utf-8 and it'll work perfectly for web pages encoded in single byte legacy encodings as well as in UTF-8. For MS-Windows, there are a couple of pretty good terminal emulators that support UTF-8 (putty is one of them) under which one can connect to a remote Unix host (ssh and telnet if somebody still wants to use it). However, as I wrote in my message Henry refered to, this does not yet work for CJK (multibyte) legacy encodings because Lynx does not know how to convert between Unicode/10646 and CJK encodings. That's why 'α' is rendered as 'a' when display charset is one of CJK encodings (i.e. the same way as it's rendered under ISO-8859-x terminal where x is not 7) although CJK legacy encodings CAN represent 'alpha' (albeit in double-width). I tried to hook up iconv(3) to chartrans module of Lynx, but I wasn't able to figure out how. Could anyone help? > If Windows98 or above, I believe > Microsoft has a variety of "code pages" free for downloading. I haven't tried a Windows-port of Lynx. Does it run under MS-DOS(or command prompt) box? If that's the case, under Windows 2k/XP (and perhaps NT4), one can set the codepage to 65001 ( 'chcp 65001' ) to get a UTF-8 command prompt box. Jungshik ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
