Aliases for control characters; BELL in particular

Jens Maurer Jens.Maurer at gmx.net
Sat Nov 6 14:59:36 CDT 2021


On 06/11/2021 18.07, Markus Scherer via Unicode wrote:
> Hallo Jens,
>
> On Sat, Nov 6, 2021 at 8:50 AM Jens Maurer via Unicode <unicode at corp.unicode.org <mailto:unicode at corp.unicode.org>> wrote:
>
>     So, given the explanation in section 24.1, CodeCharts.pdf defines a normative
>     alias "BELL" for U+0007 (it's all-caps and follows "="), despite the utterance
>     in NameAliases.txt that this is not desired.
>
>
> Here is the disconnect. The code charts, with their annotations driven by https://www.unicode.org/Public/UCD/latest/ucd/NamesList.txt <https://www.unicode.org/Public/UCD/latest/ucd/NamesList.txt> , are a presentation of glyphs, names and useful additional information.
> But the normative data is in NameAliases.txt.
>
> It would be best if you could report the discrepancy via https://www.unicode.org/reporting.html <https://www.unicode.org/reporting.html>

I've posted two bug reports, one against the use of BELL for U+0007 and
one against the presentation of aliases for U+000A (and other control
characters with more than one "control" alias).

> Please use only the data in NameAliases.txt.

The sad part here is that C++ is an ISO standard, which really likes to refer to
another ISO standard for these matters.  But the code charts in ISO 10646:2020
have these bugs in them, and it seems those charts are normative in ISO 10646.

Beyond that, according to ISO 10646 section 34.3, only the "correction" aliases
are normative, the others are informative, which differs from the viewpoint
of Unicode 14.  And which means that the control characters are not nameable
at all via ISO 10646 normative names/aliases, which makes me sad.

Jens




More information about the Unicode mailing list