- From: John Hudson <tiro@tiro.com>
- Date: Thu, 27 Mar 2014 16:30:42 -0700
- To: Behdad Esfahbod <behdad@google.com>, Jonathan Kew <jfkthame@gmail.com>
- CC: Raph Levien <raph@google.com>, "public-webfonts-wg@w3.org" <public-webfonts-wg@w3.org>
On 27/03/14 3:07 PM, Behdad Esfahbod wrote: > I understand so far it has been out of the scope of this working group. > But does the WG like to take a stance over what "smart-font" > technologies are supported by WOFF2 (OpenType, Graphite2, AAT)? Or > explicitly stay agnostic? I certainly wouldn't like to take such a stance. WOFF should compress and wrap anything put in an sfnt; WOFF2 optimises the compression for some kinds of known data, but in general terms any table is WOFFable. Which is to say, I don't recommend putting jpegs of kittens in your web fonts, but it's out of scope for this working group to prevent you from doing so. It might also be unwise to load up a web font with layout tables for technologies that are not supported in most of the platforms to which the font is served, but again that's a decision for the WOFF creator, not for this working group. [I realise that this everything-in-an-sfnt-is-valid stance contradicts my earlier suggestion to declare custom tool source tables as invalid for WOFF. I reserve the right to be contradictory.] JH
Received on Thursday, 27 March 2014 23:32:24 UTC