Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Translator] Load plurals from mo files properly#31267
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
ContributorAuthor
Stadly commentedApr 27, 2019
@nicolas-grekas This should probably be added to the |
ContributorAuthor
Stadly commentedJun 18, 2019
For those who need a MO loader that handles plurals, I have created a package providing this, while we're waiting for this PR to be merged. |
fabpot approved these changesJul 8, 2019
Member
fabpot commentedJul 8, 2019
Thank you@Stadly. |
fabpot added a commit that referenced this pull requestJul 8, 2019
This PR was merged into the 3.4 branch.Discussion----------[Translator] Load plurals from mo files properly| Q | A| ------------- | ---| Branch? | 3.4| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets |#10152 (comment)| License | MIT| Doc PR |Plurals were not handled correctly when loading mo files.```msgid "foo"msgid_plural "foos"msgstr[0] "bar"msgstr[1] "bars"```Before, the mo entry above was treated as two entries, which doesn't make sense:```'foo' => 'bar''foos' => '{0} bar|{1} bars'```With this PR, it is treated as one entry:```'foo|foos' => 'bar|bars'```This PR does the same as#31266, just for mo files instead of po files. Note, however, that the old behavior differed between po and mo files: `'foos' => 'bar|bars'` for po files and `'foos' => '{0} bar|{1} bars'` for mo files.Commits-------97d28b5 Load plurals from mo files properly
This was referencedJul 27, 2019
Merged
Merged
Merged
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading.Please reload this page.
Plurals were not handled correctly when loading mo files.
Before, the mo entry above was treated as two entries, which doesn't make sense:
With this PR, it is treated as one entry:
This PR does the same as#31266, just for mo files instead of po files. Note, however, that the old behavior differed between po and mo files:
'foos' => 'bar|bars'for po files and'foos' => '{0} bar|{1} bars'for mo files.