Update i18n strings #108
Merged
Update i18n strings #108
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
This is mainly so we don't have to retranslate this and that it matches with playlists and smart blocks again.
Basically I switched to the dev_tools dir and ran "bash update_po_files.sh". A quick check with the german translation shows me that they have about the same amount of missing strings.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 updates the translation strings so they reflect what is in the code.
It was based on running the following and committing the results.
It allows for translation using a desktop app since the new strings are contained. I would like to get these strings updated automatically from travis and then also get the translation automated through zanata, but that will need some refactoring and testing.
If anyone start translating these, the
pro.pofiles can probably be ignored, if not we need to refactor the code since pro should only have legacy upstream saas strings that we are not interested in.