I18n redesign #355
Merged
I18n redesign #355
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
[ i18n sprint ] Fixes for new individual form
[i18n sprint] Language-neutral help text in autocomplete forms
[ i18n sprint] remove terms of use controller
* Decouple email templates and translations * provide siteName variable to error templates
* making generic searh-help by using translation properties' keys and i18n bean * Adding new line at the end of the file * Adding translation for title of an anchor
…rom fr_CA (#336) * Apply fixes from french lib properties * Apply fixes from fr_CA autoCompleteObjectPropForm * fixed for fr_CA and other languages * fixes from fr_CA * fix for autoCompleteObjectPropForm.ftl * fixed wrong call for i18n bundle
…e Vitro repository (#348)
* renamed I18nBundle * added I18nBundle interface * Added translation provider * prototype of TranslationConverter * convert all properties * fixes * added caching * Removed obsolete code * Improved logging * fixed getting already existing label * Fix to get RDF Service for configuration models * fix translation request query * added INTERFACE_I18N_FIRSTTIME_BACKUP model * converter test added * formatting fixes * Translation provider tests added * cleanups, added cache test for translation provider * fix: get theme info from web app dao factory as sparql queries on both content and configuration models not supported
…itro [i18n-3762] Moving UI labels translations into vitro
adding English as default language
…of toString() method with toLanguageTag() method, adding checks for locale.stripExtensions() where it was neccessary, adding information about private tag in the drop down selection of a UI language
[3800 i18n redesign] Supporting private tags
[3801 i18n] Renaming files, removing language suffixes for rdf files
… input strings for MethodFormat.format method
* Faux data properties * Use not disjointed classes for faux properties domain and range options * Fix faux object property shadowing real property List faux data properties List faux properties which base properties domain don't match current subject * Write exception to log in VClassDaoJena * filter faux properties returned in possiblePropInstForIndividual * safety checks added * extracted getBaseLabel method, fixed base labels for data properties * fix for prev commit * Formatting fixes * More formatting fixes * More formatting fixes * More formatting fixes * More formatting fixes * More formatting fixes Co-authored-by: Georgy Litvinov <georgy.litvinov@tib.eu>
support for combining parameters and apostrophe
Co-authored-by: Georgy Litvinov <georgy.litvinov@tib.eu>
Co-authored-by: Georgy Litvinov <georgy.litvinov@tib.eu>
Co-authored-by: Georgy Litvinov <georgy.litvinov@tib.eu>
…ertyWrapper (#360) Co-authored-by: Georgy Litvinov <georgy.litvinov@tib.eu>
* fix, i18n: added link to instance in Russian translations * fixed text style * one more fix
Co-authored-by: Georgy Litvinov <georgy.litvinov@tib.eu>
ghost
approved these changes
Feb 13, 2023
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.
VIVO GitHub issue: i18n redesign project board
VIVO PR
What does this pull request do?
Moving UI labels from property files to rdfs
Removing language specific template files
Merging Vitro-language repository into Vitro repository
Support for institution specific translations (private language subtags)
What's new?
*.property UI label files are migrated to *.ttl files
i18n module is extended to support loading of UI labels from ttl files and property files
ftl files from Vitro-languages have been moved to Vitro repository (universal language constructions working for all languages has been used)
home artifacts and UI label files from Vitro-languages have been moved to Vitro
pom files have been adopted
*.yml files (build) have been adopted
How should this be tested?
Example:
Interested parties
Tag (@ mention) interested parties or, if unsure, @VIVO-project/vivo-committers