Re: [Catalyst] Re: ajax character encoding issue solved, but WHY?

2009-06-29 Thread seasprocket
On Tue, Jun 23, 2009 at 1:28 AM, Aristotle Pagaltzis pagalt...@gmx.dewrote: * seasproc...@gmail.com seasproc...@gmail.com [2009-06-23 03:00]: Thanks for your suggestion, but I'm pretty sure that the data is not getting encoded twice. C::V::JSON tests the data before it encodes (

[Catalyst] Re: ajax character encoding issue solved, but WHY?

2009-06-23 Thread Aristotle Pagaltzis
* seasproc...@gmail.com seasproc...@gmail.com [2009-06-23 03:00]: Thanks for your suggestion, but I'm pretty sure that the data is not getting encoded twice. C::V::JSON tests the data before it encodes ( Encode::is_utf8() ) and only encodes if this test is true. This test only passes if the

[Catalyst] Re: ajax character encoding issue solved, but WHY?

2009-06-20 Thread Aristotle Pagaltzis
* seasproc...@gmail.com seasproc...@gmail.com [2009-06-19 06:30]: The issue was that non-ascii chars were appearing as junk BUT only when retrieved via ajax calls. Otherwise, they displayed fine. The junk display was due to them being interpreted as ISO-8859-1, but I could not figure out why