[MAGNOLIA-5823] i18n message bundles that contain UTF-8 chars are no longer read correctly by i18n service. Created: 01/Jul/14  Updated: 07/Nov/16  Resolved: 03/Jul/14

Status: Closed
Project: Magnolia
Component/s: i18n
Affects Version/s: 5.3
Fix Version/s: 5.3.1

Type: Bug Priority: Critical
Reporter: Teresa Miyar Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: i18n, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2014-07-01 at 07.54.51.png    
Issue Links:
Relates
relates to MAGNOLIA-6861 DefaultMessageBundlesLoader might not... Accepted
causality
caused by MAGNOLIA-5635 i18n message bundle resolver cannot h... Closed
relation
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   

When I change the superuser language to use spanish, I see wrong characters, see screenshoot. It does not help adding utf-8 to tomcat server.xml



 Comments   
Comment by Christoph Meier [ 02/Jul/14 ]

DefaultMessageBundlesLoader and DefaultMessagesImpl are potential culprits which are loading bundle files; at 1st sight they look correct - loading the files with dedicated encoding.
So probably some files have wrong encoding?

Comment by Aleksandr Pchelintcev [ 03/Jul/14 ]

The linked ticket fixes the issue with property files containing the BOM marker, but the reader logic with instructions to read files in UTF-8 charset was removed.

Generated at Mon Feb 12 04:08:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.