- From: Jonathan Kew <jfkthame@googlemail.com>
- Date: Wed, 5 Oct 2011 14:55:50 +0100
- To: Chris Lilley <chris@w3.org>
- Cc: WebFonts WG <public-webfonts-wg@w3.org>
On 5 Oct 2011, at 14:24, Chris Lilley wrote: > * FontSquirrel > http://www.fontsquirrel.com/fontface/generator > > Testing in expert mode with only WOFF output, all optional fixups, subsetting and table-dropping disabled, hinting not dropped. > > Some invalid files are converted and fixed, some fail conversion (either way a pass). Looking good so far, almost done testing. > > FontSquirrel says that "OTF fonts are now converted to TTF for better rendering on Windows." which could be a problem. If this is an integral part of their system, it implies that for OpenType/CFF fonts, FontSquirrel is not providing a WOFF-packaging service. Rather, it provides a (lossy) conversion to TTF, and then WOFF-packages that. That means there's no chance of round-tripping an OpenType/CFF font through FontSquirrel's WOFF generator and back to OpenType, and ending up with glyphs that render identically to the original. While this may be a useful service for some users, it doesn't qualify as a fully-conforming WOFF generator. There's no way it can satisfy "The result of creating a WOFF file and then decoding this to regenerate an sfnt font MUST result in a final font that is bitwise-identical to the well-formed input font" for OpenType/CFF input if it's converting CFF to TT glyphs, for example. JK
Received on Wednesday, 5 October 2011 13:56:26 UTC