On Fri, 08 Sep 2006 00:27:10 +0900 (JST), [EMAIL PROTECTED] wrote: > > On kterm with ja_JP.eucJP, lynx can display a page of both > > ISO-2022-JP or euc-jp (or even UTF-8) if a source file setts > > a correct charset=ISO-2022-JP or charset=euc-jp. > > > > But on uxterm with ja_JP.UTF-8, it seems lynx fails to display > > a page of ISO-2022-JP but can dispaly correctly a page of euc-jp. > > (precisely, lynx doesn't display a page of euc-jp completely > > correctly but it can dispaly japanese characters well.) > > It must fail because there is no mechanism to convert iso-2022-jp to > utf-8 in current Lynx code.
I've understood the main problem but now the next problem comes to my mind. If lynx already knows the conversion from euc-jp to utf-8 then the following > > (precisely, lynx doesn't display a page of euc-jp completely > > correctly but it can dispaly japanese characters well.) could be a problem. I prepared two screen shots to show the problem. Please visit http://www1.pm.tokushima-u.ac.jp/~kohda/lynx/ and kterm.png is a screen shot of lynx on kterm (correct screen) and uxterm.png of lynx on uxterm (wrong screen). Is this a problem of terminal or of conversion mechanism? And is it possible to fix this in a short time, i.e. before 2.8.7? Regards, 2006-9-15(Fri) -- Debian Developer & Debian JP Developer - much more I18N of Debian Atsuhito Kohda <kohda AT debian.org> Department of Math., Univ. of Tokushima _______________________________________________ Lynx-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lynx-dev
