[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#9653: 24.0.50; `ucs-names' - Why all of the ("" . XXX) entries?

From: Drew Adams
Subject: bug#9653: 24.0.50; `ucs-names' - Why all of the ("" . XXX) entries?
Date: Wed, 5 Oct 2011 06:20:21 -0700

> > I supposed, however, that each empty-name alist entry has 
> > an alter-ego entry that has the same code point but also
> > has a non-empty name: e.g. ("" . 32) & ("SPACE" . 32).
> Yes, each character code is entered into the alist twice: once with
> its name, and another time with its "old name", which is empty for
> most of the characters.  I thought the code fragment I posted made
> that clear.

Yes, it did make it (abundantly, redundantly) clear.  As it was already clear
from Stefan's earlier code-fragment post.  And as it was clear to me from the
beginning, after looking at the code.

Not the question.  What I was incorrectly supposing was that every character
code corresponded to either a non-empty name or a non-empty old-name.  I did not
realize that both names might be empty.

> > I see in fact that there are some `ucs-names' entries that,
> > yes, constitute a pair with the same character code, yet
> > _both_ are empty.  E.g., ("" . 11565) & ("" . 11565).
> These are undefined characters.  11565 is hex 2d2d; you will not find
> such a codepoint in the Unicode database.

Great.  If they are all such, then I suppose we can in fact filter out all empty

reply via email to

[Prev in Thread] Current Thread [Next in Thread]