3 Bugs that won't let me export

Glyphs
1

Hey Guys,

Hope you have a great start of the year. I’m sending 3 bugs that appeared in version 3.5 and don’t let me export, or change glyphs just for updating to the latest version.

All of this didn’t happen in version 3.2.

  1. If I have a glyph “Oslash” with bracket layers to switch shapes, and the component “O” has an intermediate, then it won’t let me export the font. This worked fine in version 3.2. Images below:

Glyph with bracket layers to switch shapes:

Screenshot 2026-02-04 at 12.28.43 PM
Screenshot 2026-02-04 at 12.28.43 PM1024×842 95 KB

Original “O” with intermediate:

Screenshot 2026-02-04 at 12.28.56 PM
Screenshot 2026-02-04 at 12.28.56 PM1506×854 94.5 KB

  1. I use a special glyph “f.1” and add it as a component for creating ligatures. I don’t export that glyph (because I don’t want it to be in the glyphs tab in Illustrator). In version 3.2 I could export the font without a problem. Now, it doesn’t let me export with “f.1” not having the “export” option.

  2. If I have a smart component that is extrapolating (say I have max weight 900 and the smart component is 1000), AND which main glyph is a path+component or component+component. It will show it light, instead of bold. In version 3.2 it worked. Images attached:

In Glyphs 3.5:

image
image1970×1560 218 KB

In Glyphs 3.2:

image
image1946×1568 213 KB

What I’m doing now is having the two versions installed 3.2 (just for exporting) and 3.5 (to work).

Hope that you can include these fixes in the next build.

Thanks for your hard work! :black_heart:

2

Can you send me a font that shows all the mentioned problems? (you can remove all glyphs that are not relevant.)

1 Like
3

Bug01.glyphs (684.4 KB)

I couldn’t replicate bug #2, when I erase several glyphs it’s no longer an issue.
I can share the complete fonts privately if you want.

Thanks Georg :folded_hands:t2:

4

Thanks for the file. You can send the full font in a private message in the forum.

1 Like
5
  1. I see what I can do.
  2. Was a bug. I fixed it.
  3. needs more time to fix. The problem is the nested smart components. But you can quite easily circumvent the problem. Build a set of superior accents and then build the Aacutesuperior from Asuperior + acutesuperior (enable alignment for the accent).
    (I would use the .sups suffix. That is easier to read and makes it clearer that the glyphs have no unicode; the superior suffix is used for encoded glyphs).
1 Like
6

I’ll use version 3.2 to export for now.
Let me know if I can help you test any of these.

Thanks Georg! :folded_hands:t2:

Fer.