Hi, I am trying to export but I keep getting this, which means nothing exports.
I’m using an open source font (Inter).
I’m not sure how to fix it, any help would be appreciated.
Have you cloned the repo so all the .fea files are actually there on your system?
Nope – what does this mean/how would I do this?
What files did you actually open in Glyphs, and how did you get them? Did you download the .glyphspackage files from the Inter repo on Github? Or are you just opening OTF files that you’ve installed on your computer?
I’m using the glyphs package from Github. Though I created a new Instance + master as I wanted to work with a bespoke weight
All the .fea files are also part of the Github repo. There are also various toolchains that you can use to generate fonts; you’re not meant to export the Glyphs packages directly.
I’d recommend going through the contribution readme – that will tell you a lot.
1 Like
Thanks I will have a look. I am making an edited/custom version of Inter (one weight, rather than creating a whole suite of compatible masters).
Are you saying there is no way for me to simply export from Glyphs – I will have to learn Python etc?
If my memory serves correctly, the features in the inter repository are all in one directory, each as .fea files. In the Inter Glyphs file, you will see that the features have a relative file path specified. Glyphs tries to find the fea file at the specified location. If it isn’t there, the import (and subsequent export) will fail.
1 Like
Ah! You are right. I moved my file into the original folder and I don’t get those fea failures anymore!
I do still get the 'Problem compiling GPOS table" (same as a few messages above)
Do you have any knowledge on what that is?
Thanks so much!
Can you try adding a custom parameter in Font Info > Font: Use Extension Kerning (and tick it)
1 Like
Thank you! This worked 