Releases: googlefonts/ufo2ft
Releases · googlefonts/ufo2ft
v2.12.0
- Added experimental support for generating COLR/CPAL color fonts from UFO layers (thanks Just Van Rossum! #359).
- Provide fallbacks for all UFO fontinfo values so one can now build a TTFont even from an empty UFO (don't expect it to do much).
- [util] When creating a new glyph use defcon's
Layer.instantiateGlyphObject
to keep the glyph sub-elements custom classes that are associated with it by the defcon client. - Require fontTools >= 4.4.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
- Dropped support for Python 2.7. Python 3.6 or greater is now required.
- Bumped minimum requirements:
- fonttools >= 4.2.0
- cu2qu >= 1.6.6
- booleanOperations >= 0.9.0
- When computing the glyph bounding boxes, the
ufo2ft.outlineCompiler
now uses the compiledTTGlyph
orCFF CharString
objects instead of the UFO glyphs, since the latter may still contain float coordinates and component offsets, which could lead to incorrect off-by-one bounds and sidebearings (#356, googlefonts/fontmake#593).
v2.10.0
- Added
debugFeatureFile
option to the compile functions, to dump and inspect the text of auto-generated features (#354). - Added optional
sortContours
filter for sorting contours. It works around an issue with non-deterministic contour order from pyclipper across different platforms (#345, typemytype/booleanOperations#55).
v2.9.2
- [outlineCompiler] Glyphs' vertical origin default to OS/2.sTypoAscender instead of hhea.ascent (#343)
- [outlineCompiler] Do not require openTypeVheaCaret(Offset|Slope) info attributes to build vhea/vmtx (#344).
- Defcon is no longer required explicitly in
setup.py
'sinstall_requires
, since ufo2ft never imports from it directly.
The client can still load a UFO using defcon (or ufoLib2) and pass the font object to ufo2ft.
v2.9.1
Updated minimum required fonttools to 3.43.0 to incorporate some important bugfixes when building variable fonts.
Read the full fonttools changelog for more info: