Context

Vitro and VIVO are seeing increased use in territories around the world. Whether it is in Germany, Spain, Brazil, Canada, China, India, Denmark, or France,  many institutions need to have support for languages other than English.

The core infrastructure of Vitro is well designed to address these needs - the triple store allows strings to be marked with language tags, and the user interface mostly consists of Freemarker templates, that have externalized messages which can be translated into other languages.

However, while the technology is there, the current implementation does not fully address the needs of the international community. A handful of pages remain in JSP, without any internationalization support currently provided. Handling for labels and plurals is often lacking. How fields that may have multiple representations (translations) should be handled is unclear.

Objectives

  1. Deliver an internationalized VIVO able to support as many languages as possible in the interface and the content
  2. Coordinate members efforts on translations

Deliverables

The requirements document found here (https://docs.google.com/document/d/1liFlAkwocgoy_F28YiyKbegZglumy0xIDlz_zcwykzA/edit#) describes in detail all the features the task force wants to implement in order to achieve it's goals.

VIVO i18n Implementation challenges - Brainstorming document: https://docs.google.com/document/d/1wjpdlzkH7F8toQuLg1W06NnT_0cgkdl0HbwUKFu4rfo/edit?usp=sharing

Resources

Members


Meeting Times


Next ZOOM meeting is shedule for June 4th 2019 at 10 am ET at the following adress: https://uqam.zoom.us/j/5142161911

 

Communication Channels

Agendas and Notes