Escaped characters prioritized over using CDATA tags #10
Description
Right now the XML parser doesn't create CDATA elements, and instead escapes unsupported characters. These characters are "un-escaped" upon import, so the (G)UI++ user won't notice a difference, however it does create readability issues in the exported XML. Please feel free to give your thoughts here. Ideas for implementation:
- Maintain current setting - escape characters at the expense of readability
- All elements that use the innertext of an element as their value (Info, for example) get wrapped in a CDATA element regardless of the need (i.e. if there are no escapable characters, the data will still be wrapped in a CDATA element, at the expense of a marginally larger file size (basically a few extra bytes per element)
- Implement logic to determine if CDATA is needed, and only wrap in CDATA if necessary, at the expense of my time writing more code.