GNOME Bugzilla – Bug 765177
GTK Applications does not take unicode
Last modified: 2018-04-15 00:33:59 UTC
I am using Gnome wayland 3.20 built by myself using jhbuild in Fedora 23. In wayland session, some applications such as Firefox (pre-installed in Fedora) accepts unicode and shows well. But GTK applications compiled from C source - such as gedit - does not take unicode. But oddly pygtk program can accept unicode and shows well(https://github.com/wavexx/screenkey.git). Doesn't pygtk use GTK as its backend? This is only happened in wayland session, and it all works well in Xorg session. I tried to fix it, but has failed until now. Is there someone who knows how to solve this problem, or guide me to fix it? Thanks. Hyungwon Hwang
This bug report is not clear enough to answer. What do you mean with "take unicode" ? are you taking about keyboard input ? Using an input method ? Or are we talking about opening files ?
"Take unicode" is about taking about keyboard input. The screenshot #1 shows unicode character as expected. It was taken in Xorg session. But the screenchot #2 shows just English character, even the input method is in Hangul(한) mode (as it is shown from right upper corner). I am not sure, but from what I understood, I thought that the problem is in GTK because it works well in wayland session for Firefox or PYGTK program.
Created attachment 326333 [details] Screenshot #1
Created attachment 326334 [details] Screenshot #2
Not sure what is going on, maybe the ibus libraries in jhbuild are not compatible with the ibus running in your session. Or maybe the jbuild applications are not finding the ibus module (although I would expect an error message in that case)
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new