G'day,

[Tomohiro KUBOTA (Re: [I18n]Call for testers: luit in XFree86 CVS) writes:]
>> And, there exist JIS X 0213 fonts available.  You can download it
>> from a famous freeware/shareware site "vector"
>> (http://www.vector.co.jp).  If you are using Debian, install
>> xfonts-kappa20 and you can use JIS X 0213 fonts.

I've had a BDF of JISX0213 for some time, and have played with a kterm 
that can handle it.  It is really in the Whinedoze arena that I can't see 
the font support coming in a hurry. NT deriviatives have made it a 
dead-end for font developments.

>> > Whether as Kubota-san suggests JIS X 0213 will be useful in the future
>> > remains to be seen. My own humble opinion is that there appears to be
>> > little effort being put into developing fonts around the JIS X 0208 + 
>> > JIS X 0213 combination (you can't have JIS X 0213 in isolation, as it is
>> > an extension). I think the real focus is on Unicode.
>> 
>> It is wrong.  JIS X 0213 is a replacement of JIS X 0208.  

I think we can get into serious hair-splitting here. My copy of JIS X 0213
describes itself as "$B3HD%4A;z=89g(B" (enlargement or extension kanji set), 
and the text inside makes it pretty clear that it it is in addition to 
JIS X 0208. I noted the new "JIS Kanji Dictionary"  of which I saw some
proofs in Tokyo earlier this year is described as covering JIS X 0208 
and JIS X 0213. (Poor old JIS X 0212 is forgotten.)

>> Strictly speaking,
>> it is not a superset of JIS X 0208, because unification rule has changed
>> for dozens of characters.  For example, do you know there are two versions
>> of glyph of "$B9b(B" (height)?  They are so-lcalled "Hashigo-taka" and
>> "Kuchi-taka".  These two characters are unified (and thus share one
>> codepoint) in JIS X 0208 but they are treated as different characters
>> (and thus have separate codepoints) in JIS X 0213.

I think there were a total of 56 kanji "dis-unified" in this way.
 
>> Except for such a few tens of characters, JIS X 0213 includes all
>> characters of JIS X 0208.  Thus, JIS X 0213 is virtually a superset
>> of JIS X 0208.

Certainly if you set out to use JIS X 0213 you really have to  run with a 
a single set combining the characters defined in both JIS X 0208 and 
JIS X 0213, which is what the existing  font files do. 

My hope and belief is that Unicode implementations will consign all 
these legacy standards and codings to the history books.

Cheers

Jim

-- 
Jim Breen  [[EMAIL PROTECTED]  http://www.csse.monash.edu.au/~jwb/]
Computer Science & Software Engineering,                Tel: +61 3 9905 3298
P.O Box 26, Monash University,                          Fax: +61 3 9905 5146
Clayton VIC 3800, Australia      $B%8%`!&%V%j!<%s(B@$B%b%J%7%eBg3X(B
--
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/

Reply via email to