On Sat, Mar 17, 2012 at 03:41:56PM +0800, Aron Xu wrote: > Sorry I don't understand what's the problem: > > $ env | grep GTK > GTK_IM_MODULE=fcitx > $ env | grep QT > QT4_IM_MODULE=fcitx > > And even if QT*_IM_MODULE aren't exported, why it's a bug in ibus/fcitx?
Well.... they are bugs if the hook script provided for im-swich by these packages does not work with the existing im-switch implimentation. im-switch was created before QT4 and it uses QT_IM_MODULE only. Exporting of QT_IM_MODULE from im-switch works with QT4 but setting QT4_IM_MODULE for im-switch does not do what you wish im-switch should do. Since im-switch is going out soonish, let's make changes minimal. Let's make ibus/fcitx to work with archaic but exising im-switch. That is all this is about. I know this is confusing. You see, I was confused enough to agree to use QT4_IM_MODULE for the im-switch hook script. But Ikuya woke me up. Regards, Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
