-
Bug
-
Resolution: Fixed
-
Neutral
-
5.5.4, 5.5.5, 5.6
-
None
-
None
-
-
Empty show more show less
-
Kromeriz 119
-
2
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 [...]
- is duplicated by
-
MAGNOLIA-7125 YAML import uses platform encoding instead of UTF-8
- Closed
- is related to
-
MAGNOLIA-7078 YAML exporter should respect YAML syntax for multi-line values
- Accepted
- relates to
-
MAGNOLIA-7098 special characters can sometimes lead to ReaderExceptions in YAML bootstrap
- Closed
-
MAGNOLIA-6683 Offer YAML as alternative format for JCR bootstraps beside XML and revise export/import operations
- Closed