From daemon@dkuug.dk Wed Nov 21 03:47:32 1990
Received: by dkuug.dk (5.64+/8+bit/IDA-1.2.8)
	id AA29412; Wed, 21 Nov 90 03:48:31 +0100
Received: from MCSUN.EU.NET by dkuug.dk via EUnet with SMTP (5.64+/8+bit/IDA-1.2.8)
	id AA29383; Wed, 21 Nov 90 03:47:32 +0100
Received: by mcsun.EU.net with SMTP; Wed, 21 Nov 90 03:50:43 +0100
Received: from srava.sra.co.jp by srawgw.sra.co.jp (5.64WH/1.4)
	id AA27909; Wed, 21 Nov 90 11:50:16 +0900
Received: from sran8.sra.co.jp by srava.sra.co.jp (5.64b/6.4J.6-BJW)
	id AA07269; Wed, 21 Nov 90 11:50:14 +0900
Received: from localhost by sran8.sra.co.jp (4.0/6.4J.6-SJ)
	id AA28502; Wed, 21 Nov 90 11:48:46 JST
Return-Path: <erik@sran8.sra.co.jp>
Message-Id: <9011210249.AA28502@sran8.sra.co.jp>
Reply-To: erik@sra.co.jp
From: Erik M. van der Poel <erik@sra.co.jp>
To: i18n@dkuug.dk
Subject: Re: Han Character Code Ordering
Date: Wed, 21 Nov 90 11:48:45 +0900
Sender: erik@sran8.sra.co.jp
X-Charset: ASCII
X-Char-Esc: 29

------- Forwarded Message

Date: Tue Nov 20 09:25:43 1990
From: ksri@halla.dacom.co.kr
To: erik@sra.co.jp
Subject: Re: Han Character Code Ordering
Cc: unicode@SUN.com

In Korea, Phonetic-ordered dictionaries are more common either.
Most of Korean users select Han characters by their pronounciation.
Therefore, if we adopt the UNICODE, we should have the table containg
the UniHan arranged by their pronounciations in order to use the set
practically.

Jeoung S. Cho
KSRI
KOREA