VIVO Documentation
Page History
...
- Stop the VIVO application
- Update the runtime.properties file to:
- Enable language filtering
Code Block RDFService.languageFilter = true
- Enabled desired languages
..such as the following if you wanted: English, Spanish, German, French and Portuguese
Code Block languages.selectableLocales = en_US, es, de_DE, fr_CA, pt_BR
Private-use subtags are also supported, meaning in the list of selectableLocales might be used local/institutional extension of the language such as fr_CA_x_uqam or de_DE_x_tib. However, those language files are not in the VIVO/Vitro codebase, meaning it is not possible just to enable those languages without copying of the directory with translations in those languages in the [VIVO_HOME] directory.
- Enable language filtering
VIVO i18n Design
One of the goals of the most recent design of VIVO's internationalization (i18n) implementation is to simplify the process for activating a multi-lingual VIVO site. Starting with the 1.12.0 release of VIVO, all supported languages are built into the application. On start-up, VIVO loads the UI labels ttl files, and annotation and other labels RDF for the languages enabled in the runtime.properties file; see Quick Start above.
...