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 662313 - Use ScriptExtensions.txt and other tricks to improve script itemization re sc=Common
Use ScriptExtensions.txt and other tricks to improve script itemization re sc...
Status: RESOLVED OBSOLETE
Product: pango
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: pango-maint
pango-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-20 17:34 UTC by Behdad Esfahbod
Modified: 2018-05-22 13:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Behdad Esfahbod 2011-10-20 17:34:59 UTC 
Test case:

pango-view --text 'x ـبب' --font 'nazli 172'
Comment 1 Behdad Esfahbod 2011-11-02 23:06:46 UTC 
Basically, what happens right now is that TATWEEL is Sc=Common, so it's grouped with the Latin before it and hence ends up in a run different from the Arabic letters, and as a result not joined to BEH.

Two ways to fix this:

1. Make smarter use of bid levels in script itemizer.  Ie, since TATWEEL is in the same bidi run as the Arabic text, it should resolve to that script, not Latin which is in the neighboring bidi run.

2. Use ScriptExtensions.txt.  That tells us that TATWEEL is used in Arabic and Syriac.  If none of the neighboring scripts are in that list we should default to one in the list.  Roozbeh wants to provide a canonical ordered list scripts to use for prioritizing scripts in that case.

3. Of course, making Arabic joining work across runs fixes this case, but not the problem.
Comment 3 Behdad Esfahbod 2013-01-17 04:12:36 UTC 
Sample downstream bug:

  https://bugzilla.redhat.com/show_bug.cgi?id=635956
Comment 4 GNOME Infrastructure Team 2018-05-22 13:02:17 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/pango/issues/198.