[Webkit-unassigned] [Bug 61561] add support for "on demand" webfonts

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=61561


Dimitri Glazkov (Google) <dglazkov at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dglazkov at chromium.org




--- Comment #7 from Dimitri Glazkov (Google) <dglazkov at chromium.org>  2011-06-14 13:40:33 PST ---
(In reply to comment #6)
> So rather than inventing a new way for client/server to communicate, I'd try to latch onto existing concepts. We know a font can be broken up into multiple files server-side and you can serve up pieces based off unicode ranges.
> 
> If unicode range does a poor job of addressing specific sets of characters that might be very scattered, then maybe what's needed is a set of keywords for unicode range that could represent those sets (and avoid the author having to define some giant list of single characters in the unicode range).

Before jumping to a working prototype, I think we should make a good assessment of how feasible would it be to standardize something like this. It sounds like as-is, the idea is bound to remain a one-off WebKit oddity, which to me smells like death.

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