Home > Article > Backend Development > PHP page encoding declaration method header or meta encoding
php page is gbk encoded
php page is big5 encoded
Usually the above code is placed on the home page of the php page. The difference between using header or meta to implement PHP page encoding 1. Page encoding 1. Use tag to set page encoding The purpose 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 (different from mysql, which 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 belongs to html information and is just a statement. It works to indicate 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 tag. If you compare it with 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 so? Then we have to talk about the difference between https header and html information: The https header is a string sent by the server before sending html information to the browser using the http protocol. Because the meta tag belongs to html information, the content sent by header() reaches the browser first. The popular point is that header() has a higher priority than meta (I don’t know if this can be said). When adding a php page with both header("content-type:text/html; charset=xxx") and , the browser will only recognize the former http header and not the 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? This is the reason why we want to talk about apache next. 3. adddefaultcharset In the conf folder in the root directory of apache, there is the entire apache configuration document httpd.conf. Open httpd.conf with a text editor. Line 708 (may be different in different versions) contains adddefaultcharset xxx, where xxx is the encoding name. The meaning of this line of code: Set the character set in the https header of the web page file in the entire server to your default xxx character set. Having this line is equivalent to adding a header ("content-type: text/html; charset=xxx") to each file. Now you can understand why the browser always uses gb2312 even though the meta setting is utf-8. If there is a 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. Summary: Sorting
If you are a web programmer, add a header ("content-type: text/html; charset=xxx") to each of your pages to ensure that it can be displayed correctly on any server and is highly portable. As for the adddefaultcharset xxx sentence, whether it should be commented or not is a matter of opinion. Anyway, I commented it out, but I also need to write header() when writing a page, so that it can be displayed normally on the server. 2. Database encoding 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=gb2312 in the web page , 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"). 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 that "future information from this client will use 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.) php page coding unified MySQL database encoding, HTML page encoding, and the encoding of the PHP or HTML file itself must all be consistent. 1. MySQL database encoding: Specify the encoding (such as gbk_chinese_ci) when creating the database. Do not specify the encoding when creating data tables, creating fields, and inserting data. The encoding of the database will be automatically inherited. When connecting to the database, there is also coding, which can be executed after connecting to the database.
2. The encoding of the html page refers to the setting of this line: 3. Encoding of the php or html file itself: Use editplus to open the php file or html file. When saving, select the encoding. If the database and page encoding is gbk, select ansi for the encoding here; If the database and page encoding are utf-8, select utf-8 here as well. 4. Note that the data passed in JavaScript or Flash is encoded in UTF-8. If the database and page encoding is GBK, it must be transcoded and then written to the database.
5. In the PHP program, you can add a line to specify the encoding of the PHP source program:
|