InSGML,HTML andXML documents, the logical constructs known ascharacter data andattribute values consist of sequences of characters, in which each character can manifest directly (representing itself), or can be represented by a series of characters called acharacter reference, of which there are two types: anumeric character reference and acharacter entity reference. This article lists the character entity references that are valid in HTML and XML documents.

In HTML and XML, anumeric character reference refers to a character by itsUniversal Coded Character Set/Unicodecode point, and uses the format:

&#xhhhh;

or

&#nnnn;

where thex must be lowercase in XML documents,hhhh is the code point inhexadecimal form, andnnnn is the code point indecimal form. Thehhhh (ornnnn) may be any number of hexadecimal (or decimal) digits and may include leading zeros. Thehhhh for hexadecimal digits may mix uppercase and lowercase letters, though uppercase is the usual style. However the XML and HTML standards restrict the usable code points to a set of valid values, which is a subset of UCS/Unicode code point values, that excludes all code points assigned to non-characters or to surrogates, and most code points assigned to C0 and C1 controls (with the exception of line separators and tabulations treated as white spaces).

By contrast, acharacter entity reference refers to a sequence of one or more characters by the name of anentity which has the desired characters as itsreplacement text. The format is:&name; wherename is the case-sensitive name of the entity. The semicolon is usually required in the character entity reference, unless marked otherwise in the table below (see^[a]). The entity must either be predefined (built into the markup language), or declared in aDocument Type Definition (DTD) by using<!ENTITYname "value">.^[b]

XML

XML specifies five predefined entities needed to support every printable ASCII character:&,<,>,', and". The trailing semicolon is mandatory in XML (and XHTML) for these five entities (even if HTML or SGML allows omitting it for some of them, according to their DTD).

ISO Entity Sets

SGML supplied a comprehensive set of entity declarations for characters widely used in Western technical and reference publishing, for Latin, Greek and Cyrillic scripts. TheAmerican Mathematical Society also contributed entities for mathematical characters (see^[c]).

HTML Entity Sets

Early versions ofHTML built in small subsets of these, relating to characters found in three Western 8-bit fonts.

MathML Entity Sets

TheW3C developed a set of entity declarations forMathML characters.

XML Entity Sets

TheW3C MathML Working Group took over maintenance of the ISO public entity sets, combined with the MathML and documents them inXML Entity Definitions for Characters. This set can support the requirements ofXHTML,MathML and as an input to future versions of HTML.

HTML5

HTML5 adopts the XML entities asnamed character references, and does not group them into sets. The character reference names originate from XML Entity Definitions for Characters. The HTML5 specification additionally provides mappings from the names to Unicode character sequences usingJSON.

Numerous other entity sets have been developed for special requirements, and for major and minority scripts. However, the advent ofUnicode has largely superseded them.

The fullformal public identifier and system identifier for the DTD entities subset (where the character entity name is defined) is actually mapped from one of the following three defined named entities:

The ISO entities subsets are old (documented) character subsets, which are given SGML character entity names inISO 8879 and ISO 9573, and which were used in legacy encodings before the unification within ISO 10646. Their fullformal public identifiers are as follows:

HTML5 defines many named entities, references to which act as mnemonic aliases for certain Unicode characters.^[5] The HTML5 specification does not allow users to define additional entities, as it no longer accepts any DTD to be referenced or extended inside HTML documents (this is still needed in XHTML, which is based on stricter XML parsing rules but allows referencing or defining a DTD in the document header, because XML does not predefine most HTML entities).

In the below table, the "Standard" column indicates the first version of the HTML DTD that defines the character entity reference, and indicates characters that are predefined in XML without needing any DTD. To use one of these character entity references in an HTML or XML document, enter anampersand (&) followed by theentity name, and asemicolon (mandatory in XML, and strongly recommended in HTML for all entities, even if HTML allows omitting the semicolon only from some entities indicated below by^[a]), e.g., enter© for the copyright symbol©.

There are no predefined character entities in HTML for characters or sequences of most scripts encoded in the UCS (except a common subset of whitespace, punctuation, mathematical or technical symbols, currency symbols, a few Hebrew symbols used in mathematical notations, and the most common letters in Latin, Greek or Cyrillic). Note also thatnot all bidirectional controls defined in UCS/Unicode are represented as standard character entities in HTML (not even in HTML5, which defines more general directional elements and attributes for that purpose). Notably, there are no predefined HTML character entities for controls that were added in the UCS/Unicode and formally defined in version 2 of the Unicode Bidi Algorithm.

Most entities are predefined in XML and HTML to reference just one character in the UCS, but there are no predefined entities for isolated combining characters, variation selectors, or characters for private use assignments; however the list includes some predefined entities for character sequences of two characters containing some of them. Since HTML 5.0 (and MathML 3.0 which shares the same set en entities), all entities are encoded in Unicode normalization forms C and KC (this was not the case with older versions of HTML and MathML, so older entities that were initially defined with characters for private use assignments, CJK compatibility forms, or in non-NFC forms were modified^[6]).

However, all valid characters and sequences in the UCS, including all bidirectional controls or private-use assignments (but with the exception of non-whitespace C0 and C1 controls, non-characters, and surrogates) are also usable and valid in HTML, XML, XHTML and MathML, either in plain-text values of attributes or in text elements (by encoding them directly as plain text, or using numeric character references when needed).