- From: John Hudson <tiro@tiro.com>
- Date: Wed, 19 May 2010 21:01:48 -0700
- To: public-webfonts-wg@w3.org
- CC: www-font@w3.org
Christopher Slye wrote: > The overarching questions is this: If a foundry chooses to include extended metadata in a WOFF file, shouldn't that be considered an inextricable component of the WOFF? Yes, the creator of the WOFF is not required to put it there, and the UA is not required to do anything with it, but still, should the UA be permitted to accept the font data without its accompanying metadata? I understand from Sylvain's response that the matter of validating the optional metadata and private data presents challenges, and I don't have good ideas at the moment about how to address those. But I do think it is a basic principle that if the WOFF file contains metadata or private data they have a right to be there and a UA has no business stripping them. These data are optional in the sense that the WOFF file creator can opt to include them; they are not optional in the sense that a UA can opt to remove them. If the metadata or private date is malformed, then that means the WOFF file is malformed, and a UA should not use it. Font data from within a malformed WOFF file should not be used. JH
Received on Thursday, 20 May 2010 04:02:33 UTC