Re: OpenType fsType and WOFF (was: Agenda, action items and suggested WOFF changes)

I think defining conformant tool behavior based on the embedding bits
of the source OpenType font, new or old,  will be a much bigger
distraction than it's worth.  Defining the exact meaning of these bits
has always been problematic and it may not be universal; a font vendor
may be fine having a trusted service do the WOFF conversion but not a
general user.  

A WOFF conversion tool may be part of a larger application, a content
management system or a font editor.  What should conformant behavior
be for something like a font editor?

Suggesting in the spec that tools issue a warning based on embedding
bits is fine (e.g. restricted embedding) but I don't think *requiring*
tools not to produce a WOFF font based on these bits is a good idea.

Regards,

John Daggett

Received on Wednesday, 12 May 2010 03:33:24 UTC