Proper pt_br retranslation. #675
Open
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
Now it's an acceptable translation. The previous one had many contradictions to itself, and some phrases were just plain wrong.
ghost
changed the title
|
I didn't see the translation wiki page until I was checking how often pull requests are merged. Sorry about that. |
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.
Now it's an acceptable translation. The previous one had many contradictions to itself, and some phrases were just plain wrong.
Sorry if I did anything wrong, I don't anything about JavaScript. There's some comments that should be read right at the start of the file.
On line 192, I interpreted "learned to look ahead" as in "learned to look forward" since that makes more sense with the rest of the perk. Could have interpreted wrong, though, in that case I'll fix it.
Also, I don't know the reason of having a blank "" on the first line, then the phrase on the line right after. I assume it's because of spacing issues. I don't know how to test that, but wherever there was one of these cases I left it that way.