- From: Chris Lilley <chris@w3.org>
- Date: Fri, 25 Mar 2011 16:45:59 +0100
- To: Tal Leming <tal@typesupply.com>
- CC: WOFF Working Group <public-webfonts-wg@w3.org>
On Friday, March 25, 2011, 4:41:17 PM, Tal wrote: TL> http://dev.w3.org/webfonts/WOFF/spec/#conform-incorrect-reject >> If the input font has defects or anomalies that make this impossible, the WOFF-generating tool SHOULD either reject the font or issue an appropriate warning that lossless round-trip conversion will not be possible TL> Do you think a note at the top of the test suite page would be a TL> good way to address this? Yes. TL> It could say something like this: TL> The tests in this suite represent SFNT data to be used for WOFF TL> conversion without any alteration or correction. An authoring tool TL> may allow the explicit or silent modification and/or correction of TL> SFNT data. Good. TL> In such a case, the tests in this suite that are TL> labeled as "should not convert" may be converted so long as the TL> problems in the files have been corrected. The bitwise identical TL> tests may also fail as a result of an authoring tool's modifications. TL> This is a really tricky thing to explain... How about In such a case, the tests in this suite that are labeled as "should not convert" may be converted, so long as the problems in the files have been corrected. In that case, there is no longer any access to the "input font" as defined in the WOFF specification, so the bitwise identical tests should be skipped. -- Chris Lilley Technical Director, Interaction Domain W3C Graphics Activity Lead, Fonts Activity Lead Co-Chair, W3C Hypertext CG Member, CSS, WebFonts, SVG Working Groups
Received on Friday, 25 March 2011 15:46:02 UTC