> -----Original Message-----
> From: Markus Kuhn [mailto:[EMAIL PROTECTED]]
...
> Beyond that EUC tradition, I see no reason why wcwidth() should depend
> in any way on the culture, language, or region.
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". All of this is
irrelevant for applications that can use "proportional" fonts
of course, or applications that can use fonts that at least contain
the glyph width data *in* the font (which is where this kind of
information really belongs in general; NOT in an FDCC-set) even
if there are very few different widths.
Kind regards
/kent k
Quotes from UAX 11:
"Ambiguous characters occur in East Asian legacy character sets
as wide characters, but as narrow (i.e. normal-width) characters
in non-East Asian usage (Examples are the Greek and Cyrillic
alphabet found in East Asian character sets, but also some of
the mathematical symbols). Private Use characters are considered
ambiguous, since additional information is required to know whether
they should be treated as wide or narrow."
...
"In a broad sense, wide characters include W, F, and A (when in EA
context), while narrow characters include N, Na, H, and A (when not
in EA context)."
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
