Bring Portuguese plurals in line with i18next and CLDR #68
Conversation
This file contains 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
Sign up for free
to 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.
This PR addresses #67 and takes the same approach as the associated
i18nextfix i18next/i18next@c5113fbThe plural forms for Portuguese have been changed.
Now
pt-PTis the exception to the rule, takingplural=(n != 1)where as all other forms of Portuguese (includingptandpt-BR) takeplural=(n > 1). This is in accordance with the Unicode spec for Portuguese (pt) and European Portuguese (pt-PT).For
i18nextthis was seen as a breaking change and bumped a major.