Setup: baselayout-1.11.9-r1 UNICODE=yes in /etc/rc.conf KEYMAP="-u uk" in /etc/conf.d/keymaps SET_WINDOWKEYS="yes" in /etc/conf.d/keymaps With this setup, /etc/init.d/keymaps tries to load the windowskeys keymap before kbd_mode -u is called, resulting in a warning that the keymap contains unicode characters. Reproducible: Always Steps to Reproduce: 1. 2. 3.
and if you remove the '-u' from KEYMAP ?
http://www.gentoo.org/doc/en/utf-8.xml#doc_chap3_sect3 says that the -u should be present.
i didnt ask you what the docs say, i asked if removing the '-u' fixed your problem
The warning disappears and some Unicode files I tried catting worked. However I did notice that U+00BC (VULGAR FRACTION ONE QUARTER) appears to be rendered as U+0152 (LATIN CAPITAL LIGATURE OE). Kate, Mozilla and Konsole all render the character appropriately. Also, when I attempt to enter U+00A3 (POUND SIGN,
The warning disappears and some Unicode files I tried catting worked. However I did notice that U+00BC (VULGAR FRACTION ONE QUARTER) appears to be rendered as U+0152 (LATIN CAPITAL LIGATURE OE). Kate, Mozilla and Konsole all render the character appropriately. Also, when I attempt to enter U+00A3 (POUND SIGN, £) on the command line simply by pressing shift+3, it appears as U+0023 (NUMBER SIGN, #) followed by a new line. I'm not sure whether these are bugs in baselayout or some other package. As far as the documentation is concerned, should I file a separate bug for the document telling people to use -u in KEYMAP? Or is that actually intended to work and removing it is simply a workaround for a bug in baselayout?
the doc peeps already have bugs to update the unicode guide as for the other things (certain button combinations not showing the correct symbol), that's most likely a bug in kbd ... what do you have your CONSOLE* variables set to ?
get back to us