RE: [idn] call for comments for REORDERING

[Karlsson Kent - keka <keka@im.se>]

> -----Original Message-----
> From: Soobok Lee [mailto:lsb@postel.co.kr]
...
> But including 11172 hangul made Unicode more useful and 
> widely acceptable to korean community, because existing 
> KS5601's 2350 or more hangul has been criticized for not being
> able to serve many scholarly purpose or book publishings.
> 
> The pain for inclufing 11172 hangul  was REWARDED!

And still it is not sufficient, since historic Hangul
Jamo aren't covered by the precomposed Hangul syllable
characters. I have also indications that many useful
consonant (and vowel?) clusters aren't covered as separate
(Jamo) characters, but have to be constructed from multiple
'more basic' (non-cluster) Hangu Jamo characters. (The
cluster ones are the ones that had compatibility
decompositions in Unicode 2.0, but don't have such
decompositions in Unicode 3.0.)

> I know current NFC/NFKC has *severely flawed* hangul jamo 

Now that's a new complaint.  At least to me.  Not even the
delegations from DPRK complain about that. (And they have
all sorts of complaints.)  Do you care to say a little bit
more about what you mean?  Or are we just to take your word
for it?  There was a problem in earlier drafts of UAX 15
concerning Hangul and NFKC (Hangul syllables were not preserved),
but that problem was removed before that UTR became a UAX.

> I hope UTC cures this BUGGY NFC/NFKC jamo handling as an 
> exceptional case while it is in  strict adherence to UTR's backward 
> compatiblity policy & promise.

The normal forms for strings of already allocated characters
will not be changed any more.

		Kind regards
		/Kent K