Context
Vitro and VIVO are seeing increased use in territories around the world. Whether it is in Germany, Spain, Brazil, Canada, India, Denmark, France, many institutions need to have support for languages other than English.
The core infrastructure of Vitro is well placed 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 externalised messages which can be translated into other languages.
However, whilst 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 internationalisation 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
- Deliver an internationalized VIVO able to support as many languages as possible in the interface and the content
- Coordinate members efforts on tranlations with a work process on translations, documentation ...
Deliverables
The requirement document found here(https://docs.google.com/document/d/1liFlAkwocgoy_F28YiyKbegZglumy0xIDlz_zcwykzA/edit#) describes in detail all the features the task force want to implement in order to achieve it's goals.
Members
- Graham Triggs - facilitator
- Mike Conlon - facilitator
- Christian Hauschke, TIB
- Chantel Risdale, Research Data Canada
- John Fereira
- jlmunozuc3m
- Roberto JR
- Kitio Fofack, UQAM
- Tatiana Walther, TIB
- Anna Kasprzik, TIB
Meeting Times
TBD
Communication Channels
- Updates from the task force will be available in VIVO Updates
- Child pages to this page will contain meeting notes
- #i18n channel on vivo-project's slack (https://vivo-project.slack.com) is the place for unformal discussions related to i18n
- Zoom will be the tool used for the task force meetings
Agendas and Notes