[MAGNOLIA-7118] YAML import uses platform encoding instead of UTF-8 Created: 22/Aug/17  Updated: 27/Oct/17  Resolved: 27/Oct/17

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.5.4, 5.5.5, 5.6
Fix Version/s: 5.5.8, 5.6

Type: Bug Priority: Neutral
Reporter: Maxime Michel Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Bez názvu.png     PNG File Bez názvu2.png     PNG File yaml.png    
Issue Links:
Relates
relates to MAGNOLIA-7098 special characters can sometimes lead... Closed
relates to MAGNOLIA-6683 Offer YAML as alternative format for ... Closed
duplicate
is duplicated by MAGNOLIA-7125 YAML import uses platform encoding in... Closed
relation
is related to MAGNOLIA-7078 YAML exporter should respect YAML syn... Accepted
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:
Epic Link: LD: Fundamental features
Sprint: Kromeriz 119
Story Points: 2

 Description   

This problem occurs when importing YAML files in systems that have platform encoding that is not UTF-8.
XML is not affected as it shows an error when file with different ecoding than UTF-8 is being imported.

Side notes

While working on the Stories app demo, we found that YAML contents weren't imported properly, depending on the platform encoding.
The problem is that this is how it would look otherwise:

The part of the system that handles YAML content fails to deal with the special chars which are the same as in XML.
Here, the problematic content was the single apostrophe:

<p>For someone who’s traveled quite a bit [...]


 Comments   
Comment by Philip Mundt [ 22/Aug/17 ]

Can you please try provided solution (comments) of MAGNOLIA-7098? I have similar settings (utf8) and I do not experience the problem.

Comment by Maxime Michel [ 23/Aug/17 ]

I can confirm that this problem is machine-dependent, as described in the comments of MAGNOLIA-7098. I don't know what variable isn't set up on my OS X system, though. It's running in English so it's not like a foreign language like Russian is preventing it to handle basic characters such as ü. The system should assume a sane default if it can't deduce the encoding based on system variables.

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