If you are a VIVO site administrator and you simply want to enable one of the available languages in your VIVO installation, the Quick Start guide should be all you need. If, however, you are interested in design details, then continue reading.

Quick Start

1. Stop the VIVO application
2. Update the runtime.properties file to:
   1. Enable language filtering

      
      

      Code Block
      RDFService.languageFilter = true

      
      

   2. 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

      
      

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 only loads the property files and Freemarker templates for the languages enabled in the runtime.properties file; see Quick Start above. Ideally, only a single set of Freemarker template files would needed, the content of which being populated by i18n properties. A few template files, such as "terms of use", "email templates" and "search help", include large blocks of formatted text that are currently better suited to exist in their own language-specific Freemarker templates.

When internationalization is enabled, additional logic is executed that filters content triples and selects fallback content in the case that there is no triple available for the preferred language/locale.The document aims to explain the introduction of a new language in Vivo. It is particularly aimed at the directory structuring stage, containing the translated files, so that the new language is part of the VIVO installation and deployment process.