[Bug 37984] WebKit freetype backend doesn't support "locl" tables

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jan 10 21:13:28 UTC 2013


--- Comment #29 from Behdad Esfahbod <behdad at google.com>  2013-01-10 13:15:21 PST ---
(In reply to comment #27)
> (In reply to comment #22)
> > After that, it's just a matter of developing the heuristics.  I personally think that we should get rid of the fastpath and always do complex text processing (requires adding new caches).  But that's far from where we are right now.
> Get rid of the simple path altogether, in WebKit?

Yes, that's the way it should be IMO.  The reason it's not possible right now, is because WebKit does not cache shaping results.  As such, every time text is being shown, it's being shaped and shown.  That's why supposedly the complex text path is "too slow" for common usage.  With effective caching it's possible to turn full shaping on for all scripts.  Indeed, that's what Firefox does.

> Can you elaborate a little bit on the heuristics you have in mind? In this case, just something that's based on locales that need lookups in the locl table (like apparently Serbian, as in the original report)? Or something more generic?

I don't have any heuristics in mind.  You can start by adding Serbian, and then add other languages when people nag.  You can tell I'm in the same camp as Nicolas though: even for Latin I think we should do full OpenType shaping.

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