Default RobotoFlex not appearing

[dberlow]

No description provided.

[dberlow]

Nice work on this!

[Lorp]

This seems to be issue #1. The commit 2b408fc should have fixed the issue. In RobotoFlex’s case it now forces all samples to opsz 14 (because that’s RobotoFlex’s default opsz), whatever the size in px of the sample.

However RobotoFlex is still out of sync with the other fonts. For example, set XOPQ to 156, XTRA to 390 – which are both within the axis ranges of Amstelvar and RobotoFlex. You’ll observe that RobotoFlex H, specifically the transparent gap between the vertical stems, is clearly narrower than the same gap in Amstelvar and the other fonts.

[Lorp]

Note that ParaSync ignores the font’s axis defaults for the parametric axes in the UI (because the whole point is to set all fonts to identical values). By contrast it sets axes not in the UI to default, and they are not controllable in ParaSync.

[Lorp]

I’m seeing odd XTRA calibration in all the versions of RobotoFlex that I have, with the H glyph consistently too narrow. The following images show RobotoFlex compared with Amstelvar, with XTRA=500 and all user axes at default: first in ParaSync, then in Axis-Praxis. On my understanding, Amstelvar is correct.

[Lorp]

The drag-drop issue #4 is now fixed, so if you can try an up-to-date parametric RobotoFlex, that would be great.

[Lorp]

Raised an issue about the RobotoFlex XTRA calibration here googlefonts/roboto-flex-avar2#64

[Lorp]

Not a ParaSync issue. Follow up about XTRA definition in the RobotoFlex issue above.