Skip to content
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

Inconsistent family name between variable upright and variable italic #293

Closed
Erinaaaaaaa opened this issue Aug 19, 2020 · 4 comments
Closed

Comments

@Erinaaaaaaa
Copy link

Windows Font Viewer
(No, the t from ExtraLight is not cropped in the bottom window, but it is present in the Notepad font picker)

The italic variant's family name is JetBrains Mono while the upright variant is named JetBrains Mono Variable, and as such are separated when selecting the font in for example Notepad.

Notepad font picker

OS: Windows 10 v2004, build 19041.388

@philippnurullin
Copy link
Member

Hi, please do not use variable font with non variable. This will lead to bugs.
If you want to use JetBrains Mono you have to choose fors what version is suitable for you. I suggest using non variable. But variable function is essential to your project & you not expecting auto pairing with italics you can go wit it. #270

@Erinaaaaaaa
Copy link
Author

Erinaaaaaaa commented Aug 19, 2020

I raised this issue precisely because I was using the two variable variants:
image

As for day to day use, I switched to non-variable precisely because of this issue. I do not know how to make it clearer to you (with Windows' built in tools) that these were the two variable font files.

That being said, it does match issue 270 as you mentioned, but it should be made more clear.

@Erinaaaaaaa
Copy link
Author

If anything, I can suggest using the family name JetBrains Mono Variable Italic for the variable italic family in order to avoid such issues, just like the variable upright family is called JetBrains Mono Variable, or the non-ligatured version is called JetBrains Mono NL.

@philippnurullin
Copy link
Member

Thanks for names suggestion. This may solve the problem.
Actually i don't remember why i didn't use that strategy. Maybe the were some problems with it or maybe i was tired & stupid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants