You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OT Spec relates stro to OS/2.yStrikeoutPosition:
'stro'
strikeout offset
OS/2.yStrikeoutPosition
So, after looking into the font slightly further, I’m wondering if Samsa is being inaccurate here.
If I use the FontTools Instancer to instance the variable font at wght=200 vs wght=750 (opsz=72 in both), then inspect with TTX, the OS/2.yStrikeoutPosition is different but pretty similar:
<yStrikeoutPosition value="633"/> for wght=200
<yStrikeoutPosition value="615"/> for wght=750
Here’s a variable font that exhibits the issue (it has a limited/trial glyphset, so I can share it here, and folks are welcome to use it for testing purposes / inspecting internal font data:): AT-NameSansVariable.Trial.ttf.zip
Looking at a font in Samsa, I see that one of the font metrics(?) plunges way down around wght=200, and I’m not sure why, or what that value might be:
Screen.Recording.2023-05-29.at.6.19.08.PM.mov
Is there a way to see a label for that within the app?
The text was updated successfully, but these errors were encountered: