GNOME Bugzilla – Bug 715061
Text Tool: Can't type diacritics with CapsLock
Last modified: 2018-05-24 14:04:07 UTC
When I try to type Czech diacritical letters like ŽŠČŘČ with CapsLock, the program always puts in lowercase letter instead of an uppercase. I have this problem with all fonts including those that definitely support Czech (as I tried on OpenOffice Writer or Windows Notepad). More peculiar is that when I type the text in Notepad and copy-paste it to GIMP, it comes out alright with all diacritical letters uppercase. (no problem with Czech language overall, lowercase letters work fine, just the uppercase)
Check the "Use Editor" toggle in the text tool options, can you enter the characters there?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Hello Michael, the problem is still unsolved (Gimp 2.8.14). The problem is the same on both - canvas / text editor. Normal behaviour when CapsLock is active is that you gain ĚŠČŘŽÝÁÍÉÚŮ. Problem is that when you want to get it in Gimp, it gives you those letters in lowercase. Workaround is to press key with punctuation mark and then upper case letter (with SHIFT or CAPSLOCK). Feel free to ask for more details if you need them.
It seems like it's only problem in Windows (and maybe Mac - not tested). One guy at forum reported that on his Kubuntu 12.04 LTS Gimp 2.6 and Xubuntu 14.04 Gimp 2.8, it works as supposed.
OK, I've found another thing - the same problem is in Inkscape. Is it possible that it's problem of GTK?
btw, Geany has the same problem (also GTK app) - all from me tested on Windows 7 SP1 64bit Professional
Text input is handled by GTK+, this makes it likely a GTK+ problem. As such, it might already have been reported in the gtk+ product, but I could find a report in a quick search of the open gtk+ bugs.
I've probably found thread in gtk+ section, but I don't know how to mark this thread as duplicate (resp. replace it to gtk+ section). here is the link: https://bugzilla.gnome.org/show_bug.cgi?id=165385
We might decide to keep that one open in the GIMP product as a pointer to the GTK+ one, so I'll add bug 165385 as a dependency.
Confirming as per the overall description in bug 165385.
Gtk+ bug https://bugzilla.gnome.org/show_bug.cgi?id=165385 is fixed now and the fix is released in Gtk+ 3.22.7 release http://ftp.gnome.org/pub/gnome/sources/gtk+/3.22/gtk+-3.22.7.news Can be GIMP updated now to use Gtk+ 3.22.7 in Win builds?
No. GIMP does not use GTK+ 3.x yet.
The fix also landed in 2.24 branch https://git.gnome.org/browse/gtk%2B/commit/?id=516c1ba159137462dbd7709801e9aa212b05f29c Can GIMP use 2.24 current git or it must wait for 2.24.32 release (which could be quite far away)?
The capslock crashing problem definitely happens in Linux, too. I'm using Linux Peppermint, Gimp 2.8.16, and Gimp will crash, losing all my open work, if I press the CAPSLOCK key while typing using the Text tool or while renaming a layer. (Note: I have tried to update to 2.8.22 using the command line to test this in the newest release, but I get the message that "Gimp is already the newest version (2.8.16-1ubuntu1.1)"
Hello, (In reply to kataclysm from comment #14) > The capslock crashing problem definitely happens in Linux, too. I'm using > Linux Peppermint, Gimp 2.8.16, and Gimp will crash, losing all my open work, > if I press the CAPSLOCK key while typing using the Text tool or while This issue is not about a crash at all. This is about uppercase letters that the reporter cannot type with CapsLock. Please if you have another problem, create a new bug report. > renaming a layer. (Note: I have tried to update to 2.8.22 using the command > line to test this in the newest release, but I get the message that "Gimp is > already the newest version (2.8.16-1ubuntu1.1)" Maybe you can try installing from Flatpack then: https://www.gimp.org/downloads/ This said, 2.8.16 is quite an old version. Are you sure you are using a distribution version which is still being maintained? P.S.: please don't answer here. If your issue still happens after testing the Flatpak build, open a new bug report.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/510.