Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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,
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.
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.
Confirmed, seems to be a GTK bug since it affects GTK entries too.
> 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.
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".
I have verified that this fix works on my machine.
I confirmed it on my environment.
It works fine for me too.
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.