Copyright © 1998-2009 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This document defines several sets of names which are assigned to Unicode characters. Each of these sets is also implemented as a file of XML entity declarations.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document is a W3C Last Call Public Working Draft produced by the W3C Math Working Group as part of the W3C Math Activity.The goals of the W3C Math Working Group are discussed in the W3C Math WG Charter. The authors of this document are W3C Math Working Group members.
Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document contains the W3C Last Call Working Draft of the XML Entity definitions for Characters. The Last Call period ends on 8 December 2009.
Feedback should be sent to the Public W3C Math mailing list (list archives). When sending an e-mail comment that you expect to be addressed in the final XML Entity definitions for Characters, please put the text “last-call” in the subject line, preferably like this: “[Entities-last-call] …summary of comment ”.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
2 Sets of names
3 Unicode Character Blocks for Scientific Documents
4 Mathematical Alphanumeric Characters
5 Entities for Negated and Variant Characters
5.1 Negated Mathematical Characters
5.2 Variant Mathematical Characters
A Special Considerations
A.3 Multiple Character Entities
B.1 Changes since 2008-07-21
B.2 Changes between 2008-07-21 and 2007-12-14
C Differences between these entities and earlier W3C DTDs
C.1 Differences from XHTML 1.0
C.2 Differences from MathML 2.0 (second edition)
D Source Files
Notation and symbols have proved very important for human communication, especially in scientific documents, especially in mathematics. Mathematics has grown in part because its notation continually changes toward being succinct and suggestive. There have been many new signs developed for use in mathematical notation, and mathematicians have not held back from making use of many symbols originally introduced elsewhere. The result is that science in general, and particularly mathematics, makes use of a very large collection of symbols. It is difficult to write science fluently if these characters are not available for use. It is difficult to read science if corresponding glyphs are not available for presentation on specific display devices. In the majority of cases it is preferable to store characters directly as Unicode character data or as XML numeric character references. However, in some environments it is more convenient to use the ASCII input mechanism provided by XML entity references. Many entity names are in common use, and this specification aims to provide standard mappings to Unicode for each of these names. It introduces no names that have not already been used in earlier specifications.
Specifically, the entity names in the sets starting with the letters "iso" were first standardized in SGML ([SGML]) and updated in [ISO9573-13-1991]. The W3C Math Working Group has been invited to take over the maintenance and development of these sets by the original standards committee (ISO/IECJTC1 SC34). The sets with names starting "mml" were first standardized in MathML [MathML2] and those starting with "xhtml" were first standardized in HTML [HTML4].
This specification defines mappings to Unicode of many sets of names that have been defined by earlier specifications.
We first present two tables listing all the sets combined, first in Unicode order and then in alphabetic order:
Then there come tables documenting each of the entity sets. Each set has a link to the DTD entity declaration for the corresponding entity set, and also a link to an XSLT2 stylesheet that will implement a reverse mapping from characters to entity names (this is, of course, only possible for entity names that map to a single Unicode code point).
In addition to the stylesheets and entity files corresponding to each individual entity set, a combined stylesheet is provided, as well as two combined sets of DTD entity declarations. The first is a small file which includes all the other entity files via parameter entity references; the second is a larger file that directly contains a definition of each entity, with all duplicates removed.
Certain characters are of of particular relevance to scientific document production. The following tables display Unicode ranges containing the characters that are most used in mathematics.
|000||C0 Controls and Basic Latin, C1 Controls and Latin-1 Supplement|
|001||Latin Extended-A, Latin Extended-B|
|002||IPA Extensions, Spacing Modifier Letters|
|003||Combining Diacritical Marks, Greek and Coptic|
|020||General Punctuation, Superscripts and Subscripts, Currency Symbols, Combining Diacritical Marks for Symbols|
|021||Letterlike Symbols, Number Forms, Arrows|
|024||Control Pictures, Optical Character Recognition, Enclosed Alphanumerics|
|025||Box Drawing, Block Elements, Geometric Shapes|
|027||Dingbats, Miscellaneous Mathematical Symbols-A, Supplemental Arrows-A|
|029||Supplemental Arrows-B, Miscellaneous Mathematical Symbols-B|
|02A||Supplemental Mathematical Operators|
|02B||Miscellaneous Symbols and Arrows|
|0FB||Alphabetic Presentation Forms, Arabic Presentation Forms-A|
|0FE||Variation Selectors, Vertical Forms, Combining Half Marks, CJK Compatibility Forms, Small Form Variants, Arabic Presentation Forms-B|
|1D4||Mathematical Alphanumeric Symbols|
|1D5||Mathematical Alphanumeric Symbols (continued)|
|1D6||Mathematical Alphanumeric Symbols (continued)|
|1D7||Mathematical Alphanumeric Symbols (continued)|
Many of the entities defined by this specification relate to the mathematical alphanumeric characters contained in the letter-like symbols block of Unicode Plane 0, or in the Mathematical Alphanumeric Symbols block in Unicode Plane 1. The following tables list all these symbols, highlighting those that are not in Plane 1, and giving entity names where appropriate.
|Italic or Slanted|
|Bold Italic or Slanted|
|Double Struck (Open Face, Blackboard Bold)|
|Script (or Calligraphic)|
|Bold Sans Serif|
|Slanted Sans Serif|
|Slanted Bold Sans Serif|
Each of the entity definitions in a majority of the specification expands to a single Unicode character, however there are some that use multiple character combinations, as outlined in this section.
In addition to the Unicode Characters so far listed, one may use the combining characters U+0338 (/), U+20D2 (|) and U+20E5 (\) to produce negated or canceled forms of characters. A combining character should be placed immediately after its "base" character, with no intervening markup or space, just as is the case for combining accents.
In principle, the negation characters may be applied to any Unicode character, although fonts designed for mathematics typically have some negated glyphs ready composed. A MathML renderer should be able to use these pre-composed glyphs in these cases. A compound character code either represents a UCS character that is already available, as in the case of U+003D U+0338 which amounts to U+2260, or it does not, as is the case for U+2202 U+0338. The common cases of negations, of the latter type, that have been identified are listed in the tables.
Note that it is the policy of the W3C and of Unicode that if a single character is already defined for what can be achieved with a combining character, that character must be used instead of the decomposed form. It is also intended that no new single characters representing what can be done by with existing compositions will be introduced. For further information on these matters see the Unicode Standard Annex 15, Unicode Normalization Forms [Unicode15], especially the discussion of Normalization Form C.
Unicode attempts to avoid having several character codes for simple font variants. For a code point to be assigned there should be more than a nuance in glyphs to be recorded. To record variants worth noting there is a special character in Unicode 3.2, U+FE00 (VARIATION SELECTOR-1), which acts as a postfix modifier. However the legally allowed combinations with this variation selector are restricted to a list recorded as part of Unicode. The VARIATION SELECTOR-1 character may only be applied to the characters listed here. The resulting combination is not regarded by Unicode as a separate character, but a variation on the base character. Unicode aware systems may render the combination as the base if the available fonts do not support the variant glyph shape.
Historically there has been much confusion and lack of agreement over variant forms for lower case epsilon.
This specification uses the definitions below. Note that the name epsilon is used for the character used in textual Greek (U+03B5) and varepsilon used for the epsilon symbol character more commonly used in mathematics (U+03F5). Note that this usage is compatible with the naming of similar pairs of characters (for example theta, vartheta) but incompatible with the naming convention used in TeX, MathML2 and some earlier mappings of the ISO entity sets to Unicode.
|eacgr||isogrk2||=small epsilon, accent, Greek||U+03AD||GREEK SMALL LETTER EPSILON WITH TONOS|
|egr||isogrk1||=small epsilon, Greek||U+03B5||GREEK SMALL LETTER EPSILON|
|epsiv||isogrk3||/straightepsilon, small epsilon, Greek||U+03F5||GREEK LUNATE EPSILON SYMBOL|
|straightepsilon||mmlalias||alias ISOGRK3 epsiv|
|varepsilon||mmlalias||alias ISOGRK3 epsiv|
|bepsi||isoamsr||/backepsilon R: such that||U+03F6||GREEK REVERSED LUNATE EPSILON SYMBOL|
|backepsilon||mmlalias||alias ISOAMSR bepsi|
|b.epsi||isogrk4||small epsilon, Greek||U+1D6C6||MATHEMATICAL BOLD SMALL EPSILON|
|b.epsiv||isogrk4||variant epsilon||U+1D6DC||MATHEMATICAL BOLD EPSILON SYMBOL|
The situation for phi is very similar to that of epsilon, although with the further complication that early versions of Unicode had the sample glyphs for U+03C6 and U+03D5 in swapped from the current usage, and some older fonts still in use follow that older convention. The definitions used in this specification are as listed below.
|phi||isogrk3||/phi - small phi, Greek||U+03C6||GREEK SMALL LETTER PHI|
|phi||xhtml1-symbol||greek small letter phi|
|phgr||isogrk1||=small phi, Greek|
|straightphi||mmlalias||alias ISOGRK3 phiv||U+03D5||GREEK PHI SYMBOL|
|phiv||isogrk3||/varphi - straight phi|
|varphi||mmlalias||alias ISOGRK3 phiv|
|b.phi||isogrk4||small phi, Greek||U+1D6D7||MATHEMATICAL BOLD SMALL PHI|
|b.phiv||isogrk4||variant phi||U+1D6DF||MATHEMATICAL BOLD PHI SYMBOL|
In addition to the combining and variant character combinations listed in the previous sections, the following table lists the remaining entity replacement texts that consist of more than one character.
|fjlig||isopub||small fj ligature||U+0066 U+006A||fj ligature|
|ThickSpace||mmlextra||space of width 5/18 em||U+205F U+200A||space of width 5/18 em|
|race||isoamsb||reverse most positive, line below||U+223D U+0331||REVERSED TILDE with underline|
|acE||isoamsb||most positive, two lines below||U+223E U+0333||INVERTED LAZY S with double underline|
|DownBreve||mmlextra||breve, inverted (non-spacing)||U+0020 U+0311||COMBINING INVERTED BREVE|
|tdot||isotech||three dots above||U+0020 U+20DB||COMBINING THREE DOTS ABOVE|
|TripleDot||mmlalias||alias ISOTECH tdot|
|DotDot||isotech||four dots above||U+0020 U+20DC||COMBINING FOUR DOTS ABOVE|
Unicode does not have an fj character, although the other common f ligatures such as fi (U+FB01) are contained in the Alphabetic Presentation Forms block. The fjlig entity is mapped to the pair of characters "fj", modern typesetting engines should automatically use the fj ligature for this combination ligature if the font supplies such a ligature.
Unicode has a range of space characters (including all multiples of 1/18 em up to 6/18, except for 5/18 em) thus this entity is made from a pair of space characters. An alternative would have been to use U+2005 (1/4 em), but 1/4 em is not equal to 5/18 em, so the above definition was chosen, despite the fact that the difference is unlikely to be visibly noticable at most typeset font sizes.
The entities race and acE denote underlined characters for which Unicode does not have codepoints, thus combining underline characters have been used, in a way analogous to the use of combining strokes for negated operators.
For reasons explained further in [Charmod-norm], it is not advisable to to start the replacement text of an entity with a combining character, as then potentially different results may be produced depending on the order in which entity expansion and Unicode normalisation are performed. As far as possible this specification uses non combining characters, however in the three cases shown above Unicode only has combining forms of the accents, and so the entity replacement text starts with a space, to avoid the possibility that the expansion of the entity combines with preceding text.
The html5-uppercase set is now documented.
The entities ohm and angst have changed to U+03A9 and U+00C5 to match NFC. See w3c bugzilla entry.
The entity race, which had been erroneously assigned to U+29DA, is now assigned to the combination U+223D U+0331. (U+223D isn't quite the shape shown in the original ISO document which is a rotated S rather than a rotated tilde, but this appears to be the closest character in Unicode 5.2.)
The entities bsolhsub and suphsol which were previously mapped to two-character combinations U+005C U+2282 and U+2283 U+002F are now mapped to the Unicode 5 characters that were added specifically to support these entities, U+27C8 and U+27C9.
The source files have all been updated to match Unicode 5.2.
The entity ThickSpace now maps to the pair U+205F U+200A rather than the triple U+2009 U+200A U+200A (4/18 + 1/18)em rather than (3/18 + 1/18 + 1/18)em.
The entity UnderBar maps to the spacing character _ rather than the combining character U+0332.
The entity OverBar maps to the spacing character U+203E (like the XHTML entity oline) rather than the macron character U+00AF.
The entities epsiv and varepsilon are now mapped to the epsilon symbol U+03F5 rather than being aliases for the entity epsilon, U+03B5.
The entities phiv and varphi are now mapped to the phi symbol U+03D5 rather than being aliases for the entity phi, U+03C6.
Differences between the XHTML entity definitions described here and the entity set described in the XHTML 1.0 DTD.
The current drafts of [HTML5] use entity definitions derived from this specification.
The differences between MathML 2 and the current entity definitions are listed below.
The following bracket symbols have been added to the Mathematical symbols block in Unicode versions between 3.1 and 5.1. MathML2 used similar characters intended for CJK punctuation.
[MathML3] uses the entity sets defined by this specification, so there will be no differences between MathML and the entities defined here once MathML3 is finalized.
All data files used to construct the entity declarations, XSLT character maps, and HTML tables referenced from this document are available from http://www.w3.org/2003/entities/2007xml/.