Closed
Bug 660320
Opened 13 years ago
Closed 13 years ago
Indic fonts not rendering correctly.
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: abhinav.kumar.in, Unassigned)
References
()
Details
Attachments
(1 file)
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0a2) Gecko/20110527 Firefox/6.0a2
Build Identifier:
When opening a site with Indic fonts such as Devnagari (Hindi), Bengali etc, the fonts aren't rendering correctly.
Reproducible: Always
Comment 1•13 years ago
|
||
Hmm... it appears that this was working fine in 4.0.1 and 5.0beta, but is broken in Aurora and Nightly.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•13 years ago
|
Keywords: regression,
regressionwindow-wanted
Comment 2•13 years ago
|
||
This was caused by bug 643460, which updated the OTS font sanitizer to a version that actually parses and checks the OpenType layout tables (GDEF/GPOS/GSUB). Previously, we passed these tables through to Uniscribe/DWrite without checking them.
Apparently the sanitizer is rejecting one (or more) of the OpenType tables in the fonts used on the bhaskar.com site, and this means that proper rendering is no longer possible. As downloadable Indic fonts on other sites *do* work (e.g. http://webfonts.fonts.com/en-US/Project/ChooseFonts#keyword%3Ddevanagari%26page%3D1), it seems likely that this is in fact caused by a font error.
The MS Font Validator tool might help to identify any problems in the font tables.
Keywords: regressionwindow-wanted
Comment 3•13 years ago
|
||
Indeed, Font Validator reports a number of errors in the fonts used on this site. So it appears that OTS is correct to reject the OpenType tables, and "broken" rendering is the expected outcome of this.
Comment 4•13 years ago
|
||
Resolving as invalid; as described above, this is a font error and not a Firefox bug.
Reporter, I suggest you try contacting the webmaster at the site in question, and inform them about the problems with their fonts.
Reporter | ||
Comment 5•13 years ago
|
||
Oh! Ok then.
You need to log in
before you can comment on or make changes to this bug.
Description
•