-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Code Quality: Adding the possibility of plural translation using ICU format #15433
Code Quality: Adding the possibility of plural translation using ICU format #15433
Conversation
How to use it
|
Okay I'm done, we could try just these two for now, we'll see how the translators handle it. I could finish the others in the next PR |
It might be a good idea to add a link to the basic usage documentation in Crowdin's details: Crowdin ICU Message Syntax | Plural |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codebase quality reviews.
If you’ve tested in en-US for them, LGTM.
Japanese doesn’t have this kind of difference(singular and plural).
I’m not sure why but there’re duplicated functionalities including RespurceString, GetLocalized, GetLocalizedResource, LocalizationService, and this. |
If not necessary, only 'other' is used https://www.unicode.org/cldr/charts/45/supplemental/language_plural_rules.html#ja
|
I always test en-US (two options) and cs-CZ (three options) using plural |
Update Resources.resw Update Resources.resw
3a2c78d
to
0bdb970
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Resolved / Related Issues
To prevent extra work, all changes to the Files codebase must link to an approved issue marked as
Ready to build
. Please insert the issue number following the hashtag with the issue number that this Pull Request resolves.Steps used to test these changes
Stability is a top priority for Files and all changes are required to go through testing before being merged into the repo. Please include a list of steps that you used to test this PR.
Screenshot