generated from googlefonts/googlefonts-project-template-blank
-
Notifications
You must be signed in to change notification settings - Fork 3
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
checking regular #2
Comments
ok. thanks! |
There is a bunch more coming in in a separate source with my initials at the end. So no rush to do anything until then.
|
I put a meeting on for this a.m. if you'd like to discuss. The accents of Amstelvar would be the topic as well as the other changes I commmitted in a separate source ending in "DB" so we can settle the issue it contains and then merge? |
accents and accented glyphs fixed in Roman and Italic default sources. see #3 |
@gferreira2 I think this can be closed :) |
Can this be closed? |
sannorozco
added a commit
that referenced
this issue
May 30, 2024
updating PDF proofs and scripts, etc.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
am commiting AmstelvarA2-Roman_wght400 with
minor edits to optical x locations of marks
Minor edits to overlaps too close to edge of contour that hides it, (parapgrah and @)
please check marks on. dieresisbelowcomb.case
The contours of Phi were too divided. I conbined the "O" shape for easier manipilation with fewer points.
Same with Psi, phi, psi, Ef
nu was off baseline and had overlap in inner vertex removed
Schwacyr was an ipractical counter to work with. Have simplified.
yi made a component, even if dieresis is unique
ustraightstroke made a component, even if stroke is unique
El.bgr composed from Lambda
yu.bgr composed from l, stroke and o
I've reached the stacked accents. We do not plan to create gvars for a glyph like this:
A single set of unstacked accents designed and aligned for Upper and lowercase will be stored. These will be combined a single component at a time.
Like this
It took me a couple of days to straighten this all out in Roboto, and I'd not like to have to do it again, but let me know if this is not something you want to do.
Cheers!
The text was updated successfully, but these errors were encountered: