Summary and analysis of solutions to Chinese garbled characters in PHP_PHP tutorial

1. The first is the encoding of the PHP web page
1. The encoding of the php file itself and the encoding of the web page should match
a. If you want to use gb2312 encoding, then php should output the header: header(“Content-Type: text /html; charset=gb2312″), add to the static page. The encoding format of all files is ANSI and can be opened with Notepad. , save as and select encoding as ANSI, overwriting the source file.
b. If you want to use utf-8 encoding, then php should output the header: header(“Content-Type: text/html; charset=utf-8″), and add 3. PHP is related to the operating system
The encoding of Windows and Linux is different. In the Windows environment, when calling PHP functions, if the parameters are utf-8 encoding, errors will occur, such as move_uploaded_file(), filesize() , readfile(), etc. These functions are often used when processing uploads and downloads. The following error may occur when calling:
Warning: move_uploaded_file()[function.move-uploaded-file]: failed to open stream : Invalid argument in …
Warning: move_uploaded_file()[function.move-uploaded-file]:Unable to move ” to ” in …
Warning: filesize() [function.filesize]: stat failed for … in …
Warning: readfile() [function.readfile]: failed to open stream: Invalid argument in ..
Although these errors will not occur when using gb2312 encoding in a Linux environment, the file name after saving will be garbled. As a result, the file cannot be read. In this case, you can first convert the parameters into the encoding recognized by the operating system. For encoding conversion, you can use mb_convert_encoding (string, new encoding, original encoding) or iconv (original encoding, new encoding, string). After processing, The saved file name will not be garbled, and the file can be read normally, allowing uploading and downloading of files with Chinese names.
In fact, there is a better solution, which is to completely disconnect from the system, so there is no need to consider the encoding of the system. You can generate a sequence of only letters and numbers as the file name, and save the original name with Chinese characters in the database. In this way, there will be no problem when calling move_uploaded_file(). When downloading, you only need to change the file name to the original name with Chinese characters. Chinese name. The code to implement downloading is as follows
header(”Pragma: public”);
header(”Expires: 0″);
header(”Cache-Component: must-revalidate, post-check=0, pre -check=0″);
header(”Content-type: $file_type”);
header(”Content-Length: $file_size”);
header(”Content-Disposition: attachment; filename =”$file_name””);
header(”Content-Transfer-Encoding: binary”);
readfile($file_path);
$file_type is the type of file, $file_name is the original name, $file_path is the address of the file saved on the service.
4. Let’s summarize why garbled characters appear
Generally speaking, there are two reasons for the occurrence of garbled characters. The first is due to the incorrect encoding (charset) setting, which causes the browser to parse with the wrong encoding, resulting in a messy screen. The second is that the file is opened in the wrong encoding and then saved. For example, a text file was originally encoded in GB2312, but was opened in UTF-8 encoding and then saved. 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, 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 that the web page uses What encoding is used? Currently, XXX mainly uses GB2312 and UTF-8 in Chinese website development.
3. Database connection encoding: refers to which encoding is used to transmit data to the database when performing database operations. This is required here. Be careful not to confuse it with the encoding of the database itself. For example, MySQL's internal default encoding 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.
Know. After understanding where encoding is involved in WEB development, we also know the reason for the garbled code: 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.
5. Fight 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 is garbled. You need to use it before querying: mysql_query("SET NAMES GBK"); to set the MYSQL connection encoding and ensure that the page declaration encoding is consistent with the connection encoding set here (GBK is GB2312 extension). 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. It is not necessary to set the connection encoding.
Note: In fact, the data input and output of MYSQL is more complicated than what is mentioned above. There are 2 default encodings defined in the MYSQL configuration file my.ini, which are default - in [client]. character-set and default-character-set in [mysqld] respectively set the encoding used by the client connection and the database 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 used 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, the artist will create the page. What you see in the browser is garbled characters. Most of the time it is caused by fixing some minor bugs after publishing, 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.

Summary: In a word, the best and fastest way to solve the Chinese garbled code in PHP is to make the coding declared by the page consistent with the internal coding of the database. If the page number applied for the page is inconsistent with the internal coding of the database, set Set the connection code, mysql_query("SET NAMES XXX"); XXX is the connection code. This will definitely solve the problem of garbled characters.

http://www.bkjia.com/PHPjc/320460.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/320460.htmlTechArticle1. The first is the encoding of the PHP web page 1. The encoding of the php file itself and the encoding of the web page should match a. If you want to use gb2312 encoding, then php should output the header: header(“Content-Type: text/html;...