Conjoining Hangul Jamo behavior (was: Hangul script type)

From: Jungshik Shin (jshin@mailaps.org)
Date: Wed Oct 17 2001 - 04:05:39 EDT


On Tue, 16 Oct 2001, Karlsson Kent - keka wrote:

> > -----Original Message-----
> > From: Jungshik Shin [mailto:jshin@pantheon.yale.edu]

> > section 3.11 (Conjoining Jamo Behavior). In MS implementation, I.C.,
> > M.V. and F.C. can be either a single code point in U+1100 Jamo block
> > (as described in Unicode 3.0) or a composite of two or more
> > code points
> > in the block. 3.11 of TUS 3.0 may have to be revised to reflect this.
>
> Do you know if any such rewriting/expansion of the TUS text is in
> the works?

  Not that I know of.

> The (compatibility) decomposition of the double consonants
> were, however, removed from Unicode a while ago. Do you mean that
> they really should have been canonical decompositions (too late to
> change now).

  I wasn't worried about a single vs double consonant issue. For Jamos
already encoded in U+1100 block, I think it's best to use them as an unit.
However, MS products support a lot more Jamos (at the request of Korean
linguists) than there are slots in the U+1100 block. Therefore, what they
did was representing not-yet-encoded composite Jamos with a sequence
of encoded Jamos. Their fonts (TTFs) and Uniscribe rendering engine
support this. In light of thise, I think TUS text certainly needs some
'rewritting'.

   Jungshik Shin



This archive was generated by hypermail 2.1.2 : Wed Oct 17 2001 - 05:09:19 EDT