Bug 19291

Summary:	some non-functional keys Arabic keyboard layout
Product:	xorg	Reporter:	alsadi <alsadi>
Component:	Lib/Xlib (data)	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED DUPLICATE	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description alsadi 2008-12-26 01:44:15 UTC

because X can generate only one character per key the key لا is mapped to
U+FEFB ARABIC LIGATURE LAM WITH ALEF ISOLATED FORM

but it should be mapped to the sequence U+0644 U+0627
U+0644 ARABIC LETTER LAM followed by U+0627 ARABIC LETTER ALEF

when this problem noticed they disabled the key completely
(map it to null)

http://lists.arabeyes.org/archives/developer/2008/May/msg00013.html

later a solution was introduced

http://lists.arabeyes.org/archives/developer/2008/June/msg00001.html
http://mail.gnome.org/archives/gnome-i18n/2008-June/msg00030.html

the solution involve patching 
/usr/share/X11/xkb/symbols/ara
/usr/share/X11/locale/en_US.UTF-8/Compose 

those files owned by libX11 in my distro and I posted the patched files there
as I reported this to https://bugzilla.redhat.com/show_bug.cgi?id=466627

for this patch to work one must export
export GTK_IM_MODULE="xim"
export QT_IM_MODULE="xim"
I don't request doing this last step
but I request patching the two files

Comment 1 James Cloos 2008-12-26 06:32:09 UTC

The patch to libX11 was committed back in June with
commit 21e464ec682ab23ba20ddf6bd72c6db214cfbe01.

The first release since that commit was libX11-1.1.5.

Sergey committed the change to symbols/ara earlier this month
with commit c3b2fd97444f47e726b7916dd1a3ce04ada2d88d.

I don’t beleive there has been a release since then.

This, then, reduces to a dup of bugs #16426 and #18833.

Comment 2 alsadi 2008-12-26 06:38:28 UTC

thanks 

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

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.