Some "standard" keys not recognized

[GoogleCodeExporter]

I noticed some keys silently not being displayed, and some giving a "Missing 
code for" error. Thanks to the Wiki, I found the xlib.py instructions, so I'm 
providing the ones I have noticed.

This is a German layout laptop keyboard (on an HP EliteBook 8530w) running 
through NX (a remote X11 server), so that may have some effect. But in other 
X11 programs, all keys work correctly.

The caret / percent key (top left): "^" / "°":
Missing code for 41 = 65106
type:EV_KEY scancode:41 code:KEY_DUNNO value:1
type:EV_KEY scancode:41 code:KEY_DUNNO value:0

The sharp s / question mark / backslash key (to the right of the "0"): "ß" / 
"?" / "\":
ßtype:EV_KEY scancode:12 code:KEY_SSHARP value:1
type:EV_KEY scancode:12 code:KEY_SSHARP value:0

The accent / accent grave key (two to the right of "0"): "´" / "`":
Missing code for 13 = 65105
type:EV_KEY scancode:13 code:KEY_DUNNO value:1
type:EV_KEY scancode:13 code:KEY_DUNNO value:0

The plus / asterisk / tilde key (to the left of "Enter"): "+" / "*" / "~":
+type:EV_KEY scancode:27 code:KEY_PLUS value:1
type:EV_KEY scancode:27 code:KEY_PLUS value:0

The hash-pound / single-quote key (to the left of "Enter"): "#" / "'":
#type:EV_KEY scancode:43 code:KEY_NUMBERSIGN value:1
type:EV_KEY scancode:43 code:KEY_NUMBERSIGN value:0

Note that those not "Missing code" are detected fine above, yet nothing is 
shown in the key-mon GUI. I tested several themes.

Note that those actually "Missing code" are "dead keys".

Thanks!

Original issue reported on code.google.com by [email protected] on 1 Nov 2012 at 9:38

[GoogleCodeExporter]

Oh, by the way, my python-xlib is 0.14, in case that matters.

Original comment by [email protected] on 1 Nov 2012 at 9:45