Fix noDoubleEncoding with undefined XML entities #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #16
The
\S+
in the regular expression has two problems:It’s greedy, so it matches something like
¬anentity<
and prevents the first&
from being encoded.It allows any entity to pass through unencoded, but XML only recognizes a few entities.
The solution here is to not double encode only the few entities recognized by XML. This results in things like
being encoded into&nbsp;
, which seems to be what we want.You may want to backport this fix to xmlbuilder.