L1 Mastering Font checklist

[vv-monsalve]

L1 Mastering Font checklist

Diacritics

• [x] Inspect the font and choose the best version of the diacritics (in terms of balance, weight, size, contrast) and move them to comb mark.
• [x] Adjust left and right sidebearings of all the comb marks to 0.
• [x] Work on the selected diacritics to ensure the balance among all marks (contrast, weight, size, stroke or others)
• [x] Adjust position, weight, or outlines of the diacritics if needed to, without changing the design of them by using glyphs app locked guidelines.
• [x] Test the comb marks by inspecting all of them in context (right click and choose all glyphs using this component).
• [x] Inspect and balance the below marks (size, weight, balance) e.g. ogonek cedilla to avoid huge marks
• [x] Delete the legacy marks and add them back so they are made from comb marks.
• [x] Create comb.case marks by making them less tall and less narrow while keeping them at the same weight. (Preferable at the height they are intended to use, to be able to inspect them at their context)
• [x] Create the Vietnamese mark.
• [x] Make component glyphs for all of the font.
• [x] Adjust the anchor position.
• [x] Run the automatic glyphsapp command: update gyph info

Glyphs & Outlines

• [x] Create the missing glyphs needed
• [x] Run the automatic glyphsapp command: Add extremes, Correct outlines direction, Remove PS Hint.
• [x] Check kerning and spacing by using the txt files. Fix any kerning and spacing errors if needed for the most common kerning pairs.
• [x] Run the automatic glyphsapp command: Resolve all metrics to update the metrics in all the font.
• [x] Check everything once again by going glyph by glyph.
• [x] Run the automatic glyphsapp Update Glyph Info command to avoid bad names issues
• [x] Run the automatic glyphsapp Convert to cubic command to avoid qcurves

OT Features

• [x] Check OpenType features and see if all listed are valid, e.g. if .fina glyphs are actually ending shapes or ss are not repeated under different names.
• [x] Inspect if Stylistic Sets have the right name or rename .001 etc... glyphs and generate the automatic OpenType code.
• [x] Check if there is a stylistic set that would correspond to SmallCaps feature instead and change it.
• [x] Check if the OpenType code has any error.
• [ ] Hit the update & compile buttons to check everything is working well.

Testing changes

• [ ] Inspect the font created by the CI GHA to check production errors. If the action isn't included yet in the repo, export and test the font using Glyphs.
• [x] Check the before and after font using gen-html diff if needed (for update font cases)
• [x] Check the font on gen-html proof to see if it's working well on web. Use the --imgs flag to produce images.
• [ ] Commit and make PR using images.

[crystaltype]

@vv-monsalve I'm trying to get all of the stylistic sets of this font to be functional. I found scripts

to automate this procedure but I'm not sure if we should use them. I would love to hear your opinion about this!

[vv-monsalve]

@crystaltype. If those are Mekablue scripts, I haven't used them to create the features. I've been adding the calt feature following the tutorial in Glyphs, as I prefer to rule and understand the process before trying any automated solution that sometimes leads to more issues (remember the spacing/kerning we once had in another project).

You would like to save your files before trying them and create a branch to use the scripts and test the font functioning in Indesign. If everything works as intended, only then to merge it to the master branch

[vv-monsalve]

@crystaltype I've implemented the positional alternate fina in a different way, instead of calt so that it wouldn't be activated by default. Please have a look at Comforter Brush for reference

[crystaltype]

Hello @vv-monsalve I've tried to make stylistic sets work as contextual alternates, but I don't think that this behavior is desired. Please see the below video for context: https://user-images.githubusercontent.com/20129845/135559811-9adba29b-1edf-4dbf-b95b-d6f83d5088ba.mp4

Do you have any idea how should we deal with all the stylistic sets in this font?

I also created the Fina and Init features to only function when the user enables it.