-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Bugfix/revert name change #1439
Conversation
b047d5d
to
2377f60
Compare
Example of how the naming changed in which version, ID16 is the one... v3.0.3
v3.1.0
v3.1.1
Compare with these font where the familynames also differs due to abbreviations:
|
We should have used a better version bump, say v3.2 or something. |
Because it's a bug-fix that corrects the regression(breaking change) made in v3.1.0 from v3.0.0, but also a breaking change (again). I understand fonts are not like softwares where one can easily add some compatibility layers or deprecation warnings, but in my humble opinion, one wouldn't expect significant changes when they update something only by a patch version. Anyway thanks a lot again for correcting the name. |
What is the breaking change? 🤔 The breaking change from 3.0.2 to 3.1.0 was make all fonts use the Edit: Fix typo |
Ah I see this is not correct. The situation seems to be like this: The breaking change from 3.0.2 to 3.1.0 was make all fonts use the The VS2022 bug would be fixed by Why is that only a draft? 🤔 |
Description
Compare discussion in #1434
This effectively reverts #1406 (Issue #1242)
Sorry for the VisualStudio 2022 users, we need to find some other solution and/or do a proper breaking change with anouncement.
Requirements / Checklist
What does this Pull Request (PR) do?
How should this be manually tested?
Any background context you can provide?
What are the relevant tickets (if any)?
Screenshots (if appropriate or helpful)