-
-
Notifications
You must be signed in to change notification settings - Fork 800
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
[Draft] Add font objects #4093
base: main
Are you sure you want to change the base?
[Draft] Add font objects #4093
Conversation
In my opinion yes. These features are fundamentally tied to each specific font. |
Would that only apply to |
All of them. But Laurenz may have a different opinion. |
I have a feeling that it'd still be nice to be able to configure those independently of the font (while also offering the possibility of having per-font configuration). |
"But Laurenz may have a different opinion." |
Yeah! Just wanted to share mine too :)
Sure, but how could we implement those shared properties other than through the current design? |
Right now, I have font-specific features always take precedence over features set in |
I left a few comments in the Fonts forge on Discord. |
23e0a90
to
331f147
Compare
2564f83
to
4f2f785
Compare
7fc8a1f
to
99d80f8
Compare
99d80f8
to
82ff728
Compare
See #3488 and #3331.
font
type (implicitly convertible from string)font
OpenType features – will be a lot more complicated becausetext::features
assumes that text will use the same OpenType features regardless of which font is selected.font
Unicode rangesUnresolved questions:
text
?