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.

Sign up for GitHub

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

Jump to bottom

Design Issues #1

Open
14 tasks done
vv-monsalve opened this issue Sep 1, 2021 · 10 comments
Open
14 tasks done

Design Issues #1

vv-monsalve opened this issue Sep 1, 2021 · 10 comments
Assignees
@RobLeuschke

Comments

@vv-monsalve
Copy link
Contributor

vv-monsalve commented Sep 1, 2021 •
edited by RobLeuschke

Google Fonts Latin Plus coverage

  • Design all the glyphs required in the 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 matching 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
@RobLeuschke
Copy link

MoonDance is complete. Some glyphs still have overlaps.

@vv-monsalve
Copy link
Contributor Author

vv-monsalve commented Oct 11, 2021 •
edited by RobLeuschke

Hi @RobLeuschke, Moon Dance has some spacing & kerning issues:

  • Some common kerning pairs are missing
  • There is a positive kerning between space and many uppercase letters. Please review if either the space is too short or the left sidebearing of the letters needs a higher value.
  • As the uppercase set for MoonDance is more Roman style, they could be used in "All caps". Therefore the spacing among them should be improved.

Weight Issues.

  • Also, the l and o letters seem to be too light and darker respectively. In the o it could be the loop to form the eye.

Please take the latest file at the root of the 'sources' folder in DropBox to inspect the entire font and solve all the cases. Remember you could use the sidebearing arithmetics in glyphs to make it easier and consistent whenever possible.

Screen Shot 2021-10-11 at 10 20 23

Screen Shot 2021-10-11 at 10 20 28

Screen Shot 2021-10-11 at 10 22 12

Screen Shot 2021-10-11 at 10 22 30

Screen Shot 2021-10-11 at 10 41 07

Screen Shot 2021-10-11 at 10 35 35

Screen Shot 2021-10-11 at 10 21 16

Screen Shot 2021-10-11 at 10 21 36

@RobLeuschke
Copy link

RobLeuschke commented Oct 12, 2021 via email

@vv-monsalve
Copy link
Contributor Author

Please let me know your questions

@vv-monsalve vv-monsalve mentioned this issue Oct 15, 2021
Open
18 tasks
@RobLeuschke
Copy link

I have corrected the kerning pairs and made adjustments to some of the letter weights.

@vv-monsalve
Copy link
Contributor Author

Thanks. I'll download the file from DB and let you know if anything else is needed.

@vv-monsalve
Copy link
Contributor Author

vv-monsalve commented Oct 19, 2021 •
edited

Hi @RobLeuschke, the latest source file still have some issues with the spacing and kerning, like unnecessary kerning pairs for things that would be covered systematically by adjusting the spacing before.
E.g. the space between AH should be the same or similar to AF and AK but the latter are tighter.
This is happening due to the AH is being solved through a kerning pair (+40) instead of adjusting the right sidebearing of the A.

You would like to follow the Glyphs tutorial to better grasp how this could be solved, especially making use of the sidebearing arithmetic option.

Screen Shot 2021-10-19 at 18 09 27

@RobLeuschke
Copy link

RobLeuschke commented Oct 19, 2021 via email

@vv-monsalve
Copy link
Contributor Author

(are you familiar with that American phrase?)

Yes, we used to use it a lot here in Colombia. I don't know if it has a particular story though, is there one?.

@vv-monsalve
Copy link
Contributor Author

Hi @RobLeuschke after pulling the latest source file in DropBox (date 24/10/21) the spacing is starting to look better.

  • However, it seems the right sidebearings are looser than the left ones, which is leading to some gaps or inconsistencies (e.g. T, J and V)

Screen Shot 2021-10-25 at 16 31 55

Screen Shot 2021-10-25 at 16 33 16

Screen Shot 2021-10-25 at 16 33 53


- In other cases it is backwards, it is the left one the one that is loose (e.g. `M`)

Screen Shot 2021-10-25 at 16 34 23


- And, given the `A` is a triangular shape, therefore with a bigger withe area around, it can't have the same value as `H`, it is leading to some crashes and gaps with different letters. Please keep in mind that for all the cases the combination with HH and OO as key characters is crucial. The sequence with HH must be solved first and without kerning. Typically, no kerning is expected between any letter and H. Then it goes the sequence with OO which in some particular cases (like AO) could need a small amount of kerning.

Screen Shot 2021-10-25 at 16 32 31

This was referenced Oct 26, 2021
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
This was referenced Nov 23, 2021
Open
Open
Open
Open
This was referenced Nov 23, 2021
Open
Open
Open
Open
Open
Open
Open
Open
This was referenced Dec 22, 2021
Open
Open
Open
Open
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RobLeuschke RobLeuschke

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vv-monsalve @RobLeuschke