On Fri, Aug 26, 2011 at 7:32 AM, Dave Howorth
dhowo...@mrc-lmb.cam.ac.uk wrote:
There's a mail from Jim Spath in the pipermail archive that didn't make
it to the other archives (or to my inbox). It hasn't had any answers so
I'd suggest he repost it.
Thanks Dave!
Here it is:
So it turns out
James Spath wrote:
FWIW, IMHO the issue is better fixed in JSON::XS et al than in
Catalyst::Action::Serialize::JSON. I don't see why JSON can't always
encode the two problematic characters.
I suppose it could be in JSON::XS .. but JSON::XS is doing nothing
wrong ... the two characters are
