[MGNLCTS-97] Can't import UTF-8 file with BOM Created: 04/Jul/18  Updated: 26/Aug/22  Resolved: 26/Aug/22

Status: Closed
Project: Content Translation Support
Component/s: None
Affects Version/s: 2.1.8
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Christian Hamm Assignee: Unassigned
Resolution: Won't Do 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:
Team: AuthorX

 Description   

TL;DR: Import of a translated XLIFF file fails when it has a BOM (byte order mark).

 

So, we have hired a translation company that receives XLIFF files from us and we import them back to Magnolia. Unfortunately the import failed with this error:

[Fatal Error] :1:1: Content is not allowed in prolog.

After a bit of debugging and googling I found this on SO:

https://stackoverflow.com/questions/5138696/org-xml-sax-saxparseexception-content-is-not-allowed-in-prolog#7697281

So I quickly converted the files from UTF-8 BOM to UTF-8 and the import worked.

Now, we don't like to manually convert files back and forth and also I see this clearly as a bug, because a BOM should be allowed. Can you please take a look at your implementation and try to handle the file with a BOM?

 

Regards,

Christian

 

 



 Comments   
Comment by Laura Delnevo [ 26/Aug/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 00:33:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.