On Wednesday, October 24, 2001, at 09:16 AM, Thomas Chan wrote:
> That works for those that have a character set source mapping (e.g., T-
> sources for higher CNS 11643 planes) or dictionary source page and
> serial
> number mappings (e.g., kHanyuDaZidian field), but what do we do about
> those that don't? For example, although I own a copy of the _Ci Hai_
> dictionary (G-CH source), I can't tell which character in it that
> U+206C5
> is meant to be. (No doubt this can be resolved with more
> cross-references, although that still leaves the problem of
> non-dictionary
> sources such as G-FZ/FZ_BK and G-4K.)
I think under the circumstances, it's fair for the UTC to ask the IRG to
provide position information for G-CH characters &c. Meanwhile, we can
add the task to generate our own to the queue and take any donations of
data that come our way.
> Also, there's no way I can
> determine what U+20850 is, as it doesn't come from a real character set
> (K-4 source).
In such cases, of course, we have no choice but to fall back on the
glyph, as you say.
The IRG is going to a great deal of effort to make sure that the glyphs
accurately match the sources they used, but with upwards of 40,000
characters involved, we cannot guarantee that they are all perfectly
accurate. Meanwhile, the *official* definition of the character is its
mappings and the *informal* definition is its glyph. That's as much as
we can do.
==========
John H. Jenkins
jenkins@apple.com
jenkins@mac.com
http://homepage.mac.com/jenkins/
This archive was generated by hypermail 2.1.2 : Wed Oct 24 2001 - 13:28:34 EDT