Re: Revised language on: ISO/IEC 10646 as Document Character Set
Gavin Nicol (gtn@ebt.com)
Thu, 11 May 95 12:20:48 EDT
>The problem is that some people don't agree that its the same
>character. They believe that the language the character is associated
>with is part of the character that has to be preserved. According
>this logic you can talk about mapping from ISO-2022-JP to something
>you might call ISO-10646-JP, but that you cannot map to generic
>ISO-10646, and that therefore ISO-2022-JP is NOT a subset of
ISO-10646. (Some have even go so far as to assert that ISO-10646 does
>not meet the requirements of being a character set.)
At least here in Japan, the number of such people are dwindling
(though still significant).
When I talk about such things, people immediately ask "but what about
the CJK problems?", and once I explain things to them, 99% say "Oh. I
see, no problem".
Most people don't have a problem, so long as they are not forced to
loose any functionlity they currently have. For others, well... there's
no hope, because their logic stems from a belief, rather than vice
versa.