Hi,

At Sun, 4 Feb 2001 19:53:31 -0500 (EST),
Henry Spencer <[EMAIL PROTECTED]> wrote:

> So?  This problem is *not* specific to Han Unification.  Most North
> Americans cannot read the Blackletter (aka Fraktur) version of U+005A, or
> for that matter a Spencerian-calligraphy version of the same.  (The
> handwriting style I was taught was Spencerian [no relation!], and *I*
> would have trouble with some of the weird uppercase forms now.)

I don't know about Blackletter, Fraktur, nor Spencerian.  Are
anyone unhappy U+005A glyph in, for example, XFree86's 
-misc-fixed-medium-r-normal-* font?  Is it impossible to design a
world-readable glyph of U+005A?  For Han Unification characters,
it is impossible for some characters to be designed so that all
native CJK speakers can read them.


> Then the incompetent suppliers who try to ignore the font issues will go
> out of business, and the world will be a better place.  Our job is to make
> sure that Linux does *not* ignore these issues, so it can use a font that
> is appropriate to the user.  It is *not* our job to re-hash whether Han
> Unification was a good idea -- that is not our decision.

I want some mechanism for Unicode ordinal text (not rich text) to
distinguish Chinese, Japanese, and Korean version of Han Unification
character.  To let (non-CJK) people understand this need, I have to
explain why Japanese people are unhappy with Han Unification.

I understand the solution cannot be modification of Unicode.  It is
against Unicode's policy that once determined characters will not
changed in future.  Thus, I'd like you to think about non-vaporware
solution for this problem.

There are some solutions suggested so far:
 - Use Japanese fonts for Japanese version of Windows
     What is the mechanism to change font?
     How a text file specify the font?
     No mechanism, responsibility of each user?  No!
 - language tag
     It is likely that this will be a vaporware, since
     this is stateful like ISO-2022.  However, this can
     be a solution, if developers all over the world
     would come to understand this problem.

---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://surfchem0.riken.go.jp/~kubota/
"Introduction to I18N"
http://www.debian.org/doc/manuals/intro-i18n/
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/

Reply via email to