Detailed explanation of specific solutions to garbled PHP pages_PHP Tutorial

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, and save it after making the modification, garbled characters will appear ( I feel it deeply).

2. Page declaration encoding: In the HTML code HEAD, you can use to tell the browser What encoding is used for the server web page? Currently, XXX mainly uses GB2312 and UTF-8 in Chinese website development.

3. Database connection encoding: refers to which encoding is used when performing database operations. When transmitting data from the database, you need to be careful not to confuse it with the encoding of the database itself. For example, the default encoding within MySQL is latin1 encoding, which means that Mysql stores data in latin1 encoding. Data transmitted to Mysql in other encodings will be converted into latin1. Encoding.

Knowing where encoding is involved in WEB development, you will also know the reason why the PHP page is garbled: the above three encoding settings are inconsistent, because most of the various encodings are ASCII compatible, so English symbols will not appear, but Chinese characters are out of luck. Here 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 PHP page will be garbled when directly selecting data in the PHP script. You need to use:

mysql_query("SET NAMES GBK"); to set the MYSQL connection encoding to ensure that the page declares the encoding. It 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 on the page is consistent with the internal encoding of the database, you do not need to set the connection encoding.
Note: In fact, the data input and output of MYSQL is more complicated than mentioned above. There are 2 defined in the MYSQL configuration file my.ini. The default encoding is the default-character-set in [client] and the default-character-set in [mysqld] to set the encoding used by the client connection and the database internally respectively. The encoding we specified above is actually. The command line parameter character_set_client when the MYSQL client connects to the server tells the MYSQL server what encoding the client data received is used instead of 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 creating the page is garbled code. More often, it is caused by fixing some minor bugs after publishing, opening the page with 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 PHP pages 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.

http://www.bkjia.com/PHPjc/446273.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/446273.htmlTechArticle1. File encoding: refers to the encoding of the page file (.html, .php, etc.) itself To save. Notepad and Dreamweaver will automatically recognize the file encoding when opening the page, so it is less likely to...