Hello, I've found that compose table in /etc/console/boottime.kmap.gz contains strange symbols 0x255 as result of each compose line, as described in http://bugzilla.kernel.org/show_bug.cgi?id=10143. I try to change my initial console map to my own file, but after rebooting dumpkeys still return 0x255 as composed characters. Does it mean that lenny kernel doesn't contain patch from kernel bug 10143? No, it seems this patch is implemented. I think that loadkeys has to set map and then dumpkeys has to return same (or similar) map back. Any idea why some composed characters are rewritten?
Pavel On Sat, 18 Apr 2009 01:46:10 +0200 Samuel Thibault <samuel.thiba...@ens-lyon.org> wrote: > Hello, > > Pavel Vávra, le Fri 17 Apr 2009 00:11:57 +0200, a écrit : > > Searching for problem I've found strange definition in > > cz-us-qwertz.kmap(.gz): > > > > keycode 13 = dead_acute dead_circumflex equal plus VoidSymbol VoidSymbol > > (...) > > > > but I expect dead caron instead of dead_circumflex > > dead_caron is actually an alias for dead_circumflex, because the kernel > does not have any dead_caron keysym. The odd results are probably due to > the compose table you are using, see the end of the output of dumpkeys. > > Samuel >
pgpp3CIYTbn84.pgp
Description: PGP signature
