GNOME Bugzilla – Bug 710883
GTK+ does not show quotes correctly. Replaces with diacritics.
Last modified: 2015-06-13 17:21:22 UTC
I'm experiencing the same bug that others have been posting around the internet, and will link to these posts below: http://superuser.com/questions/440096/windows-pidgin-gtk-cannot-type-quotes-properly http://stackoverflow.com/questions/7866157/how-to-type-single-quote-in-j-gtk-terminal-under-windows-7 http://superuser.com/questions/518806/keyboard-types-diacritics-instead-of-double-quotes These issues seem to be cross-platform considering the third post there. I'm experiencing this problem in the latest Pidgin IM program myself, but the common denominator in all of these problems that I, and other people like me, have been experiencing is GTK+. For some reason something in GTK+ breaks the ability to use normal quotation marks " and ' and replaces them with diacritics and accents ¨ and ´. On Windows I'm using the US International keyboard setting, and I have configured Pidgin to use Lucida Sans Unicode because the native Pidgin font does not allow for Unicode characters to show. This did nothing to fix the problem. Can someone please fix this problem in GTK+? I've tried everything I could conceivably search for, tried every solution mentioned, but have as of yet not managed to fix this issue.
Which version of Gtk+ is this about?
(In reply to comment #1) > Which version of Gtk+ is this about? Whatever version Pidgin has shipped with it since 2011? The manifest folder has a file called gtk+_2.16.6-2_win32.mft, so I'm expecting it to be GTK+ 2.16.6, revision 2? If I'm reading the version number correctly. I don't believe Pidgin allows for manually updating this, since it's located within the Pidgin Program Files folder. I also seem to recall I had this problem with Open Office 3.x, but it disappeared upon upgrading to Open Office 4.x.
(In reply to comment #2) > (In reply to comment #1) > > Which version of Gtk+ is this about? > > Whatever version Pidgin has shipped with it since 2011? If the problem is about Pidgin's hardcoded ancient version of GTK that they ship, please file a bug report against the Pidgin developers to update it. See http://pidgin.im/.
(In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > Which version of Gtk+ is this about? > > > > Whatever version Pidgin has shipped with it since 2011? > > If the problem is about Pidgin's hardcoded ancient version of GTK that they > ship, please file a bug report against the Pidgin developers to update it. See > http://pidgin.im/. The problem is that Pidgin does not, in fact, respond to bug reports offered to them about this issue. They have been systematically ignoring this issue and have been giving weird remarks to people complaining about diacritics and cedilla for the past eight years. Can you confirm this problem does not currently exist within newer versions of GTK+ before closing this bug? Furthermore it is/was not just Pidgin with this issue, although Pidgin is the program I use most and is therefore the most important for me. Please confirm the problem does not exist in newer versions of GTK+.
(In reply to comment #4) > The problem is that Pidgin does not, in fact, respond to bug reports offered to > them about this issue. I cannot fix Pidgin developers. :) > Can you confirm this problem does not currently exist within newer versions of > GTK+ before closing this bug? No, because I haven't tried to compile Pidgin in my life and then try to compile it against a non-ancient version of GTK+. > Furthermore it is/was not just Pidgin with this issue, although Pidgin is the > program I use most and is therefore the most important for me. Please provide examples for other applications which do not work correctly and which use recent and supported versions of GTK+ (2.24.19, 3.8.6, or 3.10.x).
It's mostly for good reasons that we've not upgraded the GTK+ version shipped with Pidgin on Windows - for the longest time there were regressions which made it not practical to do so. I do believe that the latest 2.24 releases are pretty stable, so it probably is feasible for the version shipped with Pidgin to be upgraded. That said, I believe that this complaint is caused by the same issues as Bug 569581 and Bug 371371, which aren't fixed in any released version. The latter has a patch, which I've been meaning to try out, but I haven't had a chance to do so yet.
If the issue is third party software using an old version of GTK+, there's not much we can do. Feel free to reopen if you spot the bug in a recent version of GTK+.