On Sun, 2021-03-21 at 18:06 +, Hans-Juergen Rennau wrote:
> No, Liam, that is a misunderstanding - it *may* be escaped by a
> preceding \,
oops, thanks! Altough i shuld note that it's sort of changed over time
from recommended to "may" - but see e.g. for the rationale (Doug
Crockford
No, Liam, that is a misunderstanding - it *may* be escaped by a preceding \,
like a handful of other characters, but there is no obligation. However, you
are right in pointing out (implicitly) that my assertion was wrong that the
information content is changed by the escaping: it is not, they
On Sun, 2021-03-21 at 09:42 +, Hans-Juergen Rennau wrote:
>
> PPS: Please do not even dream of thinking about considering or not
> excluding to change the parsers behaviour which leaves the slash as
> it is - otherwise you cannot use JSON information in XML
> representation without wiggling
Thank you very much, Gerrit, interesting! But I am unwilling to get tangled up
(in blue, like Bob Dylan, or not), I want clarity. It could not be simpler: I
want to preserve information content, character for character: (a) when parsing
JSON syntax into an XML node tree, (b) when serializing
4 matches
Mail list logo
