On Tue, Jun 23, 2009 at 1:28 AM, Aristotle Pagaltzis wrote:
> * 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 t
* 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 data is decoded.
Au
On Sat, Jun 20, 2009 at 3:50 AM, Aristotle Pagaltzis wrote:
> * seasproc...@gmail.com [2009-06-19 06:30]:>
> > The problem was fixed by calling utf8::decode on the data prior
> > to sending back via ajax. BUT WHY?
>
> Looks like your code is broken and assumes bytes throughout; as
> long as all y
* 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 the browser was
> i
