On Tue, 30 Jan 2001, Tomohiro KUBOTA wrote:
> it is important XTerm (150-23-k5) is usable anyway. Thus, I think you
> may leave half-character problems for futher discussion while we should
> release XTerm with locale-sensibility ASAP. (Well, we need to integrate
> my patch and selection patch.)
I've got some fixes (mainly plane related) to sync in, are you planning a
-k6 soon?
> [1] I posted a message to Debian JP Developers Mailing List that
> XTerm will support locale encodings and we are now developping it.
> Then I received a mail to ask whether it will support ISO-2022,
> from a developer who is involved into an internationalization
> project of a text-based web browser.
> Theoretically, ISO-2022 can co-exist with almost other encodings
> such as ISO-8859-*, EUC-*, UTF-8, Shift_JIS, and so on because
> these encodings don't include ISO-2022's escape sequences.
Does ISO-2022 see much/any use as the locale encoding, or it it just used
for interchange?
> Thus, theoretically it is possible that XTerm support ISO-2022
> without damaging 8bit/UTF-8/locale encodings. Though I would
> be glad if XTerm would support ISO-2022, I know it need a large
> amount of labor and none of us (including me) are brave enough
> to try this work...
--
Robert Brady
[EMAIL PROTECTED]
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
