I was surprised to find this bug report here, along with a fix someone wrote. Back in June 2008 (a month before this bug was reported) I was annoyed by this bug, and wrote a patch for it and sent it off upstream to the scim project. I got a reply that the patch was applied and would be released a few months later as a part of a maintenance release.
This has now become part of scim-bridge release 0.4.15.2.
I'm not entirely sure about how ubuntu handles upgrading and getting rid of patches at this time, but I would at least like to notify the packagers that there will be a conflict of this sort once they do decide to upgrade from 0.4.14 to the newest version from upstream.
Oh, and about that, 0.4.15 was released februrary 2008. Is there a reason why ubuntu has not synced to upstream in 14 months?
Hi there everyone
I was surprised to find this bug report here, along with a fix someone wrote. Back in June 2008 (a month before this bug was reported) I was annoyed by this bug, and wrote a patch for it and sent it off upstream to the scim project. I got a reply that the patch was applied and would be released a few months later as a part of a maintenance release.
The original patch commit is here:
http:// scim.cvs. sourceforge. net/viewvc/ scim/scim- bridge/ client- qt/scim- bridge- client- imcontext- qt.cpp? r1=1.17& r2=1.18
This has now become part of scim-bridge release 0.4.15.2.
I'm not entirely sure about how ubuntu handles upgrading and getting rid of patches at this time, but I would at least like to notify the packagers that there will be a conflict of this sort once they do decide to upgrade from 0.4.14 to the newest version from upstream.
Oh, and about that, 0.4.15 was released februrary 2008. Is there a reason why ubuntu has not synced to upstream in 14 months?