Bug 20323 - More Arabic support claimed than existing
Summary: More Arabic support claimed than existing
Status: RESOLVED FIXED
Alias: None
Product: DejaVu
Classification: Unclassified
Component: Mono Sans (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: Deja Vu bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-25 20:42 UTC by Roozbeh Pournader
Modified: 2009-02-27 18:13 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Roozbeh Pournader 2009-02-25 20:42:59 UTC
Sans Mono has CMAP tables for some Arabic characters, but does not have all the necessary contextual glyphs to show them correctly. This results in various problems, including:

* With shaping engines like Pango, the previous and next letter will join to the incorrectly-supported letter, but the letter itself will display as isolated.

* fontconfig will incorrectly report that the font supports some languages, while it really doesn't.

This is very bad, comparable to CJK fonts having CMAPs for some Arabic letters, but no GSUB data.

The CMAP references for these characters should be removed from the font until all the contextual glyphs with proper 'fina', 'medi', and 'init' GSU?B substitutions are added.

The characters are:
066E: Dual_joining, no substitutions
066F: Dual_joining, no substitutions
067C: Dual_joining, no substitutions
067D: Dual_joining, no substitutions
0681: Dual_joining, no substitutions
0682: Dual_joining, no substitutions
0685: Dual_joining, no substitutions
0692: Right_joining, no substitutions
06A1: Dual_joining, no substitutions
06B5: Dual_joining, no substitutions
06BA: Dual_joining, only 'fina' exists ('init' and 'medi' missing)
06C6: Right_joining, no substitutions
06CE: Dual_joining, no substitutions
06D5: Right_joining, no substitutions
Comment 1 Roozbeh Pournader 2009-02-27 18:13:48 UTC
Fixed in svn r2340.


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.