Try using UTF-8 encoding for XML, and your problems with zero byte encoding will go away.
Your understanding of "easier" is oversimplified to the point that it's wrong. It's easier to do the wrong thing in JSON, it's harder to do the right thing in JSON (compared to XML).
JSON is a poorly thought-out format. It's problems become progressively more difficult to deal with the more you expect of your program.
JSON and XML both support UTF-8. Neither supports embedding arbitrary binary data directly, especially if that data is not valid in your current character set
You wanted to send zero byte. This is how you send zero byte. You are making unrelated claims now that has nothing to do with your original claim.
You can't safely send zero bytes over XML even with UTF-8 encoding. Not in practice:
echo '<zero>�</zero>' | xmllint -
-:1: parser error : xmlParseCharRef: invalid xmlChar value 0
<zero>�</zero>
^
printf '<?xml version="1.0" encoding="utf-8"?><zero>\0</zero>' | xmllint -
-:1: parser error : Premature end of data in tag zero line 1
<?xml version="1.0" encoding="utf-8"?><zero>
^ Character Range
[2] Char ::= [#x1-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF] /* any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. */
[2a] RestrictedChar ::= [#x1-#x8] | [#xB-#xC] | [#xE-#x1F] | [#x7F-#x84] | [#x86-#x9F]I explained how to do it, and yet you didn't follow instructions, have done something irrelevant, and are now complaining that it doesn't work... well sucks being you, I guess.
Re:JSON Schema Store
by peoplefromibiza on Monday August 21, 2023 @04:54AM
(#37206938)
> JSON just says do “\0” and calls it a day
nope
jq "." <<< "\0"
parse error: Invalid numeric literal at line 2, column 0
jq "." <<< '{"name": "\0"}'
parse error: Invalid escape at line 1, column 13
jq "." <<< "null"
null
jq "." <<< '{"name": null}'
{
"name": null
}"\0" is not a valid JSON string escape sequence.
However, "\u0000" is.
Re:JSON Schema Store
by peoplefromibiza on Monday August 21, 2023 @10:19AM
(#37209900)
not according to jq or firefox
>> JSON.parse("\u0000")
Uncaught SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
<anonymous> debugger eval code:1
they're not comparable at all. you can't embed a null into a string
\u0000 works fine with firefox with the proper syntax
JSON.parse(`"\\u0000"`)
"\u0000"
printf '{"null":"\u0000"}' | jq
{
"null": "\u0000"
}
Re:JSON Schema Store
by peoplefromibiza on Monday August 21, 2023 @01:52PM
(#37212980)
> the proper syntax
of course! I forgot to quote those quotes! (facepalm)
that works. and uses a single byte too.
TIL.
HTML isn’t trying to serialize abstract data and is doing what XML does best in being a document/GUI format. It doesn’t matter all that much that it can’t represent null characters in a standard way because it isn’t a printable character.