Bug#439004: libgtk2.0-0: does not correctly load im_module_file any longer

Thadeu Lima de Souza Cascardo cascardo at minaslivre.org
Wed Sep 19 10:55:21 UTC 2007


On 09/19/2007 07:07:32 AM, Josselin Mouette wrote:
> Le mardi 21 août 2007 à 11:13 -0300, Thadeu Lima de Souza Cascardo a
> écrit :
> > The im_module_file, either defined in gtkrc or as a environment
> variable,
> > GTK_IM_MODULE_FILE, is loaded before all other files in a Debian
> defined
> > directory.
> > 
> > This changes the upstream GTK+ behavior: when a user defines his
> own
> > im_module_file, that is the only file loaded.
> > 
> > I propose a minor fix, that would load the user im_module_file 
> after
> the
> > files located in the Debian directory.
> > 
> > In the patch named 020_immodules-files-d.patch, I would change
> > 
> > +  list_str = g_strjoin (G_SEARCHPATH_SEPARATOR_S,
> > +                       im_module_file_str,
> > +                       im_module_files_d_str,
> > +                       NULL);
> > +
> > 
> > into
> > 
> > +  list_str = g_strjoin (G_SEARCHPATH_SEPARATOR_S,
> > +                       im_module_files_d_str,
> > +                       im_module_file_str,
> > +                       NULL);
> > +
> 
> Are you sure of that? I think this is going to have the opposite
> effect,
> because this list is processed in reverse order.
> 
> Cheers,
> -- 
>  .''`.           Josselin Mouette        /\./\
> : :' :           josselin.mouette at ens-lyon.org
> `. `'                        joss at debian.org
>   `-  Debian GNU/Linux -- The power of freedom
> 

Yes, I am sure of that.

In the times before etch, when I had GTK+ 2.8.x installed on my sid 
system, I configured my .gtkrc-2.0 as this:
im_module_file "/home/cascardo/.gtk-cedilla"

And even though I used en_US as my language, I could type 'c and have 
cedilla instead of a c with an acute.

However, when I upgraded to GTK+ 2.10.x, that stopped working. I didn't 
know why, and that couldn't possibly be a change in upstream, since 
I've learned that trick reading GTK+ 2.10.4 source code.

When I thought that a debian patch could be the reason, I checked and 
found out that patch. I've changed it just like I am proposing, built 
it and it worked again just like before upgrading to GTK+ 2.10.x.

If you'd like I try removing my configuration file and see if the 
Debian directory still works, I'd be glad to do it. I think the matter 
here, however, is: should a user configuration overwrite the Debian 
directory configuration? And I think the answer should be yes.

Regards,
Thadeu Cascardo. 













More information about the pkg-gnome-maintainers mailing list