Re: Missing test assertion, reconstructing (searchRange, entrySelector and rangeShift).

On Tuesday, November 29, 2011, 3:56:13 PM, Tal wrote:

TL> On Nov 29, 2011, at 8:49 AM, Chris Lilley wrote:

>> On a third hand, the assertion could be broadened to include authoring tools which perform round-trip or bidirectional conversion,and would be testable (perhaps the bitwise-identical authoring tool tests already cover this).

TL> The Authoring Tool cases invalidsfnt-searchrange-001,
TL> invalidsfnt-entryselector-001 and invalidsfnt-rangeshift-001 have
TL> invalid values for these fields for SFNT input testing.

Good, but that seems to be a different test. Its about conversion from sfnt to woff.

The quoted spec text is about conversion from woff (which does not explicitly store these values) to sfnt (so they need to be correctly calculated).

-- 
 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 Tuesday, 29 November 2011 18:21:29 UTC