This only applies to the interpolated instances, not the masters. Everything looks normal inside glyphs.
I suspect this problem was created when a Marc from Google Fonts removed the «Scale to UPM» parameters and scaled the UPM to 1000. Or maybe it has to do with all the metrics custom parameters in the font info dialog?
In any case, this broken version is currently live on Google Fonts, and it has 80+ million serves per week, so I’m really anxious to get it fixed…
Looks like only glyphs that (1) are made from components and (2) are switched into place by the Replace Glyphs custom parameter during export are affected! The same glyphs, which are accessible by stylistic sets in the default Cormorant fonts, look correct there. Does that help you fix the bug?
(Also, does that mean our source files might not be corrupted after all?)
I tried to export the files CormorantRoman.glyphs with the latest version and tested the ‘Medium’ instance. And the result is fine. Can you tell me how you export, what file you are using and what instance your are testing?
It’s for the problem I’ve been telling you about for a while now… if I don’t decompose beforehand, Replace Glyphs will produce stealth errors throughout the font. That’s why the Google Fonts version of Cormorant SC didn’t have an /at sign, for instance. /at.sc contained /at as a component, so when Replace Glyphs overwrote the latter with the former, it broke.
I suppose as a workaround I could just decompose my whole Glyphs file before exporting (and then trash the copy), but that’s hardly a satisfying solution on the long run.
The problem is not with the export. But the file itself is not proper. Scroll through all glyphs in both masters to trigger auto alignment for all layers. You will see a lot of grey cells. Save the file and open it again and it will stay clean.
And wouldn’t it be better to remove the ‘normal’ lowercase from the SC fonts? You can do that if you put a ‘Remove Glyphs’ Parameter. It is applied after the ‘Rename Glyphs’ so it need to get the .sc names.