Thanks for all this information and sorry for the late reply.
For edgy we now have scim-chewing 0.3.1 and libchewing 0.3.0.
If scim-bridge is installed, we use it for the GTK_IM_MODULE, otherwise we use xim.
For Qt we use scim as QT_IM_MODUL if scim-qtimm is installed and xim otherwise.
From my reading of this bugreport this sounds like we are fine in edgy (both database corruption wise and im-switch default settings).
I would like to close this report (if my analysis is correct) and add a new task to backport the current scim-chewing to dapper-backports.
Cheers, Michael
Thanks for all this information and sorry for the late reply.
For edgy we now have scim-chewing 0.3.1 and libchewing 0.3.0.
If scim-bridge is installed, we use it for the GTK_IM_MODULE, otherwise we use xim.
For Qt we use scim as QT_IM_MODUL if scim-qtimm is installed and xim otherwise.
From my reading of this bugreport this sounds like we are fine in edgy (both database corruption wise and im-switch default settings).
I would like to close this report (if my analysis is correct) and add a new task to backport the current scim-chewing to dapper-backports.
Cheers,
Michael