[FOLIO-2866] Add Amazigh language Created: 06/Nov/20  Updated: 03/Sep/22

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Mark Allcock Assignee: Peter Murray
Resolution: Unresolved Votes: 0
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File lokalise-custom-language-settings.png     PNG File screenshot-1.png    
Sprint: DevOps: Sprint 101
Development Team: Core: Platform

 Description   

Lokalise does not have an entry for this language, so will need to use a custom code. There is a Wikipedia entry for Berber languages.

The *Berber languages, also known as **Berber* or the *Amazigh languages* (Berber name: Tamaziɣt, Tamazight; Neo-Tifinagh: ⵜⴰⵎⴰⵣⵉⵖⵜ, Tuareg Tifinagh: ⵜⵎⵣⵗⵜ, pronounced tæmæˈzɪɣt, θæmæˈzɪɣθ, are a branch of the Afroasiatic language family. They comprise a group of closely related languages spoken by the Berbers, who are indigenous to North Africa. The languages were traditionally written with the ancient Libyco-Berber script, which now exists in the form of Tifinagh.

There isn't an ISO 639-1 two-letter code for Berber. There is an ISO 639-2 three-letter code (ber). Since the Stripes code is based on two-letter codes (see supportedLocales in stripes-core, it isn't clear how to make this happen.



 Comments   
Comment by Peter Murray [ 06/Nov/20 ]

Zak Burke: What do you think would happen if I put a three-letter code ("ber") into supportedLocales of loginServices.js of stripes-core? This language does not have an ISO 639-1 (two-letter) code, but it does have an ISO 639-2 (three-letter) code.

Comment by Peter Murray [ 06/Nov/20 ]

Custom language settings in Lokalise.

Comment by Zak Burke [ 06/Nov/20 ]

Peter Murray, ber is not recognized as a locale the way, say en-US or ur are:

12:19:05.975 (new Intl.DisplayNames(['en'], { type: 'language' })).of('en-US')
12:19:05.982 "American English"
12:19:11.300 (new Intl.DisplayNames(['en'], { type: 'language' })).of('ur')
12:19:11.309 "Urdu"
12:19:14.201 (new Intl.DisplayNames(['en'], { type: 'language' })).of('ber')
12:19:14.209 "ber"

Is the issue truly that FOLIO may be translated into Amazigh or that it needs to be able to show Amazigh glyphs, e.g. in ui-inventory?

Comment by Peter Murray [ 06/Nov/20 ]

My understanding is that Amazigh/Berber is a distinct language/translation and simply (simply?) a matter of glyphs. I needed to use one of the custom language slots in Lokalise to define it. I'm getting the sense that we might need a blocking issue on stripes-core to get it recogized in FOLIO?

Comment by Peter Murray [ 06/Nov/20 ]

Mark Allcock: One of the consequences of this is that it will take slotting this into a development sprint cycle to get it recognized.

Comment by Peter Murray [ 03/Sep/22 ]

Mark Allcock: I'm not sure if we are in a chicken-and-egg situation...no one working on this translation because it isn't in the UI and we aren't putting in the time to get it into the FOLIO UI because no one is working on a translation. I am tempted to remove the translation and close this issue, though. Do you have any updated details?

Generated at Thu Feb 08 23:23:49 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.