Might be interesting to take a look. I don’t know how that happened.
patch.vl (20.0 KB)
I have another very similar document.
broke2.vl (22.1 KB)
I think it happened because I put some non-ascii symbols in the document. Not sure
Judging from the screenshot, these symbols could be here. And I did not enter them directly, but displayed them in IOBOX from bytes.
the same situation in second file
Problem still here
I took a data string that was guaranteed to be valid for my purposes (from the beta, by the way), saved it to IOBox and now I have no patch. This was quite brutal, please take note.
Fixed in upcoming. Strings containing invalid XML characters will get Base64 encoded. Thanks for reporting.
1 Like