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.

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 :)

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:

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.

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

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.

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

The font is in proof-of-concept-complete stage, meaning that the YEXT vertical metric interpolation works. Meanwhile, the YEXT PR over at the axisregistry has been merged in preparation for Emery Cubic.

I recently fixed loads of outline interpolation issues after the conversion from Fontlab sources, and asked the author on October 15th by email to add a few missing glyphs as well correct the metrics of the tabular figures (or alternatively delete them).

If he doesn't respond in a while, I can also make the necessary changes myself which shouldn't take more than a few hours, so either way I expect that I can hand in the fonts at the end of Q4.

Fixed remaining outline and glyph issues myself after author responded he only work on Windows (= no Glyphs.app).

Now waiting for a description text from author for onboarding.