From keld@dkuug.dk Sun Nov 18 14:13:07 1990
Received: by dkuug.dk (5.64+/8+bit/IDA-1.2.8)
	id AA23266; Sun, 18 Nov 90 14:30:37 +0100
Received: by dkuug.dk (5.64+/8+bit/IDA-1.2.8)
	id AA22923; Sun, 18 Nov 90 14:13:07 +0100
Date: Sun, 18 Nov 90 14:13:07 +0100
From: Keld J|rn Simonsen <keld@dkuug.dk>
Message-Id: <9011181313.AA22923@dkuug.dk>
To: Becker.OSBU_North@xerox.com, erik@sra.co.jp
Subject: Re: Han Character Code Ordering
Cc: arnet@hpcupt1.cup.hp.com, arnet@hpda.cup.hp.com, i18n@dkuug.dk,
        unicode@sun.com
X-Charset: ASCII
X-Char-Esc: 29

> So what's the conclusion? As far as Unicode and collation are
> concerned, UniHan is probably the way to go. ISO 10646 is somewhat at
> a disadvantage in this respect. But 10646 has many other advantages
> that far outweigh its disadvantages.

I would like to have this spelled out:
For Unicode UniHan is OK, that is ordering by most common pronounciation
for the single Han character is OK?
Can this ordering also be used for 10646 and X0208 and X0212?

Is this ordering (on pronounciation) also OK for China and Korea?
Or are Chinese and/or Koreanese more used to radicals/stroke count
ordering?

Keld Simonsen