Keyboard issue: Where to store dead key / multi key combinations?
by hw99 from LinuxQuestions.org on (#4Y94J)
Hello,
I've just created a new keyboard layout file and stored it in /usr/share/X11/xkb/symbols. Then I adopted evdev.xlm in /usr/share/X11/xkb/rules to make the new layout show up in GUI and installed it. All works fine so far, but no I am stuck with my next task: I would like to redefine some deadkey and multikey behaviour; I found out, that these combinations are stored in file "Compose" in /usr/share/X11/locale/en_US.UTF-8. If I append some new definitions, e.g.
<dead_caron> <Cyrillic_TSE> : "D"
<Multi_key> <comma> <Cyrillic_ie> : U467
...
to that file, it works. But there should IMHO be a better way. Can the dead-key / multikey-entries be stored within the keyboard-file itself? This would be very convenient for passing it on to collegues and the best solution. If this is not the case, is it at least possible to store these combinations in a separate file and somehow tell my new keyboard to use this file to look up the combinations? I would like to avoid editing the very big Compose file in en_US.UTF-8. In other words: How can a specific keyboard file be linked to a specific Compose file?
Any help is highly appreciated,
Helmut
(Linux Mint 19.3 Cinnamon)
I've just created a new keyboard layout file and stored it in /usr/share/X11/xkb/symbols. Then I adopted evdev.xlm in /usr/share/X11/xkb/rules to make the new layout show up in GUI and installed it. All works fine so far, but no I am stuck with my next task: I would like to redefine some deadkey and multikey behaviour; I found out, that these combinations are stored in file "Compose" in /usr/share/X11/locale/en_US.UTF-8. If I append some new definitions, e.g.
<dead_caron> <Cyrillic_TSE> : "D"
<Multi_key> <comma> <Cyrillic_ie> : U467
...
to that file, it works. But there should IMHO be a better way. Can the dead-key / multikey-entries be stored within the keyboard-file itself? This would be very convenient for passing it on to collegues and the best solution. If this is not the case, is it at least possible to store these combinations in a separate file and somehow tell my new keyboard to use this file to look up the combinations? I would like to avoid editing the very big Compose file in en_US.UTF-8. In other words: How can a specific keyboard file be linked to a specific Compose file?
Any help is highly appreciated,
Helmut
(Linux Mint 19.3 Cinnamon)