iconv standardization (Re: xterm and XIM)

[Tomohiro KUBOTA <tkubota@xxxxxxxxxxx>]

Hi,

At Fri, 08 Jun 2001 11:38:13 -0700 (PDT),
hiura@xxxxxxxxxxx wrote:

>> It is a good effort.  It will improve the portability of iconv().
>> ("we" means Li18nux?)
> Not necessarily limit to Li18nux, all of us whom with good will to
> resolve the problem. ;-)

Who is "all of us"?  I have heard some commercial Unix systems
have curious iconv() behavior.  For example, iconv() of SunOS 5.6 
cannot convert "eucJP" -> "UCS-4", though it can convert
"eucJP" -> "UTF-8" -> "UCS-4".  HP-UX 10.x cannot convert
"eucJP" -> "ucs4" while it can convert "eucJP" -> "ucs2" -> "ucs4".
It must be "ucs4", not "UCS-4".
(I heard these problems from Hironori Sakamoto, a developer of
w3m-m17n.)  Do you think such confused situation will be fixed?

Some systems add BOM while others don't.  How about endian?


> Please accept my sincere apologees (;-;).
> I (as a part of UTC) will continue work hard fixing and improving Unicode.

I know you are working hard to fix these problems.  However, nobody
knows your work will be accepted or not, because of some political
reasons.  Of course I strongly hope your work to be accepted.

---
Tomohiro KUBOTA <kubota@xxxxxxxxxx>
http://www.debian.or.jp/~kubota/
"Introduction to I18N"  http://www.debian.org/doc/manuals/intro-i18n/
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/