On Sat, 30 Jun 2001, Tomohiro KUBOTA wrote:
> Ah, I didn't think about this possibility. I guess you mean
> you might be bothered by many encodings such as EUC-TW,
> Shift_JIS, GB18030, and so on. Then how about using iconv()
> for "luit"? Portability problem? Then try libiconv.
I think, Juliusz has already understood that naively using iconv() alone
might not necessarily be well suited well for luit, because it doesn't
resynchronize all encodings cleverly. You need a bit additional logic. If
you press ^C in an application that spits out BIG5 in an unfortunate
moment or truncate a string by counting bytes, then you will loose BIG5
synchronization, and the terminal has to skip characters in the input
stream until is finds two G0 characters in a row to be sure again where
the next character starts. BIG5 is an example of a rather messy encoding,
not only in that respect. ISO 2022 is far worse.
Markus
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
