On 8/28/2011 9:46 PM, Doug Ewell wrote:
Philippe Verdy wrote:
If there are other mappings to do with other standards, and those
standards must be only informative, we already have the "/MAPPINGS"
directory beside the "/UNIDATA" directory where the UCD belongs too.
But in general, with the exception of MAPPINGS/VENDORS/MISC/SGML.TXT,
the MAPPINGS directory isn't really a place for character *name*
mappings. It's primarily a place for *code point* mappings, for
identifying U+0430 CYRILLIC SMALL LETTER A with 0xD0 in ISO 8859-5,
and 0xC0 in Windows-1251, and 0xE0 in MacCyrillic, and 0xC1 in KOI8-R.
Character names in other standards, like 'acy' for U+0430, are
comparatively less important.
Right, however NAME mapping has not been a major issue - except for
control codes, since Unicode did not name these, even though they were
routinely "named" by people dealing with them.
It's really important to not jump off the deep-end and appear to create
a precedent for name MAPPING across standards when what is desired is to
have IDENTIFIERS for certain characters as well as SHORT IDENTIFIERS for
characters very commonly referred to by identifier in source code
(regular expressions, etc.).
A./
