-
Notifications
You must be signed in to change notification settings - Fork 115
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
Is there a way to handle Fira Code's style variants? (e.g. ss02, ss03, zero, etc.) #88
Comments
For the former, if they're published as different font files, you can probably just replace the one it uses as input to the patcher wth the variant you want. If they're all different styles embedded in the same font...I have no idea. For the latter, I can investigate when I'm updating to a more recent Fira, but time to work on this has been short lately. |
The way it basically works is you can replace "liga" with the alternate set you want.
Turn it into:
This gives your fonts the alternate >= symbol when Visual Legends: https://github.com/tonsky/FiraCode/blob/master/extras/stylistic_sets.png This isn't really porting the styles over tho, it's just selecting which style you want frozen onto the output fonts. |
That seems like a decent workaround if you know up front what variants you want; I don't know enough about fonts to know how to make them runtime-selectable, though. |
@Cons-Cat this makes sense, thank you - but what about The ligatures.py script you referenced seems to only cover ligatures ( |
I'd like to be able to specify that I copy from Fira Code, for example, the versions of
≤
and≥
which have a horizontal bar instead of an angular bar, which is what I get now.There's also something new in Fira Code that turns the
x
in a hexadecimal number like0xFF
into a raised×
, like0×FF
. I don't know if that's done using sixteen different ligatures, from0x0
through0xF
, or by some other font trick, but it would be great to be able to copy that feature into other fonts as well.The text was updated successfully, but these errors were encountered: