[Top][All Lists]

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

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

From: Kenichi Handa
Subject: Re: single-key-description no good for Japanese and Chinese chars
Date: Fri, 22 Sep 2006 15:12:10 +0900
User-agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI)

In article <address@hidden>, Richard Stallman <address@hidden> writes:

>     I don't think it is unreasonable for single-key-description to use the 
>     same description for these many thousands of characters especially if 
>     they are not produced directly by any keyboard in common use.

> If those values are meaningless junk, then it is not crucial what happens
> for those argument values.  But if they are meaningful, then they should be
> handled right.

> Handa, can you tell us whether these values are meaningful?
> Please ask Drew for more info if you need it.

It seems that Drew misunderstand generic characters.

"Drew Adams" <address@hidden> writes:
> `single-key-description' returns the exact same key description for
> each key in the asian character sets (Japanese, Chinese, etc.).

> For example, for the different input events (keys) 20864 and 20992,
> the exact same description is given: "Character set JISX0208.1978
> (Japanese): ISO-IR-42".

Both 20864 and 20992 are generic characters, i.e. not an
acutual character but a code representing a group of
characters (a charset or a row of characters).  For
instance, (insert 20864) signals an invalid-character error.

> This is useless. The single-key description must be unique for a given
> key. If nothing else, the event value should be included in the
> description: e.g. "Character set JISX0208.1978 (Japanese): ISO-IR-42 -
> 20864".

As (split-char 20864) => (japanese-jisx0208-1978 35 0),
the description can be changed to "Characters in row 35 of
character set JISX0208.1978 (Japanese): ISO-IR-42 - 20864"
if that is more useful.

> I have code, for instance, that lets you complete key sequences.  The
> completion candidates are the `single-key-descriptions' of the key
> sequences typed so far.  At top level, they are the descriptions of
> all top-level bindings and commands.  For example, this is a possible
> completion:

>  "a = self-insert-command"

> And so is this:

>  "Character set JISX0208.1978 (Japanese): ISO-IR-42" = self-insert-command"

How did you get the key 20864?

Kenichi Handa

reply via email to

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