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 574581 - some non-functional keys Arabic keyboard layout
some non-functional keys Arabic keyboard layout
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
2.14.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-03-08 19:59 UTC by muayyad alsadi
Modified: 2018-02-10 03:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description muayyad alsadi 2009-03-08 19:59:49 UTC
Please describe the problem:
even after fixing the problem in X
some keys are not functional

I put it against gdk just a guess

the entire problem is reported to both freedesktop and redhat buzgilla's
http://bugs.freedesktop.org/show_bug.cgi?id=19291
https://bugzilla.redhat.com/show_bug.cgi?id=466627

when one presses some keys like the one with "b" in English layout
two characters should be generated

after doing the fixes in X
one needs to export GTK_IM_MODULE="xim"
it will work then

but this is a special case
for example on windows [ie. no X there]
the problem is still there in Gtk+ applications
ie. one don't get any thing when he presses b

which made me to guess it's in gdk


Steps to reproduce:
1. install gimp on windows
2. change layout to arabic
3. press b to get لا


Actual results:
nothing

Expected results:
لا is typed

Does this happen every time?
yes

Other information:
feel free to move it to win32 or clone it
Comment 1 Matthias Clasen 2009-03-10 16:25:33 UTC
See bug 537457 for multiple-codepoints-per-compose-sequence support for the builtin gtk input method
Comment 2 Matthias Clasen 2018-02-10 03:23:01 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.