[i18n-3762] Moving UI labels translations into vivo

[chenejac]

VIVO GitHub issue: 3762

Companion PR

What does this pull request do?

Moving UI labels translations from VIVO-languages into VIVO (+ adoption of a pom file)

What's new?

webapp directories from VIVO-languages repository are not needed any more. Together with PR for doing the same for home directories from Vitro-languages should enable archiving the VIVO-languages repositories.

How should this be tested?

• Checkout https://github.com/vivo-project/VIVO-languages/tree/i18n-redesign as VIVO-languages project
• Remove VIVO home and install the new, fresh instance of VIVO
• Validate it is working as expected
• Try switching between all 8 languages (set in the runtime.properties languages.selectableLocales = en_US, de_DE, sr_Latn_RS, ru_RU, fr_CA, en_CA, es, pt_BR)

Interested parties

Tag (@ mention) interested parties or, if unsure, @VIVO-project/vivo-committers

[litvinovg]

It looks like there are some differences with current data in VIVO. Report reportVIVO.txt

[litvinovg]

report3.txt

[michel-heon]

@litvinovg and @chenejac A new generation of ontologies is available at

(https://github.com/michel-heon/vivo-i18n-onto-lang)

Details about directories

• Data : contains the transformation transient files -- Note: data/ontologies_ttl/ contains for each key the ontological correspondence in all languages.
• script: contains the transformation programs
• target: contains the result of the distrubuted transformation according to the structure of the Vitro, Vitro-languages and VIVO-languages folders

[litvinovg]

vivo-report-29.11.2022-1.txt

[michel-heon]

For @chenejac and @litvinovg

TESTING COMMENT

INSTALLATION ACTIONS;

• git clone VIVO, Vitro and checkout PR"s for each repo git clone git@github.com:vivo-project/VIVO.git gh pr checkout 3798 git clone git@github.com:vivo-project/Vitro.git gh pr checkout 350
• Config settings.xml. applicationSetup.n3, runtime.properties
• setting runtime.properties : RDFService.languageFilter = true languages.selectableLocales = en_US, de_DE, sr_Latn_RS, ru_RU, fr_CA, en_CA, es, pt_BR
• clean .m2 (rm -rf ~/.m2/*)
• start vivo installation (cd $VIVO; mvn clean install -s installer/settings.xml
• copy sample sample-data-i18n.ttl sample-data-i18n-de_DE.ttl sample-data-i18n-en_CA.ttl sample-data-i18n-en_US.ttl sample-data-i18n-fr_CA.ttl sample-data-i18n-fr_FR.ttl in $HOME/vivo/home/rdf/abox/filegraph
• Start VIVO

  FIRST TESTING (read only mode) and RESULTS:

• Check the home page for each language (Result OK)
• Capability map: Does not work for data not implemented in the target language
• For a person ( ex.: Peters, Jasper I ) the title (Professor and Associate Dean) only in english and position values translate only for (English, French, German) and German is defalut value (English must be)
• Menu title - changes appropriately for all languages
• Physics Department ( The title - The Physics Department is in the College of Science of Sample University - still remains in English - must be accept translation)
• for the event "17th Annual Conference on Philosophy and Rhetoric" (the default language of the title is German for all non-implemented languages, when it should be English)
• the file tomcat/webapps/vivo/themes/nemo/i18n/all.properties is installed

SECOND TESTING (Edition mode and RESULTS):

• For organization: Physical (http://localhost:8080/vivo_i18n/individual/n1927) the preview value is not translated
• I added an organization with a summary in English, French and German and it works well
• I added a book and a publisher with labels in French and English and associated with a person (the language change works well for all additions)

  CONCLUSTION

• the sample project ( https://github.com/vivo-project/sample-data ) should be enhanced for each of the languages implemented in the VIVO core
• Check the behavior of Capability Map
• Pay attention to the default language (German instead of English)
• Several titles are not translated (position of persons/title of organizations, etc)
• In the runtime.properties file, I suggest to add a languages.default= property to allow setting the default language.

[michel-heon]

Test on version 1.13.0 to validate that new problems are not caused by this PR

Case 1:

For a person ( ex.: Peters, Jasper I ) the title (Professor and Associate Dean) only in english and position values translate only for (English, French, German) and German is defalut value (English must be)

Result:

The problem exists before this PR

Case 2

Physics Department ( The title - The Physics Department is in the College of Science of Sample University - still remains in English - must be accept translation)

Result:

The problem exists before this PR

Case 3

for the event "17th Annual Conference on Philosophy and Rhetoric" (the default language of the title is German for all non-implemented languages, when it should be English)

Result:

The problem exists before this PR

---

Conclusion

All the problems existed before this PR