-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix fi & ffi glyph widths to match non-ligated sequences; set other ligatures to non-exporting glyphs #431
Comments
I’ve discovered/realized another two issues which I might as well fix at the same time:
Solutions:
|
I made a script (permalink) to quickly check ligature widths vs expected widths. Caveat: this script is somewhat simple, because it doesn’t check for kerning – because Recursive doesn’t have kerning for ff, fi, fl pairs. But, if a font had a similar goal of multiplexing, it might need to check for kerning. Here are the current issues to fix:
|
Okay, so the issue of having a long-running project is that it’s possible to forget certain things. In testing the variable font again, I’ve remembered the the ligature feature is set up so that only the So, I after finishing with basic ligature caret & width fixes, I will set the |
Build issues that I’ve had to resolve:
Traceback (Click to expand)🏗 Constructing variable font 🚚 Generating sources |
Problem description
In Sans Linear Light Italic, the
fi
ligature is a different width thanf + i
(800
vs750
). Forfl
, the width is different fromf + l
across all Sans styles.It is likely that this discrepancy may exist in other ligatures, like
ffl
andffi
. It should be fixes.Expected behavior
Recursive Sans is meant to be superplexed/multiplexed – words should have the exact same width regardless of weight or style. So, a word like "fly" should be exactly the same width whether upright or slanted. Currently, it is just slightly wider when slanted, because the slant axis activates the
fl
ligature.Additional Context
There is already a script to check for widths of glyphs being the same across sources (permalink). I will likely start from this in the ligature check.
The text was updated successfully, but these errors were encountered: