[Webkit-unassigned] [Bug 10691] WebKit text system needs support for non-system FontData providers

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=10691





------- Comment #2 from macdome at opendarwin.org  2006-09-03 23:16 PDT -------
(In reply to comment #1)
> I would like to know where the current FontCahce fits in under this proposal:
> is it going to become one of the FontDataProviders or is it going to stay as a
> layer above them? I think Eric has a reply to that which he's going to add here
> :)
> 

With regards to the current FontCache, Hyatt and I talked about keeping it as a
layer above any of the FontDataProviders, but adding a "URL" or some sort of
scoping information.  That way system fonts can be long-lived in the cache,
document-specific fonts can be purged at the end of a document's lifetime, and
also one document would not interfere with any other.  This could also be
accomplished by having a separate cache on the document.

Also, I've gone back and re-read how WebFonts are supposed to work.  I was
initially confused.  I thought that a single style would reference a particular
font by URL (such as font: url("foo.svg")).  This is no the case.  Instead a
@font-face definition (or in SVG a <font-face> element) describes a font to be
added to the "pool" of selectable fonts.  This font is generally given a name. 
It is through this name that the font is later referenced.  For example, if our
@font-face declaration gave our font the name "Foo Font" (and referenced
foo.svg), then later styles might use "font: Foo Font, Times, serif;" to use
this font.  This changes the architecture slightly.  Instead of needing the
FontFamily to hold a pointer to the dataprovider as I initially thought,
instead the @font-face or <font-face> elements need a way to register
themselves and their info for font fallback.  I've not yet read enough about
how font fallback works in our engine to comment on how this might be
accomplished.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.