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 132378 - Problem with Arabic Orphan Marks
Problem with Arabic Orphan Marks
Status: RESOLVED DUPLICATE of bug 103938
Product: pango
Classification: Platform
Component: general
Other Linux
: Normal normal
: ---
Assigned To: pango-maint
Depends on:
Reported: 2004-01-24 09:16 UTC by Soheil Hassas Yeganeh
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4

Description Soheil Hassas Yeganeh 2004-01-24 09:16:35 UTC
We were working on Fall-Back rendering for Arabic language, but there are
some problems for Arabic Orphan Marks:

1- Pango doesn't find any valid shape engine for Orpahn marks, because, the
script specified for Arabic marks in "pango_script_table" is

2- FriBIDI gives an Odd level number for Arabic Orphan marks, so, even if
Pango shape them with Arabic shape engine, positioning rules can not be
applied to them, because in OpenType lookup and rules (OTL), Arabic runs
are assumed to be RTL.

Best Regards
Comment 1 Behdad Esfahbod 2004-01-24 22:51:58 UTC
From what I see in the code, Pango renders all marks on the previous
character in the visual stream.  So never assumes that a mark is used
in an RTL context.  Moreover, I really doubt that FriBidi assigns an
odd level to an orphan mark.  Marks simply get the level of their base

Moreover, ASAIK Arabic module in Pango does nothing about marks, so I
cannot see what the bug is.
Comment 2 Owen Taylor 2004-02-23 18:41:09 UTC
I don't think trying to make sure that "orphan" Arabic fonts
always go to the Arabic shaper makes sense, so this just
duplicates bug 103938 or bug 127176; whatever engine gets
the orphan mark needs to handle it the best it can.

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