VIVO Documentation
...
User's preferred locale | displayed text |
---|---|
en_UK | colouring |
en_CA | colouring |
es_MX | colorear |
fr_FR | coloring |
...
...
VIVO uses the Java language's built-in framework for Internationalization. You can find more information in the Java tutorials for resource bundles and properties files.
Note | ||
---|---|---|
| ||
"Internationalization" is frequently abbreviated as "I18n", because the word is so long that there are 18 letters between the first "I" and the last "n". |
In In the I18n framework, displayed text strings are not embedded in the Java classes or in the Freemarker template. Instead, each piece of text is assigned a "key" and the code will ask the framework to provide the text string that is associated with that key. The framework has access to sets of properties files, one set for each supported language, and it will use the appropriate set to get the correct strings.
...
The text strings are processed by the Java I18n framework for message formats. Here is a tutorial on message formats. Full details can be found in the description of the MessageFormat class.
...
Code Block | ||
---|---|---|
| ||
if ( area == "global" ) { text = " " + i18nStrings.countriesAndRegions; } else if ( area == "country" ) { text = " " + i18nStrings.statesString; } |
Warning | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
This functionality was removed in the 1.12 release (
|
i18nChecker is a set of Ruby scripts that are distributed with VIVO, in the the utilities/languageSupport/i18nChecker
directory. Use them to scan your language properties files and your freemarker templates. The scripts look for common errors in the files.
...