-
Notifications
You must be signed in to change notification settings - Fork 820
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
Can't enable stylistic set using otf files #530
Comments
I'm not sure but is the "static" relevant here? Like these files don't include the style features? If so which files in the release should I be using? |
This appears to be a limitation in Sublime Text. Unlike Fantasque Sans Mono, The For example, if you change the |
For reference, I have opened a bug on the Sublime Text forum here: https://forum.sublimetext.com/t/font-options-ss01-does-not-work-if-not-in-regular-weight/59633 |
Gotcha, that's really interesting. Hopefully Sublime can fix it! Although knowing them it won't be anytime soon. |
Yeah… that’s my concern :). I’ll probably add the empty features for the next version. Sorry for the trouble! |
No worries, keep up the good work! Love the font. |
How can I enable stylistic set in Windows Terminal? |
@gmr458 I don't believe there is a mechanism to do so at this time. See microsoft/terminal#1790 |
any update to this? no traction on sublime side and cascadia code (as of 2111.01) still does not appear to have the stylistic set enabled for regular, such that the set works for the italic. |
or is it something i can add myself for now? |
Cascadia family version
2106.17
Cascadia family variant(s)
Cascadia Code (the version with ligatures)
Font file format(s)
.otf (static)
Platform
macOS 11.4
Other Software
Sublime Text build 4107
What happened?
I'm using Sublime, where stylistic sets are added like
However this does not work with the included otf files in cascadia code 2106.17. I confirmed this setting does work with a different font that also uses
ss01
(fantasque sans mono).attaching screenshot
The text was updated successfully, but these errors were encountered: