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 588131 - NEO keyboard layout not working correctly
NEO keyboard layout not working correctly
Status: RESOLVED DUPLICATE of bug 165385
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.16.x
Other All
: Low normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
: 789233 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-07-09 04:22 UTC by Alejandro
Modified: 2017-10-20 08:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alejandro 2009-07-09 04:22:47 UTC
Please describe the problem:
I'm using the NEO keyboard layout (http://neo-layout.org/ - page is in german only unfortunately but by hovering over the "Ebene 1" to "Ebene 6" buttons you can see how the layout works) and text input isn't working at all for the non standard 'layers' (Ebenen).

Example: I want to type a '_' so I'll have to hold down SHIFT and press "W" on a normal QWERTY keyboard ('v' in Neo). Instead of the '_' a 'v' appears.

Steps to reproduce:
Just type text in any text box provided by GTK+

Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
I tested this with XChat, Gimp, Pidgin and TortoiseHG (see bug report there http://bitbucket.org/tortoisehg/stable/issue/189/text-input-not-working-correctly-with-alternative-keyboard )

I'm not sure but this might be related (or even the same) to #165385, #371371, #453068 and #559115
Comment 1 debach 2009-09-28 14:41:47 UTC
I can confirm this one. Non-standard modifiers like CAPSLOCK and the #-key have no effect: CAPSLOCK+W same as #+W should get you an underscore, but actually outputs a 'w'. Only GTK+ applications fail to work with the Neo2 layout, whereas Qt applications, Mozilla software etc. do work.

Note that this holds only for the keyboard driver. If an analogous Autohotkey program is used instead, the layout works as expected. Yet, Autohotkey lacks some of a driver's functionality which is why it is no appropriate replacement.
Comment 2 Tor Lillqvist 2009-09-28 18:06:39 UTC
You just have to decide then, which is more important: Using an alternative keyboard layout that GTK+ doesn't seem to handle, or using GTK+ applications.

*** This bug has been marked as a duplicate of bug 165385 ***
Comment 3 Markus Lasermann 2017-10-20 08:51:45 UTC
*** Bug 789233 has been marked as a duplicate of this bug. ***