[PATCH] Keypad keys and normal keys should always behave the same in Compose
Mike FABIAN
mfabian at redhat.com
Thu Aug 19 15:18:47 UTC 2021
"Jonathan A. Kollasch" <jakllsch at kollasch.net> さんはかきました:
> On Tue, Aug 17, 2021 at 12:01:44PM +0200, Mike FABIAN wrote:
>> https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/82
>>
>> Keypad keys and normal keys should always behave the same in Compose
>>
>> I.e. the keysyms below in the right column should always do the same
>> as thouse in the left column when using Compose:
>>
>> <0> <KP_0>
>> <1> <KP_1>
>> <2> <KP_2>
>> <3> <KP_3>
>> <4> <KP_4>
>> <5> <KP_5>
>> <6> <KP_6>
>> <7> <KP_7>
>> <8> <KP_8>
>> <9> <KP_9>
>> <minus> <KP_Subtract>
>> <plus> <KP_Add>
>> <slash> <KP_Divide>
>> <asterisk> <KP_Multiply>
>>
>> Signed-off-by: Mike FABIAN <mfabian at redhat.com>
>>
>> --
>> Mike FABIAN <mfabian at redhat.com>
>> 睡眠不足はいい仕事の敵だ。
>>
>
> Special casing this seems wrong. I'm also of the opinion that this
> behavior is not actually desired.
Why is that not desired?
Before my patch, the Compose.pre file contains many cases where
you can use for example the keysym slash in two orders but the
keysym KP_Divide only in one order, like this:
$ grep Ø ./nls/en_US.UTF-8/Compose.pre
<dead_stroke> <O> : "Ø" Oslash # LATIN CAPITAL LETTER O WITH STROKE
<Multi_key> <slash> <O> : "Ø" Oslash # LATIN CAPITAL LETTER O WITH STROKE
<Multi_key> <O> <slash> : "Ø" Oslash # LATIN CAPITAL LETTER O WITH STROKE
<Multi_key> <KP_Divide> <O> : "Ø" Oslash # LATIN CAPITAL LETTER O WITH STROKE
This is nonsense, why should the user care whether to use slash or
KP_Divide and why should there be such subtle differences?
If “<Multi_key> <slash> <O>” and “<Multi_key> <O> <slash>” both work and
produce the same result, then it makes no sense that when using
KP_Divide instead of slash, only one order works.
--
Mike FABIAN <mfabian at redhat.com>
睡眠不足はいい仕事の敵だ。
More information about the xorg-devel
mailing list