1.1.7 release notes
Released
Two spec-conformance fixes in the subsetter, both found while extracting it into a separate project and validating the output against the OpenType spec and fontTools rather than against daegun itself. Output bytes move for anything that rebuilds a font, so pinned subset fingerprints need re-recording. Nothing in the public API changed.
Fixed
head’s directory checksum was computed over the wrong bytes.build_ttfchecksummed the table as written, including whatevercheckSumAdjustmentthe incoming font happened to carry. The spec computes that entry with the field read as zero, since it is derived from the very checksum it would otherwise feed into. 26 of 27 test fonts came out with a wrong entry. Nothing caught it because the whole-file adjustment subtracted the stale value straight back out, so the file checksum validated and the one rule nobody was checking stayed broken. OTS runs over every font a browser downloads, and fontbakery checks the same field.- A subset could not address any codepoint above U+FFFF. Format 4 covers the BMP and nothing
else, and nothing emitted a format 12 subtable, so a supplementary-plane glyph was embedded and
named correctly in the glyph map while the cmap had no way back to it.
STIX2Mathwent from 5 of 16 requested codepoints addressable to all 16, and the plane 15 private-use test fonts from none to all of theirs. Fonts living entirely in the BMP emit nothing extra and their bytes are unchanged.
Changed
build_format4_cmapis nowbuild_unicode_cmap. It emits a format 12 subtable beside the format 4 one, with the(0, 4)and(3, 10)encoding records, whenever a mapping sits above the BMP. It is internal to the subsetter and absent from the C API.- The
subset fontsandinstanced fontsfingerprints moved. Theheadfix changes exactly two fields in every rebuilt font: its directory entry checksum, andcheckSumAdjustment, which shifts with it because the entry sits inside the header the file checksum covers. No other table and no glyph data changes.
Both fixes carry a test that was confirmed to fail without it, which the head bug in particular
earned: it had already survived one checksum rule that passed the whole time.