[I18n] Compose and Gtk2/Mozilla

2003-09-30 Thread Marius Gedminas
I'm using a customized /usr/X11R6/lib/X11/locale/lt_LT.UTF-8/Compose file to enter a different number of accented letters (a ogonek, c caron, e dot etc) with a single dead key (dead_tilde). This worked fine in all X11 apps. Then quite some time ago (somehere around 1.0 or 1.2) Mozilla stopped

Re: [I18n] Compose and Gtk2/Mozilla

2003-09-30 Thread Danilo Segan
, 30. 2003. 17:58:33 CEST Owen Taylor : As far as I know, you shouldn't lose that. That's done completely separate from input method handling. Uhm, I must have been mistaken. I remember having problems with it a week or so ago (with Gtk+ 2.2.4), but I cannot replicate it now. It must have

Re: [I18n] Compose and Gtk2/Mozilla

2003-09-30 Thread Marius Gedminas
On Tue, Sep 30, 2003 at 11:58:33AM -0400, Owen Taylor wrote: On Tue, 2003-09-30 at 11:08, Danilo Segan wrote: , 30. 2003. 15:42:25 CEST Vasilis Vasaitis : GTK+ 2.x uses by default its own input methods for character composition. Nevertheless, you can force GTK+ applications to use

Re: [I18n] Compose and Gtk2/Mozilla

2003-09-30 Thread Noah Levitt
On Tue, Sep 30, 2003 at 19:34:33 +0200, Danilo Segan wrote: Dead keys can be defined for any key of the keyboard. That means that you can put dead_acute at A if you wish, and yes, XKB can be used for that. OTOH, Compose sequences cannot be defined with XKB (I believe there were some