3 ms·
Wait, this can't be right for purely technical reasons: what would this to do a string containing vertical tab characters? Such strings are illegal in XML. I
by dyoo1979 12y ago
Wait, this can't be right for purely technical reasons: what would this to do a string containing vertical tab characters?
Such strings are illegal in XML. I see nothing in the "JSONx Conversion Rules" that addresses the problem that the strings representable in XML are a smaller set than those in JSON.
[edit] Yup, confirmed. The documentation says: "The \b (backspace) and the \f (form feed) characters are not supported in XML and, subsequently, are not supported in JSONx." So not only does this JSON->XML thing seem obtuse, but it's partial.
I wrote a rant about this point a few days ago. Seems more well timed than I had hoped. https://plus.google.com/117593568781545916065/posts/ViNzo5JjbRf https://plus.google.com/117593568781545916065/posts/ViNzo5Jj...
- dragonwriter 12y ago> So not only does this JSON->XML thing seem obtuse, but it's partial. If it wasn't partial, it would be useful -- allowing existing XML tools to easily consume and/or produce JSON tools by applying a JSON -> XML on input and/or XML -> JSON on output would be valuable. But when the conversion is restricted to an XML-1.0-compatible-subset of JSON, the value drops considerably.