3 ms·
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
by crabbone 3y ago
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.
- unilynx 3y agoJSON 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
- crabbone 3y agoYou 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.
- unilynx 3y agoYou 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> ^ And not in theory: https://www.w3.org/TR/2006/REC-xml11-20060816/#sec-well-formed https://www.w3.org/TR/2006/REC-xml11-20060816/#sec-well-form... 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]
- crabbone 3y agoI 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.