The problem of Chinese encoding in PHP programming has troubled many people. The reason for this problem is actually very simple. Each country (or region) stipulates the character encoding set for computer information exchange, such as the extended ASCII code of the United States, and the Chinese GB2312-80, Japan’s JIS, etc. As the basis for information processing in this country/region, character encoding sets play an important role in unifying encoding. Character encoding sets are divided into two categories according to length: SBCS (single-byte character set) and DBCS (double-byte character set). In early software (especially operating systems), in order to solve the computer processing of local character information, various localized versions (L10N) appeared. In order to distinguish, concepts such as LANG and Codepage were introduced. However, due to the overlapping code ranges of various local character sets, it is difficult to exchange information with each other; the cost of independent maintenance of each localized version of the software is high. Therefore, it is necessary to extract the commonalities in localization work and process them consistently to minimize special localization processing content. This is also called internationalization (118N). Various language information is further standardized as Locale information. The underlying character set processed became Unicode, which contains almost all glyphs.
Most of the core character processing of software with international characteristics are now based on Unicode. When the software is running, the corresponding local character encoding settings are determined based on the locale/Lang/Codepage settings at that time, and local characters are processed accordingly. During the processing, it is necessary to convert between Unicode and local character sets, or even between two different local character sets with Unicode as an intermediate. This method is further extended in the network environment, and any character information at both ends of the network also needs to be converted into acceptable content according to the character set settings.
Character set encoding issues in databases
Popular relational database systems all support database character set encoding, which means that you can specify its own character set settings when creating a database, and the database data is stored in the specified encoding. When an application accesses data, there will be character set encoding conversion at entry and exit. For Chinese data, the database character encoding setting should ensure the integrity of the data. GB2312, GBK, UTF-8, etc. are all optional database character set encodings; of course we can also choose ISO8859-1 (8-bit), but we have to split a 16-bit Chinese character or Unicode before the application writes data. Divide it into two 8-bit characters. After reading the data, you need to merge the two bytes and identify the SBCS characters. Therefore, we do not recommend using ISO8859-1 as the database character set encoding. Not only does this not make full use of the character set encoding support of the database itself, but it also increases the complexity of programming. When programming, you can first use the management functions provided by the database management system to check whether the Chinese data is correct.
Before querying the database, the PHP program first executes mysql_query("SET NAMES xxxx"); where xxxx is the encoding of your web page (charset=xxxx). If charset=utf8 in the web page, then xxxx=utf8, if charset= in the web page gb2312, then xxxx=gb2312. Almost all WEB programs have a common code to connect to the database, which is placed in a file. In this file, just add mysql_query("SET NAMES xxxx").
SET NAMES shows what character set is used in the SQL statement sent by the client. Therefore, the SET NAMES 'utf-8' statement tells the server "future information from this client uses the character set utf-8". It also specifies the character set for the results that the server sends back to the client (for example, if you use a SELECT statement, it indicates what character set is used for the column values).
Commonly used techniques when locating problems
To locate Chinese encoding problems, the stupidest and most effective method is usually used - printing the internal code of the string after processing by the program you think is suspicious. By printing the internal code of a string, you can find out when Chinese characters are converted to Unicode, when Unicode is converted back to Chinese internal code, when one Chinese character becomes two Unicode characters, when a Chinese string is converted to A string of question marks, when did the high-order bits of the Chinese character string be truncated...
Using appropriate sample strings can also help distinguish the type of question. For example: "aaah aa?@aa" and other Chinese and English character strings with both GB and GBK characteristic characters. Generally speaking, English characters will not be distorted no matter how they are converted or processed (if you encounter them, you can try to increase the length of consecutive English letters).
Solve the garbled problem of various applications
1) Use tags to set page encoding
The function of this tag is to declare what character set encoding the client’s browser uses to display the page. xxx can be GB2312, GBK, UTF-8 ( Unlike MySQL, MySQL is UTF8) and so on. Therefore, most pages can use this method to tell the browser what encoding to use when displaying this page, so as to avoid encoding errors and garbled characters. But sometimes we will find that this sentence still doesn't work. No matter which xxx is, the browser always uses the same encoding. I will talk about this later.
Please note that it belongs to HTML information and is just a statement, which only indicates that the server has passed the HTML information to the browser.
2) header("content-type:text/html; charset=xxx");
The function of this function header() is to send the information in the brackets to the http header. If the content in the brackets is as mentioned in the article, the function is basically the same as the label. If you compare the first one, you will find that the characters are similar. But the difference is that if there is this function, the browser will always use the xxx encoding you requested and will never be disobedient, so this function is very useful. Why is this happening? Then we have to talk about the difference between http header and HTML information:
The http header is a string sent by the server before sending HTML information to the browser using the http protocol. The tag belongs to HTML information, so the content sent by header() reaches the browser first. The popular point is that header() has a higher priority (I don’t know if I can say this). If a PHP page has both header("content-type:text/html; charset=xxx") and header("content-type:text/html; charset=xxx"), the browser will only recognize the former http header and not meta. Of course, this function can only be used within PHP pages.
There is also a question left, why does the former definitely work, but the latter sometimes doesn’t work? This is the reason why we want to talk about Apache next.
3) AddDefaultCharset
In the conf folder of the Apache root directory, there is the entire Apache configuration document httpd.conf.
Use a text editor to open httpd.conf. Line 708 (different versions may be different) contains AddDefaultCharset xxx, where xxx is the encoding name. The meaning of this line of code: Set the character set in the http header of the web page file in the entire server to your default xxx character set. Having this line is equivalent to adding a line of header("content-type: text/html; charset=xxx") to each file. Now you can understand why the browser always uses gb2312 even though it is set to utf-8.
If there is header("content-type:text/html; charset=xxx") in the web page, the default character set will be changed to the character set you set, so this function will always be useful. If you add a "#" in front of AddDefaultCharset xxx, comment out this sentence, and the page does not contain header("content-type..."), then it is the meta tag's turn to take effect.
The above priority order is listed below:
.. header("content-type:text/html; charset=xxx")
.. AddDefaultCharset xxx
..
If you are a web programmer, it is recommended Add a header ("content-type: text/html; charset=xxx") to each of your pages, so that it can be displayed correctly on any server and has strong portability.
4) The default_charset configuration in PHP.ini:
The default_charset = "gb2312" in php.ini defines the default language character set of PHP. It is generally recommended to comment out this line and let the browser automatically select the language based on the charset in the web page header instead of making a mandatory requirement. This way, web services in multiple languages can be provided on the same server.
Conclusion
In fact, Chinese coding in PHP development is not as complicated as imagined. Although there are no fixed rules for locating and solving problems, and various operating environments are also different, the principles behind it are the same. Understanding the knowledge of character sets is the basis for solving character problems. However, with the changes in the Chinese character set, not only PHP programming, but also problems in Chinese information processing will still exist for some time.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
