L1 Mastering Font checklist

[vv-monsalve]

L1 Mastering Font checklist

Diacritics

• Inspect the font and choose the best version of the diacritics (in terms of balance, weight, size, contrast) and move them to comb mark.
• Adjust left and right sidebearings of all the comb marks to 0 (so that they are easy to edit)
• Ensure the diacritics consistency with the font characteristics + among related marks, see issue of reference.
• Work on the selected diacritics to ensure the balance among all marks (contrast, weight, size, stroke or others)
• Adjust position, weight, or outlines of the diacritics if needed, without changing the design of them, and using glyphs app locked guidelines.
• Decomposed transformed components, review proportions ensuring round coordinates.
• Test the comb marks by inspecting all of them in context (right-click and choose all glyphs using this component).
• Inspect and balance the below marks (size, weight, balance) e.g. ogonek cedilla to avoid huge marks
• Create Catalan Punt Volat
• Delete the legacy marks and add them back so they are made from comb marks.
• 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 in their context)
• Create the Vietnamese diacritics by using a specific anchor (e.g. topviet) so that composite glyphs could be automatically updated
• Make composite glyphs for the entire font.
• Review and adjust the anchors position.

Glyphs & Outlines

• Create the missing glyphs to cover the Latin Core and Plus GF encodings if they are easy to go cases. Otherwise, please report them to the designer in the Design Issue.
• Inspect all the included glyphs has the Upper and Lowercase.
• Ensure the above item by inspecting there are no glyphs with double encodings (Uppers + lowercase)
• Decompose the Currency symbols to avoid inconsistencies when the current components are changed (e.g. hyphen)
• Check, solve or report as needed the currency symbols size, weight, consistency with the font.
• Inspect current kerning and delete the pairs that are not needed or not ideal (e.g. numerals and quotes)
• Check kerning and spacing by using the .txt files. Fix any kerning and spacing critical cases (covering the most common kerning pairs).
• Check spacing and kerning for numerals (main .lf .osf) and use arithmetic -key- spacing for the .lf ones
• Check the spacing of terminal forms to avoid crashes or collisions. Issue of reference
• Check @ ¿? ¡! ”” «» and overall punctuation position and spacing is ok. Use key sidebearings + kerning groups to ensure consistency. Include // kerning.
• Run the automatic Glyphsapp command: Resolve all metrics to update the metrics in the entire font.
• Check everything once again by going glyph by glyph.
• Run the automatic Glyphsapp Update Glyph Info command to avoid bad names issues
• Lining figures based on main ones + spacing + kerning
• Inspect the ligatures coherence with the font.
• Inspect/solve fraction consistency with the fractions. Adjust its sidebearings.

OT Features

• 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.
• Create Lookup for positional alternates for fina and init cases. Luxurious as reference case
• All the features/classes that should be done automatically to be done in that way, e.g. All Letters
• Inspect if Stylistic Sets have the right name (ss01 instead of .001 etc) glyphs and generate the automatic OpenType code.
• Check if there any Stylistic Set should be treated as any other feature, e.g. SmallCaps or osf.
• 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.
• Check the before and after font using gen-html diff if needed (for update font cases)
• 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.