Prev: Backtrace in fatal error?
Next: 'dl() is deprecated' Error in PHP5.2.3
From: "Jo�o C�ndido de Souza Neto" on 1 Sep 2010 10:25
In this case, you are right. It has nothing to do with the browser.

You�ll need a more detailed debug so you can see excatly what�s happening.

--
Jo�o C�ndido de Souza Neto

"Christoph Boget" <cboget(a)hotmail.com> escreveu na mensagem
news:AANLkTikcTht0nXz1hi0EzJ=i2M3716Wepd=DepPKedgo(a)mail.gmail.com...
>> Sorry about the error:
>> In this case, you must set IT via meta tag to avoid it.
>
> Ok, let's try this using a different approach. Consider the following
> pseudo-code:
>
> <?php
> $result = mysql_query( 'SELECT name, date FROM table WHERE field =
> "value"' );
> $array = array();
> while( $row = mysql_fetch_assoc( $result ))
> {
> $array[] = $row;
> }
>
> $string = json_encode( $array );
> ?>
>
> Why does the charset of the browser matter one whit to the value of
> either $row['name'] or $row['date'] such that it would break
> json_encode() in one case and not the other. Is it that PHP is taking
> the string which is returned as part of the result set and encoding it
> to match the charset passed in from the browser?
>
> thnx,
> Christoph
>
> * Disclaimer : the actual code (and data repository) I am using is
> slightly different from the above but is similar enough so that it's a
> valid representation


First  |  Prev  | 
Pages: 1 2 3
Prev: Backtrace in fatal error?
Next: 'dl() is deprecated' Error in PHP5.2.3