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

[Jason Rumney]

Drew Adams wrote:
>     There is nothing in the documentation that suggests that it
>     should generate a unique value for every possible key sequence.
>
> Maybe there is nothing about that in the doc, but doesn't it seem logical?
>   

No. If that was its purpose, then it should be called something like 
`single-key-unique-identifier'. A "description" has never had any 
connotation of uniqueness in any context I have ever seen.

> Wouldn't the Chinese (or whatever)
> character itself (as a string) be the best value to use as the output of
> `single-key-description'? Or can't we have a string with Chinese characters
> in it?
>   

I don't know for sure, I would expect descriptions to be ASCII 
descriptions, but that does not seem to be true for the £ key on my 
keyboard.

> Again, I'm no expert on this stuff. I'm just thinking out loud and asking.
> I'm thinking that, logically, I should be able to do the same thing with a
> Chinese character that I can do with some of the other "strange" characters
> that are bound to `self-insert-command'. I see, for instance, lots of
> characters that I doubt would be associated with a key from any keyboard -
> and they all work OK with my code. They probably belong to ISO-*, but I'm
> not sure they're on any keyboard.
>   

Most iso-8859-* characters are on their respective nations' keyboards.