Repository navigation
Replies: 1 comment
|
I reproduced the HTML entities with v2.8.1. In v3.11.2, the same conversion preserves the actual string value. The v3 flags are '<foo>"bar>baz"</foo>' | dasel -i xml -o jsonThe output is: {
"foo": "\"bar\u003ebaz\""
}Here I checked both releases and decoded the v3 JSON to verify the value. This gives the value you need, although the JSON serializer writes The v3 JSON writer uses JSON string encoding. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm trying to convert XML (from a system I don't control) to JSON. The XML sometimes contains double quotes and other "special" characters in the text content.
Daselversion2.8.1currently encodes:"as"where I would like it to be\">as>where I would like it to be>I assume this is html encoding? Is there an argument that controls this that I am missing?
Here is a sample string showing what I'm sending:
It returns:
{ "foo": ""bar>"" }I need it to return:
{ "foo": "\"bar>baz\"" }I'm running this on Windows if that matters.
All reactions