W3C home > Mailing lists > Public > www-style@w3.org > May 2011

RE: [css3-fonts] multiple formats in src descriptor

From: Levantovsky, Vladimir <Vladimir.Levantovsky@MonotypeImaging.com>
Date: Thu, 26 May 2011 10:04:30 -0400
To: John Daggett <jdaggett@mozilla.com>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <7534F85A589E654EB1E44E5CFDC19E3D0BE17F049E@wob-email-01.agfamonotype.org>
On Thursday, May 26, 2011 2:27 AM John Daggett wrote:
> Daniel Glazman wrote:
> > Sorry, but in the case of the src font descriptor [1], I don't
> > understand exactly the use case for a format() hint containing more
> > than one format string. For instance:
> >
> >    src: url(foo) format("woff", "opentype");
> >
> > Is it to handle the case where a single URL can reference multiple
> > font objects of different formats? In that case, what's the mechanism
> > used for the format selection between user agent and server? Content
> > negociation based on the format string?
> There are font formats that overlap (e.g. various subflavors of
> TrueType) but user agents will typically support both format hints, so
> I'm not sure there's a real need for this.  The format hint is there
> to tell a user agent when *not* to download a font, not to identify
> the data format in any great detail.

Actually, format hints containing more than one format string may come handy with WOFF, where one string would identify WOFF as a container format, and another one (as in Daniel's example above) could be used to identify the format of a font encapsulated inside WOFF file. For this to be useful, the format hints should be well defined and specific  -e.g.:

src: url(foo) format("woff", "opentype-cff");

would allow UA to skip downloading a WOFF resource containing OpenType CFF font if it is known that the device cannot render CFF outlines.


> [1] http://www.w3.org/TR/1998/REC-CSS2-19980512/fonts.html#referencing

Received on Thursday, 26 May 2011 14:04:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:46 UTC