Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support *origin special anchor #997

Open
anthrotype opened this issue Apr 11, 2024 · 0 comments
Open

Support *origin special anchor #997

anthrotype opened this issue Apr 11, 2024 · 0 comments

Comments

@anthrotype
Copy link
Member

While working on googlefonts/fontc#769, we realised that glyphsLib (and hence fontmake) currently don't handle the *origin anchors.

These are sometimes used for glyphs that are used as components in other composite glyphs. The positon of this specially named *origin anchor becomes the new glyph origin, meaning that the entire glyph gets shifted (all its point coordinates and components and anchors are subtracted by the *origin offset). Composite glyphs using these as components and which do NOT use the component automatic alignement feature will also be influenced by the presence of this special anchor, ie. the component whose base glyph contains the *origin anchor gets shifted accordingly (not because the component transform changed, but because the base glyph itself moves to the new origin).
This special anchor also influences the anchor propagation algorithm, because composites would inherit the anchors from the components with the *origin anchor offset already applied.

@schriftgestalt schriftgestalt changed the title Support *origin special achor Support *origin special anchor May 17, 2024
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

No branches or pull requests

1 participant