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

---

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, I'm creating the Design Issue just to confirm everything was covered in the file.

[RobLeuschke]

This is ready!

[vv-monsalve]

Hi @RobLeuschke, Alumni Sans Inline is technically ready to go. However, after creating some proof images the inline effect is barely visible even at 36pt. What is the intended point size of use for it? Would you like to make any changes to it?

OS X High Sierra Safari_11

Windows 10 Chrome_71

Windows 10 Edge_18

[RobLeuschke]

Vivi, I am a bit under the weather (American colloquialism for "I am not feeling well") with a bad cold, so I haven't been working lately. Did you see my question about separating American Calligraphic Titling from the Pro version? As for the Alumni Pinstripe version.... it is really a display font to be used at large sizes for print or used at extremely large sizes on the web. So, no, I don't wish to make any changes. Thanks, Rob

…

On Tue, Dec 7, 2021 at 12:28 PM Viviana Monsalve ***@***.***> wrote: Hi @RobLeuschke <https://github.com/RobLeuschke>, Alumni Sans Inline is technically ready to go. However, after creating some proof images the inline effect is barely visible even at 36pt. What is the intended point size of use for it? Would you like to make any changes to it? *OS X High Sierra Safari_11* [image: Desktop_OS_X_High_Sierra_safari_11 1_] <https://user-images.githubusercontent.com/48698976/145085490-65b8c0e4-4ef5-4d98-a92f-9035e9ede9fc.png> *Windows 10 Chrome_71* [image: Desktop_Windows_10_chrome_71 0_] <https://user-images.githubusercontent.com/48698976/145085503-2bd33dc7-9e87-4e82-a655-f2c342311b9d.png> *Windows 10 Edge_18* [image: Desktop_Windows_10_edge_18 0_] <https://user-images.githubusercontent.com/48698976/145085509-e549b059-e984-4aae-958d-610a7e1f1dfa.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/ANXDGHLBKY5DTJ3IN65WVWDUPZG3LANCNFSM5ISKYWHQ> . 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>.

[vv-monsalve]

I am a bit under the weather (American colloquialism for "I am not feeling
well") with a bad cold, so I haven't been working lately.

Sorry to hear that. I'm feeling the same here, but trying to get the Batch 4 finished this year.

Did you see my question about separating American Calligraphic Titling from the Pro version?

I haven't been able to inspect this yet as we are focused now on solving all the related issues for the Alumni set of sibling families, as the priority now is to finish and publish Batch 4.
I'll inspect that as soon as we move ahead with the Alumni Cases.

Pinstripe version.... it is really a display font to be used at large sizes
for print or used at extremely large sizes on the web. So, no, I don't wish
to make any changes.

The question was about the Inline version. As you can see in the preview images above the effect is not going to be visible in Safari even at sizes like 36 pt, so probably it wouldn't be noticeable in the preview sample in the Google Fonts Catalog.
Perhaps we should validate this with @davelab6

[RobLeuschke]

I said Pinstripe, but I was referring to the Inline. Sorry. R That's what happens when you don't feel good.

…

On Wed, Dec 8, 2021 at 8:34 AM Viviana Monsalve ***@***.***> wrote: I am a bit under the weather (American colloquialism for "I am not feeling well") with a bad cold, so I haven't been working lately. Sorry to hear that. I'm feeling the same here, but trying to get the Batch 4 finished this year. Did you see my question about separating American Calligraphic Titling from the Pro version? I haven't been able to inspect this yet as we are focused now on solving all the related issues for the Alumni set of sibling families, as the priority now is to finish and publish Batch 4. I'll inspect that as soon as we move ahead with the Alumni Cases. Pinstripe version.... it is really a display font to be used at large sizes for print or used at extremely large sizes on the web. So, no, I don't wish to make any changes. The question was about the Inline version. As you can see in the preview images above the effect is not going to be visible in Safari even at sizes like 36 pt, so probably it wouldn't be noticeable in the preview sample in the Google Fonts Catalog. Perhaps we should validate this with @davelab6 <https://github.com/davelab6> — 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/ANXDGHP6MZVKAKYE7UBFM3LUP5UIHANCNFSM5ISKYWHQ> . 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>.

[davelab6]

The catalog design will evolve over time, so I'm OK for this to move ahead, but the description should tell users what is going on. Eg, "This typeface is designed to be used above 32pt in print (assuming 300 dpi) and above 64px in digital media."