is JSON data garbled under non-UTF-8 encoding? The authority of the next

is JSON data garbled under non-UTF-8 encoding? The authority of the next

Reply to discussion (solution)

It's not going to match your file code.

So the argument to Json_encode () must be utf-8 encoded, otherwise the null character or null will be obtained.

Handwriting is not, just a text, but the program generated is hard to say, encoding and decoding depends on the ability of the JSON control

This depends on the content of the data contained in your JSON data, if it contains a few language content, there will be garbled. Even with double quotes, the contents are garbled. I've come across it before.

You need to encode the parameters when passing them. I remember meeting the questions you said.

Garbled is just a subjective feeling
When you watch Utf-8 content in a GBK environment, watch GBK content in a utf-8 environment, and watch content in Chinese in a Western language environment, you see symbols that you're unfamiliar with, so you're saying that there are garbled characters. But in fact, that's what it's supposed to show in these environments, but you don't know it.

So, if you want to show some text to the public, use a context that fits the crowd. Instead of letting the public get used to you.

