-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Old style nums variant prevents lot of ligatures #561
Comments
Makes sense, but still leaves lots of characters that do change. May I ask what’s your use-case? Why are you turning on both old-style numerals and ligatures? |
Because I like coding with old-style nums (for some reason it helps me read long numbers) and I like this font ligatures! Besides removing features seemed like an easy fix, since most ligatured chars (at least the one I use) do not change. |
FYI I removed (with fontforge I don't have access to glyphs) all |
Would someone be so kind to explain this change for curious simpletons like myself? |
Ligatures are pattern based. E.g. you want to replace
So if your program sees Old-style numbers are implemented the same way:
The problem is that it used to replace not only numbers but some symbols like -, +, <, >, % and so on. If onum substitution happens first ligatures won’t work because character is not different:
This change removes substitutions for everything except the numbers, so both old-style numbers and ligatures can work at the same time. |
Problem
Some characters like
=
(equal
) have an identical onum variant (equal.tosf
). This breaks the ligatures since there are none withequal.tosf
.Exemple
Normal:
With ligatures (default):
With oldstyle nums:
With both:
Suggestion:
Remove the
.tsof
variant for characters that doesn't change with the onum feature to restore default ligatures.Thanks
The text was updated successfully, but these errors were encountered: