Peter T. Daniels scripsit:

> Which doesn't concern the user.

Right now, if you want to do things with your Unicode-encoded text other
than render it (count the number of words, transliterate, change upper case
to lower case, etc. etc.) you do in fact have to understand something
about Unicode, or you may get unexpected results. Eventually this will
go away, but it hasn't yet.

> > It means that there are two encodings of Korean writing within Unicode
> > (regrettably): one which encodes Korean hangul individually, and one which
> > encodes Korean syllables (only the modern ones, but including ones which
> > are not actually required by the Korean language).
>
> Well, that was silly!

A combination of political pressure and practical necessity.

--
"Clear? Huh! Why a four-year-old child John Cowan
could understand this report. Run out jcowan@...
and find me a four-year-old child. I http://www.ccil.org/~cowan
can't make head or tail out of it." http://www.reutershealth.com
--Rufus T. Firefly on government reports