Design Issue

[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

---

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

[vv-monsalve]

Hi @RobLeuschke, how are you coming along with Love Light?

[RobLeuschke]

All issues of this font have been addressed and it is ready for review/production.

[vv-monsalve]

Hi @RobLeuschke, Oslash in Love Light needs to be adjusted.
I've updated the Source file in DropBox, please take it to make the change.

[vv-monsalve]

Hi @RobLeuschke, have you changed the oslash for Love Light? Please let me know as soon as you have updated the latest file in DropBox to go ahead with the publishing process.

[RobLeuschke]

The Oslash has been updated to better reflect the character of the O.

[vv-monsalve]

I've just downloaded the latest file in DropBox and the Oslash is still the old one. Please ensure su have uploaded the latest version of the file.

[RobLeuschke]

I updated it. It's intentionally not got the heart embellishment, but the same shape as the O. With the embellishments in the O's, the new Oslash has removed the embellishment to make it obviously a slash in the form. Rob

…

On Fri, Nov 26, 2021 at 8:18 PM Viviana Monsalve ***@***.***> wrote: I've just downloaded the latest file in DropBox and the Oslash is still the old one. Please ensure su have uploaded the latest version of the file. [image: Screen Shot 2021-11-26 at 21 12 58] <https://user-images.githubusercontent.com/48698976/143665054-91f40236-5af5-4441-aa1f-5af98b3269d0.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANXDGHNLTYSFI3DYVTM4PM3UOA5Y5ANCNFSM5GYHDQFQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.