-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
[Translation tool] fa #1815
Comments
Thanks @hpez, currently we can only handle custom number either globally or nowhere. So I have to know if it's also correct to use persian numbers in year: is |
Yes it is correct for using it anywhere in fa locale. |
I just check and persian numbers are already properly output in years and days of month. This is a general issue, alternative numbers (for all languages using them) are not displayed in translated duration strings. I will open a dedicated issue. |
Hi, so I split the fix related to #1817 and the pure translation fixes. For the from_now/ago/before/after, I will need more input as we need the complete rule for all units and quantities. I also need to know if the current translations are wrong or just a bit less accurate to decide if it worth to change them. Right now, static wording is used: But custom rules can be handled using closure: |
There are rather small but I think necessary fixes to the fa locale file which I made a pull request for regarding this issue. |
Thanks! |
Finally the current behavior will be kept as it seems in many language where we support alternative numbers, the digits So with 2.23.0, you will be able to get duration translated strings ( ->forHumans(['altNumbers' => true]); // for all locales
->forHumans(['altNumbers' => 'fa']); // for fa* locales
->forHumans(['altNumbers' => ['fa', 'ja']]); // for fa* and ja* locales |
To be fixed by #1817:
Numbers should all be persian numbers as I have corrected among a few minor issues
To be fixed in translations
The text was updated successfully, but these errors were encountered: