Skip to content

[glyphs] Propagate anchors regardless of ufo2ft filters - #2155

Open
cmyr wants to merge 1 commit into
mainfrom
propagate-anchors-custom-param
Open

cmyr wants to merge 1 commit into
mainfrom
propagate-anchors-custom-param

Conversation

@cmyr

@cmyr cmyr commented Sep 16, 2026

Copy link
Copy Markdown
Member

If the default master's userData had a ufo2ft filters list, we only set PROPAGATE_ANCHORS when propagateAnchors appeared in it. But glyphsLib propagates anchors before it ever looks at filters, gated only by the "Propagate Anchors" custom parameter (default true), so any source with that userData key (e.g. anything produced by ufo2glyphs) silently lost propagation in fontc while fontmake still propagated.

With this patch, the custom parameter alone decides; a propagateAnchors filter entry is a no-op, as in glyphsLib.

This fixes major layout diffs in NotoSans.

If the default master's userData had a ufo2ft filters list, we only set
PROPAGATE_ANCHORS when propagateAnchors appeared in it. But glyphsLib
propagates anchors before it ever looks at filters, gated only by the
"Propagate Anchors" custom parameter (default true), so any source with
that userData key (e.g. anything produced by ufo2glyphs) silently lost
propagation in fontc while fontmake still propagated.

With this patch, the custom parameter alone decides; a propagateAnchors
filter entry is a no-op, as in glyphsLib.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant