Page History

...

• Go into the VIVO project folder and uncomment the section for multiple language support (search for '<!-- Dependencies for multilingual support -->' and '<!-- Overlays for multilingual support -->' inside of the files)  in each of the two pom.xml files listed below:

  • Vitro/installer/webapp/pom.xml (Uncomment dependencies and overlays)

  • VIVO/installer/home/pom.xml (Uncomment dependencies)

  • VIVO/installer/webapp/pom.xml(Uncomment dependencies and overlays)

  Change the <version> in the two pom.xml files to the same version as in the 'VIVO-language/pom.xml' and 'Vitro-language/pom.xml' file respectively.  You may need to change the version in multiple places in the files.
• Build VIVO from the VIVO project folder using mvn install -s installer/my-settings.xml
• Edit the vivo_home_dir/config/runtime.properties file in your VIVO home directory:
  
  • uncomment/add RDFService.languageFilter = true
  • uncomment/add languages.selectableLocales = en_US, de_DE
• Restart the tomcat
• You should now be able to select your installed language (in this case German) in the header of your VIVO site

...

If your VIVO theme is named "frodo", then your text strings (using the default bundle name) would be searched your theme  in

• webapp/themes/frodo/i18n/all.properties
• webapp/i18n/all.properties

If you specify a complex more than one locale for VIVO, this search pattern becomes longer. For example, if your user has chosen Canadian French as his language/country combination, then these files (if they exist) will be searched for text strings:

...