During development to prevent font cache issues and to make it easy to compare versions, I have set up a my instances to use “My Font Name {{{version}}}” as the localised family name. This shows up nicely in the Exports tab, but when I export the instances - or a variable font - the localised family name is “My Font Name version”, not the expected “My Font Name 0.864”.
What version of Glyphs do you have? I just tried it in the latest version and it did work. Could you show a screenshot of your setup? Or send a sample font?
Sure, will send a DM with coordinates in the not too distant future.
Here’s where I see the problem: trying to install the next version alongside the previous one in Font Book:
To be clear: this is a variable font with four instances in it.
This is the setup:
etc. etc.
Thanks for the file. I fixed the problem.
What is the reason that the font is split into so many families? I would put the “Regular”, “Narrow”, “Caption” and “Display” into the style name and put them all into the same family.
That’s to appease apps like Word and Pages - I’m exporting four instances of each sub family: regular, bold, italic, bold italic. All ears if there is a better way to do this - but to be frank this is what users expect too, really!
I guess my wish-list for Glyphs features would be the ability to have multiple VF exports that not only can filter masters, but also instances. I want to always export the caption and display masters so that opsz works (even though Word and friends don’t support that…) but not the instances.
Word will get the families grouped by four automatically. And Pages can deal with larger families like this just fine. You might need to play around with the style linking but I would not overdo this. More details: Naming | Glyphs
I followed that tutorial literally, but it didn’t work for me - word for mac just lumped them all together - and it didn’t respect the style linking at all well. Pages faired no better!
I also think it is more in line with user expectations to have separate font files for some of the axis variations - condensed and wide in particular.
Would you mind sending me the exported font files? Then I can have a look why that didn’t work. It really should.
For finding issues, I highly recommend dropping your files onto Fontspector. That’ll show you all kinds of errors (look out for those pertaining to naming and style linking especially).