Internationalization and Localization
(UXPROD-779)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Internationalization and Localization |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | i18n | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Epic Link: | Internationalization and Localization | ||||||||||||||||||||||||||||||||
| Back End Estimate: | Large < 10 days | ||||||||||||||||||||||||||||||||
| Back End Estimator: | Jakub Skoczen | ||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R5 | ||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R5 | ||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R5 | ||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R5 | ||||||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R5 | ||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R4 | ||||||||||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R5 | ||||||||||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R5 | ||||||||||||||||||||||||||||||||
| Rank: Leipzig (ERM Aut 2019): | R5 | ||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R5 | ||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R5 | ||||||||||||||||||||||||||||||||
| Description |
|
The base permissions that come with apps are apparently not translatable. See screenshot in comments. |
| Comments |
| Comment by Cate Boerema (Inactive) [ 11/Jun/18 ] |
|
Screenshot of base permissions. These display in both Settings > Users > Permission sets and Users |
| Comment by Zak Burke [ 09/Sep/20 ] |
|
This was handled in
|
| Comment by Erin Nettifee [ 10/Feb/21 ] |
|
I was looking at this ticket, and only some names actually appear to be translating: Also, the names of the permissions sets themselves don't translate: The screenshots are from Duke's honeysuckle environment, but I tested on snapshot as well and it's showing the same behavior. Zak Burke - in terms of the display in the permissions set creator (first screenshot), is that something that would be a bug in Settings, or is it something that needs to be fixed in the underlying module serving up those permissions? I assume for the permission set names themselves, that's a feature in settings, and I'll open a bug for that one. |
| Comment by Zak Burke [ 10/Feb/21 ] |
|
Erin Nettifee, in your first screenshot, values like "Fees/Fines: Can charge" are, in fact, translatable but translations have not been supplied. IOW, this is a legit bug. The problem is a missing translation value (not a code problem) in the underlying module that contains the permission set (ui-users in this case). In the second, that screenshot is from Settings > Users > Permission sets (/settings/users/perms), and thus shows permission sets that have been created at runtime. This is user-entered data, so just like you wouldn't expect a user named Daisy to show up as Marguerite, or your titles in inventory to be automatically translated, "All Permissions" doesn't automatically become "Toutes les permissions" when you change the locale. IOW, I don't think this is a legit bug. That said, we have heard from folks who would like ability to provide translations for runtime values, e.g. so you could have item-locations like "Central Library" appear as "Bibliotheque Centrale" for a user from a French locale. That work is not presently integrated, but I can loop you in if you want more details. |
| Comment by Erin Nettifee [ 10/Feb/21 ] |
|
Thanks Zak Burke - your point about the second makes sense to me, and I understand it better now and agree it's not a bug. I don't need to be looped in further (this work came from exploring existing permissions features/bugs as part of gearing up for app interaction to work on permissions problems, so there's enough there already |
| Comment by Erin Nettifee [ 09/May/23 ] |
|
As Zak noted, this was done as part of translation work for displayName values. |