Comments on: JSON, Ajax, and UTF8

By: rodelMayo

rodelMayo — Tue, 20 Mar 2007 16:08:49 +0000

Another solution without using json is to convert UTF8 to a character encoding supported by your serverside scripting language. The problem is caused by javascript’s native encoding which is UTF8 not directly supported in some scripting languages. Strings submitted using ajax are UTF8 encoded. By converting the submitted data to ISO55891, you make the data understandable by your script and also safe for DB storage. Another thing I want to emphasize is when fetching remote information using AJAX. Remote information must be encoded back to UTF8 to make it compatible with javascript. ISO55891 is not the only encoding used by scripting languages, use whichever is applicable to your scripting language.

By: Pierre

Pierre — Fri, 13 Oct 2006 02:32:42 +0000

Maybe this is to late. But I had some issues with this a while ago, working with an old JSON-PHP. What version of JSON-PHP was this fixes?

By: moraes

moraes — Fri, 01 Sep 2006 13:55:13 +0000

It would be nice if you included a license notice on the code. Is it under GPL? LGPL? BSD?

But thanks anyway. It works perfectly and helped a lot. :-)

By: Ruturaj K. Vartak

Ruturaj K. Vartak — Wed, 12 Jul 2006 07:07:01 +0000

That was very helpful, indeed you’ve saved lot of my time :D

By: Noah Winecoff

Noah Winecoff — Fri, 07 Jul 2006 19:31:27 +0000

Thanks for the post! This will save me some time in the future.

By: Ryan Campbell

Ryan Campbell — Fri, 07 Jul 2006 15:58:41 +0000

Thanks for the heads up. I’ll give it a try.

By: Michal Migurski

Michal Migurski — Fri, 07 Jul 2006 01:45:09 +0000

The '\"' character combination problem was the result of a bug fixed in JSON-PHP just last week - if you download a fresh copy, it should no longer be an issue. By way of background, I was incorrectly detecting escaped and unescaped quotes in strings when preceded by backslashes, JSON's escape character.