[w3m-dev-en 00007] Re: iso-2022-kr (Re: w3m-i18n/m17n)

From: Hironori Sakamoto (h-saka@lsi.nec.co.jp)
Date: Mon Jan 17 2000 - 23:55:04 CST


>> From: ChiDeok Hwang <cdhwang@sr.hei.co.kr>
>> > >> From: ChiDeok Hwang <cdhwang@sr.hei.co.kr>
>> > >> A comment from korean.
>> > >> Forget ISO-2022-kr. None uses that encoding for web pages
>> > >> nowoaday in korea.
>> > Does not any korean use ISO-2022-kr in plain text or e-mail ?
>> No. Usage of ISO-2022-kr in mail was deprecated from the several
>> years ago in Korea. We use (base64 or qp)+euc-kr or just euc-kr.

Thank you. I had thought that ISO-2022-kr is coding for e-mail in Koren.

>> The recent glibc seems to support iconv. We can convert successfully to EUC-KR
>> from UTF-16 or conversely. In such system, charmap table is spurious.
>> How about using iconv if available?

I think we should try using iconv, but becase it isn't installed
in my system(FreeBSD), I don't know it well.
# I have Chuguev's iconv-0.2. Is it same as iconv of glibc ?

When iconv is used, there are some problems which I understand.
* The tables of JIS X 0208 and CP1258 in w3m are special,
  because the tables in unicode.org have problems.
* The tables of JIS X 0208/0212 and CNS 11643-1/2 are combinated
  in order to treat simply.
Therefore, I am afraid that the replacement is difficult.

-----------------------------------
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