Thorsten Glaser wrote: > 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)
some work? Do you mean some work and some doesn't work? Please tell me in what case Lynx doesn't work with Shift_JIS setting. > - utf-8 pages don't work in kterm (no conversion) Please try --enable-japanese-utf8 configure option which is introduced from 2.8.6dev.4. > - 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 -> 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 -- Takeshi Hataguchi E-mail: [EMAIL PROTECTED] _______________________________________________ Lynx-dev mailing list [EMAIL PROTECTED] http://lists.nongnu.org/mailman/listinfo/lynx-dev
