Bug#577852: libgtk2.0-common: dead_stroke has no visible effect

[Mario Frasca]

On 2010-0416 09:57:59, Josselin Mouette wrote:
> Le jeudi 15 avril 2010 à 09:04 +0200, Mario Frasca a écrit :
> > 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.
> 
> 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”.

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.

-- 
There are 10 types of people. Those who understand binary and those who don't