Versions Compared

Old Version 8

changes.mady.by.user Ralph O'Flinn

Saved on

compared with

New Version Current

changes.mady.by.user Kitio Fofack

Saved on

Key

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

...

Attendees

(star) Indicating note-taker

  1. Kitio Fofack

    2.  (star)

  3. Mike Conlon

  4. Christian Hauschke

  5. Andrew Woods

    6. Mike Conlon

  6. Joachim Dornbusch

  7. Manuel Schwarz

  8. Graham Triggs

  9. Anna Kasprzik

  10. Huda Khan

  11. Muhammad Javed

  12. Ralph

    13. O'Flinn
  13. ... your name here ...

  14. O’Flinn


Agenda

  1. Task force governance
    1. Objectives
    2. Schedule
  2. Technical choices for i18n implementation
  3. i18n issues
    1. fallback mechanism
    2. release policy
    3. maintenance of language versions - tools and processes to be notified of language related changes in the VIVO code
    4. better usability for switching languages in standard themes (no flags)

  4. JIRA tickets

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=14602
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes

...

  1. Task force governance

    1. Objectives

      1. To fulfill the requirements the document specifies
        https://docs.google.com/document/d/1liFlAkwocgoy_F28YiyKbegZglumy0xIDlz_zcwykzA/edit#

      2. Constructing rules for including I18N into the development process

    2. Schedule

      1. Mike is suggesting once every two weeks

  2. Requirements (https://docs.google.com/document/d/1liFlAkwocgoy_F28YiyKbegZglumy0xIDlz_zcwykzA/edit#)

    1. Complete multilingual interface - everything will be language-agnostic. English is treated as one of many possible languages.

    2. Multilingual content edition

    3. Configure available languages on the fly

      1. Rephrased in “Make language configuration easier”

    4. Fallback mechanism

      1. Fallback for data. What happens when no french label exists, but the user chose to view VIVO in French

      2. If a thing has a label, translations should be tied to this one thing.

      3. Hard to decide on a fallback mechanism

        1. Falling back to a pre-defined language

        2. Showing nothing or an error if label in the selected language does not exist

        3. Fallback languages should be customizable (like Portuguese in Macao-China).   

  3. i18n issues

    1. fallback mechanism

    2. release policy

      1. There needs to be a review and release policy for /vivo-languages

    3. maintenance of language versions - tools and processes to be notified of language related changes in the VIVO code

      1. VIVO languages should be maintained by its language community

      2. Language repositories are separate so they can be released independently and be used as artefacts.

    4. better usability for switching languages in standard themes (no flags)



Actions

  •  ...