I have a font where one glyph causes this export issue.
Is there any way this error could be more specific? Glyph indices? Master at fault? Underlying error?
Based on other topics I’ve read with the same search result I suspect this may be to do with too small segments, but here is a couple of things I find puzzling:
this is a static font export, what does it even try to optimize here, and can I opt out?
the glyph shows as interpolating
direction and start indices are correct
it’s a single path without overlap — why is it even trying to remove any overlap?
when I set Font Info > Other > Font type: Variable it exports? — what even does this setting do, exactly, I couldn’t find it in the Handbook?
Are these corners likely to be the source of my issue? (I have 64 masters… “testing to find out” is going to be tedious…)
There is no overlap removal in variable font exports. Unless you add it as a custom parameter. That is why you don’t get the error there.
In a static font, you can choose not to remove overlaps. Just uncheck the checkbox in the export dialog.
It does a few things more like remove superfluous handles and remove self-intersections. I suspect the tiny curve segments close to the corner (why do you think they are a good idea?) may count as self-intersecting.
With the tiny handles, why though does the removal step fail? I mean, why wouldn’t it just do what it does, then output “mangled fonts” instead if some of the small segments are what causes the issue? You could then inspect where things are off, let’s say if the algorithm removed a node that makes a curve “explode” like you’d expect with a self intersection?
Also not sure why Glyphs would remove short segments if they are there, drawn. I like handrails, not fences, if you get my meaning.
In the Blacks the round part ends at the crossbar, while lighter weights have a straight segment before curving.
While I’m asking… with “Font type: Variable” I am seeing some crazy head table yMin/yMax values. The font is 1000 UPM, winAsc/Desc something like 1025/275 — if I export with “Font type: Default” I get regular looking head yMin/yMax values (within the actual metrics, which are based on extrema found from the master drawings), with “Variable” they jump to over 3000… that doesn’t make sense. What does that setting do, exactly?
Can you show the design? I still don’t get why you need handles. I suspect a cusp curve, i.e. the BCPs switched places (ACBD instead of ABCD). There’s a script called Path Problem Finder that can pick these out.
Different font, same useless error message. I have a trimmed down version of a MM font, added back one master from an older version of the font and then the export fails; without even a glyph name, there’s really not much I can do as a user
v 3.4 (3418)
Is there some place where I can access a better trace of where it’s actually failing? Layer, glyph, step, anything at all?
[deleted screenshot]
No glyphs are shown as “incompatible”, just for the record…
I don’t know… this is still wonky, and very frustrating.
I have Glyphs give me warnings about issues when removing overlap of certain glyphs. Okay, so I go in, for each layer, Path > Remove Overlap; all layers compatible, re-export: Still that glyph is listed as having Remove Overlap issues.
Additionally, there is warnings about component glyphs, but not the components? Like “S” is not listed, but a glyph containing “SS” as components is listed? There is no overlap to remove, so surely the warning has to come from the base glyph, too, only it is not listed. This is just… not good.
yes, of course, this way around.
