tr34-32.html
564 lines<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html dir="ltr" lang="en-US">
<head><base href="https://www.unicode.org/reports/tr34/tr34-32.html">
<title>UAX #34: Unicode Named Character Sequences</title>
<link rel="stylesheet" type="text/css" href="https://www.unicode.org/reports/reports-v2.css">
</head>
<body>
<table class="header">
<tr>
<td class="icon" style="width:38px; height:35px">
<a href="https://www.unicode.org/">
<img border="0" src="https://www.unicode.org/webscripts/logo60s2.gif" align="middle"
alt="[Unicode]" width="34" height="33"></a>
</td>
<td class="icon" style="vertical-align:middle">
<a class="bar"> </a>
<a class="bar" href="https://www.unicode.org/reports/"><font size="3">Technical Reports</font></a>
</td>
</tr>
<tr>
<td colspan="2" class="gray"> </td>
</tr>
</table>
<div class="body">
<h2 class="uaxtitle">Unicode® Standard Annex #34</h2>
<h1>Unicode Named Character Sequences</h1>
<table class="simple" width="90%">
<tr>
<td valign="top" width="20%">Version</td>
<td>Unicode 17.0.0</td>
</tr>
<tr>
<td valign="top">Editors</td>
<td valign="top">Ken Whistler</td>
</tr>
<tr>
<td valign="top">Date</td>
<td valign="top">2025-07-31</td>
</tr>
<tr>
<td valign="top">This Version</td>
<td valign="top">
<a href="https://www.unicode.org/reports/tr34/tr34-32.html">https://www.unicode.org/reports/tr34/tr34-32.html</a></td>
</tr>
<tr>
<td valign="top">Previous Version</td>
<td valign="top">
<a HREF="https://www.unicode.org/reports/tr34/tr34-31.html">
https://www.unicode.org/reports/tr34/tr34-31.html</a></td>
</tr>
<tr>
<td valign="top">Latest Version</td>
<td valign="top"><a href="https://www.unicode.org/reports/tr34/">https://www.unicode.org/reports/tr34/</a>
</td>
</tr>
<tr>
<td valign="top">Latest Proposed Update</td>
<td valign="top"><a href="https://www.unicode.org/reports/tr34/proposed.html">https://www.unicode.org/reports/tr34/proposed.html</a></td>
</tr>
<tr>
<td valign="top">Revision</td>
<td valign="top"><a href="#Modifications">32</a></td>
</tr>
</table>
<h4>Summary</h4>
<p><i>This annex defines the concept of Unicode named character sequences,
specifies a notational convention for them and a set of rules constraining
possible names applied to character sequences.</i></p>
<h4>Status</h4>
<!-- NOT YET APPROVED
<p><i class="changed">This is a<b><font color="#ff3333"> draft </font></b>document which
may be updated, replaced, or superseded by other documents at any time.
Publication does not imply endorsement by the Unicode Consortium. This is
not a stable document; it is inappropriate to cite this document as other
than a work in progress.</i></p>
END NOT YET APPROVED -->
<!-- APPROVED -->
<p><i>This document has been reviewed by Unicode members and other interested
parties, and has been approved for publication by the Unicode Consortium.
This is a stable document and may be used as reference material or cited as
a normative reference by other specifications.</i></p>
<!-- END APPROVED -->
<blockquote>
<p><i><b>A Unicode Standard Annex (UAX)</b> forms an integral part of
the Unicode Standard, but is published online as a separate document.
The Unicode Standard may require conformance to normative content in a
Unicode Standard Annex, if so specified in the Conformance chapter of
that version of the Unicode Standard. The version number of a UAX
document corresponds to the version of the Unicode Standard of which it
forms a part.</i></p>
</blockquote>
<p><i>Please submit corrigenda and other comments with the online reporting
form [<a href="https://www.unicode.org/reporting.html">Feedback</a>].
Related information that is useful in understanding this annex is found in Unicode Standard Annex #41,
“<a href="https://www.unicode.org/reports/tr41/tr41-36.html">Common References for Unicode Standard Annexes</a>.”
For the latest version of the Unicode Standard, see [<a href="https://www.unicode.org/versions/latest/">Unicode</a>].
For a list of current Unicode Technical Reports, see [<a href="https://www.unicode.org/reports/">Reports</a>].
For more information about versions of the Unicode Standard, see [<a href="https://www.unicode.org/versions/">Versions</a>].
For any errata which may apply to this annex, see [<a href="https://www.unicode.org/errata/">Errata</a>].</i></p>
<h4>Contents</h4>
<ul class="toc">
<li>1 <a href="#Overview">Overview</a>
<ul class="toc">
<li>1.1 <a href="#NamedSequ">Named Character Sequences</a></li>
<li>1.2 <a href="#VarSequ">Relation to Variation Sequences</a></li>
</ul></li>
<li>2 <a href="#Def_Notation">Definitions and Notation</a>
<ul class="toc">
<li>2.1 <a href="#Definitions">Definitions</a></li>
<li>2.2 <a href="#Notation">Notational Conventions</a></li>
</ul></li>
<li>3 <a href="#Conformance">Conformance</a>
<ul class="toc">
<li>3.1 <a href="#ProvProc">Provisional Process for Named Character Sequences</a></li>
<li>3.2 <a href="#Stability">Stability of Approved Named Character Sequences</a></li>
</ul></li>
<li>4 <a href="#Names">Names</a></li>
<li>5 <a href="#DataFile">Data Files</a></li>
<li><a href="#Acknowledgments">Acknowledgments</a></li>
<li><a href="#References">References</a></li>
<li><a href="#Modifications">Modifications</a></li>
</ul>
<hr>
<h2>1 <a name="Overview" href="#Overview">Overview</a> </h2>
<p>The Unicode Standard specifies notational conventions for referring to
sequences of characters (or code points) treated as a unit, using angle brackets surrounding a
comma-delimited list of code points, code points plus character names, and
so on. For example, both of the designations in <i>Table 1</i> refer to a combining character sequence consisting of the letter “a”
with a circumflex and an acute accent applied to it.</p>
<p class="caption">Table 1. <a name="Combining_Character_Example_Table" href="#Combining_Character_Example_Table">Example of a Combining Character Sequence</a></p>
<div align="center">
<table class="simple">
<tr>
<td><U+0061, U+0302, U+0301></td>
</tr>
<tr>
<td><U+0061 LATIN SMALL LETTER A, U+0302
COMBINING CIRCUMFLEX ACCENT, U+0301
COMBINING ACUTE ACCENT></td>
</tr>
</table></div>
<p>See <i>Appendix A,</i> <i>Notational Conventions,</i> in [<a href="../tr41/tr41-36.html#Unicode">Unicode</a>] for the
description of the conventions for expression of code points and for the
representation of sequences of code points.</p>
<p>The Unicode conventions for referring to a sequence of characters (or
code points) are a generalization of the formal syntax specified in ISO/IEC
10646 for UCS Sequence Identifiers, or USI. A USI has the form</p>
<blockquote>
<p><UID<sub>1</sub>, UID<sub>2</sub>, ... UID<sub>n</sub>></p>
</blockquote>
<p></p>
<p>where the UID<sub><i>i</i></sub> represent the short identifiers for code points—most commonly “U+0061” or “0061”. A USI must contain at least two code points.</p>
<p>Such a generalized notation for sequences of Unicode code points
is often useful in discursive text.
More formally, other standards may need to refer to
entities that are represented in Unicode by sequences of characters.
Mapping tables may map single characters in other standards to sequences of
Unicode characters, and listings of repertoire coverage for fonts or
keyboards may need to reference entities that do not correspond to single
Unicode code points.</p>
<h3>1.1 <a name="NamedSequ" href="#NamedSequ">Named Character Sequences</a></h3>
<p>In some limited circumstances it is necessary to also provide a name for
such sequences. The primary example is the need to have an identifier for a
sequence to correlate with an identifier in another standard, for which a
cross-mapping to Unicode is desired. To address this need, the Unicode
Standard defines a mechanism for naming sequences and provides a list
of sequences that have been formally named. This list is deliberately
selective: it is neither possible nor desirable to attempt to provide names
for all possible sequences of Unicode characters that could be of
interest. </p>
<p>This annex defines the concept of a <i>Unicode named character sequence</i>,
specifies a notational convention for such sequences, and a set of rules constraining
possible names applied to character sequences. <i>Section 5,
<a href="#DataFile">Data Files</a></i>, identifies the data file containing the normative list
of Unicode named character sequences. As is the case for character
names, named character sequences are strictly synchronized with ISO/IEC
10646.</p>
<p><i>Table 2</i> provides some examples of Unicode named character sequences to
illustrate the kinds of entities that have been formally named. The
“Sequence” column illustrates the entity in question with a representative
rendering above the sequence of encoded Unicode
characters that represent that entity. The “Name” column shows the name
that has been associated with that sequence.</p>
<p class="caption">Table 2. <a name="Named_Sequences_Example_Table" href="#Named_Sequences_Example_Table">Examples of Named Character Sequences</a></p>
<div align="center">
<table class="subtle">
<tr>
<th>Sequence</th>
<th>Name</th>
<th>Notes on Usage</th>
</tr>
<tr>
<td style="text-align: center">
<img src="../tr34/images/i-macron-grave.jpg" border="0" alt="012B, 0300"></td>
<td style="vertical-align: middle">LATIN SMALL LETTER I WITH MACRON AND GRAVE</td>
<td style="vertical-align: middle">Livonian</td>
</tr>
<tr>
<td style="text-align: center">
<img src="../tr34/images/high-low-tone.jpg" border="0" alt="02E5, 02E9"></td>
<td style="vertical-align: middle">MODIFIER LETTER EXTRA-HIGH
EXTRA-LOW CONTOUR TONE BAR</td>
<td style="vertical-align: middle">Contour tone letter</td>
</tr>
<tr>
<td style="text-align: center">
<img src="../tr34/images/katakana-ainu-p.jpg" border="0" alt="31F7, 309A"></td>
<td style="vertical-align: middle">KATAKANA LETTER AINU P</td>
<td style="vertical-align: middle">Ainu in kana transcription</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align:center">
<img src="../tr34/images/17BB17C6.jpg" border="0" alt="17BB, 17C6"></td>
<td style="vertical-align: middle">KHMER VOWEL SIGN OM</td>
<td style="vertical-align: middle">Khmer</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align:center">
<img src="../tr34/images/17B617C6.jpg" border="0" alt="17B6,17C6"></td>
<td style="vertical-align: middle">KHMER VOWEL SIGN AAM</td>
<td style="vertical-align: middle">Khmer</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align:center">
<img src="../tr34/images/17D21780.jpg" border="0" alt="17D2,1780"></td>
<td style="vertical-align: middle">KHMER CONSONANT SIGN COENG KA</td>
<td style="vertical-align: middle">Khmer</td>
</tr>
</table>
</div>
<p> </p>
<h3>1.2 <a name="VarSequ" href="#VarSequ">Relation to Variation Sequences</a></h3>
<p>Unicode named character sequences differ from Unicode variation
sequences. The latter are documented in <i>Section 23.4</i>, <i>Variation Selectors</i> in [<a href="../tr41/tr41-36.html#Unicode">Unicode</a>] and are listed in the data file StandardizedVariants.txt
in the Unicode Character Database [<a href="../tr41/tr41-36.html#UCD">UCD</a>]
or in the data file emoji-sequences.txt associated with
UTS #51, "Unicode Emoji" [<a href="../tr41/tr41-36.html#UTS51">UTS51</a>].</p>
<p>Variation sequences always consist of a sequence of precisely
two defined code points,
the second of which must be a variation selector. There are additional constraints on which types
of characters they can start with. Variation sequences have a restricted
range of
glyphic shapes, but have no associated name.</p>
<p>Named character sequences can, in principle, consist of code point
sequences of any length, without constraints on what types of characters are
involved. They do not have a specifically defined glyphic shape, but they <i>
do</i> have a formally specified name associated with them.</p>
<h2>2 <a name="Def_Notation" href="#Def_Notation">Definitions and Notation</a></h2>
<h3>2.1 <a name="Definitions" href="#Definitions">Definitions</a></h3>
<p><i><b><a name="UAX34-D1" href="#UAX34-D1">UAX34-D1</a>.</b> Unicode named character sequence:</i> A specific sequence of two or
more Unicode characters, together with a formal name designating
that sequence.</p>
<p><i><b><a name="UAX34-D2" href="#UAX34-D2">UAX34-D2</a>.</b> Unicode namespace:</i> A set of strings used to label
entities in some context in the Unicode Standard, together with a rule or list of rules
which specify how the strings are constructed and a uniqueness rule which specifies
how candidate strings are determined to be unique within the set.</p>
<p>Examples of Unicode namespaces include the namespace for character names
themselves, the namespace for character property aliases, and the
separate namespace for the property value aliases of each
enumerated property.</p>
<p><i><b><a name="UAX34-D3" href="#UAX34-D3">UAX34-D3</a>.</b> Unicode namespace for character names:</i> The
Unicode namespace consisting of Unicode character names,
code point labels, character name aliases,
and the names for Unicode named character sequences.</p>
<blockquote>
<p><i>Note:</i> It is tempting to refer to the elements of the Unicode namespace for character
names just as "character names" for short. However, such practice is misleading
and not recommended. The point of this namespace is to provide a guarantee of name
uniqueness that encompasses the normative names of Unicode characters, but which also
includes certain other labels and names of character-like entities and names of
sequences of characters. Formally, the elements are defined by the following list:</p>
<ul>
<li>Non-null values of the Unicode Name property. This consists of the
names of all assigned graphic characters, including those names which are generated
algorithmically based on code point, such as CJK UNIFIED IDEOGRAPH-4E00.</li>
<li>Code point labels. These are algorithmically generated labels based
on code point values, used to refer to assigned characters that do not have a non-null
value of the Unicode Name property, such as control characters and noncharacters,
and to all unassigned code points in the Unicode codespace.</li>
<li>Formal name aliases. This consists of all values listed in the data file
NameAliases.txt, comprising various corrections and abbreviations for character
names, including aliases for some characters which have null values of the Unicode
Name property.</li>
<li>Names for Unicode named character sequences.</li>
</ul>
</blockquote>
<p>The rules which specify how the names in the Unicode namespace for
character names are constructed are spelled out in <i>Section 4.8, Name</i> in
[<a href="../tr41/tr41-36.html#Unicode">Unicode</a>].
Further conventions which apply specifically to the creation of appropriate names
for Unicode named character sequences are provided in <a href="#UAX34-R4">UAX34-R4</a> below.</p>
<p>The uniqueness rule for names in the Unicode namespace is specified
in <a href="#UAX34-R3">UAX34-R3</a> below.</p>
<h3>2.2 <a name="Notation" href="#Notation">Notational Conventions</a></h3>
<p>The notation for a Unicode named character sequence consists of the
general conventions for character sequences in <i>Appendix A, Notational
Conventions,</i> of [<a href="../tr41/tr41-36.html#Unicode">Unicode</a>], together with
name conventions as specified in <i>Section 4, <a href="#Names">Names</a></i>. Thus a typical representation of a Unicode named character sequence
would be a USI followed directly by the name of the sequence:</p>
<blockquote>
<p><U+012B, U+0300> LATIN SMALL LETTER I WITH MACRON AND GRAVE</p>
</blockquote>
<p></p>
<p>In contexts that supply other clear means for delimitation, such as data
files or tables, the bracketing and comma delimitation conventions for the
sequences may be dropped, as in</p>
<blockquote>
<p>012B 0300;LATIN SMALL LETTER I WITH MACRON AND GRAVE</p>
</blockquote>
<h2>3 <a name="Conformance" href="#Conformance">Conformance</a></h2>
<p>Conformance to the Unicode Standard <i>requires</i>
conformance to the specification in this annex. The relationship between
conformance to the Unicode Standard and conformance to an individual Unicode
Standard Annex (UAX) is described in more detail
in <i>Section 3.2, Conformance Requirements</i> in [<a href="../tr41/tr41-36.html#Unicode">Unicode</a>]. </p>
<i><b><a name="UAX34-C1" href="#UAX34-C1">UAX34-C1</a>.</b> If a process purports to implement Unicode named
character sequences, it shall use only those named character
sequences defined in the file NamedSequences.txt in the Unicode
Character Database.</i><p>Only the named character sequences in NamedSequences.txt are
named in
this standard. No other Unicode character sequences are given names in this
version of the Unicode Standard, although named character
sequences may be added in the future. Only sequences that are in Normalization
Form NFC are given names in the Unicode Standard.</p>
<p>Conformance to this clause should not be construed as preventing
implementers from providing informal names of their choice to any entities
or character sequences, as appropriate. However, such informal names are not
specified in any way by this standard for use in interchange.</p>
<p>The use of unnamed character sequences is not affected by the specifications in
this annex.</p>
<h3>3.1 <a name="ProvProc" href="#ProvProc">Provisional Process for Named Character Sequences</a></h3>
<p>When named character sequences are first suggested for inclusion in the
Unicode Standard, they may be accepted provisionally. In such cases, they
are listed in the file NamedSequencesProv.txt. See [<a href="../tr41/tr41-36.html#DataProv">DataProv</a>].
</p><p>
Character sequences and proposed names listed in
NamedSequencesProv.txt are <i>provisional</i> only
and have no other status. They become part of the
standard itself only when approved for inclusion in NamedSequences.txt.
</p><p>
The use of a provisional list is meant to allow sufficient time
for review and comment on proposed named character
sequences before they are finally approved. This also
enables the normative data file, NamedSequences.txt, to remain stable.</p>
<h3>3.2 <a name="Stability" href="#Stability">Stability of Approved Named Character Sequences</a></h3>
<p>Once a Unicode named character sequence has been approved, it is stable and will not
be changed in any way in future versions of the standard. This stability applies both
to the name of the named character sequence and to the sequence of code points associated
with the name. See [<a href="../tr41/tr41-36.html#Stability">Stability</a>] for more
information on the Unicode Consortium Stability Policies.</p>
<h2>4 <a name="Names" href="#Names">Names</a></h2>
<p>Names of Unicode named character sequences are unique.
They are part of the Unicode namespace for character names.</p>
<p>Names for named character sequences are constructed
according to the following rules:</p>
<p><a name="UAX34-R1" href="#UAX34-R1"><i><b>UAX34-R1.</b></i></a> Only Latin capital letters A to Z,
digits 0 to 9 (provided that a digit is not the first character in a word),
SPACE, and HYPHEN-MINUS are used for writing the names.</p>
<p>This rule is intended to be the same as the rules for Unicode character names,
because they share the same namespace. The rules for names are specified in more detail in
<i>Section 4.8, Name</i> in [<a href="../tr41/tr41-36.html#Unicode">Unicode</a>].</p>
<p><a name="UAX34-R2" href="#UAX34-R2"><i><b>UAX34-R2.</b></i></a> Only one name is given to each
named character sequence, and each named character sequence must
be unique within the Unicode namespace for character names.</p>
<p><a name="UAX34-R3" href="#UAX34-R3"><i><b>UAX34-R3.</b></i></a> Names are unique
in the Unicode namespace for character names if they are different even when SPACE and <i>medial</i>
HYPHEN-MINUS characters are ignored, and when the strings “LETTER”,
“CHARACTER”, and “DIGIT” are ignored in comparison of the names.</p>
<p>There are two grandfathered exceptions to the general statement of
this uniqueness rule. These pairs of names are explicitly specified to be distinct, for
historical reasons in the development of the standard, and thus must be treated as
exceptional cases by any algorithm checking for name uniqueness. One of these
exceptions involves two Unicode character names:</p>
<blockquote>
<p>116C HANGUL JUNGSEONG OE<br>
1180 HANGUL JUNGSEONG O-E</p>
</blockquote>
<p>The other exception involves two character name aliases:</p>
<blockquote>
<p>CANCEL (character name alias for the control code U+0018)<br>
CANCEL CHARACTER (character name alias for the control code U+0094)</p>
</blockquote>
<p>The rule UAX34-R3 specifies that only <i>medial</i> HYPHEN-MINUS characters
are ignored in comparison. The term "medial" is
construed here as occurring directly after a letter (or digit) <i>and</i>
directly before a letter (or digit) in the name. It is possible for a HYPHEN-MINUS character
to occur in initial position (following a SPACE) in a subpart of
a Unicode character name
or in final position (preceding a SPACE). In those
positions the HYPHEN-MINUS is not ignored for comparison, so the following
two existing Unicode character names are distinct in
the namespace:</p>
<blockquote>
<p>0F68 TIBETAN LETTER A<br>
0F60 TIBETAN LETTER -A</p>
</blockquote>
<p>Although there are a few Unicode characters that have a final HYPHEN-MINUS,
for example, U+0F0A TIBETAN MARK BKA- SHOG YIG MGO, currently there are no character
names which contrast <i>only</i> by the presence or absence of a HYPHEN-MINUS in that
position.</p>
<p>The following example shows two hypothetical names that would
not be unique by application of UAX34-R3:</p>
<blockquote>
<p>SARATI LETTER AA<br>
SARATI CHARACTER AA</p>
</blockquote>
<p>These two names would not be unique if the
strings “LETTER” and “CHARACTER” were ignored.</p>
<p><a name="UAX34-R4" href="#UAX34-R4"><i><b>UAX34-R4.</b></i></a> Where possible, names
for named character sequences are constructed by
appending the names of the constituent elements together while eliding
duplicate elements, and possibly introducing the words “WITH”
or “AND”
between elements for clarity. Should this process result in a name that
already exists, the name is modified suitably to guarantee uniqueness in the namespace.</p>
<p><i>Table 3</i> gives some examples of names for hypothetical sequences
constructed according to UAX34-R4.</p>
<p class="caption">Table 3. <a name="Hypothetical_Sequences_Example_Table" href="#Hypothetical_Sequences_Example_Table">Examples of Hypothetical Sequence Names</a></p>
<div align="center">
<table class="subtle">
<tr>
<th>USI</th>
<th>Alternate Representation of Sequence</th>
<th>Name</th>
</tr>
<tr>
<td nowrap><0041, 0043, 0043></td>
<td><A, B, C></td>
<td>LATIN CAPITAL LETTER A B C</td>
</tr>
<tr>
<td nowrap><00CA, 0046></td>
<td><AE, F></td>
<td>LATIN CAPITAL LETTER AE F</td>
</tr>
<tr>
<td nowrap><0058, 030A></td>
<td><X, COMBINING RING ABOVE></td>
<td>LATIN CAPITAL LETTER X WITH RING ABOVE</td>
</tr>
</table>
</div>
<p><a name="UAX34-R5" href="#UAX34-R5"><i><b>UAX34-R5.</b></i></a> Where applicable, the rules
from Annex L, "Character naming guidelines" in ISO/IEC
10646:2020 apply.</p>
<blockquote>
<p><span class="note">Note:</span> Just
as for character names, the names for sequences may be translated, with the translated
names for each language being unique with respect to each other and the corresponding
set of translated character names. However, translated names are not restricted to the same limited character
set as the English names. Translated names may not be suitable as
identifiers without modification.</p>
</blockquote>
<h2>5 <a name="DataFile" href="#DataFile">Data Files</a></h2>
<p>A normative data file, NamedSequences.txt, is available consisting of those named
character sequences defined for this version of [<a href="../tr41/tr41-36.html#Unicode">Unicode</a>]. The sequences are listed in the
data file in an abbreviated format. For the location of the data file, see [<a href="../tr41/tr41-36.html#Data34">Data34</a>].</p>
<p>In addition, a provisional data file, NamedSequencesProv.txt, is available containing
sequences and names proposed for the standard but not yet approved as part
of the normative list of named character sequences. For the location of the
data file, see [<a href="../tr41/tr41-36.html#DataProv">DataProv</a>].</p>
<p>The abbreviated format for named character sequences in the data files uses space
delimitation of code points, without the "U+" prefix and without angle brackets. This format for
code point sequences is widely shared in data files of the Unicode Character Database. The names
for named character sequences are listed in a separate, semicolon-delimited field. Thus a
typical entry for the data file is as follows:</p>
<pre>
TAMIL CONSONANT K; 0B95 0BCD</pre>
<p>Implementations of Unicode named character sequences may use other formats for this
data, as appropriate. The key information is the name itself and its associated code
point sequence.</p>
<h2 class="nonumber"><a name="Acknowledgments" href="#Acknowledgments">Acknowledgments</a></h2>
<p>Ken Whistler authored the initial version and
maintains the text.</p>
<p>Thanks to Asmus Freytag, Mark Davis and Julie Allen for comments on
this annex, including earlier versions. Addison Phillips
helped to maintain the text for Revisions 13 through 17.</p>
<h2 class="nonumber"><a name="References" href="#References">References</a></h2>
<p>For references for this annex, see Unicode Standard Annex #41, “<a href="../tr41/tr41-36.html">Common
References for Unicode Standard Annexes</a>.”</p>
<h2 class="nonumber"><a name="Modifications" href="#Modifications">Modifications</a></h2>
<p>The following summarizes modifications from the previous version of this
annex.</p>
<h3>Revision 32 [KW]</h3>
<ul>
<li><b>Reissued</b> for Unicode 17.0.0</li>
</ul>
<p>Previous revisions can be accessed with the “Previous Version” link in the header.</p>
<hr width="50%">
<p class="copyright">© 2005–2025 Unicode, Inc. This publication is protected by copyright, and permission must be obtained from Unicode, Inc. prior to any reproduction, modification, or other use not permitted by the <a href="https://www.unicode.org/copyright.html">Terms of Use</a>. Specifically, you may make copies of this publication and may annotate and translate it solely for personal or internal business purposes and not for public distribution, provided that any such permitted copies and modifications fully reproduce all copyright and other legal notices contained in the original. You may not make copies of or modifications to this publication for public distribution, or incorporate it in whole or in part into any product or publication without the express written permission of Unicode.</p>
<p class="copyright">Use of all Unicode Products, including this publication, is governed by the Unicode <a href="https://www.unicode.org/copyright.html">Terms of Use</a>. The authors, contributors, and publishers have taken care in the preparation of this publication, but make no express or implied representation or warranty of any kind and assume no responsibility or liability for errors or omissions or for consequential or incidental damages that may arise therefrom. This publication is provided “AS-IS” without charge as a convenience to users.</p>
<p class="copyright">Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries.</p>
<p> </p>
</div> <!-- body -->
</body>
</html>
Rendered documentLive HTML preview