how to avoid encoding problems using ajax-json and php-postrgesql

Question

i have problems with encoding when using json and ajax. chrome and ie encode umlauts as unicode when jsonifying, firefox and safari returning those utf-8 escaped umlauts like ¼Ã.

where is the best place to give all the same encoding? js / php-get or by writing them to the database.

and i think the next trouble is, when i reload the utf-8 encoded stuff from the db, and write them to the browser and then rewrite them to the db, again via ajax-request a get a real chaos?

can i avoid the chaous? can i handle the encoding in an easy way? pls. help :-)

very important is to also provide security

It's not clear what you're doing from your question and what went wrong. Perhaps some snippets would help. — Artefacto
– Artefacto, Commented Aug 31, 2010 at 14:39
i even didn't say something went wrong ;-). the thing is, that the browsers jsonify machines giving back strings with different characters for the same input, and the question is: how to handle that, best practice. i think code wont make the problem easier, but one could stick to my code and resolve the problem for my special case - the thing is i am searching for a more reuseable solution. — helle
– helle, Commented Aug 31, 2010 at 14:56
You can set UTF-8 encoding in php.ini and if you are using Apache2 you can use the directive AddDefaultCharset with UTF-8 as — John P
– John P, Commented Oct 27, 2010 at 16:12

Dominique · Accepted Answer · 2010-08-31 14:30:22Z

1

You must set everything to UTF-8, this means :

Database collation

Table collation

Field collation

Your coding software (example notepad++) encryption.

answered Aug 31, 2010 at 14:30

Dominique

9081 gold badge7 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Artefacto Over a year ago

Collation is not particularly relevant here, and you certainly don't set encryption in notepad++.

misterte · Accepted Answer · 2010-10-05 19:38:32Z

0

Had a similar problem. Maybe you are actually interpreting encoding the wrong way, clientwise. Try setting the frontend encoding before your queries.

<?php
$connection = pg_pconnect("dbname=data");
pg_set_client_encoding($connection, "encoding goes here"); //check enconding aletrnatives on PostgreSQL
$result = pg_query($connection, "SELECT whatever FROM wherever");
//and so on...
?>

I'm a newbie, but it may help. Also won't affect security in anyway if you are already protected against db injection.

Cheers

answered Oct 5, 2010 at 19:38

misterte

1,0071 gold badge12 silver badges21 bronze badges

Collectives™ on Stack Overflow

how to avoid encoding problems using ajax-json and php-postrgesql

2 Answers 2

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related