Open GoogleCodeExporter opened 9 years ago
I had to upgrade antisamy from 1.4.4 recently to use the directive
entityEncodeIntlChars for i18n . Thats when I observed this bug .This turns a
valid json to a invalid json .
Original comment by anshalm...@gmail.com
on 18 Feb 2014 at 5:24
[deleted comment]
Try to change the formatOutput directive in the policy to false (default seems
to be true)
<directive name="formatOutput" value="false" /><!-- default: true -->
I'd argue that the default should be false, as I spent a good amount of time
trying to figure out this error too and I don't believe antisamy should modify
this for most cases.
Original comment by matt...@longsight.com
on 4 Jun 2014 at 6:43
Original issue reported on code.google.com by
anshalm...@gmail.com
on 18 Feb 2014 at 5:22