On Tue, 15 May 2001, Markus Kuhn wrote:
> > Markus Kuhn writes:
> > > I'd like to have in some standard tool a function that looks at
> > > nl_langinfo(CODESET) and then sends out the corresponding ISO 2022
> > > sequence to make sure the terminal knaows about the encoding of the
> > > current locale.
> In any case, I don't really care at all about full ISO 2022 support for
> any imaginable encoding. I really just want a simple mechanism to keep
> locale and terminal in sync for those users who use both ISO 8859 and
> UTF-8 for some interim period before a permanent adoption of UTF-8
> becomes feasible. Whether there is an ISO 2022 sequence for BIG5 or not
> is completely irrelevant in that context. The tool would simply output
> nothing if the locale isn't ISO 8859 or UTF-8. For BIG5 etc. users,
> nothing would change.
Hmm, may I call this idea too Eurocentric ;-)? As for non-ISO-2022
compliant encodings such as Big5/CP950, Shift-JIS/CP932, CP949(Unified
Hangul Code), CP936/GBK, JOHAB/CP12xx, I agree with you. However, there
are people like me who want to switch between fully ISO-2022 compliant
encodings (which are not ISO-8859-x) and UTF-8 depending on the locale.
ISO-2022-compliant encodings other than ISO-8859-x include EUC-KR,
EUC-CN (usually/misleadingly refered to as GB2312-80), EUC-JP and EUC-TW.
All right, EUC-TW is very rarely used if used at all. However, EUC-JP,
EUC-CN, and EUC-KR are as widely used as ISO-8859-x and there ARE
ISO-2022 ESC seq. to activate these encodings.
Jungshik Shin
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
