[MGNLUI-2431] i18n:pageEditor i18n is broken - always uses english for some keys Created: 16/Sep/13 Updated: 09/Mar/21 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
create new message-bundles each for stk (according to new i18n-concept) There is a problem in that some of the values are always in english - no matter the set language. |
| Comments |
| Comment by Christoph Meier [ 18/Nov/13 ] |
|
Some of the texts in STK are somehow strange assembled which leads into language-mix-labels. (see screenshot) |
| Comment by Christopher Zimmermann [ 19/Nov/13 ] |
|
These strings appear to be assembled at: line 187: Somehow getI18nMessage appears to be operating in english even if another language is specified. Looks like its a problem with how values are put into the dictionary used by: public static String getI18nMessage(final String key) { return dictionary.get(key); }Huh - what is this? |