Hi,
At Fri, 2 Feb 2001 18:11:40 +0000 (GMT),
Robert Brady <[EMAIL PROTECTED]> wrote:
>> (1) ISO-2022 is free from 'mojibake', as I wrote.
> How come?
If ISO-2022 escape sequences were be recognized in every modes,
xterm -8, -u8, and -lc. If so, even if you invoked xterm with
wrong mode, ISO-2022 string will be displayed correctly. Thus,
application softwares can use ISO-2022 for very important messages.
>> (2) ISO-2022 is free from Unicode's overreaching CJK han unification.
>> (bad legacy from mess 16bit Unicode.)
> Would support for plane14 language tags make you happy?
> (Note : this is not a promise to implement them).
I don't know well on them. Where can I study it?
I also heard about 'variant tag'.
However, I imagine it would be a vaporware. How difficult
is it to implement language/variant tag? It introduces
new 'backspace' problem but we have to solve this in future.
(Well, I think they will have higher priority than ISO-2022.)
>> (4) ISO-2022 support is easier for the current implimentation of w3m
>> than Unicode. (I don't know about the internal of w3m; this is
>> what the w3m developer said.)
>
> That doesn't sound like a very convincing reason, you can just stuff all
> output through a 2022 -> UTF-8 converter. Don't see any reason for this
> to be in the terminal itself...
Ok, I stop to be a spokesperson for w3m developers, because I don't
know the real reason.
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
