And thank you for the chance to not look like a dummy for a change. :)
On Jan 9, 2008, at 1:32 PM, Daniel McBrearty wrote:
Thanks Ashley, that did indeed fix the JSON problem!
(wish I'd remembered to write a test *before* I fixed it like this
though ;-)
cheers
Daniel
On Jan 7, 2008 9:28 PM, Ashley Pond V <[EMAIL PROTECTED]> wrote:
This may or may not be germane: try installing JSON::XS and updating
your JSON and JSON::Any. JSON::XS is one of, if not the, fastest
serializers in all data classes and its utf8 handling is better. JSON
now, IIRC, calls it if it's present instead of its older Perl
version.
-Ashley
On Jan 7, 2008, at 7:57 AM, Daniel McBrearty wrote:
Data is actually sent in URI encoded utf8 (looks like "ab%C3%A7
...."), which is fine. The string is then picked up, decoded and
stored in the db just fine. The problem is that what gets sent back
the other way (via Catalyst::View::JSON ) is not getting encoded. I
don't know quite why just now (according to the docs it should do).
Manually adding the Encode::encode_utf8( $result ) step fixes it for
now. I may try peeking to see why it doesn't get handled by the
View.
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
