On Thu, 16 Nov 2000, Karlsson Kent - keka wrote:
> Maybe not those, but it is my understanding that the "Ambiguous"
> width value (in the Unicode EA Width data) indicates that the
> character is "Wide" in some non-Unicode EA encodings, and
> "Narrow" in some other, usually not EA, encoding. So you need
> to know the "context" (here: originally used, non-Unicode,
> character encoding) to figure out the "width".
Exactly. This why said UTR is totally useless for terminals.
We can't send context information along with text files or telnet/ssh
sessions - we just have to define a context that is acceptable for as
many people as possible and just use it everywhere.
This won't support silly CJK contexts with doublewidth cyrillic letters,
but does anyone care?
--
Robert Brady
[EMAIL PROTECTED]
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
