2011/10/9 Oliver Gorwits oli...@cpan.org:
On 07/10/2011 10:21, jul@gmail.com wrote:
I have installed and ran successfully the AutoCRUD plugin, I set up a
mysql database tables to use UT8 charset, the charset in the ajax
requests is utf-8, everything seems correct, except the data in the
On 07/10/2011 16:22, jul@gmail.com wrote:
Only simple catalyst.pl calls, a simple sqlite3 database, using
default debian environnement.
I have added a line in the sqlite database with éè, and you can see
the result...
Thanks for testing to confirm (or not) if you have the same behaviour.
On 07/10/2011 10:21, jul@gmail.com wrote:
I have installed and ran successfully the AutoCRUD plugin, I set up a
mysql database tables to use UT8 charset, the charset in the ajax
requests is utf-8, everything seems correct, except the data in the
grids are double encoded, that means é
Hi,
I have installed and ran successfully the AutoCRUD plugin, I set up a
mysql database tables to use UT8 charset, the charset in the ajax
requests is utf-8, everything seems correct, except the data in the
grids are double encoded, that means é instead of é.
I am pretty sure that the data in
I have hacked around this AutoCRUD JSON view, and end up with a solution
It is probably a bad solution, as I can't imagine that
Catalyst::JSON::View is wrong, but I wonder what is the correct way to
do it.
In terms of AutoCRUD, I can't offer a lot more, only to add I'm very
pleased that you
As I sayed in one another thread, I have developped a simple Catalyst
application to test this utf-8 bug. You can download it at
http://gilles.tk/TestUTF8-0.01.tar.gz
Only simple catalyst.pl calls, a simple sqlite3 database, using
default debian environnement.
I have added a line in the sqlite
JSON will try to encode in UTF-8 format and if the data is already in UTF-8,
most likely it will be double encoded.
This could be fixed in two ways:
1) when loading your UTF-8 data, convert it to perl's internal encoding with:
use Encoding qw(decode_utf8);
my
