-
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
Issue with IBM Plex Sans Arabic Font Rendering for Central Kurdish (ckb) #597
Comments
Can you please try with the latest font files from this repository? |
Yes, sure. I'll test and get back to you. |
I couldn't find the Arabic range in the GitHub version of @ibm/plex-sans@1.0.0. The older version from Google Fonts is available online and I have tested it there. Any idea @BoldMonday ? |
Arabic has its dedicated fonts: |
Thank you |
Hi @BoldMonday, Thank you for the updated version link. After testing the latest IBM Plex Sans Arabic font from this release, I’ve encountered the same rendering issues for Central Kurdish (ckb) text. PDF version: Raw Text:
Thank you for your continued support, and I look forward to any potential fixes or guidance on resolving these issues. Best, |
Describe the bug
I have identified a rendering issue with the IBM Plex Sans Arabic font, particularly in its support for Central Kurdish (ckb). Central Kurdish employs the RTL (Right-to-Left) writing system and utilizes Arabic letters. Although the font generally supports Arabic, it presents certain inconsistencies when used for Central Kurdish text.
To Reproduce
Here's the Central Kurdish (ckb) text I used:
Screenshots
NOTE:
In spots where the font switched to Arial for the letter "ت," I added a ZWNJ character to fix it. However, using this character with others causes significant issues. It's commonly used in Persian and occasionally in Central Kurdish, but not very often.
Additional context
I tested the font on various platforms, including browsers (Chrome, Brave Browser, Firefox), MS Word, Gedit, and VS Code, and encountered the same issue consistently.
Last note is that this issue has also been reported on the Google Fonts GitHub repository: google/fonts#7089
The text was updated successfully, but these errors were encountered: