Hello, this is a rather odd issue. I remember running into something similar some years back, but in that case, it was (probably) due to nested components. This time, glyphs like i, ü and : (all component-based) are exhibiting very weird behaviour when printed. The font used is installed as static TTFs. Any idea what could be causing this? Many thanks!
Also, it appears my client is using Word, so please forgive the missing kerning. The font is, in reality, properly kerned
For the moment, I somewhat hotfixed this by adding a Decompose Glyphs custom parameter to all instances and adding all (composite) Glyphs as a value. This increased the file size per instance by ~20kB but at least it works.
I’m afraid to say the export from above is from Glyphs 2. I can personally only test the same file exported from Glyphs 3 on a printer on Monday, but I will happily let you know if the issue persists.
In any case, I’d be very interested to know whether this issue with composites jumping around in print is common, or was, with Glyphs 2, and why it occurs.
I have the same problem.
The dots that are loaded as components in the letters are moved in some printers.
How can I decompose them all when exporting?
It is not destroyed, but you do need to convert RTL kerning, which in Glyphs 3 is now separate from other directions. There is a mekkablue script for the exact purpose.
I tried to fix the kerning with the mekkablue script in G3 but it does not work properly and some of the kerning still on the LTR.
We will have to rebuild all our previous fonts in G3