Bug 87827

Summary: Option kpdl:dotoss (and others) applies to the first layout only
Product: xorg Reporter: Denis Lisov <dennis.lissov>
Component: Input/KeyboardAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Denis Lisov 2014-12-29 11:58:53 UTC 
If using layouts en,ru the option kpdl:dotoss (and the other kpdl options) applies only to the first layout. I'd personally strongly prefer to have the keypad delete key produce dot in both layouts. However, this requires separate configuration like, for example, a separate call

setxkbmap -symbols '+kpdl(dotoss):2'

Is it intentional that the kpdl options apply to the first layout only?

$ setxkbmap -query
rules:      evdev
model:      pc105
layout:     us,ru
variant:    ,
options:    grp:caps_toggle,kpdl:dot,compose:sclk,grp_led:scroll


xkeyboard-config 2.13 (Gentoo unstable, KDE)
Comment 1 Denis Lisov 2014-12-29 15:00:34 UTC 
This applies to both kpdl:dot and kpdl:dotoss, as well as other values and likely other options (for example, bug #14074 https://bugs.freedesktop.org/show_bug.cgi?id=14074 talks about the eurosign:e option).
Comment 2 Sergey V. Udaltsov 2015-01-14 01:37:10 UTC 
This is general issue of XKB code. xkeyboard-config applies all options to the first group. There was already discussion to fix that - but it is not up to xkeyboard-config
Comment 3 GitLab Migration User 2018-08-10 20:55:53 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-input-keyboard/issues/19.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.