[immodule-qt] a environment variable to control the module

[Daisuke Kameda]

YamaKen <yamaken at bp.iij4u.or.jp> wrote:

> Hi Daisuke, thanks for your response from busy life.

I am sorry in the response being late.


> I said "Users expect $QT_IM_MODULE is available for the immodule
> for Qt because $GTK_IM_MODULE is available for immodule for
> GTK+. The two implementation is both named 'immodule', so same
> mechanism (but in different variable name) must be available".

Sorry, I didn't understand that it included the concrete thought 
that $QT_IM_MODULE should be introduced.


> > But, I also approve of the idea that it becomes the origin 
> > of confusion and trap. And, I think that introduction of environment 
> > variable named QT_IM_MODULE also become the origin of confusion, 
> > since it increases the contents to set up.
> > 
> > It is the better solution for users to prepare a setting tool which 
> > performs both the writing to qtrc and a setup of GTK_IM_MODULE.
> 
> I can't agree with you, especially reusing GTK_IM_MODULE for the
> immodule for Qt. Ordinary users will not recognize that
> GTK_IM_MODULE is affecting the immodule for Qt. It will
> introduce considerable confusion quite bigger than
> QT_IM_MODULE. You should consider the power of names.

No. My opinion is that it should not neither reuse GTK_IM_MODULE in 
Qt, nor introduce QT_IM_MODULE, since it increases the configuration.
I can't think good solution adding an environment variable, either.



-- 
Daisuke Kameda <kaminmat at cc.rim.or.jp>