Are you setting the charset in your html head? If not, its using the charset set in your browser, which can be different from one to another. In this case, you must set if via meta tag to avoid it. -- João Cândido de Souza Neto "Christoph Boget" <cboget@xxxxxxxxxxx> escreveu na mensagem news:AANLkTimbfbgUnifhThZTP+2JNhZgmO8UQvwyDQ4vdu5k@xxxxxxxxxxxxxxxxx >> http://www.w3.org/TR/html4/charset.html >> I hope it can help you. >> PS: json_decode works only in utf8. > > I understand charsets. I understand the difference between the > charsets. What I don't understand is how json_encode() is taking the > *exact same input* and behaving differently (breaking in one case, > working in another) depending on the browser being used. And taking > your statement that json_encode() works only in utf-8 as a given, how > can I guard against the different behaviors on the backend, where > json_encode() is getting executed. Should I do some kind of header > sniffing prior to every call to json_encode() and massage the data > accordingly depending on what I find? That seems somewhat excessive. > But based on what you are saying and based on what I'm witnessing, it > seems like there is no other way around that. > > thnx, > Christoph -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
