> -----Original Message-----
> From: Robert Brady [mailto:[EMAIL PROTECTED]]
...
> > 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?
I don't know if anyone *really* cares, but they are there, and
they are "doublewidth". But: 1) UAX 11 does care about this for
compatibility reasons; and 2) this kind of "width" data really
belongs *in* (or associated with) the font. So by choosing an
appropiate font list (in your terminal emulator preferences, or
whatever) one could provide the "context" needed, even for PUA
characters. An FDCC-set is most certainly the wrong place (unless
you also consider putting fonts there...).
Kind regards
/kent k
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
