Hi,
At Fri, 2 Feb 2001 14:46:59 +0100 (CET),
Bruno Haible <[EMAIL PROTECTED]> wrote:
> If you say Japanese terminals are usable without ISO-2022 support, why
> do you want XTerm to support ISO-2022? This would only lead to more
> Japanese software that does special hacks for supporting this old
> ISO-2022. It'd be better if software from Japanese authors would use
> standard APIs (mb/wc etc.), so it can be more useful outside Japan.
I wrote the reason in the previous mail.
| Note my original story is not about ISO-2022-JP but ISO-2022.
| And more, the advantage of ISO-2022 which I wrote above would be
| lost if ISO-2022 is used only under ISO-2022 locale. (The point
| of this idea is that ISO-2022 can co-exist with any other encodings.
| Thus, terminals can [theoretically] support both locale encoding
| and ISO-2022 at the same time. Novice users may fail to set-up
| locale and LANG variable properly but ISO-2022 can be used everytime.)
> Take for example w3m, a superb text mode browser. It has special
> options for JIS, Shift_JIS, EUC-JP, but nothing which works with all
> encodings.
I have discussed with a w3m developer. He said w3m will support
ISO-2022 output in future and he was interested in whether XTerm
will support ISO-2022 or not.
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://surfchem0.riken.go.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/lists/
