What to do if php reads Chinese garbled characters from the database

Solution to php reading garbled Chinese characters from the database: 1. Use the "mysql_query" function to set the MYSQL connection encoding and ensure that the page declaration encoding is consistent with the connection encoding set here; 2. Use FTP software to modify it directly online file; 3. Add "AddDefaultCharset GB2312" to the virtual machine of the configuration file to override the global configuration, or configure it in .htaccess of the directory.

The operating environment of this tutorial: Windows 10 system, PHP version 8.1.3, Dell g3 computer.

The reason why php reads Chinese garbled characters from the database:

Generally speaking, there are two reasons for the occurrence of garbled characters. The first is due to the incorrect encoding (charset) setting. The browser parses it with the wrong encoding, resulting in a messy "Book of Heaven" all over the screen. Secondly, the file is opened with the wrong encoding and then saved. For example, a text file was originally encoded in GB2312, but opened in UTF-8 encoding. Save again. 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 ones Error situation and solution:

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 data directly SELECTed in the PHP script is Garbled code, you need to use:

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

before querying to set the MYSQL connection encoding to 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 If so, you can use:

mysql_query（”SET NAMES UTF8“）;

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

Note: Facts The data input and output of MYSQL is more complicated than what is mentioned above. There are two default encodings defined in the MYSQL configuration file my.ini, which are default-character-set in [client] and default-character-set in [mysqld]. set to set the encoding used by the client connection and the database internally by default. The encoding we specified above is actually the command line parameter character_set_client when the MYSQL client connects to the server, which tells 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 you see in the browser when you create the page will be garbled. More often than not, it is caused by fixing some minor bugs after release, opening the page in the wrong encoding 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.

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