[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Emacs Unicode support
> > Second, I find the behaviour of "wcwidth" for the conjoining Johab
> > range irrational. It doesn't make any sense to make the leading
> > consonant full-width, with vowels and finals being half-width. I don't
> > want to have to split my glyphs over two fonts to see the Johab
> > elements on software that doesn't support conjoining. (On a
> > conjoining renderer the result of conjoining should of course be
> > full-width.)
>
> What do you mean by "conjoining Johab range"?
>
> I was under the impression that when decomposing a Hangul syllable,
> the result were a consonant, vowel and final, all three in the range
> U+3131..U+318E - which are marked as "wide" in EastAsianWidth.txt.
The range U+3131..U+318e exists for compatibility with KSC5601 only.
These characters are ordinary letters, with no special combining
behaviour, and they are all full-width.
I was referring to the range U+1100 to U+11f9, the conjoining Jamo.
There is really no direct mapping of these elements to glyphs, as a
conjoining renderer would have to assemble a choseong, jungseong, and
(perhaps) a jongseong into a single full-width glyph (and the Unicode
standard defines this mapping for the characters in the Hangul block
U+ac00..U+d7a3).
However, when working with text containing syllables composed of Jamo
on software that does not (yet) support conjoining, I would like to be
able to see some representation of these elements. It doesn't make
sense that the representation for choseong is full-width, while the
jungseong and jongseong are half-width. (Even though
EastAsianWidth-3.txt seems to indicate this.)
Otfried
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/