SPUG: ajax character encoding issue solved, but WHY?

C.J. Adams-Collier cjac at colliertech.org
Wed Jun 10 12:49:48 PDT 2009

perhaps it didn't know you wanted to decode it as utf-8?


On Wed, 2009-06-10 at 12:40 -0700, Phil Mitchell wrote:
> I solved the character encoding issue that I wrote about earlier, 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 them being interpreted as ISO-8859-1, but I
> could not figure out why the browser was interpreting that way. All my
> data is handled as UTF-8.
> The problem was fixed by calling Encode::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 represents as "internal" utf8. But why should this be
> necessary?
> -- 
> ==========================
> http://www.bikewise.org
> 2People citizen's network for climate action: http://www.2people.org
> Greater Seattle Climate Dialogues: http://www.climatedialogues.org
> ==========================
> _____________________________________________________________
> Seattle Perl Users Group Mailing List
>      POST TO: spug-list at pm.org
> SUBSCRIPTION: http://mail.pm.org/mailman/listinfo/spug-list
>     MEETINGS: 3rd Tuesdays
>     WEB PAGE: http://seattleperl.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://mail.pm.org/pipermail/spug-list/attachments/20090610/3ae5d361/attachment.bin>

More information about the spug-list mailing list