L1 - Design Issues

[vv-monsalve]

Google Fonts Latin Core & Plus coverage

• Design all the glyphs required both in the Latin Core + GF Latin Plus encoding
• Create all the comb marks as mentioned below
• Leave only the compound glyphs (e.g. adblgrave) marked in dark grey as pending to be created using the components

---

Diacritics

• Please ensure the definitive design is adjusted in the combining marks, so they will be ready to create the compound glyphs.
• Once the definitive design is ensured in the comb marks Legacy marks, delete the legacy marks and add them back so they are made using the comb marks as components.
• Diacritics need to be balanced (in weight, size, contrast) and match the style of the typeface design.
• Adjust the vertical position using glyphs app locked guidelines.
• Ensure related marks are consistent between them, e.g. caron and circumflex
• Caron.alt need to have the alternate shape used in Ľ Slovak On page 30 of this document you can find detailed info around the vertical Caron.
• Leave a 0 sidebearings value for the marks

---

Glyphs

• The ampersand and Eng need to be consistent (in size and style) with the font. See RUSerius as reference
• The German Double SS need to be fixed. This article is a good reference
• Currency symbols are related to the overall design and have balanced proportions
• ordfeminine and ordmasculine as well as superior numbers are well proportioned and with a balanced stem thickness. Issue of reference
• fractions and superior numerals have a good proportion + weight. Issue of reference
• Check the ligatures are not wider than the original combination of letters. E.g. fi

---

Spacing

• Inspect the spacing and kerning of the font to ensure it is working properly and most common cases are covered. Issue of reference
• Terminal forms spacing should avoid crashes or collisions. Issue of reference

[RobLeuschke]

This font is ready for review.

[vv-monsalve]

Hi @RobLeuschke,

copyright, registered and trademark symbols are sanserif instead of brush style.
I've just updated the source file in DropBox. Please use it to fix the glyphs.

Thanks

[RobLeuschke]

Hi Vivi, I have replaced the glyphs with brush styles. I have to confess that I am unsure of the size of the ® and TM symbols. I think of them as being smaller at the end of words or images. The © I think of needing to be a size consistent with the numerals. It is the ® that I am unsure about. Should it also be small like the TM or should it be the same size as the ©? If these are the appropriate sizes, then this is done, otherwise, please advise. Thanks, Rob

…

On Thu, Mar 24, 2022 at 10:41 PM Viviana Monsalve ***@***.***> wrote: Hi @RobLeuschke <https://github.com/RobLeuschke>, copyright, registered and trademark symbols are sanserif instead of brush style. I've just updated the source file in DropBox. Please use it to fix the glyphs. Thanks [image: Screen Shot 2022-03-24 at 22 13 49] <https://user-images.githubusercontent.com/48698976/160049818-7fc51bc7-8ba5-43a3-8fda-2b3ba39fa6f6.png> — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANXDGHPQ42KKF53LJLDS4PLVBUYXBANCNFSM5KRTOXBQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[vv-monsalve]

Hi @RobLeuschke,

Thanks for the quick response with this.

I think of them as being smaller at the end of words or images. The © I think of needing to be a size consistent with the numerals.

That would be the logic, although ® tends to be a bit taller than ™. I haven't inspected the new source file yet but I'm sharing here some pictures of examples.

PT Seif

Zapfino

Corinthia Regular (yours :))

There are some cases where they use the same size as copyright for the registered mark, but out of its use it wouldn't say that is the ideal, it looks disproportionate.

macOS System

[vv-monsalve]

Hi @RobLeuschke,

Please let me know if you perform any changes on the symbols after my previous comment. Thanks