Re: single-key-description no good for Japanese and Chinese chars

[Richard Stallman]

    That would be OK. A box is already displayed (for me) for lots of characters
    ("keys"). That happens, I assume, whenever my machine doesn't have the
    proper font to display the character.

Many keys will fail to display on various terminals, and that can't be
avoided.  However, when key-description returns something that won't
display properly on certain terminals, it means that help displays
such as that of C-h b are not meaningful either.  That is not good.

Perhaps single-key-description ought to describe every non-ASCII
character using ASCII.  Or perhaps it should do this for characters
that can't display on the current terminal.

Anyway, that sort of change should wait for after the release.

    My concern here is the multi-byte chars (keys), for which
    `single-key-description' does not return a single-character string (which
    might or might not be displayed as a box, depending on your font support).

How many bytes are used internally to represent the character
should be irrelevant to this issue, and not visible either.
Latin-1 characters take two bytes, for instance.  Why do you
mention the byte-length in this context?