-
Notifications
You must be signed in to change notification settings - Fork 573
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
Hebrew kerning is way off on Sketch #343
Comments
Thanks for reporting! Three questions about the kerning issue you're experiencing:
|
Hi, sure thing!
Hope this helps.. |
Thanks, I will pass this through to our Hebrew experts so they can have a look. Can you provide the full technical specifications please? Thx. |
macOS: 10.15.6 I downloaded Plex's version here from github that says v5.1.3 It happens both on the OpenType and TrueType files... |
@BoldMonday Let’s fit into an update schedule. |
@mjabbink We are on it. Update will be ready in a week or two. |
Are there any news? The version I'm seeing is still 5.1.3..? |
@BoldMonday Will this update be ready in the new year? Would be nice to release together with Cyrillic updates. I believe an Arabic update is in the horizon as well but let me know the date for those. |
it's been almost a year, and still not fixed. that's a real bummer. |
@elyran2 I’m pretty certain this is fixed in the upcoming release. It’s been fixed for quit some time but we've been waiting a series of other fixes so we can do one release all at once. |
@BoldMonday Can you give an update on any details. |
@mjabbink we sent IBM updated Hebrew files back in December. The Arabic update was sent to IBM in February. |
I’m not sure why these could not be released in March but Plex Next will release these updates along with Japanese and other improvements for font usage. |
Fixed in Plex Sans Hebrew v1.3 (part of Release v6.0.0). |
Hi, I have the latest version of the font available, and yet the kerning in Hebrew is making this font unusable...
see attached:
are you aware of this issue?
The text was updated successfully, but these errors were encountered: