Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design Issue #1

Open
17 tasks done
vv-monsalve opened this issue Oct 26, 2021 · 6 comments
Open
17 tasks done

Design Issue #1

vv-monsalve opened this issue Oct 26, 2021 · 6 comments
Assignees

Comments

@vv-monsalve
Copy link
Contributor

vv-monsalve commented Oct 26, 2021

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
@RobLeuschke
Copy link

This font is ready for review.

@crystaltype
Copy link
Contributor

@vv-monsalve @RobLeuschke
I noticed a lot of uppercase spacing issues for this typeface:
Screen Shot 2021-11-13 at 04 14 53
Screen Shot 2021-11-13 at 04 14 40
Screen Shot 2021-11-13 at 04 14 29
Screen Shot 2021-11-13 at 04 14 15
Screen Shot 2021-11-13 at 04 13 29
Screen Shot 2021-11-13 at 04 13 17
Screen Shot 2021-11-13 at 04 12 33
Screen Shot 2021-11-13 at 04 12 13
Screen Shot 2021-11-13 at 04 06 39
Screen Shot 2021-11-13 at 04 12 01

(Please wait for Viviana's before trying to fix these issues, thanks a lot!)

@vv-monsalve
Copy link
Contributor Author

@crystaltype Thanks for reporting this.

@RobLeuschke While perhaps capitalizing is not the primary intended use for Oooh Baby, given its caps are more roman than really cursive, I think it would be possible even for short expressions. In those cases, the spacing should be functional. Here you can see the Browsers Preview Issue

Screen Shot 2021-11-12 at 17 25 18

I've already updated the source file in DropBox, please look for the pink Uper&Lower case as a hint of it being the latest file, please use that one to review and solve the spacing.

@RobLeuschke
Copy link

I have addressed the issue of capital spacing and kerning. I think the texture of text is working. I am not concerned about being strict with it as it really isn't designed to be used in all caps. Let me know if you still see things that need to be addressed.
image

@RobLeuschke
Copy link

The connectors for this font are not as critical as in other more formal connecting scripts. Having said that, I have addressed those forms that do connect, particularly the 'c' and 'e.'

image

@RobLeuschke
Copy link

@vv-monsalve Please review the file in Dropbox and let me know if there are any other issues that need my attention.
R

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants