Releases: googlefonts/glyphsLib
Releases · googlefonts/glyphsLib
v5.3.0
- Fix infinite loop in GSPath.segments (#621)
- Fix applyTransform for paths (#625)
- Fix out-of-order array access in bezierminmax (#627)
- Improve vertical typesetting (#629)
- Fix problem where axis with no mappings was erroring out during roundtrip (#630)
- Use Proxy for GSFont.features/featurePrefixes (#632)
- Improve compatibility with Glyphs: Make GSNode.position settable with a tuple. (#644)
- ufo2glyphs: Make really sure to preserve the Designspace axis order (#649)
CI is now done via GitHub Actions, thanks to Simon & Cosimo.
v5.3.0b1
Testing automatic deployment via Github CI.
v5.2.0
v5.1.11
Fixed two issues with anchor propagation in composite glyphs (#617, googlefonts/fontmake#682).
- marks that are in turn composed of other marks (e.g. "shadda_fatha-ar") didn’t receive propagated anchors at all. A solution was already developed in ufo2ft's
PropagateAnchorsFilter
, so Yanone ported that piece of code over here. - ligature anchors (top_1, top_2 etc) weren’t correctly propagated when composed of base glyphs and a mark (e.g. "lam_alefHamzaabove-ar"). To fix that, we now check for marks attached to a named
GSComponent.anchor
(stored in UFO asGlyph.lib['com.schriftgestaltung.Glyphs.ComponentInfo']
), and adjust the named anchor’s position by the component transformation.
v5.1.10
v5.1.9
- Make sure we don't end up with a Designspace with empty axes, even when there is only a single master at default location (googlefonts/fontmake#644).