>> Hironori Sakamoto <hsaka@mth.biglobe.ne.jp> wrote:
>> > http://www2u.biglobe.ne.jp/~hsaka/w3m/patch/w3m-0.1.6-i18n-3.patch.gz
>> Since w3m is also a pager, I've tried to use it to look at the
>> UTF-8 example texts included in Markus Kuhn's ucs-fonts package,
>> with both display encoding and document encoding set to UTF-8.
>> This doesn't work correctly. Many characters are missing. Cyrillic
>> isn't affected, but Greek and IPA are badly mangled, Georgian
>> disappears entirely.
Now, w3m-i18n basically uses Unicode as a table for conversions
between character sets. The display and output are optional.
Unicode is always re-mapped to ISO-2022 based character sets or
CP???(which are similar to ISO-8859-*) because it is difficult
to handle Unicode as own code points.
Therefore, some characters which are in only Unicode can not be
handled, and some conbinated characters can not be correctly handled.
In the future, Unicode may be handled as own code points.
But, I have no plan now. Sorry.
-----------------------------------
Hironori Sakamoto <hsaka@mth.biglobe.ne.jp>
http://www2u.biglobe.ne.jp/~hsaka/
This archive was generated by hypermail 2b29 : Wed Jul 19 2000 - 10:30:43 CDT