On Tue, Sep 30, 2003 at 03:40:42PM +0300, Marius Gedminas wrote: > 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 using my customized Compose file (e.g. dead_tilde + e now > produces eacute instead of eogonek that is specified in my Compose > customizations). Later I noticed the same problem with OpenOffice and > now I see the same problem with all applications that use Gtk version 2. > Gtk 1.2, KDE 3, and traditional X11 apps seem to work fine. > > Am I missing some new convention for determining the behavior of dead > keys, or is this just a pervasive bug shared by Gtk2, Mozilla and > OpenOffice.org?
It's Not A Bug, It's A Feature. (TM) GTK+ 2.x uses by default its own input methods for character composition. Nevertheless, you can force GTK+ applications to use the Xlib composition mechanisms by setting GTK_IM_MODULE=xim among your environment variables. -- Vasilis Vasaitis [EMAIL PROTECTED] +306976604701 _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
