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.
• Work on the selected diacritics to ensure the balance among all marks (contrast, weight, size, stroke or others)
• Ensure the consistence among related marks, see issue of reference.
• Adjust position, weight, or outlines of the diacritics if needed to, 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 mark.
• Make compound glyphs for the entire font.
• Adjust the anchor position.
• Run the automatic Glyphsapp command: update glyph info.

Glyphs & Outlines

• Create the missing glyphs needed.
• Run the automatic Glyphsapp commands: Add extremes; cubic curves; correct outlines direction; tidy up paths; round coordinates; remove PS Hint
• Check kerning and spacing by using the txt files. Fix any kerning and spacing errors if needed for the most common kerning pairs.
• Check terminal forms spacing avoids crashes or collisions. Issue of reference
• 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
• Run the automatic Glyphsapp Convert to cubic command to avoid qcurves
• @ ¿? ¡! ”” «» position, spacing is good
• Lining figures based of main ones + spacing + kerning

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
• Inspect if Stylistic Sets have the right name or rename .001 etc... glyphs and generate the automatic OpenType code.
• Check if there is a stylistic set that would correspond to SmallCaps feature instead and change it.
• 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.

[vv-monsalve]

Hi @RobLeuschke, We've created a separate repo for Luxurious Roman.

Please use the latest file Luxurious-Roman.glyphs that I've just uploaded in DropBox to check the design issues checklist for it.

There are some issues already found.

• M height does not match the uppercase height.

• second glyph is missing and minute needs to be adjusted.

• Thorn not matching with related glyphs

• Superior numerals need to be balanced in weight

• Ideally, outlines to be improved deleting many extra/unnecessary nodes (e.g. it has been done in c)

[vv-monsalve]

Also, would you please provide information for this font Description file?
Thanks

[RobLeuschke]

@vv-monsalve I have completed the modifications of the forms of this font and created a preliminary exercise of the spacing and kerning. Nodes have been simplified in most (if not all) characters. Please review this font before moving on to production.

[vv-monsalve]

Hi @RobLeuschke. I'll check the current file in DropBox and let you know.

[vv-monsalve]

@crystaltype After merging the latest PR with the Mastering job, the anchor position for n was not ok in Luxurious.
Please remember what we've talked about the counter and the anchor position relationship.