After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 561097 - Char "^" in German keyboard layout not working as expected
Char "^" in German keyboard layout not working as expected
Status: RESOLVED DUPLICATE of bug 145058
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.14.x
Other All
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-11-16 19:45 UTC by Jonathan Schleifer
Modified: 2008-11-17 08:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jonathan Schleifer 2008-11-16 19:45:45 UTC
Please describe the problem:
To write a "^" on the German keyboard layout, you need to use the composing key "^". If you press it once, nothing happens, as expected. When you press it twice, one "^" is generated. Other Windows applications generate "^^" then.  This means a user has to press 4 times "^" in Gtk on Win32 to get the "^^" smilie in for example an instant messenger. This is something a lot of our Win32 users complain about (we = Gajim).

Steps to reproduce:
1. Press the "^" key twice.
2. Only one "^" appears.
3. Press the "^" key twice in any other Win32 application.
4. "^^" will appear there.


Actual results:
You get "^" instead of "^^".

Expected results:
It should be "^^".

Does this happen every time?
Yes

Other information:
Comment 1 Tor Lillqvist 2008-11-17 08:54:41 UTC
The correct term is "dead key", not "composing key". Using "composing" is misleading as it can easily be confused with the concept of the "Compose" key which isn't used on Windows keyboard layouts as far as I know.

Anyway, if you want the same behaviour in both GTK+-based and other Windows application, and also on X11, you just need to type the dead key followed by a space instead of the dead key twice.

That said, this is a duplicate of bug #145058. Yes, that bug has been open for over four years. Patches still welcome.

*** This bug has been marked as a duplicate of 145058 ***