[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#267062: xlibs: [xkb] wrong Compose file for pl_PL.UTF-8?



On Mon, 2004-09-20 at 14:55, Branden Robinson wrote:
> On Mon, Aug 30, 2004 at 12:42:18AM +0200, Shot wrote:
> > ...uxterm, you say. This gets interesting - uxterm works for
> > me according to the compose maps, that is it seems to be using
> > en_US.UTF-8/Compose; I *can* get per mille, I *can't* get aogonek.
> > Does this mean there's something broken in GTK/GNOME? Mozilla, Galeon,
> > gnome-terminal: all broken. xterm, uxterm, OpenOffice.org Writer:
> > all working.
> 
> Jeff Licquia told me this has to do with the GNOME input method you have
> configured.
> 
> Jeff, can you mail 267062-submitter@bugs.debian.org  with a little more
> elaboration?

Sorry for the late reply; it appears that Debian's mail system held onto
these messages for a while, so I just now got them.

GTK+ has its own input method framework that is separate from the X
input methods.  This is necessary because GTK+ is supposed to be
independent of X.

The default input method is, of course, Latin.  When implementing this
method, the GTK+ people focused on ISO-8859-1, and did not implement
many of the other Latin character sets.  This is why GTK-based programs
seem not to be able to type characters that other pure X programs can.

There are several things you can do about the problem.  All of them
involve using a different GTK+ input method.  You can test these by
opening some GTK+ app that takes input, such as gedit.  Right-click on
the edit box, and there should be a submenu for "Input Methods".  The
new input method should show up in that submenu.

 - Get a better GTK+ input method.  The gtk-im-extra Sourceforge project
(http://gtk-im-extra.sourceforge.net/) contains a Latin Plus input
method, for example.  While you're at it, you might also lobby the GTK+
people to include gtk-im-extra, and make Latin Plus the default.

 - There are alternative input method projects out there that provide
GTK+ IM shims; look for the packages iiimgcf, scim-gtk2-immodule, and
uim-gtk2.0 in testing/unstable.  Most of these, though, are aimed at
non-Latin issues, so I can't tell you if any of them would be
appropriate.

 - Additionally, GTK+ ships with a XIM shim module.  This is the
solution I've implemented.

If you want to make some other input method the default, edit
/etc/environment, and set the environment variable GTK_IM_MODULE there
to the input method module you want ("xim" for the XIM shim).  Of
course, you can do the same thing for just yourself by setting that
environment variable in .profile, .bashrc, or whatever.





Reply to: