Thomas Dickey dixit:
>It would not be surprising if there are some remaining display problems,
I'm okay with the current feature set:
- most japanese pages work in kterm (note that my lynx is
still English, and neither locale nor gettext/nls support
exists in the operating environment)
- some work if I set both lynx and kterm to display character
set Shift-JIS (lynx seems to not convert between them)
- utf-8 pages don't work in kterm (no conversion)
- utf-8 pages still look more than weird in uxterm
(screenshot on request)
What would be nice is if 2-4 could be fixed as well.
As for the conversion: you're already converting well
between ASCII approximations of chars (� -> Ue, € -> EUR
and others), can't we do that with japanese stuff as
well? The tables required should be to find in eg. iconv
or the big unicode.txt file; the code 'seems' to be
there (else I would see garbage when viewing the
latin1/latin2 test pages in kterm).
bye,
//mirabile
_______________________________________________
Lynx-dev mailing list
[EMAIL PROTECTED]
http://lists.nongnu.org/mailman/listinfo/lynx-dev
