& written instead of & #110
Assignees
Labels
bug
Something isn't working
Comments
|
I think it's similar issue: |
|
Seems to be related. Note that in my example, there are .spaces between the |
|
Yes, yes, I tested with your example, same problem. |
coffeemakr
added a commit
to coffeemakr/xmlbuilder2
that referenced
this issue
Mar 28, 2022
The current regex for replacing ampersands has a flawed check to see if the ampersand is used HTML-encoded character. The regex isn't working because it ignores whitespace between the `&` and the `;` character. Also I don't think it's the responsibility of the writer to interpret if a value has been encoded already. This should fix oozcitak#110 and oozcitak#109
kmasterson-nprdm
pushed a commit
to npr/xmlbuilder2
that referenced
this issue
Nov 11, 2022
|
Any news on this? |
This was referenced Apr 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I export the following string to XML:
Hello & world today; or tomorrowThe XML that I get is:
<text>Hello & world today; or tomorrow</text>This is invalid, because the
&must be encoded as&To Reproduce
Export the string
Hello & world today; or tomorrowto XML.Expected behavior
Expected value:
<text>Hello & world today; or tomorrow</textVersion:
Additional context
I suspect that the root cause is that the parser has a regular expression that assumes that all in between the
∧are treated as an entity.In the example above, if you'd remove the semicolon, it will export
The text was updated successfully, but these errors were encountered: