-
Notifications
You must be signed in to change notification settings - Fork 575
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
Add latest updates to repo #544
Comments
Another update has just been uploaded: |
@tay1orjones Here are the specifics: IBM PLEX SERIF V3.1 - 2023-11-27Added
Changed
IBM PLEX SANS ARABIC V1.5 - 2023-10-31Added
Changed
IBM PLEX SANS V3.5 - 2023-09-20Added
Changed
|
@tay1orjones Another update has been completed: [IBM PLEX MONO V2.4] - 2023-12-21Added
Fixed
Changed
|
Where can I look at these updated fonts? The info above says loclBRG has been added now. Thanks. |
@kenmcd these files are not in the repository yet. Question for @vpicone @tay1orjones -- if I would replace existing font files in this repo with updated ones: would that break anything? I know that someone else still needs to build a release. Perhaps there’s a way to have updated files faster on this repo? The last release was seven months ago. |
@tay1orjones Please add this new extension for Traditional Chinese as well: [IBM PLEX SANS TC V1.0] - 2024-01-11Added
|
We'll be working on putting this into a release this week |
This is great news. The IBMers in China will especially be happy in addition to all the IBM.com Chinese pages. |
When will the |
3—4 weeks from now is my best guess if all the final checks and tests go well. |
Any chances the SC version will get to be released with TC since the release is scheduled for this week?
|
@NightFurySL2001 There is no way to release SC with TC. We received files for SC from Sandoll only in January, so we’ll need a few weeks to prepare it for release. We received the files for TC in mid-December weeks ago, so we are releasing them today or early next week. |
Sans v3.5
Arabic v1.5
The text was updated successfully, but these errors were encountered: