Skip to content
This repository has been archived by the owner on Jul 24, 2023. It is now read-only.

Design Issues #1

Open
15 of 18 tasks
vv-monsalve opened this issue Dec 22, 2021 · 4 comments
Open
15 of 18 tasks

Design Issues #1

vv-monsalve opened this issue Dec 22, 2021 · 4 comments
Assignees

Comments

@vv-monsalve
Copy link
Contributor

vv-monsalve commented Dec 22, 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
  • 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
Copy link

This font is ready for review.

@vv-monsalve
Copy link
Contributor Author

vv-monsalve commented Apr 6, 2022

Hi @RobLeuschke,

Please use the latest source file in DropBox Splash.glyphs to review and solve the following in Splash

  • The cedilla mark is the wrong way around. Please take the latest source in DropBox to adjust it.

Screen Shot 2022-04-05 at 22 56 06

Screen Shot 2022-04-05 at 22 56 58

  • Please adjust the size and position of the © ® ™ symbols as talked for Water Brush

Screen Shot 2022-04-05 at 22 55 41

  • Would you please provide an image with an example of the intended use of the current 'swash' shapes in the font?

Screen Shot 2022-04-05 at 18 41 15

@RobLeuschke
Copy link

I have corrected the cedilla and the © symbol. I think the ® and ™ can remain as is. I have also updated the Splash.png image to include a Swash. The SWSH glyphs are simple embellishments that can be used as underlines in display words.

@vv-monsalve
Copy link
Contributor Author

vv-monsalve commented Apr 7, 2022

Thanks, Rob. I'll download the latest source file from DropBox and let you know if something else is needed.

The SWSH glyphs are simple embellishments that can be used as underlines in display words.

In that case, they should be accessed as ornaments instead of swash ;-)

I'll take care of that in the source file.

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

No branches or pull requests

2 participants