When I try to load a German keymap with Unicode support, e.g., /etc/conf.d/keymaps: ... KEYMAP="-u de-latin1-nodeadkeys" ..., I get the following error message: extensa ~ # /etc/init.d/keymaps start * Loading key mappings ... unknown keysym 'Meta_acute' /usr/share/keymaps/i386/qwertz/de-latin1.map.gz:34: syntax error syntax error in map file key bindings not changed * Error loading key mappings [ !! ] * Setting terminal encoding to UTF-8 ... [ ok ] extensa ~ # It seems that the Meta_acute symbol appears _only_ in the de-latin1 maps: extensa ~ # find /usr/share/keymaps/ | xargs zgrep Meta_acute /usr/share/keymaps/mac/all/mac-de-latin1.map.gz: alt keycode 24 = Meta_acute /usr/share/keymaps/i386/qwertz/de-latin1.map.gz: alt keycode 13 = Meta_acute extensa ~ # So, maybe the 'Meta_acute' is in error and should be 'Meta_apostrophe' (which appears in a lot of keymaps)? This is just a wild guess, however, so I would be thankful for someone more competent looking into this problem. Thank you for your time! Reproducible: Always Steps to Reproduce: 1. Add/change line 'KEYMAP="-u de-latin1-nodeadkeys"' in /etc/conf.d/keymaps 2. Make other changes to enable unicode, e.g. 'UNICODE="yes"' in /etc/rc.conf (however, this is not necessary to reproduce the error) 3. (Re)start the /etc/init.d/keymaps service Actual Results: (See above.) Expected Results: Install the de-latin1-nodeadkeys keymap with unicode support.
i assume you're running baselayout-1.11.x ... i cant tell for sure though because you didnt paste `emerge info` ... if that is the case, i dont think you need the '-u' crap in KEYMAPS anymore ... could you try it w/out -u ?
Sorry for my not including `emerge info`, but you got it right anyway -- I am in fact using baselayout-1.11.9-r1. And, yes, loading the keymap WITHOUT the '-u' prefix in /etc/conf.d/keymaps works perfectly! Since I went by the Gentoo UTF8-guide (http://www.gentoo.org/doc/en/utf-8.xml, in particular code listing 3.4), I just thought that leaving this out might cause trouble not immediately obvious to me. But probably it doesn't, as you say. Thanks to your hint regarding the baselayout, I also found http://bugs.gentoo.org/show_bug.cgi?id=32111 mentioned in /usr/doc/baselayout-1.11.9-r1/ChangeLog.gz This looks pretty much like my problem (which turned out to be located between keyboard and chair... ;-). So, I think you can close this bug (or regard it as a suggestion to update the UTF8-guide). Thanks again!
the UTF guide has some bugs open to get it updated, but i'm glad it works now ;)
