762090 - Error displaying font since update

Status: RESOLVED INCOMPLETE

(Core :: Layout: Text and Fonts, defect)

Description

[northabyss]

Attachment: comparison.png

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0
Build ID: 20120420145725

Steps to reproduce:

I updated Firefox to version 13.0.


Actual results:

Ugaritic characters appear like blank blocks [see attachment]. I reverted to version 12.0 and everything was fine again.
Tried deleting and reinstall the fonts which support these special letters with no avail. The options in Firefox seem the same, also.
The font I'm using now is MPH 2B Damase [damase_v.2.ttf], but this is also reproducible with any other font that supports Ugaritic language.


Expected results:

They should appear normally.

Comment 1

[northabyss]

Problem is identical to https://bugzilla.mozilla.org/show_bug.cgi?id=756850 but this still persists after the patch.

Comment 2

[Jonathan Kew [:jfkthame]]

Hmm, this seems to be specific to the DirectWrite backend; I don't see the problem on OS X, and on Windows, disabling hardware acceleration (so that we use the GDI backend instead) avoids the issue.

With a suitable font (such as MPH 2B Damase from http://www.dafont.com/mph-2b-damase.font) installed, the regression can be seen on Alan Wood's sample page at http://alanwood.net/unicode/ugaritic.html.

Comment 3

[Jonathan Kew [:jfkthame]]

Oh, I know what's going on here - this is a result of bug 705594. If you go to about:config and set gfx.font_rendering.fallback.always_use_cmaps to "true", then restart the browser, the problem will go away.

This suggests that the DirectWrite-based system fallback (patch 2c) from bug 705594 is not working very well.

Comment 4

[Fanolian]

Another workaround suggested by Groovy Gregor from Mozillazine[1]:
In about:config, adding the fonts you want to use in Firefox to font.name-list.sans-serif.x-unicode and/or font.name-list.serif.x-unicode .

[1]: http://forums.mozillazine.org/viewtopic.php?p=11808611#p11808611

Comment 5

[u554753]

Hi Reporter,

Are you still having these issues with newer versions of Firefox or Nightly? Thanks!

Comment 6

[u554753]

Closing due to lack of response. If this is still pertinent, please respond with information provided in Comment 5.