[UXPROD-2605] User defined fields localization | MultiLingual FOLIO - Modules Policies Names are of a Singular Language Structure Created: 22/Jan/19  Updated: 12/Mar/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: P3
Reporter: Massoud Alshareef Assignee: Khalilah Gambrell
Resolution: Unresolved Votes: 0
Labels: i18n
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Users Module - Arabic Patron Groups Policies Names Description Settings.png     PNG File Users Module - Arabic Patron Groups Policies Names Description while in LRT.png     PNG File Users Module - Arabic Patron Groups Policies Names Settings.png     PNG File Users Module - Arabic Patron Groups Policies Names in use while in RTL (2).png     PNG File Users Module - Arabic Patron Groups Policies Names in use while in RTL.png     PNG File Users Module - English Patron Groups Policies Names in use while in RTL.png     PNG File Users Modules - Arabic Patron Groups Policies Names Appearing while in English UI.png    
Issue links:
Relates
relates to FOLIO-2802 Recruit translators for library-defin... Open
Development Team: Stripes Force
PO Rank: 0
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R5

 Description   

Hello مرحبا

Since mid of nineties, it has been a custom to experience the multi-linguality of localized global ILSs coming to the GCC region, not only at the UI menus, drop down lists, screens, dialog boxes, help and manual text, but also at the policies names and descriptions as well. This means in a multicultural environment like ours, where the same ILS system serves students from Arab countries along with students from other non-Arabic speaking countries, like India, in the same school, the ILS must provide the UI fully in Arabic and fully in English, including library-defined policies names like those defining item types, branch libraries names, patron groups, etc.

With the RTL enabled FOLIO system we have for testing, I've translated the Patron Groups names description to Arabic in Users Module Setting:

Then, when using the Users module, the Patron Groups names still appeared in English:

And that is not going to be appreciated by Arabic users.

However, Patron Groups Descriptions appear in Arabic, not only in RTL but also in LTR (English):

Then, after I made the Patron Groups Names in Arabic as well:

The Arabic Users Module showed Patron Groups Names in Arabic as desired:

However, the Arabic Patron Groups names appeared in Arabic while in English UI also, which is for sure not going to be appreciated by users and staff who are not of Arabic culture:

Now you can see how important to enable FOLIO in supporting Multilingual Policies Names and Descriptions, Arabic policies names for Arabic and English policies names for English users, in a multi pollutant library environment.

Best,
Massoud.



 Comments   
Comment by Khalilah Gambrell [ 29/Jul/20 ]

Massoud Alshareef, I think this is a FOLIO Feature, I will create a UXPROD feature so that it is prioritized by FOLIO implementing libraries.

Comment by Khalilah Gambrell [ 29/Jul/20 ]

Cate Boerema and Jakub Skoczen, I am unsure that this is a stripes-force feature this seems like platform feature that may require backend work. We will need to discuss further.

cc: Ryan Berger and John Coburn

Comment by Massoud Alshareef [ 31/Jul/20 ]

Khalilah Gambrell Cate Boerema Jakub Skoczen As we have demoed to PC before our solution toward enabling libraries to translate their policies (dynamic vocabularies) to their Local language. The plan was to submit the PR with documentation for the translation app along with the user-defined Locales switcher code by now. We had to consume extra weeks over the anticipated time because we needed to re-build our solution on top of the latest FOLIO software released recently with Goldenrod. We hope to submit our solution PR within two weeks from now.

It worth noting that in order to make use of the multi-lingual library-defined policies solution, apps developers need to make any value referencing apps policy tables translatable. The PR will contains detailed documentation on the guidelines to follow for the variables naming conventions needed in order to reference each translatable policy table by the apps.

cc: Ryan Berger John Coburn Zak Burke and attia.alshareef

Comment by Cate Boerema (Inactive) [ 03/Aug/20 ]

Thanks for the clarification, Massoud Alshareef. So, would you say the scope of this feature is:

  1. Enabling libraries to translate their policies (dynamic vocabularies) to their Local language OR
  2. In order to make use of the multi-lingual library-defined policies solution, apps developers need to make any value referencing apps policy tables translatable OR
  3. Something else

On a side note, do you think it would be possible for your team to submit PRs making the referencing apps policy tables translatable? It seems like you would know best what needs to be done and it might speed the process along. Just a thought. Zak Burke and others may have an opinion on whether this might be a sensible plan.

Comment by Massoud Alshareef [ 03/Aug/20 ]

Thanks Cate Boerema for your comment. In response to your inquiry about how to enable allowing library-defined policies to be translatable, points 1 and 2 will need to be implemented. For point 1, most likely that once the first library completes the translation of the policies to a particular language, say to French or German, the other libraries needing to use FOLIO library policies in the same language(s) will be able to simply import the policies translation(s) onto their FOLIO installation (tenant). The translation app we have developed will provide the import/export tools and services needed.

For point 2, we will follow the same approach implemented by md331 in https://github.com/folio-org/ui-users/pull/1240 to allow for localizable permission names, with the exception that our solution is based on a dynamic translation technique where libraries can generate/ edit/ delete policy names and their translations to any FOLIO supported language on the fly. What it means is that all apps developers (at least those with policy names that are library-definable) will need to add a few translation keys. App and policy table names are currently used in our solution for forming all polices translatable keys.

We will be more than happy to submit PRs making the referencing apps policy tables translatable, after coordinating with Zak Burke and other colleagues in the development team.

On a side note, it worth mentioning that in order for developers to enable the multi-lingual library-defined policies feature within their apps, they will need to conform to the guidelines in the documentation when referencing policy names in the future. I cannot emphasis enough how important this conformation is when you realize how many multi-lingual strings out there in the static repository (Lokalize) that are not in use in some apps simply because their translation keys are not in use yet within those apps. Furthermore, Lisa and you had experienced how the "Item Status" appeared translatable in the Search Filters section of the Inventory app where it appeared in a single language (English) in the item status screen section of the same app! I understand that developers main focus at the time of development is more on making the feature working as expected than worrying about how it may appear in other Gibberish (just kidding!) letters in the future. I hope that once approved and ready for merge, using the library-defined policies translatable keys, as well as the translatable keys for the static screen fields labels and permission names, will be part of the FOLIO developers guidelines to speed up the process of bringing all apps and thus FOLIO faster to the international markets.

Massoud.

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