Sorry about the error: In this case, you must set IT via meta tag to avoid it.
-- João Cândido de Souza Neto ""João Cândido de Souza Neto"" <j...@consultorweb.cnt.br> escreveu na mensagem news:16.27.07419.e0e5e...@pb1.pair.com... > 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" <cbo...@hotmail.com> escreveu na mensagem > news:aanlktimbfbgunifhthztp+2jnhzgmo8uqvwydq4vd...@mail.gmail.com... >>> 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
