Open RosaWagner opened 1 year ago
I'm seeing this also in another project. I wonder if Glyphs perhaps ignores layers with duplicate locations?
Perhaps glyphsLib is correct in choking on this ambiguous data, though. But if Glyphs itself can resolve it, then glyphsLib should perhaps also do that.
if Glyphs itself can resolve it, then glyphsLib should perhaps also do that.
the question is how does Glyphs.app resolve these duplicate locations, if at all?
Glyphs just picks the first layer it finds for each location.
But the setup with a "Width" and "Short" axis doesn’t make much sense for me.
@schriftgestalt what would make sense to you so we can fix and export?
repo: https://github.com/Alexandre-Bassi/ChaumontScript