HTML (Hypertext Markup Language) has been in use since 1991, but HTML 4.0 (December 1997) was the first standardized version where internationalcharacters were given reasonably complete treatment. When an HTML document includes special characters outside the range of seven-bit ASCII two goals are worth considering: the information’s integrity, and universal browser display.
Specifying the document’s character encoding
There are several ways to specify which character encoding is used in the document. First, the web server can include the character encoding or “
charset” in the Hypertext Transfer Protocol (HTTP)
Content-Type header, which would typically look like this:
Content-Type: text/html; charset=ISO-8859-1 For HTML (but not in XHTML) it is possible to include this information inside the
head element near the top of the document:
Content-Type: text/html; charset=ISO-8859-1
For HTML (but not in XHTML) it is possible to include this information inside the
headelement near the top of the document:<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
HTML5 also allows the following syntax to mean exactly the same:<meta charset="utf-8">
XHTML documents have a third option: to express the character encoding via XML processing instruction, as follows:<?xml version="1.0" encoding="ISO-8859-1"?>
A known misconception about <meta http-equiv="Content-Type"> is that meta element is intended to be interpreted directly by a browser, like an ordinary HTML tag. According to WWW Consortium, it helps HTTP server to generate some headers when it serves the document. The HTTP/1.1 header specification for a HTML document must label an appropriate encoding in the Content-Type header, missing charset= parameter results in acceptance ofISO-8859-1 (so HTTP/1.1 formally does not offer such option as an unspecified character encoding), and this specification supersedes all HTML (or XHTML) meta element ones. This can pose a problem if the server generates an incorrect header and one does not have the access or the knowledge to change them.
As each of these methods explain to the receiver how the file being sent should be interpreted, it would be inappropriate for these declaration not to match the actual character encoding used. Because a server usually can't know how a document is encoded—especially if documents are created on different platforms or in different regions—many servers simply do not include a reference to the "
charset" in the
Content-Typeheader, thus avoiding making false promises. However, if the document does not specify the encoding either, this may result in the equally bad situation where the user agent displaysmojibake because it cannot find out which character encoding was used. Due to widespread and persistent ignorance of HTTP charset= over the Internet (at its server side), WWW Consortium disappointed in HTTP/1.1’s strict approach and encourage browser developers to use some fixes in violation of RFC 2616.
If a user agent reads a document with no character encoding information, it can fall back to using some other information. For example, it can rely on the user's settings, either browser-wide or specific for a given document, or it can pick a default encoding based on the user's language. For Western European languages, it is typical and fairly safe to assume Windows-1252, which is similar to ISO-8859-1 but has printable characters in place of some control codes. The consequence of choosing incorrectly is that characters outside the printable ASCII range (32 to 126) usually appear incorrectly. This presents few problems for English-speaking users, but other languages regularly—in some cases, always—require characters outside that range. In CJK environments where there are several different multi-byte encodings in use, auto-detection is also often employed. Finally, browsers usually permit to override incorrect charset label manually as well.
It is increasingly common for multilingual websites and websites in non-Western languages to use UTF-8, which allows use of the same encoding for all languages. UTF-16 or UTF-32, which can be used for all languages as well, are less widely used because they can be harder to handle in programming languages that assume a byte-oriented ASCII superset encoding, and they are less efficient for text with a high frequency of ASCII characters, which is usually the case for HTML documents.
Successful viewing of a page is not necessarily an indication that its encoding is specified correctly. If the page's creator and reader are both assuming some platform-specific character encoding, and the server does not send any identifying information, then the reader will nonetheless see the page as the creator intended, but other readers on different platforms or with different native languages will not see the page as intended.
In addition to native character encodings, characters can also be encoded as character references, which can be numeric character references (decimal or hexadecimal) or character entity references. Character entity references are also sometimes referred to as named entities, or HTML entities for HTML. HTML's usage of character references derives from SGML.
HTML character references
Numeric character references can be in decimal format,
DDis a variable number of decimal digits. Similarly there is a hexadecimal format,
HHHHis a variable number of hexadecimal digits. Hexadecimal character references are case-insensitive in HTML. For example, the character 'λ' can be represented as
λ. Numeric referencesalways refer to Unicode code points, regardless of the page's encoding. Using numeric references that refer to permanently undefined characters and control characters is forbidden, with the exception of the linefeed, tab, and carriage return characters. That is, characters in the hexadecimal ranges 00–08, 0B–0C, 0E–1F, 7F, and 80–9F cannot be used in an HTML document, not even by reference, so "™", for example, is not allowed. However, for backward compatibility with early HTML authors and browsers that ignored this restriction, raw characters and numeric character references in the 80–9F range are interpreted by some browsers as representing the characters mapped to bytes 80–9F in the Windows-1252 encoding.
Character entity references have the format
&name;where "name" is a case-sensitive alphanumeric string. For example, 'λ' can also be encoded as
λin an HTML document. (For a list of all named HTML character entity references, see List of XML and HTML character entity references.) The character entity references
&are predefined in HTML and SGML, because
&are already used to delimit markup. This notably does not include XML's
'(') entity. For a list of all named HTML character entity references, see List of XML and HTML character entity references (approximately 250 entries).
Unnecessary use of HTML character references may significantly reduce HTML readability. If the character encoding for a web page is chosen appropriately then HTML character references are usually only required for a markup delimiting characters mentioned above, and for a few special characters (or not at all if a native Unicode encoding like UTF-8 is used).
XML character references
Unlike traditional HTML with its large range of character entity references, in XML there are only five predefined character entity references. These are used to escape characters that are markup sensitive in certain contexts:
&→ & (ampersand, U+0026)
<→ < (less-than sign, U+003C)
>→ > (greater-than sign, U+003E)
"→ " (quotation mark, U+0022)
'→ ' (apostrophe, U+0027)
All other character entity references have to be defined before they can be used. For example, use of
é (which gives é, Latin lower-case E with acute accent, U+00E9 in Unicode) in an XML document will generate an error unless the entity has already been defined. XML also requires that the
x in hexadecimal numeric references be in lowercase: for example
ਛ rather than
ਛ.XHTML, which is an XML application, supports the HTML entity set, along with XML's predefined entities.
However, use of
' in XHTML should generally be avoided for compatibility reasons.
' may be used instead.
& has the special problem that it starts with the character to be escaped. A simple Internet search finds thousands of sequences
&amp;amp;amp; ... in HTML pages for which the algorithm to replace an ampersand by the corresponding character entity reference was applied too often.