-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Arabic and Hebrew percent sign display issues under RTL layout #6145
Comments
I wonder what's the logic behind it. The standard doesn't make a difference between languages. There are RTL, LTR, weak, strong and neutral characters. But I haven't seen something like % behaves differently language by language. I've checked other translator tool and the result the same as in Google Translate. So there needs to be something that I/we don't know. Arabic/Hebrew native speakers, please join. 🙂 |
I don't know why there is this difference, maybe it is a special language habit. So I handed over the neutral setting to the user, and reset the neutral in the Hebrew environment. At this time, neutral does not contain %. |
We need some feedback on this issue. Now we mark this as "stale" because there was no activity here for 14 days. Remove the "stale" label or comment else this will be closed in 7 days. |
It seems you are right. I've just approved the PR. |
For Arabic, percentage sign is fixed on the left side of the digit: %10 and for Hebrew, percentage sign is on the right side of digit: 10%. |
Thank you for confirming it. With #6146 we can set a custom list of neutral characters where As PR is merged, I close this issue. |
LVGL version
v9.1.1
What happened?
Both Arabic and Hebrew have RTL layouts. The percent sign in Hebrew is on the right side of the number, and the percent sign in Arabic is on the left side of the number. The RTL layout will force the percent sign to the left side of the number. as follows:
How to reproduce?
lvgl adds a language setting and recognizes the percent sign as LV_BASE_DIR_RTL in Hebrew. Is it possible?
The text was updated successfully, but these errors were encountered: