Michael Ummels wrote:
> Another workaround is to use the XIM input method plugin instead of the
> scim-bridge one. You can enable it by executing "im-switch -s scim".
I have suggested that scim-bridge* and skim are removed from the Kubuntu
seeds for Intrepid. That means, they should not be installed anymore on
a pristine install from the final image. However, when upgrading from
Hardy, things might go wrong and the user would need to remove those
packages by hand.
> BTW, is it possible to compile the scim immodule (package scim-qtimm)
> for Qt3 with Qt4?
My guess is that the code would need to be ported to qt4 first.
Anyways, scim-qtimm should not be needed for qt4 applications, AFAIK
plain XIM works fine. But for legacy qt3 apps, I'm not sure how to
handle this... setting the QT_IM_MODULE variable should affect both qt3
and qt4 applications and in this case conflict...
(damn this design!) I hope we can do better for Jaunty...
Michael Ummels wrote:
> Another workaround is to use the XIM input method plugin instead of the
> scim-bridge one. You can enable it by executing "im-switch -s scim".
I have suggested that scim-bridge* and skim are removed from the Kubuntu
seeds for Intrepid. That means, they should not be installed anymore on
a pristine install from the final image. However, when upgrading from
Hardy, things might go wrong and the user would need to remove those
packages by hand.
> BTW, is it possible to compile the scim immodule (package scim-qtimm)
> for Qt3 with Qt4?
My guess is that the code would need to be ported to qt4 first.
Anyways, scim-qtimm should not be needed for qt4 applications, AFAIK
plain XIM works fine. But for legacy qt3 apps, I'm not sure how to
handle this... setting the QT_IM_MODULE variable should affect both qt3
and qt4 applications and in this case conflict...
(damn this design!) I hope we can do better for Jaunty...