Releases: googlefonts/ufo2ft
Releases · googlefonts/ufo2ft
v3.4.2
- Fixed bug whereby OS/2 codepage range bits weren't correctly computed for variable fonts (all unset except fallback bit 0).
This happened when a designspace contained a<variable-font>
element with a'public.fontInfo'
lib key that did not explicitly overrideopenTypeOS2CodePageRanges
(#897).
v3.4.1
v3.4.0
- [postProcessor] fontTools.varLib.cff.convertCFFtoCFF2 is deprecated (#882)
- [outlineCompiler] Warn when building COLRv0 if gid1 is not blank (#886)
- [instantiator] Use designspace.findDefault() the first time designspace.default is checked (#887)
- [markFeatureWriter] Fix ligatures with unnumbered contextual anchors having their mark attachment dropped (#890)
- [markFeatureWriter] Support contextual mark2mark anchors (#895)
- [markFeatureWriter] Drop “ambiguously connected” info message (#892)
- [removeOverlaps] Capture TypeError and ValueError that pathops and booleanOperations might raise (#492)
- [doc] Document lib keys modifying ufo2ft's behavior (#286)
v3.3.1
v3.3.0
v3.2.8
- [featureWriters] Ensure CursFeatureWriter comes first, before kerning mark feature writers; in some non-HarfBuzz implementations the GPOS lookup order matters (#864).
- [kernFeatureWriter] Ignore zero-valued class-class kerning pairs when generating variable kern feature as they are no-op (#866).
- Take discrete axes into account when checking for feature compatibility across masters (#867).
v3.2.7
- cursFeatureWriter: Remove stray print()