XKB issues
Basically, this list is a subset of the bugs related to the component 'Input/XKB' of the product 'xorg' in bugzilla.freedesktop.org (see full list)
xkbcomp at X startup
Issue Description
xkbcomp at X startup is unnecessary performance penalty. Possible alternatives:
- Rewriting xkbcomp to make it more effecient (for example, by caching the configuration)
- Using shared library directly from X server. That library would also be used by setxkbmap.
Status/Owner
Bug(s)
XKM format should be deprecated
Issue Description
XKM as a binary format has some serious issues:
- Not readable
- Some information is not presentable (see #4927)
- TBC (Daniel, feel free to express all your hatred here;)
Textual XKB format should be the only format of the persistant configuration data used by XKB.
Status/Owner
Bug(s)
xkbcomp needs :all syntax for rules
Issue Description
The following functionality is needed in xkbcomp: If some XKB option is using some symbols in group 1, they should be propagated to all groups present in the configuration. Something like
! option = symbols
og:abc = symfile(v):all
// equal to og:abc = symfile(v):1 + symfile(v):2 + ... till the last group
Status/Owner
Bug(s)
setxkbmap is unable to explain the rules it applied
Issue Description
Sometimes setxkbmap makes non-trivial decisions regarding the way it applies the rules. Even using dozen of -v options does not help. What would be useful to have is some way to see the list of the rules applied to the input components (with references to line numbers in the rules file perhaps).