The third step is to define your language encoding, similar to this:
In order to be correctly interpreted by the browser and through the universal Code verification, all XHTML documents must declare the encoding language they use, we generally use gb2312 (Simplified Chinese), the production of multi-lingual pages may also be used in Unicode, iso-8859-1, etc., according to your needs to define.
This is usually the way to define it. However, it is to be added that XML documents are not encoded in such a way that the XML is defined as follows:
You can see similar statements in the first line of Macromedia.com's homepage code, which is also the recommended definition method for the user. So why don't we just take this approach? The reason is that some browsers have imperfect support for standards, and cannot correctly understand such definitions, such as ie6/windows. So under the current transition scenario, we still recommend the use of meta-methods. Of course, you can write both of these methods.
Look at the source code of the site, you will find the language coding definition of the place more than one sentence:
This is written for older browsers to ensure that the pages are interpreted correctly by various browsers.
Note: At the end of the statement above, you see a slash "/", which differs from our previous HTML4.0 code. The reason is that the XHTML syntax rules require that all identities have to start and end. such as and,
And
, for an unpaired identity, ask for a space at the end of the logo, followed by a "/". For example
Written
, write, add a space reason is to avoid the code connected to the browser is not recognized.