Kitio Fofack is inviting you to a scheduled Zoom meeting.
Topic: VIVO i18n task force Meeting
Time: Aug 14, 2018 10:00 AM Pacific Time (US and Canada)
Every 2 weeks on Tue, until Nov 05, 2019, 33 occurrence(s)
Aug 14, 2018 10:00 AM
Please download and import the following iCalendar (.ics) files to your calendar system.
Join from PC, Mac, Linux, iOS or Android: https://uqam.zoom.us/j/673342989
Or iPhone one-tap :
Dial(for higher quality, dial a number based on your current location):
Canada: +1 647 558 0588
Meeting ID: 673 342 989
International numbers available: https://zoom.us/u/zUfPayic
Or an H.323/SIP room system:
188.8.131.52 (US West)
184.108.40.206 (US East)
220.127.116.11 (Hong Kong)
Meeting ID: 673 342 989
Agenda and Notes
What to implement for next VIVO Sprint?
Multilingual interface (making English a language as others)
Christian: Sounds like a good idea, has to be done anyway.
Graham : separate strings extraction from grammar. We can focus
Christian: Sounds like something a student assistant could do, it’s a lot of manual work.
Andrew: We could focus on Templates first, then codes, maybe ontology later.
Graham: Pluralization is an issue, has to be solved.
Christian: summarizes to scope of the work to do in :
Identify all the places where i18n
Transfer all the the strings to english language package
Provide translations for French and German
Graham: suggest to slice the work following the code in order to simplify the work.
Kitio: Is going to propose JIRA tasks on code based approach
Christian: Is going to provide a german version of VIVO that will simplify the process to identify all the places where there are i18n. Ideally that work should happen before the sprint. Kitio is going to participate in this effort.
Andrew : if Kitio try to create a French version of VIVO going from German artifacts, this will help in identifying what needs to be done additionally to achieve the goal.
Andrew : things that using the german version of VIVO we are pretty much close to achieve the goal.
Graham: We have a tool to identify changes in translation
Christian: there are still difficulties in integrating additional languages in VIVO.
Graham: Using maven this should be a straightforward process but languages artifacts need to be released to enable this feature.
Andrew: it is possible to release SNAPSHOTS for languages artifacts and have that process working.
- Review German VIVO and identify missing delta in languages files provided by Christian Hauschke
- Propose JIRA tasks for effective creation of language artifacts following the preceding review