Bug #58483 for Catalyst-Plugin-AutoCRUD: Encoding on AJAX interface not allowing non-English chars :(

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Sawyer, On 22/06/2010 09:45, Sawyer X via RT wrote: Show quoted text
Okay that's a pity - but thanks for testing and letting me know. Show quoted text
Yes having access to the data would be very useful and speed things up for me. I won't have time to look at it this week, but next week I will have time. If you want to mail me details outside of this RT system, use my address <oliver.gorwits@oucs.ox.ac.uk>. regards, - -- Oliver Gorwits, Network and Telecommunications Group, Oxford University Computing Services -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwgeO4ACgkQ2NPq7pwWBt63GACffdQk00dd9GrDsN4exK/9Uu3T D40An1Lr+bmLMx8R52Gz+hG+0rUnFZKm =cwoA -----END PGP SIGNATURE-----

I have just been emailed the following from "shirirulestheworld" (apologies for the correspondence on this ticket but RT.cpan does not seem to permit plain ticket comments): Hi, Thank you for this great software! I was having a problem with japanese not being displayed properly via the extjs interface. It seems that the package needs to set the encoding latin1 and use JSON::XS to avoid any problems. Perhaps JSON::PP is find too though. But using JSON::Any might switch to JSON::Sticky which might have encoding troubles. utf8 seems to not work but latin1 works just fine... Anyhow, the fix below allowed me to display Japanese properly. Hope it can help: package Catalyst::Plugin::AutoCRUD::View::JSON; use strict; use warnings FATAL => 'all'; use base 'Catalyst::View::JSON'; use JSON::XS (); sub encode_json { my($self, $c, $data) = @_; my $encoder = JSON::XS->new->latin1->allow_nonref; $encoder->encode($data); } __PACKAGE__->config( expose_stash => 'json_data', ); 1;