Yanone

Emery Cubic https://github.com/google/fonts/issues/6124 needs this axis to be registered

@vv-monsalve I updated Emery Cubic to conform to the axis registry for both YEXT and SHRP axes (0-100 instead of 1-1000)

@aminabedi68 We just internally discussed this axis proposal again, and found that the behaviour of both your fonts’ Kashida axis is actually almost identical to how the width axis would...

@aminabedi68 What’s your opinion about the [GEXT](https://github.com/microsoft/OpenTypeDesignVariationAxisTags/blob/master/Proposals/Glyph_Extension_Axis/ProposalSummary.md) axis that @moyogo mentioned early on here? It was proposed by an Arabic type designer for the sole purpose of accommodating Kashidas, while...

> So, first I'm curious as to what people think the longest possible kashida is? My WIP typeface has a Kashida width of 0 to 5000 font units (2500 units...

I don't want to impose myself too much here because a font-level `jstf` axis (or even table) is really not my area of expertise, but I want to outline how...

I'm happy with the name, but not the units, as has already been acknowledged, so I don't know what to say now. With the axis using font units, I can...

I think all width-related adjustments should be counted in font units. You also don't apply tracking as a percentage of the font’s widest sidebearing.

@vv-monsalve asked me to review all the axes proposals aimed at Bitcount, and this goes for all of them: The only thing I'm confused about are the units proposed. In...

-100 is good. Reverse contrast is definitely a thing :) Would a third fallback needed called "Reversed" for -100?