Open fabi1cazenave opened 6 months ago
@fabi1cazenave There may be a hybrid option :
kalamine/
kalamine/*
files. So you can use e.g. setxkbmap fr -variant lafayette
as well as the canonical setxkbmap kalamine/lafayette
.This way your configuration via DE GUI tools should survive XKB update (being based on the XML file, it points to kalamine/*
files), while only the aliases in the system files are deleted.
With this solution your hard work on the locale files was not all in vain!
xkalamine
installs layouts inxkb/symbols/[locale]
files for historical reasons, and because let’s face it : writing… is the coolest thing ever. ^_^
But that relies on some clunky text delimiters around every layout definition in those files, which is a very debatable design decision to say the least ; and it does not survive to an XKB upgrade, which is a pity.
A much saner approach would be to put all kalamine layouts in an
xkb/symbols/kalamine
subdirectory and associate those layouts to the proper locale in thexkb/rules/{base,evdev}.xml
files. And selecting a layout on XOrg would become :+1:And an intermediate approach would be to put all kalamine layouts directy in
xkb/symbols
buf forbid to overwrite non-kalamine layouts, which implies keeping the clunky text delimiters. We’d still avoid the loss of our layouts on an XKB upgrade, and the layout selection would become :… which looks pretty darn cool, too. ^_^