I’ve noticed a somewhat bad issue a couple of times in the past week or so, and wanted to let you know about it.
I’m working with .glyphspackage files, which I really appreciate for use with Git. This problem doesn’t occur with normal .glyphs files, but only because I can’t get those to accept background updates at all (which also seems like an issue, but not something I’m focussed on at the moment).
I’m working in Glyphs 3.4 (3402) (cutting edge releases).
Here’s a minimal reproduction of the issue…
The setup
My /quoteright uses the /quoteleft as a component, rotated by 180 degrees
Where the error occurs
If I change anything outside of GlyphsApp (e.g. the version number, or in this test case, the family name), while the font is still open in the app, the app gives me the opportunity to update the font:
The problem
After the update, any components that are rotated end up badly shifted downwards:
The shifted components really are shifted, and if I build a font from this, the problem ends up in the font.
Here’s a zip of the font itself, which you can feel free to use however (it’s only an /H and some quotes):
TEST-font-250317.glyphspackage.zip (25.3 KB)
This issue has also occurred in larger, much more final fonts, which would have been pretty embarrassing if the glitch hadn’t been caught before publication.
My general build bumps the minor version number of fonts during build, including in the Glyphs sources, so if those files are also open in Glyphs during the build, this can happen. Obviously, if this is something that can’t reasonably be fixed in the app, I can change my build approach or just avoid rotating components. Still, this kind of issue could also strike if a team were collaborating on a glyphspackage project via Git and wasn’t being paranoid about component rotation, so it would be great to see resolved.
PS: Thanks, as always, for the software! I really appreciate how great it is to work in Glyphs and how excellent you are at patching bugs like this. Please let me know if any further info would be helpful here, or if it seems the problem is something only on my end.