- Package:
- libgtk2.0-common
- Source:
- gtk+2.0
- Submitter:
- Mario Frasca
- Date:
- 2010-04-28 06:00:03 UTC
- Severity:
- normal
I don't use many gtk applications, just gnome-terminal and sometimes nautilus. this affects both. Emacs and xterm (not gtk) are unaffected. I use dead_stroke in a keymap table file that I pass to xmodmap and I don't manage to obtain any visible effect. to reproduce the bug, I used this keymap table file, » clear Lock keycode 66 = Multi_key keycode 48 = dead_stroke « and activate it with xmodmap. hitting the key associated to dead_stroke followed by l should produce ł (small L with stroke) but gives l (small L). compose slash l works correctly. also dead_breve does not work. other dead keys like dead_macron, dead_acute and dead_breve do work with this method. I observe the same behaviour also on maemo, both on os2008 (using xmodmap) and meamo5, where I don't use xmodmap but setxkbmap.
Le jeudi 15 avril 2010 à 09:04 +0200, Mario Frasca a écrit : This is because GTK+ uses its own composition tables and extends them in its own way. If you want to use the X input method in an application, you can right-click, select “Input method”, then “X input method”. You can also select it by setting GTK_IM_MODULE=xim in the environment. Cheers,
no, I actually really want to use GTK+'s own input method... can you point me to references on how to use them? (I am a bit internet-impaired at the moment, laptop was stolen, I can use email but home browsing is more or less limited to my maemo5 device) what I suspect is that there's a problem with dead_stroke and dead_breve, and I base this on: 1) xmodmap manages to alter GTK+ composition tables for all dead keys except dead_stroke and dead_breve. 2) on maemo5, which is AFAIU GTK+ based, I am using its own keyboard definition table and dead_stroke and dead_breve do not work. to verify my suspicion I want to use GTK+'s native input method on my old desktop system and check if there I do manage to get dead_stroke and dead_breve to work.
hi here, I'm looking for the proper gtk+ way to define and set keyboard layouts. is it through usage of `setxkbmap`? this is what one uses on Maemo so I assume it is the way to go. well, also using setxkbmap dead_stroke does not work. in the us(mac) layout dead_stroke is associated to the 'S' key, with shift and right alt modifiers. after `setxkbmap "us(mac)"` the behaviour I get is exactly as what I get when I alter the keyboard layout using xmodmap, namely: * gnome-terminal: dead_stroke does not compose with following key * xev shows the KeyPress event for dead_stroke * uxterm: dead_stroke correctly composes ħđøł I've googled in a few different sessions and I don't find anything looking like composition tables for gtk+ anywhere, except possibly this very bug report.