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

6.1.0: IBM Plex Serif TTF styles are all wrong #469

Closed
codeman38 opened this issue Aug 17, 2022 · 7 comments · Fixed by #475
Closed

6.1.0: IBM Plex Serif TTF styles are all wrong #469

codeman38 opened this issue Aug 17, 2022 · 7 comments · Fixed by #475

Comments

@codeman38
Copy link

Something seems to have gotten scrambled with the font styles in IBM-Plex-Serif/fonts/complete/ttf as of v6.1.0 - none of the fonts are the correct style that corresponds to their name. For instance, the font named "IBM Plex Serif Bold" is actually thin and italicized, while "IBM Plex Serif Thin Italic" is bold.

This issue doesn't exist in the OpenType fonts, only in the TrueType ones.

@tay1orjones
Copy link
Member

@codeman38 Thanks for reporting, we'll look into it. cc @BoldMonday

@tay1orjones
Copy link
Member

Can confirm I see the same

image

@tay1orjones
Copy link
Member

We'll work on getting a fix out. For now if you need to use TTF you'll need to revert back to v6.0.2.

@kenmcd
Copy link

kenmcd commented Aug 17, 2022

Note: it also affects the Web fonts.

@BoldMonday
Copy link
Collaborator

@tay1orjones The files in question have been fixed and replaced in Box.

@tkapias
Copy link

tkapias commented Sep 7, 2022

I have the same problems for Serif , but, in OTF too, and in v6.02 too.

image

@tkapias
Copy link

tkapias commented Sep 7, 2022

Sorry, I was wrong in the last message.

Only v6.1 is concerned.

Gnome Font-viewer display characters with version in cache locally and not the one that the program opened, it's stupid, I got it after checking in FontForge.

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

Successfully merging a pull request may close this issue.

5 participants