[GTK] @font-face fonts do not have complex text support

• Component: WebKitGTK
• Status: RESOLVED DUPLICATE

[Khaled Hosny]

Using r36309, Arabic text got rendered with the specified font (thanks to fixing #16942), but when I use @font-face CSS property (downloadable fonts) only Latin part get rendered using the specified font, while Arabic is rendered using one of my system fonts.

[Khaled Hosny]

Created attachment 23347 [details]
testcase

The web-font.html and installed-font.html should be rendered the same (of course you need to install the font for the later to work)

[Khaled Hosny]

Created attachment 23348 [details]
Screenshot of the font installed

[Khaled Hosny]

Created attachment 23349 [details]
Screenshot of the font unsing @font-face

Notice that Latin text is rendered the same in both screenshots.

[Alp Toker]

Confirmed. This is blocked by Pango: http://bugzilla.gnome.org/show_bug.cgi?id=347237

Downgrading bug to P3 because there's nothing we can do about it until Pango is fixed and the text is still legible. Please let us know when the fix gets into Pango so we can support this!

[Khaled Hosny]

I'm not sure if this is relevant, but you might be interested in this comment http://bugzilla.gnome.org/show_bug.cgi?id=346942#c14

[Martin Robinson]

This no longer appears to be an issue. The @font-face font is used (with the FreeType backend). Unfortunately, since we do not have complex text support for @font-face fonts yet, the render is totally incorrect. The attached test cases are very nice and I'd like to preserve them, so I'll update the title of this issue to reflect the current state of things.

[Eric Seidel (no email)]

Is this covered by bug 92098?

[Martin Robinson]

Yeah, switching to HarfBuzzNG will fix this issue.

[Martin Robinson]

*** Bug 72837 has been marked as a duplicate of this bug. ***

[Martin Robinson]

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