[SCIM] Re: [immodule-qt] how about built-in dead key support?
LiuCougar
liucougar at gmail.com
Mon Jul 19 10:36:26 PDT 2004
On Tue, 20 Jul 2004 00:12:46 +0800, Zhe Su <james.su at gmail.com> wrote:
> Implementing this feature as a special IMEngine of SCIM maybe the
> easiest way, but it's not the best way. Because user must choose a
> special input method in the menu in order to use compose keys. Just
> closing SCIM by ctrl-space won't make it work.
I think a dedicated "dead/compose key" IMEngine is a good short term
solution for scim: we can use this IMEngine as "cascading method" in
our frontends (such as gtk-imm or qt-imm), just as a slave input
context (of course, this should be configurable, not all users need
compose keys)
As to long term solution, I agree with you that the proxy mechanism is
needed: all the frontends of scim should not deal with compose key
themselves: it should be transparent to them, that means scim-lib
makes all the necessary translation internally (if it is told to
support compose/dead keys).
Regards,
Cougar
--
"People's characters are strengthened through struggle against
difficulties; they are weakened by comfort."
- Old Chinese adage
More information about the scim
mailing list