- From: <bugzilla@jessica.w3.org>
- Date: Mon, 15 Jun 2015 18:51:29 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28812 --- Comment #3 from Josh Spiegel <josh.spiegel@oracle.com> --- What do you think about changing the unescape=false feature such that it doesn't unnecessarily preserve escape sequences for valid XML characters? Here are a few of concrete ideas: Option 1: * Change the meaning of unescape such that when unescape=false, only non-XML characters are converted to escape sequences, regardless of how the character was modeled in the JSON. Option 2: * Remove the unescape parameter * Allow setting fallback=xs:string("escape") so that it will convert non-XML characters to JSON escape sequences Option 3: * Remove the unescape parameter * Have the default fallback behavior be to insert JSON escape sequences for non-XML characters * Fallback can still be set to function($s){"�"} to get the current default behavior -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 15 June 2015 18:51:31 UTC