Some Turkish characters from my Toshiba A300D not shown with key-mon 1.7

[GoogleCodeExporter]

Hi,

First thanks for key-mon. It's very nice app for screencasters. I'm maintaining 
a package for Pardus at my playground [1]. And newly I updated package to 1.7 
version but some keys not works on my laptop.

Here is the keys:

$ python ./xlib.py 
Press ESCape to quit
Xlib.protocol.request.QueryExtension
Xlib.protocol.request.QueryExtension
"type:EV_KEY scancode:41 code:KEY_QUOTEDBL value:1
type:EV_KEY scancode:41 code:KEY_QUOTEDBL value:0
type:EV_KEY scancode:13 code:KEY_MINUS value:1
-type:EV_KEY scancode:13 code:KEY_MINUS value:0
type:EV_KEY scancode:12 code:KEY_ASTERISK value:1
*type:EV_KEY scancode:12 code:KEY_ASTERISK value:0
ütype:EV_KEY scancode:27 code:KEY_UDIAERESIS value:1
type:EV_KEY scancode:27 code:KEY_UDIAERESIS value:0
Missing code for 26 = 699
ğtype:EV_KEY scancode:26 code:KEY_DUNNO value:1
type:EV_KEY scancode:26 code:KEY_DUNNO value:0
type:EV_KEY scancode:40 code:KEY_I value:1
itype:EV_KEY scancode:40 code:KEY_I value:0
Missing code for 39 = 442
type:EV_KEY scancode:39 code:KEY_DUNNO value:1
ştype:EV_KEY scancode:39 code:KEY_DUNNO value:0
type:EV_KEY scancode:53 code:KEY_PERIOD value:1
.type:EV_KEY scancode:53 code:KEY_PERIOD value:0
çtype:EV_KEY scancode:52 code:KEY_CCEDILLA value:1
type:EV_KEY scancode:52 code:KEY_CCEDILLA value:0
ötype:EV_KEY scancode:51 code:KEY_ODIAERESIS value:1
type:EV_KEY scancode:51 code:KEY_ODIAERESIS value:0
Missing code for 23 = 697
type:EV_KEY scancode:23 code:KEY_DUNNO value:1
ıtype:EV_KEY scancode:23 code:KEY_DUNNO value:0

I hope there is a solution for these.

Thanks in advance.

[1] 
http://svn.pardus.org.tr/pardus/playground/maidis/2011/accessibility/key-mon/

Original issue reported on code.google.com by ozbekanil on 20 Aug 2011 at 4:23

[GoogleCodeExporter]

There is an fixed issue with 'i' in keysym, see Issue 77. Could you try to 
clone the repo and see if those with 'i' can be shown with latest code?

These should work:

type:EV_KEY scancode:13 code:KEY_MINUS value:1
-type:EV_KEY scancode:13 code:KEY_MINUS value:0
type:EV_KEY scancode:12 code:KEY_ASTERISK value:1
*type:EV_KEY scancode:12 code:KEY_ASTERISK value:0
type:EV_KEY scancode:40 code:KEY_I value:1
itype:EV_KEY scancode:40 code:KEY_I value:0
type:EV_KEY scancode:53 code:KEY_PERIOD value:1
.type:EV_KEY scancode:53 code:KEY_PERIOD value:0

These I am not sure:

ütype:EV_KEY scancode:27 code:KEY_UDIAERESIS value:1
type:EV_KEY scancode:27 code:KEY_UDIAERESIS value:0
çtype:EV_KEY scancode:52 code:KEY_CCEDILLA value:1
type:EV_KEY scancode:52 code:KEY_CCEDILLA value:0
ötype:EV_KEY scancode:51 code:KEY_ODIAERESIS value:1
type:EV_KEY scancode:51 code:KEY_ODIAERESIS value:0

Not sure why this didn't work:

"type:EV_KEY scancode:41 code:KEY_QUOTEDBL value:1
type:EV_KEY scancode:41 code:KEY_QUOTEDBL value:0

I will need to check, are these having its own key? I mean they are not 
generated by combination keys.

Missing code for 26 = 699
ğtype:EV_KEY scancode:26 code:KEY_DUNNO value:1
type:EV_KEY scancode:26 code:KEY_DUNNO value:0
Missing code for 39 = 442
type:EV_KEY scancode:39 code:KEY_DUNNO value:1
ştype:EV_KEY scancode:39 code:KEY_DUNNO value:0
Missing code for 23 = 697
type:EV_KEY scancode:23 code:KEY_DUNNO value:1
ıtype:EV_KEY scancode:23 code:KEY_DUNNO value:0

Original comment by livibet...@gmail.com on 20 Aug 2011 at 4:56

[GoogleCodeExporter]

Could you also upload `sudo dumpkeys` and `xmodmap -pk`? I think we might need 
to make a tr.kbd.

What's your keyboard layout called? I checked Wikipedia [1], there are two F 
and Q, what are their keyboard layouts' names?

[1] http://en.wikipedia.org/wiki/Keyboard_layout#Turkish

Original comment by livibet...@gmail.com on 20 Aug 2011 at 6:17

• Changed state: Accepted

[GoogleCodeExporter]

I added this diff [1] from Issue 77 to my package. Now:

- works
* not works
i / İ and ı / I is a little complicated :) [2, 3] I don't know much about the 
issue.
. works

All of the above (", ı, I, ç, Ç, ş, Ş, ö, Ö, ü, Ü, i, İ, ğ, Ğ) have 
their own single key.

sudo dumpkeys [4]

xmodmap -pk [5]

[1] 
http://svn.pardus.org.tr/pardus/playground/maidis/2011/accessibility/key-mon/fil
es/hede.diff
[2] 
http://webcache.googleusercontent.com/search?q=cache:zO4wRxC2s10J:www.i18nguy.co
m/unicode/turkish-i18n.html+Why+Applications+Fail+With+The+Turkish+Language&cd=1
&hl=tr&ct=clnk&source=www.google.com
[3] http://www.moserware.com/2008/02/does-your-code-pass-turkey-test.html
[4] http://paste.pardus-linux.org/1029/
[5] http://paste.pardus-linux.org/1030/

Original comment by ozbekanil on 20 Aug 2011 at 7:01

[GoogleCodeExporter]

If you don't mind, I want to fix this off this Issue Tracker because I
don't want we comment to each other, back and forth here. I will CC
you when I finish a first-step fix in my clone. We will test using my
clone, I don't want to commit a lot of fixes to fix fixes.

If anyone would like to help, feel free to join and give a hand about
this issue. I will post a link to an issue in my clone later.

Original comment by livibet...@gmail.com on 21 Aug 2011 at 2:36

[GoogleCodeExporter]

Please check out Issue 94, I think rewrite the keymap system might be a better 
way to fix this issue. Be sure to star it if you can help.

If anyone wants to submit a tr.kbd meanwhile, go ahead to upload it. I will add 
it.

Original comment by livibet...@gmail.com on 21 Aug 2011 at 6:01

[GoogleCodeExporter]

I feel I am keeping change my decide. Anyway, this should be fixed in 
ra80c57d19119.

Please try it out and let me know if any still missing.

It should be working by just running without any commandline argument because 
default kbdfile is now reflecting your system xkb layout as long as there is no 
keymap option set in your configuration file

You can specify the new kbdfile if default doesn't work:

  key-mon --kbdfile=tr.kbd
  # or
  key-mon --kbdfile=tr_f.kbd

Original comment by livibet...@gmail.com on 21 Aug 2011 at 10:01

• Changed state: Started

[GoogleCodeExporter]

With last changes all Turkish characters shown on key-mon by using key-mon 
--kbdfile=tr.kbd command or selecting tr.kbd at Settings > Mics > Keymap 
section. Thanks for your effort on this.

But now there is a tiny new error in ra80c57d19119. When i press < key on 
key-mon crashing with following [1] messages on console. I don't sure if this 
is a packaging problem or a bug belongs to key-mon.

After a few crash:

$ ls /tmp/*keymon*
/tmp/keymon-AsOh5o.svg  /tmp/keymon-h0vKIH.svg  /tmp/keymon-ly4hQX.svg

xlib.py output for <

$ python ./xlib.py 
Xlib.protocol.request.QueryExtension
Xlib.protocol.request.QueryExtension
Press ESCape to quit
<type:EV_KEY scancode:86 code:KEY_LESS value:1
type:EV_KEY scancode:86 code:KEY_LESS value:0

[1] http://paste.pardus-linux.org/1031/

Original comment by ozbekanil on 21 Aug 2011 at 3:25

[GoogleCodeExporter]

Hmm... that svg is malformed due to unescape '<', but it shouldn't be sent to 
generate svg at all and I couldn't find a key is '<' [1]. Except the 
[AltGr]+["] to generate '<'.

Where is that key on your keyboard? (Could you also give me the output 
`setxkbmap -v`?)

[1] http://en.wikipedia.org/wiki/File:KB_Turkey.svg

Original comment by livibet...@gmail.com on 21 Aug 2011 at 3:47

[GoogleCodeExporter]

I don't sure whether it is standart or not but < is quite common in Turkish 
keyboards. My keyboards both have < key [1] :)

Here is setxkbmap -v output:

$ setxkbmap -v
Trying to build keymap using the following components:
keycodes:   evdev+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc+tr+inet(evdev)
geometry:   pc(pc104)

[1] http://i.imgur.com/UNHHl.jpg

Original comment by ozbekanil on 21 Aug 2011 at 4:23

[GoogleCodeExporter]

Please pull to get re1e4aeffebbc, it should be fixed now.

Original comment by livibet...@gmail.com on 21 Aug 2011 at 4:53

[GoogleCodeExporter]

Everything works fine now. Thank you very much.

Original comment by ozbekanil on 21 Aug 2011 at 5:47

[GoogleCodeExporter]

You are welcome, thanks for reporting!

Original comment by livibet...@gmail.com on 21 Aug 2011 at 6:00

• Changed state: Fixed