Red Hat Bugzilla – Bug 209626
scim doesn't show preedit text from fallback context
Last modified: 2007-11-30 17:11:45 EST
The gtk input context implementation in scim-bridge uses a GtkIMContextSimple as
a "fallback" context, but it does not show preedit text from that fallback context.
Try the following:
1) enable scim
2) hold control-shift
3) type u123
4) releaes control-shift
5) by surpised by an accented g popping up
Notice that there is no preedit text displayed in 3)
This is the feature of SCIM itself.
Please try "export GTK_IM_MODULE=scim; gedit" from the terminal.
You can confirm that exactly the same thing happens.
If you're annoying by this feature, please report this to SCIM project directly.
This is not a feature, it is a bug
Okay, but I think Dairiki-san means it is not a regression relative to
the scim gtkimm.
Reproduced for both scim and scim-bridge.
Since scim provides the rawcode engine for unicode input (currently hidden by
default though in Fedora), perhaps it would be better if it didn't pass the
Ctrl-Shift-U event to GtkIMContextSimple.
I think Ctrl-Shift-U should not be the feature of scim, but the feature of
gtk(or x-window?), so the preedit window won't shown as scim don't know this at all.
Ctrl-Shift-U work even when scim is not running(or be killed).
If you want to see the preedit window, just choose scim's rawcode im engine,
then enter 123 and the preedit window will be shown, the first character is just
what you input by Ctrl-Shift-U with 123.
So this is not a bug.
Well, if scim uses some other input method as fallback (like in thie case
GtkIMContextSimple), it better made sure that any preedit text of the fallback
input method finds its way back to the application. It doesn't, and thats a bug.
I think the best way to fix this bug by disabling this feature, but GtkIMContext
does not provide an interface to do it. It is difficult to disable it in scim
and scim-bridge. I suggest asking gtk to add this API.
No, this is an scim bug. If it decides to fallback to GtkImContextSimple, it
needs to do it properly.
And if it cannot be bothered to do it properly, it should not do the fallback
Yeah. It's an bug in scim. But it is difficult fix without an API to disable it
in GTK. I found other IMs have similar problem, like uim.
I do not suggest showing preedit text from GtkIMContextSimple, it will conflict
with own preedit text.
It is very simple - if you cannot display preedit text from the fallback, then
don't fallback to something that produces preedit text...
Do you mean discarding Ctrl+Shift+U key event?
I mean just don't fall back to GtkImContextSimple. But filtering out C-S-u may
be good enough.
Fixed in scim-bridge-0.4.12-3.fc8.
try to reproduce and test with latest version.
use gedit, use scim-bridge- > Press Ctrl+Shift+U+012-> No pre-edit buffer
ctrl-Space (deactivate Scim) - >press Ctrl+Shift+U+012->Showing Preedit buffer.
it seems bug still present with scim-bridge.
can someone please have a look and help to correct me with stop I used to produce.
Does "Control+Shift+u123" still work in current rawhide?
(It doesn't seem to do anything for me anymore.)
Hmm nevermind, probably it is a local issue on my test machine:
it works for me on another rawhide install (without scim).
"C-S-u123" preedit works for me under scim-bridge on a fresh japanese install
of rawhide. So this looks good to me now. :)
(In reply to comment #16)
> use gedit, use scim-bridge- > Press Ctrl+Shift+U+012-> No pre-edit buffer
> ctrl-Space (deactivate Scim) - >press Ctrl+Shift+U+012->Showing Preedit buffer.
This only needs to work when scim is deactivated so that is ok.
Thanks for testing. :)