- From: <bugzilla@jessica.w3.org>
- Date: Mon, 15 Jun 2015 17:36:49 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28812 --- Comment #2 from Josh Spiegel <josh.spiegel@oracle.com> --- > it should say that if unescape=false is specified, escaped characters will be retained in escaped form, and unescaped characters will be converted to escaped form if they are not valid XML characters. If the goal of unescape=false is just to prevent non-XML characters then why doesn't it just do that? Why does it also preserve XML characters that happened to be escaped in the JSON? In the case of valid XML characters, this seems like a meaningless distinction and is analogous to preserving character references and CDATA sections in XDM. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 15 June 2015 17:36:52 UTC