Re: [tlug] japanese encoding question

[David Oftedal <david@example.com>]

> It's true that Unihan is annoying in multilingual CJK pages, but there
> are ways to deal with it, and they're going to be valid essentially
> forever.
> 

All you have to do is use some sort of tag around each segment that 
correctly identifies what language it's in. Then you'll be able to put 
specific font settings in your CSS settings. This is already implemented.

I for one don't particularly mind the Unihan thing though, as long as 
both my Chinese and Japanese fonts are antialiased and the same size...

  I rather think China, Japan, Korea, Taiwan and... Singapore and 
whatever should sit down and agree on a standard, and preferably one 
where each kanji doesn't have a 1,000 different variants depending on 
whether it's a radical, a name kanji, or what the weather's like on a 
particular day. I know I'd be more optimistic about kanji learning, 
anyway, and perhaps I'd even consider learning Chinese.

Unihan is pure love, from Unicode to you. Unicode, wo ai ni!

-Dave