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

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Kenichi Handa <handa@m17n.org>,  9653@debbugs.gnu.org
> Date: Wed, 05 Oct 2011 08:40:13 -0400
> 
> >> I'm not sure because there are multiple use-cases of
> >> get-char-code-property, and nil is better only in some of them.
> >> But, it's just "I'm not sure".  If you are sure, as I wrote above,
> >> I'll change it back.
> 
> I'm sure.
> 
> > what-cursor-position etc., where we will now need to display an empty
> > string when we get nil.
> 
> Big deal: that's just an (or ... "").
> 
> And in any case no matter what the standard says, I'm pretty sure end
> users would prefer to be told explicitly that a char doesn't have a name
> rather than to see an empty field and wonder what that means.

I asked for some reasoning, but you didn't provide any.  Fine.  But
should we now change the `iso-10646-comment' property to be nil when
it doesn't exist?  Currently, any string attribute is returned as ""
if the attribute is not defined in the Unicode database.