Skip to content
This repository was archived by the owner on Sep 8, 2023. It is now read-only.

Update Spec/README for Zero Origin naming tip (followup PR) #98

Open
felipesanches wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Spec/README for Zero Origin naming tip (followup PR) #98

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions Spec/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -306,6 +306,16 @@ A variable font is simply a static font which has some additional tables FVAR, G

Often font developers are unaware what the font origin is within their fonts. They'll then complain that fontbakery is failing many checks. It is recommended that font developers read the [Microsoft OpenType Font Variations Overview](https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview) to better understand how a variable font works.

For example, your `nameID 1` string should match the name of the Master used for the `glyf` table outlines.
If this is not what you want, you can choose another master to be used instead.
In GlyphsApp, do this 'implicitly' by going to Font Info, Masters (second tab), and move your preferred master to the first position in the list.
Typically this is a Regular, but if you don't have a Regular master, use the closest;
eg, a opsz-min wght-min such as `14pt Light`.

Or, if you want to keep the order, then go to Font Info, Font (first tab), and add a Custom Parameter `Variable Font Origin` and give it the name of the master you want to be used.

You should also always set a font-level Custom Parameter, `Variable Font Family Name`, and add your family name there, without any style particles. Eg, `Merriweather`.


### New vs Pre-existing

Expand Down