bug#32562: 26; `read-char(-exclusive)' and `characterp'

[Drew Adams]

> > > A character with modifiers doesn't satisfy characterp, but it is still a
> > > character (which read-char can return).
> >
> > Yes, well, that's what I found a bit confusing wrt the
> > doc and function names. It wasn't (isn't?) too clear
> > just what we mean by "character", in that case.
> 
> I made the documentation say "character event" where it matters.

I imagine that you made it clearer (I don't have the new doc).

But see what I replied to Andreas. It seems like we talk in some
places about reading a character even if what gets read might
not be `characterp'. "Character event" doesn't clarify that, for me.

Seems like the doc (but I don't have time now to search it)
doesn't distinguish "character" meaning something that is
`characterp' from other meanings of it (not sure what those
are, but apparently `read-char' can return such things).

It's not clear to me, at least. Why isn't `chararcterp' necessary
and sufficient for testing whether something is a character?