Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Scope: This document explains how to use the i18n features in the VIVO front-end editing functionality.

For detailed explanations of how i18n functionality works in VIVO please consult the following :

How VIVO supports languages:

...

https://wiki.lyrasis.org/display/VIVODOC112x/Internationalization#Internationalization-HowVIVOsupportslanguages

...

The VIVO interface is composed of various elements, not all of which are accessible to the end user during the addition or editing of content. Language as part of the interface and page templates is not available to the end user and must be configured by the VIVO administrator.
Language as part of the data must be entered in as many languages as are available in the interface. Any newly added text or accompanying elements must should be added in all versions of the available languages.

...

If text is added in only one language, i.e., English, the other language will look first for a German version, and if not present will display the English version.

[screenshots? from which interface? vanilla? specific institution?]

...

When editing existing entries, you must also remember to edit the text in both all available language contexts, use the language switcher to move from one language to the other.
[screenshots? from which interface? vanilla? specific institution?]

...

In some situations, there may be unexpected behavior when displaying pages after adding or editing text in a multi-language installation. This may be for several reasons:
- [faulty mapping in template or properties files]
- [cached pages in one language, lag in update of content]
- [necessity of rebuilding the index for content]

...