Export/vector error with variable fonts

Hi!

My Glyphs file has 3 masters, defined instances with 10 weights (Thin 50, Light 100, … Black 900 - whereby the weights are individually defined) and basically works without any problems.

The following happens when exporting a VF:

With one of 3 “&” between 122.8 and 123.0 there is a gap in InDes and AI.
(It is not visible in FontGauntlet, for example …)

Even more interesting is the following “effect” in InDes:
Top: both “&” default
Center: right “&” selected via “Alternative character display” on the text frame
Bottom: StyleSet activated for the entire frame (incl both “&” )

In my opinion, the vectors are not overly complex or complicated, but they do overlap. As soon as I merge the shapes, everything is fine.

Unfortunately, I cannot understand what is causing the problem. Glyphs listed by the Mecca Blue script “Path Problem Finder” do not show the above-mentioned effect.

What could be the problem?
How can I find other faulty characters without having to test all 1600 glyphs individually?

I would be grateful for any helpful hints!

See if this appears also in FontGoggles. If not: congratulations, you have found (another) InDesign Bug.

Which version of InDesign are you using? The 2023/24 versions were a disaster, 2025 versions are much better, even though Adobe engineers insist on keeping bugs for backwards compatibility and consistency. :woozy_face:

I have now tested the font and the three “&” with FontGoggles. The problem does not occur here. :victory_hand:

So I have found an Adobe bug - yeah! :sparkles:

Fortunately I can prevent it with merged vectors, but I don’t know if the problem occurs with other glyphs or why!
Do you have any additional tips on what I can do to be able to distribute the font with a clear conscience?

Just test as much as you can. :man_shrugging:

I assume that there is a script or plug-in called “Just test as much as you can”, right? :rofl:

(The “long” paths/curves or the overlays in the “&” cannot generally cause problems with VF?)

They shouldn’t.

OK, I’ll do a little more testing … :roll_eyes: