Bug 12958 - Composition String (a.k.a preedit string) of IME isn't shown
Summary: Composition String (a.k.a preedit string) of IME isn't shown
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.0.9
Hardware: PC Windows
: --- normal
Target Milestone: master
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2013-06-29 08:50 UTC by Takuro Ashie
Modified: 2013-07-16 12:42 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Takuro Ashie 2013-06-29 08:50:56 UTC
When I try to input Japanese string via IME on a text widget, composition string isn't shown on it.

On the other hand, when I continue typing then commit the string by pressing "Enter" key, a result string is correctly entered to the widget. And I confirmed that "System (Windows IME)" in the "Input Methods" menu in the context menu of the widget is correctly selected. So IME seems work.


Although a similiar issue is fixed recenctly,

  https://github.com/mono/monodevelop/commit/b2af5536d0c4271fac425105b3568f5cd51c7265

I think that the issue I met is different problem, because

* It's also reproduced on standard GTK+ widgets.
* No preedit string is entered (the caret doesn't move). Not a color issue.


FYI I also using GTK+ on windows (gtk+-2.24.10) with my some products, I have not seen such a problem on them.
Comment 1 Mikayla Hutchinson [MSFT] 2013-07-01 14:08:23 UTC
I recently fixed an issue where the first preedit string would not be rendered: https://github.com/mono/monodevelop/commit/37ebb263107972de4cc0b68fe159a014c0c5b2cf

Though if GTK+ widgets are affected too, then it sounds like a gtk+ bug.
Comment 2 Mikayla Hutchinson [MSFT] 2013-07-01 14:18:16 UTC
Confirmed, seems to be a GTK bug since it affects GTK entries too.
Comment 3 Takuro Ashie 2013-07-05 07:00:20 UTC
> FYI I also using GTK+ on windows (gtk+-2.24.10) with my some products, I have
> not seen such a problem on them.

I updated GTK+ in my products to 2.24.20 and tested it.
I can't still reproduce this issue with it.
Comment 4 Mikayla Hutchinson [MSFT] 2013-07-11 20:16:36 UTC
We have prepared a new build of GTK+ that contains a fix for this issue. To test it, please download https://mjhutchinson.com/files/temp/gtk-2.24.20-2013-07-11.zip and copy the directories it contains "C:\Program Files (x86)\GtkSharp\2.12". You can verify it is installed by checking that "Help->About->Show Details" shows "GTK 2.24.20".
Comment 5 Mikayla Hutchinson [MSFT] 2013-07-11 20:17:02 UTC
I have verified that this fix works on my machine.
Comment 6 Takuro Ashie 2013-07-12 07:05:49 UTC
> https://mjhutchinson.com/files/temp/gtk-2.24.20-2013-07-11.zip

I confirmed it on my environment.

It works fine for me too.
Thanks!
Comment 7 Mikayla Hutchinson [MSFT] 2013-07-16 12:42:24 UTC
The new GTK+ binaries have been included in the GTK# 2.12.22 installer, which is now in the beta update channel and will roll out to stable after we're reasonably confident there are no regressions.