[VIVO-1892] i18n: added i18n support for the capability map #179
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.
JIRA Issue
2nd related PR
What does this pull request do?
With this PR all text from the Capability Map template is replaced with i18n-properties und pull into the property-file.
In addition the property-files for the Capability Map in VIVO-languages will be updated and the language specific templates in VIVO-languages will be deleted.
What's new?
Only a single i18n compatible template for the capability map instead of one for each language
How should this be tested?
Go to the capability map and switch between languages, everything should be translated.