-
Notifications
You must be signed in to change notification settings - Fork 17
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
MathGlyph: Variable fonts loose carefully prepared stacked nodes #232
Comments
He Vassil thanks for the proposal! but I think it better to keep the current implementation and add a strict mode. Strict mode would mean it fails whenever two glyphs are different in structure (contour compatibility), component, anchor, guidelines and other glyph attributes must also be compatible (like the current implementation) glyph structures are the same when:
I believe this would also fix your issue. |
WIP, but here's a start 149b1c8
I need to do some more tests. |
Hey, thank you will give it a try right away :) |
Closed by #235 |
Hi
fontMath
team. I am having trouble with a variable font project that uses stacked nodes to keep compatibility across masters. Tracing the root of the problem I have arrived here. I've also heard colleagues complaining about facing similar issues with their projects. Fiddling with the code I think I have found a civilized solution and I am offering it to you.Fix utilizes simple name/tag technique to sort out the newly introduced nodes from
MathGlyphPen
, thus leaving stacked nodes intentionally made by the type designer alone.Problem first referred here: LettError/ufoProcessor#35
I believe my issue is similar to: #127
Please see the attached code: mathGlyph.zip
The text was updated successfully, but these errors were encountered: