Path: csiph.com!weretis.net!feeder4.news.weretis.net!feeder5.news.weretis.net!news.solani.org!.POSTED!not-for-mail
From: "Christoph M. Becker" <cmbecker69@arcor.de>
Newsgroups: comp.lang.php
Subject: Re: Problem between PHP and JavaScript with json
Date: Wed, 3 May 2017 13:37:24 +0200
Organization: solani.org
Lines: 26
Message-ID: <oecfde$m79$1@solani.org>
References: <oea1nl$rh4$1@shakotay.alphanet.ch> <oea36s$2ku$1@solani.org> <oea8h6$9hp$1@shakotay.alphanet.ch> <oea98u$7ca$1@solani.org> <oeae5t$pa0$1@shakotay.alphanet.ch> <oeag13$cbq$1@solani.org> <oebopb$i98$1@shakotay.alphanet.ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Trace: solani.org 1493811438 22761 eJwFwYEBwCAIA7CXYLQVzkHU/09YwpBrFkSBj8+ZLWyL2llr/KTBumjH6D3CIGszeTvqfvYDA6EQQA== (3 May 2017 11:37:18 GMT)
X-Complaints-To: abuse@news.solani.org
NNTP-Posting-Date: Wed, 3 May 2017 11:37:18 +0000 (UTC)
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
In-Reply-To: <oebopb$i98$1@shakotay.alphanet.ch>
X-NNTP-Posting-Host: eJwFwQkRwEAIBDBL5YAF5Ozw+JfQxBWCDoPD/PxkiazCCb8SrTDvwT4lTaZTxzX2UZLEnP4RohED
Cancel-Lock: sha1:SDFD+Qh2G8IEyvVAsTMTypZoSuE=
X-User-ID: eJwNysEBwCAIBMGWorAXKYeg9F+CmfdgGqrXhZym06Zyhu0P2ruU50A8Cq38U7LlxT6LMQ27G7MQsA==
Content-Language: de-DE
Xref: csiph.com comp.lang.php:17400

On 03.05.2017 at 07:11, Une Bévue wrote:

> Le 02/05/2017 à 19:35, Christoph M. Becker a écrit :
>
>> Hm, that is correct for ISO-8859-1,
> 
> the code is also US-ASCII then UTF-8 for those caracters (common to
> US-ASCII, UTF-8 and ISO-8859-1).

Of course, you're right.  Sorry for the noise.

>> for instance.  Does the JSON
>> response specify an appropriate Content-Type header including the
>> correct charset?
> 
> yes :
> 
> header('Content-Type: application/json; charset=utf-8');

That appears to be correct.

Don't know for what else to look.  Maybe you should consider asking in
JavaScript/ECMAScript related newsgroup.

-- 
Christoph M. Becker