What to do if php reads garbled characters from the database

Solution to php reading garbled database code: 1. Modify the file encoding; 2. Declare the encoding in the HTML code HEAD; 3. Modify the database connection encoding; 4. Set the page declaration encoding and database connection encoding to consistent.

The operating environment of this tutorial: Windows 7 system, PHP version 5.6. This method is suitable for all brands of computers.

Recommended: "PHP Video Tutorial"

php database reads garbled characters and explains the reason

Generally speaking, garbled characters There are two reasons for this. First, the encoding (charset) setting is wrong, causing the browser to parse it with the wrong encoding, resulting in a messy "heavenly book" filling the screen. Second, the file is opened with the wrong encoding and then saved. For example, a text file was originally encoded in GB2312, but it was opened and saved in UTF-8 encoding. To solve the above garbled code problem, you first need to know which aspects of development involve encoding:

1. File encoding: refers to the encoding in which the page file (.html, .php, etc.) itself is saved. . Notepad and Dreamweaver will automatically recognize the file encoding when opening the page, so there will be less problems. However, ZendStudio does not automatically recognize the encoding. It will only open the file in a certain encoding according to the configuration of the preferences. If you accidentally open the file with the wrong encoding while working, garbled characters will appear as soon as you save it after making the modification.

2. Page declaration encoding: In the HTML code HEAD, you can use "meta http-equiv="Content-Type" content="text/html; charset="XXX" /" (this sentence must be Written in front of "TItle" An encoding.

3. Database connection encoding: refers to which encoding is used to transmit data to the database when performing database operations. It should be noted here that it should not be confused with the encoding of the database itself. For example, the internal default of MySQL is laTIn1 Encoding, that is to say, Mysql stores data in laTIn1 encoding, and data transmitted to Mysql in other encodings will be converted into latin1 encoding.

If you know where encoding is involved in WEB development, you will know Reasons for garbled codes: The above three encoding settings are inconsistent. Since most of the various encodings are compatible with ASCII, English symbols will not appear, and Chinese characters will be unlucky. The following are some common error situations and solutions:

　1. The database uses UTF8 encoding, and the page declaration encoding is GB2312. This is the most common cause of garbled characters. At this time, the direct SELECT data in the PHP script will be garbled. You need to use it before querying:

　mysql_query（”SET NAMES GBK“）;
　　或mysql_query（”SET NAMES GB2312“）;

To set the MYSQL connection encoding, ensure that the page declaration encoding is consistent with the connection encoding set here (GBK is an extension of GB2312). If the page is UTF-8 encoded, you can use:

mysql_query（”SET NAMES UTF8“）;

Note that it is UTF8 instead of the commonly used UTF-8. If the encoding declared by the page is consistent with the internal encoding of the database, the connection encoding does not need to be set.

Note: In fact, the data input and output of MYSQL is more complicated than mentioned above. Some, MYSQL configuration file my.ini defines two default encodings, namely default-character-set in [client] and default-character-set in [mysqld] to set the default client connection and database respectively. The encoding used internally. The encoding we specified above is actually the command line parameter character_set_client when the MYSQL client connects to the server, to tell the MYSQL server what encoding the client data received is, instead of using the default encoding.

　2. The page declaration encoding is inconsistent with the encoding of the file itself. This rarely happens, because if the encoding is inconsistent, what the artist sees in the browser when creating the page is garbled code. More often, some small bugs are modified after release, so as to Caused by incorrect encoding when opening the page and then saving it. Or you use some FTP software to directly modify files online, such as CuteFTP. Due to incorrect software encoding configuration, the wrong encoding is converted.

3. Some friends who rent virtual hosts still have garbled codes even though the above three encodings are set correctly. For example, if the web page is encoded in GB2312, it is always recognized as UTF-8 when opened by browsers such as IE. The HEAD of the web page has already stated that it is GB2312. After manually changing the browser encoding to GB2312, the page displays normally. The reason is that the server Apache sets the global default encoding of the server and adds AddDefaultCharset UTF-8 in httpd.conf. At this time, the server will first send the HTTP header to the browser, and its priority is higher than the encoding declared in the page. Naturally, the browser will recognize it incorrectly. There are two solutions. Administrators should add AddDefaultCharset GB2312 to the configuration file of their own virtual machine to override the global configuration, or configure it in .htaccess in their own directory.

For more programming related knowledge, please visit: Programming Video! !

The above is the detailed content of What to do if php reads garbled characters from the database. For more information, please follow other related articles on the PHP Chinese website!