Add Emery (with another name)

[davelab6]

Font Project Git Repo URL:

https://github.com/googlefonts/emery-3

Super short description of the Font Family:

Christian Mosmüller emailed fonts@ with,

I am writing to submit my font, Emery³, for consideration to be included in the Google Fonts library. Emery³ is a striking, variable Display Font specifically designed for animation on the web, featuring three variable axes.

Feel free to also use my website to check out the font: https://cmosmueller.ndu.schulwebspace.at/varWeb/

As the sole original author of Emery³, I would like to declare that I hold all the necessary rights to license the font under the Open Font License (OFL).

Enclosed in this email is the source file for Emery³ as well as a variable TTF file, which is available for you to take care of everything else. I believe that Emery³ would be a great addition to the already impressive collection of fonts available on the Google Fonts website.

Thank you for considering my submission. I look forward to hearing back from you soon.

I created a Github repo for it, above.

Requirements:

I understand that Google Fonts will publish only fonts that matches its requirements, and I can confirm the project meets them (by ticking the cases, or putting x between the square brackets in text mode):

• [x] The entire font project is licensed under the OFL
• [x] There is no "Reserved Font Name" mention in the OFL license
• [ ] Family name is unique according to namecheck.fontdata.com I asked Christian to propose a new name, as a simple Google search shows existing fonts with the name "Emery"
• [ ] The font supports at least GF Latin Core glyphset (I didn't check this yet.)
• [x] The repository respect the upstream repo structure
• [x] The source files are available in the repository
• [x] I read, agree and comply with the full contributing requirements
• [x] I am the author of the font or the author agreed to this submission
• [x] I will maintain the repository He's asked to do so :)

Image:

[davelab6]

I expect the "length" axis would be onboarded as YTRA, since it effects the Y transparency overall. This will need review of the line-height behaviour with our v metrics policy. @vv-monsalve will investigate that as part of the Playpen onboarding and its "extenders" axis.

[davelab6]

As a large designSpace VF project, I love Emery, and would like to see it onboarded soon, but @vv-monsalve is focued on Playwrite in Q2... and since it has VFB sources I'm reassigning from @vv-monsalve to @yanone for an initial review in Q2 :)

[yanone]

I don't see how the vertical extension axis makes sense. I tried out the font in a browser as well as in Indesign, and neither environments respect the change in vertical metrics that comes as part of the vertically extended masters, see screenshots (with length axis fully extended).

If indeed only a single-line typesetting is intended here it might work, but then again you have the issue that the default weight's v-metrics are applied, so unless the vertical extension is planned-for in the design document, a change in axis parameters might cause the text to crash into visual objects above it.

One possible solution is to apply the vertically extended v-metrics for all masters, leaving an awful lot of white space for the default master, which in turn is very unusual for a font and might leave users confused.

The GF Guide technically allows v-metrics of over 120% of UPM, but I don't see how we can create or offer a meaningful user-experience for such weird metrics. The sum of v-metrics is 3,120 for the extended lengths, so 312% of UPM.

Edit: An automatic adjustment of line-height could be implemented programmatically in a browser alongside a change in axis value, but that doesn't come as part of the default CSS font usage, and static environments like DTP apps won't be supported.

Browser:

Indesign:

[yanone]

Update: I wasn't aware of the proper production process for the YTRA axis and checked the shipped .ttf file rather than producing new fonts using our toolchain.

I will repeat the process again next week and report back.

[yanone]

Sources are unusable as-is with regards to mostly anchor compatibility, double above/below use of components. @davelab6 says to notify author to update sources in line with GF guide (need to cross-check some details). Waiting for contact details, as the website link at the top won't yield any

[yanone]

Emailed author about how to approach improvements. Since assignment by Dave is "initial review", I consider this done for now and we'll see whether the author returns with updated sources.

[chrissimpkins]

Will leave this with Yanone and pick up work on it in September.