Web|web Standard | code |web standard | Code The third step is to define your language code, similar to this: <meta http-equiv= "Content-type" content=; charset=gb2312 "/> In order to be properly interpreted by the browser and through the universal Code checksum, all XHTML documents must declare the encoding language they use, we generally use gb2312 (Simplified Chinese), the production of multi-language pages may also be in Unicode, Iso-8859-1 and so on, according to your need to define.
This is usually the way to define it. But to add that the XML document does not define language encoding in this way, XML is defined as follows:
? XML version= "1.0" encoding= "gb2312"?>
You can see similar statements in the first line of Macromedia.com's home code, which is also the recommended definition for the consortium. So why don't we just take this approach? The reason is that some browsers have imperfect support for standards, and do not correctly understand such definitions, such as ie6/windows. So under the current transition programme, we still recommend using meta methods. Of course, you can write both ways.
Look at this site source code, you will find that the language code definition of the place more than one sentence:
<meta http-equiv= "Content-language" content= "gb2312"/>
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 is different from our previous HTML4.0 code. The reason is that the XHTML grammar rules require that all identities must have a start and an end. For example, <body> and </body>, <p> and </p>, for a pair of identifiers, require a space in the logo and then a "/". For example <br> written <br/>, written as , and the reason for the space is to avoid the code linked to the browser does not recognize.
