2023-08-16 Product Owner Meetings

POs - Please post your questions here by Wednesday June 12 so that presenters have enough time to prepare. 

Julie: Could someone/people give an overview of the "lifecycle" of localisation, e.g.:
_ What need to be considered in the programming in the original/US English version, so that FOLIO also works in other languages.
_ How does the community contribute the translations.
_ How quickly do the translations then appear in FOLIO.
_ What kind of maintenance needs to happen (e.g. how to you know there are new entries to update each release)

Julie: Can someone (in no more than 2mins ) explain the difference between how FOLIO is currently translated vs. how KnowledgeWare do localisation.

Thomas Trutt : Is personal localisation supported? 

Thomas Trutt : how do dates and times (timezones) work in general and specifically where a single tenant includes campuses that are spread across different time zones?

Tim Auger : Is the page on "How to translate FOLIO" still accurate? There are several "To Dos" and wondering if they are needed and, if so, how do we move them forward? [PM: Will update based on this meeting.]

Tim Auger : What is the scope of our localization efforts? Is it just translations or is it more? (Good resource on the difference between internationalization and localization). 

Thomas Trutt : should titles be translated?

Tim Auger : There is an Internationalization SIG. Is this still active and, if so, how can we take advantage of their efforts? Can we invite a member of the SIG to join and present to the POs? [PM: Not active for half a decade. Essentially it has been Zak Burke and Peter Murray.]

Tim Auger : Maybe related to Julie's question above...should the community continue DIY or should this be outsourced to a firm that specializes in localization? 

Stephanie Buck: A quick overview of what we mean when we talk about localization may be helpful for newer POs, and a good refresher in general

Ann-Marie Breaux (Deactivated) Timing questions: As long as new UI text/data elements are coded in a way that they can be translated, do any translations actually have to exist and be checked before the UI story can be closed? Or do translations just follow along after the UI story is completed, and display for whichever language whenever they are completed? If a UI module version is released in a flower release, will any new translations made after that release show up in the flower release version (e.g. Orchid), or not until the next flower release (e.g. Poppy)?

Peter's slide deck -

Owen commments:

• If someone does translate the word in curly brackets the message will fail to work as expected! I’ve seen that occaisionally
• A couple of other issues I’ve seen:
  
  • Developers failing to add a new key to the en.json file
  • And as Peter has just mentioned, users reporting translation issues that are simply caused by the delay between the initial update to the app, and the update to the translations
  • Especially this is a situation where a particular language is being used for the first time but the release being used is already out (so say Japanese libraries now implementing Nolana) - they see the lack of translations as a bug but it’s just that the translations weren’t supplied before the Nolana release
  • People in the German community have written some instructions on how to backport translations to previous versions - this is aimed at service providers rather than libraries or developers Backport
    • @owen The German instructions - would those backported translations need to be released as CSPs?
    • @Ann-Marie Breaux no - if we released translation updates as CSPs those wouldn’t be needed. These essentially are instructions for pulling the latest translations and rebuilding the UI module with them in
• https://folio-snapshot.dev.folio.org/settings/tenant-settings/locale - But please please don’t change the locale on that page in the hosted reference environment!