[UXPROD-779] Internationalization and Localization Created: 27/Feb/17  Updated: 16/Sep/23

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: Epic Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Peter Murray
Resolution: Unresolved Votes: 0
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-517 Ability to set default currency for a... Closed
relates to STRIPES-17 Internationalisation (i18n) Closed
relates to FOLIO-821 Translation Management Tools Closed
Epic Name: Internationalization and Localization
Development Team: None
Rank: BNCF (MVP Feb 2020): R1
Score: 26.75
Start date (migrated):
End date:
Epic Color: ghx-label-6

 Description   

Localization refers to the adaptation of folio content to meet the language, cultural and other requirements of a specific target market (a locale). Internationalization is the design and development of folio to enable easy localization.



 Comments   
Comment by Kristin Martin [ 19/Jun/18 ]

Is the base language for FOLIO English? If developers create apps in the future for FOLIO, will they be expected to be available in English as well as other languages?

Comment by Cate Boerema (Inactive) [ 19/Jun/18 ]

Thanks Kristin Martin. Yes, we can assume that the base language for FOLIO is English. Certainly all of the apps being developed by the teams working now will be available in English. I am not sure if we can require that future apps be available in English, but we can certainly make it a best practice. Looping in Peter Murray and Hkaplanian in case they want to weigh in.

Comment by Hkaplanian [ 19/Jun/18 ]

Kristin MartinCate Boerema
I would say the default language of FOLIO is English. I think it's safe to say we expect all FOLIO applications to support English as well. I don't think we can necessarily say that for an organization or developer to contribute an app, it must have English translations, but we can state/demand that it must support internationalization and localization so others involved in the project can add English (or any other language). Especially if it's an App that others in the community really want and the developer has done a great job in building it.

Comment by Peter Murray [ 20/Jun/18 ]

To the best of my knowledge, there has not been a discussion of a requirement that apps have a default language or have translations available for any particular language. (As a project, we might be able to make a statement about apps that are created as open source by shared project resources, but of course, with the concept of third-party apps the only thing we can do is make suggestions.)

There was recently a thread of conversation (that, unfortunately, I can't find again) that talked about the need for regional forms of translations in addition to the language. For instance, the difference between `en` ("English") and `en_US` ("U.S. English") and `en_GB` ("U.K. English").

It was decided in the Durham meeting, I believe, to have the user interface display English translations if a particular localization translation wasn't available.

Generated at Fri Feb 09 00:10:20 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.