-
Notifications
You must be signed in to change notification settings - Fork 814
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
[Question] How can I use only light and light italic by default in vscode? #500
Comments
Ok, two things. One is that you should use the PR that I submitted last week as that has necessary improvements to the name table (it should be pushed to main this week). Two, it appears you’re trying to use the Variable font version of the fonts. So either you will need to set the font weight in VSCode to a lighter weight (say, 300), or switch to the stat instances (which the name table fix should help with). |
Hi, thanks for your quickly reply :-)
I have installed from this source. (I believe the code lays here: https://github.com/aaronbell/cascadia-code/tree/work)
Here is the screenshort when no setting lighter weight: Here you can see that I'm using the source code from your PR (the italic font shape has changed.) Here is another screenshort when setting lighter weight (everything goes into italic again): Oh, by the way, may I ask what's the meaning of |
Can you zip up all of the fonts that you’re generating And attach them here so I can take a look at what might be going on? As for |
Sure, here is the file. |
Hi, sorry for the delay in getting back to you. Finally had a chance to take a look at the files you sent over and, honestly, I don't see anything wrong with them. I suspect that the issue might end up being something related to font conflicts in your font cache. I'd suggest removing all Cascadia Code fonts from your system, restarting, then reinstalling. Also, potentially clear the font cache. Sorry for the trouble! |
I am seeing similar behavior with the latest release. If I set Plot twist: Setting the font weight to anything other than 300 works fine. It's only 300 that makes everything italic. |
@spaceaardvark Hi, would you please try to use the ttf I upload from here can solve your issue? I have tried it again @aaronbell , it seems that it works on my windows machine, but failed in Mac machine, After tried to clear cache, the problem still exists too.
Oh, I got the same behavior too. |
@WindSoilder that doesn't fix the problem. |
Hi! Please try the new release and let me know if it resolves your issues. Thanks! https://github.com/microsoft/cascadia-code/releases/tag/v2106.17 |
Yeah, I'm using Mac, I have tried both |
Out of interest, can you provide a bit more information about the system / VS Code version that you're using? I feel like this is likely a platform-specific issue but want to make sure. |
System version: Vscode about information:
|
hmmmm. For fun, what happens if you set the font weight to 301. |
Another thing I'd be interested for you to test out. Can you visit this site: https://vscode-web-test-playground.azurewebsites.net/ (ideally in Chrome) Click the triple lines in the upper left
Does the issue repro there as well? |
Good news bad news time! Good news: This issue is isolated to Big Sur, it seems I will need to investigate further tomorrow. |
Thanks !.! I have checked the new build ttf in your pr, and it works! |
Oh, by the way , I found that |
:/ |
## Summary of the Pull Request This includes two fixes: - [x] Closes #500 Changes the build process to use gftools.stat instead of statmake. The issue was caused by an 'unused' italic axis in the fonts, which has been removed, but statmake gets unhappy without it there. So the process has been adjusted to a more amenable build library. - [x] Closes #552 Adds the Hebrew language tag to the Regular to ensure that Hebrew positioning works correctly. Also: Adjusts calt feature to ensure LIG substitutions properly function under rare conditions where the `ignore` activate incorrectly. I thought this had already been PR'd but seems not. For example: `===]` First = becomes "equal_equal.liga", and ignore would activate on second =, blocking LIG from being substituted. If the liga form appears, LIG should appear. Turned back on the =>> =<<, etc. ligatures as there is a glyph for them now.
I have tried to build my self based on main branch, and I just allow
CascadiaMono-Roman_Light
andCascadiaMono-Italic_Light-Italic
font in my font setting.But I have issue to make use of them in vscode, all fonts in vscode is italic..
If I enable
CascadiaMono-Roman
andCascadiaMono-Italic
, this issue disappeared... But the weight is too high for me, so I just want to use a lighter version..The text was updated successfully, but these errors were encountered: