On 15 May 2001, Juliusz Chroboczek wrote:
> JS> However, there are people like me who want to switch between fully
> JS> ISO-2022 compliant encodings (which are not ISO-8859-x) and UTF-8
> JS> depending on the locale.
>
> This is an issue which is currently of concern to me. Which of the
> non-ISO 2022 encodings do we want to support?
Ooops, in the paragraph you quoted, I was talking about ISO2022 *compliant*
encodings such as EUC-KR/CN :-)
> Do they all preserve at least C0?
>
> - UTF-8;
> - ???.
Anyway, as for non-ISO 2022 encodings I mentioned in my other message,
all of them (CP932/Shift-JIS, CP949/UHC, CP950/Big5, GBK/CP936,
Johab/CP12xx) preserve C0 as far as I know.
> What escape sequences do you suggest they should use?
I can't be of much help,here. I don't think much thought has been
given to this and I doubt there's any esc. seq. devised for those encodings.
Do you really want to support switching to and from those NON-ISO-2022
encodings? If you really have to, Big5 may have to be supported because
zh_TW does not use an ISO 2022 compliant encoding even in Unix (I
don't know how they worked around problems arising from conflict with
C1. Perhaps, that issue was set aside....)
Jungshik Shin
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
