Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Escaped characters prioritized over using CDATA tags #10

Open
theznerd opened this issue Jul 22, 2020 · 0 comments
Open

Escaped characters prioritized over using CDATA tags #10

theznerd opened this issue Jul 22, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@theznerd
Copy link
Owner

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.
@theznerd theznerd added the enhancement New feature or request label Jul 22, 2020
@theznerd theznerd self-assigned this Jul 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant