Update pt-BR translation #3124
Merged
Update pt-BR translation #3124
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
kgardnr
approved these changes
Aug 20, 2020
kgardnr
added
the
🚀 merge it!
|
Thank you @desk467! |
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.
What does this PR do?
This PR updates pt-BR translation for features that were introduced up to version 6.3.2
As it is just an update of the fluent language files, there was no change in the GraphQL schema/Database. To test you can run coraltalk, selecting Portuguese (Brazil) language. It's expected that there will be no English term for the interface, unless the English word also applies to Portuguese :D