https://bugzilla.redhat.com/show_bug.cgi?id=2122899
--- Comment #18 from Mike FABIAN <mfabian(a)redhat.com> ---
*If* we cannot fix ibus and Gtk to handle the Arabic compose sequence correctly
*then* we probably need to change default-input-sources.h and we could use
"m17n:ar:kbd" for most (or even all) Arabic locales but we would need to check
carefully the differences between these layouts and maybe even create new
variants of "m17n:ar:kbd" (Because the current "m17n:ar:kbd" would not
work
right if the underlying layout is not US English, so maybe a variant which
would work on top of a French AZERTY layout would need to be added).
*And* langtable/anaconda would need to set the US English layout for Arabic
locales then, assuming that the "m17n:ar:kbd" imput method on top of that would
handle the Arabic.
Also, the current 'ara' Arabic keyboard layout uses western digits in the
number row:
key <AE01> { [ 1, exclam,
Arabic_1, NoSymbol ]}; // 1 ! ١
The Arabic digit one is only produced by typing AltGr+1.
This is different from what "m17n:ar:kbd" does, /usr/share/m17n/ar-kbd.mim
contains:
(map
(generic
("1" "١")
("2" "٢")
("3" "٣")
("4" "٤")
("5" "٥")
("6" "٦")
("7" "٧")
("8" "٨")
("9" "٩")
("0" "٠")
i.e. it replaces the Western digit "1" *always* with the Arabic digit
"١", when
using "m17n:ar:kbd" you cannot type Western digits anymore, which might be a
problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2122899