[Bug 37984] [Freetype] Support for "locl" tables

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Mar 30 09:14:57 UTC 2013


--- Comment #39 from Georg Duffner <g.duffner at gmail.com>  2013-03-30 02:13:08 PST ---
(In reply to comment #38)
> (In reply to comment #35)
> > I’ve updated the page with an explanation and with a screenshot of the expected result.
> Thanks - that's a good starting point for creating some LayoutTests later.

(In reply to comment #37)
> (In reply to comment #36)
> > On Chromium/Linux one locl is active, namely the one corresponding to your system’s locale. 
> That's wrong, the browser should use the locl corresponding to the locale the run of text is marked with
> (I suspect chromium has no locl awareness and it only "works" because it is unaware the system font stack is locl-compatible)

Thinking deeper about the above said, it looks, like this is not an issue of webkit any longer. The example of Chromium shows that locl is applied, just not the correct one because the browser doesn’t handle the lang-attribute correctly.

I think, we have to look into the browsers we use and file bugs at their trackers.

I did so for Chromium here: http://code.google.com/p/chromium/issues/detail?id=224170

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the fonts-bugs mailing list