-
Notifications
You must be signed in to change notification settings - Fork 32
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
Translation of numbers (in forced translation) #1
Comments
I could add a special case for Roman Numerals |
Good suggestion at the end of your comment! Having a toggle for not translating roman numerals would be handy too, as screen space is limited. For other number systems, such as in (simplified) Chinese, I don't think you'd want to avoid translating the numbers (一,二,三,...) as they can be contained in words made of multiple characters. This could really confuse the machine translation! |
I think that a toggle for not translating roman numerals would be great. "71" being translated to "Seventy one" when it should fit in a tiny space doesn't really work properly. |
+1 to not translate Arabic numerals. Roman numerals are I II..X. The English number system is Arabic, originating from Al-Jabr, the first documented algebra reference book. |
Latest update pushed to github solves this issue - user editable input fields are no longer translated. Will push update xposed repo version soon. |
A text-input field has e.g. my phone number usually, and forced translation with AllTrans actually turns the numbers into words (so my phone number is like thirteen billion fifty two million.....).
Whilst it's quite amusing, it'd be great if there could be an option to omit numbers from translation (should they need translating, anyway?). Turning numbers into words means that the text-input breaks, so I have to disable AllTrans for that app and clear the cache to remember & input my number.
The text was updated successfully, but these errors were encountered: