On 11/8/97 3:38 AM, Werner Lemberg (sx0005@sx2.hrz.uni-dortmund.de) wrote:
>
>
>On Fri, 7 Nov 1997, Michael Kung <MKUNG@us.oracle.com> wrote:
>
>> >So one more reason to
>> >use ISO 2022 if you need linguistically exact information on CJK
>> >characters.
>>
>> Unicode does not preclude you doing so. If we look at the horizontal
>> extension, you can perform the same 'feature' within your program.
>
>What do you mean with `horizontal extension'? The planned CJK extension?
>I heard it will be not before 1999 in the standard officially.
>
The IRG uses exclusively a mutli-column format for its code charts, each
column indicating the mapping to one of the national source sets and a
typical glyph for that national character set.
There are two extensions to the charts used for printing 10646 coming out
of the IRG. One is the vertical extension, which adds new ideographs.
The other is the horizontal extension, which adds a fifth column and
additional mappings to the existing charts.
If I understand Michael's point, he's saying that if you want to get the
kind of "linguistically exact information on CJK" you want, you just need
to specify the column you're using, G, T, J, K, or V. This *still*
doesn't buy you all of CNS, because too much of CNS is unifiable from the
IRG's perspective -- but frankly, you could use the user zone or user
planes to hold any bits and pieces of CNS that were vital for you to use.
=====
John H. Jenkins
jenkins@apple.com
tseng@blueneptune.com
http://www.blueneptune.com/~tseng
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:37 EDT