[MAGNOLIA-1060] I18n messages does not fallback to default if message is not translated Created: 19/Sep/06  Updated: 23/Jan/13  Resolved: 20/Sep/06

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.0 RC2
Fix Version/s: 3.0 RC3

Type: Bug Priority: Major
Reporter: Sameer Charles Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

Problems with i18n

  • Encoding is not set in popup menus
  • Broken strings is message key is not found eg. "?central.user?" It should fallback to default language if message is not translated.


 Comments   
Comment by Sameer Charles [ 20/Sep/06 ]

fixed

http://svn.magnolia.info/svn/magnolia/trunk/magnolia-core/src/main/java/info/magnolia/cms/i18n/MessagesManager.java

Now MessageManager always chains the system default messages with the context messages.

Comment by Philipp Bracher [ 21/Sep/06 ]

I commited additional changes:

chain with the same basename (not the admin central default) and only if the requested local isn't the default locale

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