[MAGNOLIA-3487] Introduce super-fallback language Created: 04/Jan/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: gui, i18n
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Zdenek Skodik Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3488 Improve the notation for missing valu... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Since we started with moving outputs of the international effort into real world, people tend more and more to switch from English at all.

On the other hand the i18n process is a constant work-in-progress and as such it will always lag behind default English localization which will most likely be the only one language kept up to date.

Since we used to release a properties files just with few translated keys, you can easily end up with a pretty malformed interface with few languages and missing values of a lot of keys (the ???key??? notation) like f.e. with current stk-1.4.1.

Thus it would be nice to introduce a super fallback language so the i18n chain will be like this: user's language -> configured fallback language -> English.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:46:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.