On Fri, Jun 19, 2009 at 6:23 AM, wrote:
>
> The problem was fixed by calling utf8::decode on the data prior to sending
> back via ajax. BUT WHY?
>
> I am using the JSON view to render ajax responses, and it sets the charset
> header correctly to UTF-8. Of course, even when you decode, perl still
On Fri, Jun 19, 2009 at 12:52 AM, Moritz Onken wrote:
>
> Am 19.06.2009 um 06:23 schrieb seasproc...@gmail.com:
> What is the encoding of the web page that issues that ajax request?
charset=UTF-8
>
> Does this occur on different browser as well?
yes (tested on FF and IE)
>
> I had similar pr
Am 19.06.2009 um 06:23 schrieb seasproc...@gmail.com:
I had a character encoding issue that I finally solved, but I don't
understand why the fix works. I'm hoping someone can explain this to
me!
The issue was that non-ascii chars were appearing as junk BUT only
when retrieved via ajax ca
I had a character encoding issue that I finally solved, but I don't
understand why the fix works. I'm hoping someone can explain this to me!
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
