<?xml version="1.0" encoding="UTF-8"?>
<metanorma xmlns="https://www.metanorma.org/ns/standoc" type="semantic" version="2.8.6" schema-version="v2.1.6" flavor="ribose">
<bibdata type="standard">
<title language="en" type="main">Internationalized semantic punctuation framework</title>
<docidentifier primary="true" type="Ribose">115</docidentifier><docnumber>115</docnumber><date type="updated"><on>2025-09-23</on></date><contributor><role type="author"/><organization>
<name>Ribose Asia Limited</name>
<abbreviation>Ribose</abbreviation></organization></contributor><contributor><role type="publisher"/><organization>
<name>Ribose Asia Limited</name>
<abbreviation>Ribose</abbreviation></organization></contributor><edition>1</edition><version>2025-09-23</version><language>en</language><script>Latn</script><status><stage>draft</stage></status><copyright><from>2025</from><owner><organization>
<name>Ribose Asia Limited</name>
<abbreviation>Ribose</abbreviation></organization></owner></copyright><ext><doctype>standard</doctype><flavor>ribose</flavor></ext></bibdata><metanorma-extension><semantic-metadata><stage-published>false</stage-published></semantic-metadata>
<presentation-metadata><toc-heading-levels>3</toc-heading-levels><html-toc-heading-levels>3</html-toc-heading-levels><doc-toc-heading-levels>3</doc-toc-heading-levels><pdf-toc-heading-levels>3</pdf-toc-heading-levels></presentation-metadata></metanorma-extension>
<boilerplate><copyright-statement>

<clause id="_e7df828a-3e38-a44b-e1d3-06eee96b9b34" obligation="normative"><p id="_ec0ed287-9c00-c6cb-c0ed-f7e8883a816e">© Ribose Asia Limited 2025</p>
</clause>
</copyright-statement>

<license-statement>

<clause id="_3179d22c-816d-e694-6037-341f744bc6dc" obligation="normative">
<title id="_5ad8fb30-fcae-1072-87a2-407e6b4939ec">Warning for Drafts</title>
<p id="_a24807ee-0381-7ef8-1167-c3aacbb0fd73">This document is not a Ribose Standard. It is distributed for review and comment, and is subject to change without notice and may not be referred to as a Standard. Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.</p>
</clause>
</license-statement>

<legal-statement>

<clause id="_7e0f3c63-3fc9-65cf-37f7-b94afa0dbc5d" obligation="normative"><p id="_50bbfa02-61c3-8332-bad8-61e7389d1808">All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from the address below.</p>
</clause>
</legal-statement>

<feedback-statement>

<clause id="_d43a5e83-e752-e9bc-955e-4282a8ebb43a" obligation="normative"><p id="_0145a561-c9cc-a509-4784-ac2a1e6ea922" anchor="boilerplate-name" align="left">Ribose Asia Limited</p>

<p id="_80954cc8-1f49-9d20-5987-829595995a92" anchor="boilerplate-address" align="left">Suite 1, 8/F, New Henry House<br/> 10 Ice House Street<br/> Central<br/> Hong Kong<br/> <br/> <link target="mailto:copyright@ribose.com"/><br/> <link target="https://www.ribose.com">www.ribose.com</link></p>
</clause>
</feedback-statement>
</boilerplate><preface><foreword id="_f8e18836-d8a4-f81b-47dd-133aeb1724a2" obligation="informative">
<title id="_41c9fad3-d4c1-eecc-4fad-f91704acc026">Foreword</title>
<p id="_93ec9a6b-1127-d514-ac82-3748a0371e58">This document is part of the Metanorma specifications series that defines requirements for internationalized document rendering, specifically addressing punctuation usage across multiple languages and writing systems.</p>
</foreword><introduction id="_ebfd9112-f08b-bea7-6db1-ebeca40d36ed" obligation="informative">
<title id="_2b2e98d1-114a-3da4-8556-01ae0a724280">Introduction</title>
<p id="_0628778d-fce5-e4bb-f7b4-4affda65afe4">Metanorma is a semantic authoring system that supports multiple languages and the publication of multi-lingual output.</p>

<p id="_961d37ba-95b8-3f65-2ff7-4a568107033c">A major component of Metanorma architecture is dedicated to providing presentation rendering for the semantic content it encodes. This means that Metanorma often composes punctuated text to  represent semantic text, and that punctuation needs to follow the norms of a target language. Metanorma requires a semantic framework to capture the various types of punctuation it will add to the text it composes, and to provide well-governed rendering of that punctuation in supported languages.</p>

<p id="_caf5ef45-988d-cef9-0a8b-87bab86ae95f">This document defines a framework for semantic punctuation usage across multiple languages and writing systems, to be drawn from in the generation of punctuated text based on semanticly marked up text. This framework is  <strong>not</strong> intended to supplant the punctuation provided by authors in originally authored texts.</p>

<p id="_be0ba59a-d643-6722-2cc2-632ea2fcfbad">The document covers the following languages and writing systems:</p>

<ul id="_738d5202-e39a-0d18-49d3-2aa86ab231ba"><li><p id="_1e39b061-9236-8f72-c721-c30ef8443812">CJK (East Asian ideographic writing systems)</p>
<ul id="_c163fbbd-1196-db64-00f9-00113bf5659f"><li><p id="_07083cd8-e810-3954-bc6a-67409ba0b36c">Traditional Chinese (Taiwan/Hong Kong conventions)</p>
</li>
<li><p id="_5e86bbbc-198c-1b3b-45c0-a035e04392a8">Simplified Chinese (Mainland China conventions)</p>
</li>
<li><p id="_e399f376-8a7e-98f5-5132-b185931cd60b">Japanese (including vertical text layout)</p>
</li>
<li><p id="_aae51682-604c-c6f8-b182-40fd81e47c6a">Korean (Hangul-specific rules)</p>
</li>
</ul>
</li>
<li><p id="_07f666f1-b972-e072-2b05-9cd36cb310da">Latin-script languages (English, Spanish, French)</p>
</li>
<li><p id="_75018010-2d32-4bf5-075a-d726c92d090b">Cyrillic-script languages (Russian)</p>
</li>
</ul>

<p id="_4e68a2c9-8b11-f2ab-8b04-2bfe56fa01ce">The document defines punctuation marks through primary usage categories based on the semantic function of the punctuation marks.</p>

<p id="_4846bd84-1f4d-5c68-3243-42fa9e9fed4f">This document addresses critical challenges including:</p>

<dl id="_5c8657bf-c211-aafa-9ca4-3c3bf327a4ad"><dt>Internationalization of auto-numbered elements</dt>
<dd id="_b2d1c25d-812e-1baa-cc7c-af61231f5f9b"><p id="_be00d5c9-90fb-cbaf-b8e0-503012bd0d16">Applying appropriate punctuation to document elements, such as: phrases, lists, figures, tables and references use. Enabling definition of Label Auto-assignment Definition Language profiles (LADL) (<eref type="inline" bibitemid="MN112" citeas="MN 112"/>).</p>
</dd>
<dt>Internationalization of bibliographic citations</dt>
<dd id="_30baa3e1-42b4-09f2-fe36-d98a6d2f395f"><p id="_1c7c5d09-4105-5f96-f464-8f2ab726675c">Applying appropriate punctuation to in-text citations and reference lists, allowing for citation style definition and language-specific variations.</p>
</dd>
<dt>Automatic spacing</dt>
<dd id="_f32f4514-72f3-cdd8-32fd-9efe976a73e1"><p id="_6c764adc-eed7-54fb-fc2e-f109c8a5d985">Applying appropriate whitespace around punctuation marks based on language-specific rules.</p>
</dd>
<dt>Rendering in vertical text layouts</dt>
<dd id="_f95a945d-9abb-ff33-b8fd-fc53a70c5891"><p id="_efddc374-ff1f-9f51-bac4-bb5550ddbe8c">Proper punctuation positioning and transformation in vertical text modes.</p>
</dd>
</dl>
</introduction></preface><sections>

<clause id="_40958402-6621-9429-8f42-22d63e74e457" type="scope" obligation="normative">
<title id="_f70b6ff6-6131-0e24-81e1-850dbe94b63d">Scope</title>
<p id="_e3e27812-ae8e-8c58-5a1f-99cbcc2f994b">This document defines a framework for semantic punctuation usage across multiple languages and writing systems. It also outlines how that framework is realised in Metanorma implementation, and how its configuration can be updated.</p>

<p id="_43d3b9cc-bde9-7587-d33e-6d5017b4c48b">Examples and discussion about specific writing systems are as of this writing limited to CJK, Latin and Cyrillic; but the document is intended to be generally applicable.</p>

<p id="_9a3a155d-24c4-1c6f-adc4-3846b4bee6bb">Formal notation systems that use punctuation in ways divergent from normal language,
such as mathematical notation, chemical notation, and computer programming,
are out of scope of this document. Numeric punctuation is in scope,
but it is not discussed in detail, as it is handled in Metanorma by distinct mechanisms.<note id="_0af80384-5930-b4c6-35a4-621fdc37ab9d"><p id="_d310e2fc-15b7-6a39-e5aa-6ad2cd07febf">Following linguistic practice, and to avoid confusion with quotations, individual characters are cited in angle brackets, and where necessary followed by Unicode codepoint, and preceded by Unicode name; e.g.</p>

<ul id="_87d5961a-d2d8-c88e-887f-3fda159ae31a"><li><p id="_6a44366f-fc0b-321e-020f-ee1b220ab8fc"><tt>&lt;，&gt;</tt></p>
</li>
<li><p id="_9dccb4fa-ce16-d979-c76d-df36d062de2c"><tt>&lt;，&gt;</tt> (U+FF0C)</p>
</li>
<li><p id="_a1a360bd-aa14-943f-50b6-a64d4548bf37">FULLWIDTH COMMA <tt>&lt;，&gt;</tt> (U+FF0C).</p>
</li>
</ul>
</note></p>


</clause>



<terms id="_30fad410-92d5-cb72-695d-84ee0858e76b" obligation="normative">
<title id="_dfb2eab2-f980-6365-3c47-81d0eb272962">Terms and definitions</title><p id="_1fbc7bf1-a8de-c3eb-ee88-3b4cf950e61b">For the purposes of this document, the following terms and definitions apply.</p>
<term id="_d444842d-9be2-d283-840e-e60da4e32f25" anchor="term-script"><preferred><expression>
<name>script</name>
</expression>
</preferred>
<definition id="_66a8b491-23dc-e3f6-b55f-07d338e0cc14"><verbal-definition id="_33e11158-32a8-0e95-fb15-800c020c7676"><p id="_6bf9dbef-9b60-e5a1-7e3f-f0700064fca7">set of symbols representing a particular language</p></verbal-definition></definition>
 </term>

<term id="_d72f6449-f32c-50ab-5483-43ee833ad543" anchor="term-writing-system"><preferred><expression>
<name>writing system</name>
</expression>
</preferred>
<definition id="_c47a6dd3-c22a-c87e-c267-3d78f2903975"><verbal-definition id="_feead599-de76-dce6-5423-e0014e781594"><p id="_df1273ab-8dda-20e4-9620-0b2a09255ce4">script, and the rules whereby it represents a particular language</p></verbal-definition></definition>
 </term>

<term id="_18db54a1-af9a-eef4-457e-ae1946fb0eff" anchor="term-locale"><preferred><expression>
<name>locale</name>
</expression>
</preferred>
<definition id="_65df05c9-c17c-e7f1-a776-356e7e51d3e6"><verbal-definition id="_7cad7ce4-c3ed-091a-e4b7-970adfd27e50"><p id="_27ff1dd5-1646-e575-d8fd-117967e1b657">regional variant of a language and/or script,  specific to a country or region</p></verbal-definition></definition>
 </term>

<term id="_aa89282e-300d-aaa7-d038-268ca131cc54" anchor="term-morpheme"><preferred><expression>
<name>morpheme</name>
</expression>
</preferred>
<definition id="_cb7ec98e-a6fa-ae0a-e8b8-78c91d10bc45"><verbal-definition id="_9918e24a-2727-dfdc-343d-9a7edc9bb415"><p id="_397a735b-0fb4-59fe-82f1-6dd22709c407">semantic component of a language</p></verbal-definition></definition>
 </term>

<term id="_3b469e1d-6551-2944-10cc-c6bf3cee2319" anchor="term-ideograph"><preferred><expression>
<name>ideograph</name>
</expression>
</preferred>
<definition id="_868ed425-a252-48e7-7d2d-9ecf22b6f0e7"><verbal-definition id="_f9a6464c-1a3a-728e-c8ce-9758e4b79cd7"><p id="_9b23a831-8dd0-e1e5-4bf0-453bbfb9db80">written character that represents a morpheme, rather than a sound in a language</p></verbal-definition></definition>
 </term>

<term id="_65ed2065-7f80-2596-0067-0d34eb2423eb" anchor="term-CJK"><preferred><expression>
<name>CJK</name>
</expression>
</preferred>
<definition id="_d6d2c3ea-0d88-06fb-0881-244ba2a59c4f"><verbal-definition id="_1688d3a3-f5fb-cd0a-e0f1-2a87a1f5349b"><p id="_5dfd5990-c072-56ca-e61c-a9c17a82c976">Chinese, Japanese, Korean, and other writing systems based on East Asian ideographs</p></verbal-definition></definition>
 </term>

<term id="_eee70ffe-a33e-c6c6-dda7-2b82f50611a0" anchor="term-internationalisation"><preferred><expression>
<name>internationalisation</name>
</expression>
</preferred><admitted><expression>
<name>i18n</name>
</expression>
</admitted>



<definition id="_6e788680-0243-0ecf-bc6a-666f2627d5ef"><verbal-definition id="_5bda2d9e-feef-f2e3-1eb6-3873cfaa77ca"><p id="_bb3b0793-3484-36b9-8abc-48f7872d687b">support in software for input and output in more than one language</p></verbal-definition></definition>
 </term>

<term id="_c355fbe1-52c1-f9fe-6474-d60cdd437194" anchor="term-punctuation-mark"><preferred><expression>
<name>punctuation mark</name>
</expression>
</preferred>
<definition id="_7a03e7b3-fbe2-1789-f697-c43694adc240"><verbal-definition id="_df57fb4f-ffbd-e8a4-03f0-920c8479c7d2"><p id="_13347fb5-afb1-0f4d-489f-f0dac268c8f7">symbol used in written language to clarify meaning, indicate text structure, separate elements, or convey syntactic relationships</p></verbal-definition></definition>
 </term>

<term id="_68409812-a116-397b-1b50-bd50eb224197" anchor="term-usage-category"><preferred><expression>
<name>usage category</name>
</expression>
</preferred>
<definition id="_75dc664c-ecb2-6372-1cd6-d0427ff77fc4"><verbal-definition id="_e78461ef-d720-3bcb-d68a-fa624b188b19"><p id="_72b4c68c-fc50-2878-7931-e5c538e08230">functional classification of punctuation marks based on their primary purpose in text structure</p></verbal-definition></definition>


 <termexample id="_3e09cfd6-bae4-78b3-1ccf-042fb47c661c"><p id="_e3750db7-5fb5-2a9f-0f3c-fdd47ef11492">Sentence delimiters, pause indicators, grouping markers.</p>
</termexample></term>

<term id="_f41ab6bc-13bb-1ae2-4906-26299ea113ce" anchor="term-full-width-character"><preferred><expression>
<name>full-width character</name>
</expression>
</preferred>
<definition id="_37383717-c3b0-f396-3aa4-e6dec988b4b1"><verbal-definition id="_e813dcb0-4341-764f-5398-c8179795faad"><p id="_915b6c7b-0c9a-07c0-bb1e-e8746bc382ba">character that occupies the width of an ideographic character, commonly used in CJK typography</p></verbal-definition></definition>
 </term>

<term id="_239ca4b1-f16b-fac0-e6ba-070f73c0f859" anchor="term-half-width-character"><preferred><expression>
<name>half-width character</name>
</expression>
</preferred>
<definition id="_1cb8f61d-a232-55b6-84c2-f36526f7819c"><verbal-definition id="_0c05b918-4ea5-a51f-2ac0-fcafc1b1dcaf"><p id="_f0fa9945-4855-6e89-4d3b-5177eba38c6a">character that occupies standard Latin character width, used in Western typography and mixed CJK text</p></verbal-definition></definition>
 </term>

<term id="_0f039fb1-2cae-c9fa-f568-f50121e8f760" anchor="term-directionality"><preferred><expression>
<name>directionality</name>
</expression>
</preferred>
<definition id="_6f01bd9a-a873-1f05-433f-53890eb1b0ea"><verbal-definition id="_046375a1-e280-36a9-019d-876033628511"><p id="_ce6b0a7a-c112-2ff1-ea0e-349cbe13535e">text arrangement of characters, including left-to-right (LTR), used in Latin and Cyrillic, right-to-left (RTL), used in Hebrew and Arabic, horizontal (identical to LTR), usually used in CJK, and vertical (top-to-bottom in columns arranged from right to left), traditionally used in CJK</p></verbal-definition></definition>
 </term>

<term id="_4edf77bf-e505-fa99-55dd-c0f1d010c7ce" anchor="term-spacing-rule"><preferred><expression>
<name>spacing rule</name>
</expression>
</preferred>
<definition id="_16dad8fd-93ca-9b2d-514d-d57fbfd4ff46"><verbal-definition id="_fab1a2ef-7260-f7a6-c463-70213bbb7541"><p id="_762e0082-46cd-41f1-98a3-fa0fc1a39b7b">specification for whitespace insertion around punctuation marks that varies by language, locale, and context</p></verbal-definition></definition>
 </term>

<term id="_7cf78f32-0c07-f174-1024-dfcde8d632ff" anchor="term-phrase"><preferred><expression>
<name>phrase</name>
</expression>
</preferred>
<definition id="_cd1941b3-1c9f-c612-d6d8-1d4e5f91e5f0"><verbal-definition id="_3651e216-c889-bd1e-748c-183082a34d2b"><p id="_dab74999-0b1d-13b7-4433-8cdf6f3b82be">meaningful grouping of words, that is smaller than a sentence</p></verbal-definition></definition>
 </term>
</terms>

<clause id="_ebb2eef9-e1a1-2c3d-e5a0-899232377902" obligation="normative">
<title id="_4b9fd3c0-0c48-3749-1700-40a2b89fe2e0">Framework</title>
<clause id="_a9e97513-f969-c354-3a1a-aac847f1a150" obligation="normative">
<title id="_53d82e48-1024-e16a-9901-40ceda1ab9b0">General</title>
<p id="_eff41468-2dc2-6fab-baf5-8d1d5f368fcf">This framework provides guidelines for the consistent application of punctuation marks across different languages and writing systems. It aims to ensure that punctuation usage aligns with semantic meaning and cultural conventions.</p>

<dl id="_3c21be3f-a40b-6d62-ef9a-e4144b01942d"><dt>Punctuation profile</dt>
<dd id="_6335cacf-4841-d6b3-322f-02c64f663781"><p id="_2135021c-9e75-094e-525d-cd366493bf54">A set of rules and mappings that define how punctuation marks are applied in a specific language, locale or document context. Even in the same language and locale, different publishers may require different punctuation styles.</p>
<example id="_eb9b6617-4b0e-036c-4eb7-2cfaa689492c"><p id="_8e813ecf-304d-6d3d-1e69-381613a09c22">In Japanese, the <link target="https://www.bunka.go.jp/seisaku/bunkashingikai/kokugo/hokoku/pdf/93651301_01.pdf">「公用文作成の考え方」（建議）（付）「公用文作成の考え方（文化審議会建議）」解説</link> of the Agency for Cultural Affairs (2022) specifies different punctuation rules from JIS X 8301:2019, the Japanese Industrial Standard stating requirements for punctuation in Japanese standards</p>

<ul id="_d93e93ab-07e6-056a-ec3f-2425b8540e45"><li><p id="_7cbb35a5-1de2-7d56-a844-6d325ff66b1d">sentence pausal mark: the former requires use of the <em>ten</em>, IDEOGRAPHIC COMMA <tt>&lt;、&gt;</tt> (U+3001), but the latter requires the use of the full-width Latin comma, FULLWIDTH COMMA  <tt>&lt;，&gt;</tt> (U+FF0C).</p>
</li>
</ul>
</example>
</dd>
<dt>Punctuation mark</dt>
<dd id="_17deb264-788e-24bf-ab35-10e63cb953a6"><p id="_2d3c5ec5-322c-43c3-3c06-05a7088b5374">A symbol used in writing to clarify meaning, indicate text structure, separate elements, or convey syntactic relationships. Each punctuation mark can have several semantic functions, and therefore belong to multiple usage categories; these may vary across languages. Not all punctuation marks exist in all languages. A mark is commonly represented by one or more glyphs.</p>
</dd>
<dt>Semantic function</dt>
<dd id="_d9edc7bc-a6cb-256c-25ae-e82ee5805072"><p id="_a1b4f281-eb32-82c3-243f-1398676b69a5">The purpose or role of a punctuation mark in text, which may include indicating sentence and phrase boundaries, grouping, emphasis, indicating relationships, and semantic categorisation such as for numerals. Semantic functions are grouped as usage categories. The correspondence of semantic function to punctuation mark is many-to-many.</p>
<example id="_b6d1175c-cf93-1827-b427-8238ef47e50a"><p id="_3941be3f-e202-0c0c-65ec-410c06491319">The semantic function of “minor phrase separator within a sentence” is part of the “phrase stop” usage category, and is represented by different punctuation marks in different languages:</p>

<ul id="_26ef068e-e67a-a0c9-035f-87281bb95439"><li><p id="_35ad128a-00b5-9852-dae8-4f35a07d48d6">Japanese: IDEOGRAPHIC COMMA <tt>&lt;、&gt;</tt> (U+3001)</p>
</li>
<li><p id="_636ac11a-39b0-b708-3359-d81dc38f97c7">Chinese: FULLWIDTH COMMA <tt>&lt;，&gt;</tt> (U+FF0C)</p>
</li>
<li><p id="_649bf833-c626-0bc9-f26c-c2926c814a50">English: COMMA <tt>&lt;,&gt;</tt> (U+002C)</p>
</li>
</ul>
</example>

<p id="_a8e99fc8-15e7-e7ea-a0cb-480881812081">Not all semantic functions have distinct punctuation marks expressing them in all languages.</p>

<example id="_1f6adf44-8d40-4fcc-78e8-73d50d77552b"><p id="_6b3897ee-ce61-113a-06f4-4873536c715e">The semantic function of “enumeration delimiter”, used in Traditional Chinese and Simplified Chinese, does not exist in English or Japanese as a separate punctuation mark. It is instead conflated with the punctuation mark for minor phrase separator, the comma.</p>
</example>

<p id="_ee6576ff-bc7b-3e71-5914-817642c6084d">The correspondence of semantic function to punctuation mark is many-to-many.</p>

<example id="_db3cdc6b-33b5-8bf1-d552-fe4085a959b8"><p id="_8dabc2e2-9943-f384-4f89-3903dd52eeea">In English, a period can be used as a declarative sentence stop (<xref target="declarative-sentence-stop"/>), but also as an abbreviation mark (<xref target="abbreviation-mark"/>) (<em>Bros.</em>, <em>p.m.</em>). So English period is a punctuation mark fulfilling two semantic functions. In Hebrew, there are two abbreviation marks,</p>

<p id="_e49e4c24-8c3a-2eb5-18f4-2c2a8bdfe4d3"><em>geresh</em> <tt>&lt;׳&gt;</tt> (U+05F3) for a single word (ר׳ “r.” = רבי rabbi), and <em>gershayim</em> <tt>&lt;״&gt;</tt> (U+05F4) for multi-word phrases (ארה״ב “U.S.” =  ארצות הברית “United States”); these are distinct from the sentence delimiter:</p>

<quote id="_846afa8e-b333-6896-d6c5-64b7e01db16c"><p id="_802cea21-aad2-8d79-9d25-08ee3829c7eb">ר׳  יעקב גר בארה״ב. וגם אני, “R(abbi) Yaakov lives in the U.S. And so do I”.</p>
</quote>

<p id="_aa5318b5-b40c-df50-539b-aaa51bd9527d">So the abbreviation mark function is conflated with the sentence delimiter function into the period punctuation mark in English, whereas it is split into a single-word and a multi-word punctuation mark in Hebrew.</p>

<p id="_ece82d9a-dd16-8efb-8684-26c158f1736c">The <em>geresh</em> also has other semantic functions, such as indicating numerals, or as a diacritic for non-Hebrew sounds (גם /ɡam/ “also” vs ג׳ם /dʒam/ “jam”). As a diacritic, the  <em>geresh</em> is no longer punctuation, but represents phonological sounds.</p>
</example>
</dd>
<dt>Punctuation rule</dt>
<dd id="_de7d78ea-a3bf-23d8-e2d1-806ba62cc901"><p id="_4a95368c-f0a9-513b-0d54-01c273ab0add">A guideline that specifies how a punctuation mark should be used in a particular language or context, including placement, spacing, and variations. Some punctuation rules are completely predictable, and can be automated. Other punctuation rules are not predictable, and need to be applied manually and on an idiosyncratic basis.</p>
<example id="_390c7830-3b58-880a-6dbf-846d2a401929"><p id="_3173aa5f-b698-99e1-9dab-f2cb45f555bc">The semantic function of range in Chinese differentiates between word ranges, which use EN DASH <tt>&lt;—&gt;</tt> (U+2013) (1月—7月 “January to July”, literally “Month 1–Month 7”), and numeric ranges, which use WAVE DASH  <tt>&lt;〜&gt;</tt> (U+301C), (5～20個字 “5 to 20 words”). This punctuation rule is predictable: wave dash is used between two numerals (including Chinese numerals).</p>
</example>

<example id="_86c343de-c182-e03b-9b8b-829a15d8ae8f"><p id="_66602e5d-f9df-7f8a-58e5-3f004d9ae814">In Hebrew, <em>geresh</em> follows the initial letters of a word as an abbreviation mark in Hebrew, but the abbreviation may involve just the first letter (ר׳ “r.” = רבי “rabbi”), or more than one letter (גב׳ “Mrs, Ms” = גברת “lady”). It is not predictable how many letters appear in a Hebrew abbreviation: implementing Hebrew abbreviation derived from full words, in a semantic punctuation model, involves either a lookup table of abbreviations, or providing the already abbreviated words as input. (The latter is what is already done by typing גב׳, just as it is in English by typing  <em>Mrs</em> instead of a directive like  <tt>abbreviate("Mistress")</tt>.)</p>
</example>
</dd>
</dl>

<p id="_4d9e4ded-46ee-93b4-b52c-5469a949fdc9">A punctuation profile is defined by:</p>

<ul id="_cacc7508-d89a-a0e6-337e-5a436ebe9ba0"><li><p id="_aea6bdeb-9718-4654-c061-1cbd6f8c8a7c">A set of semantic functions that apply to semantic elements in text</p>
</li>
<li><p id="_f7b0cda3-33eb-96cc-ae92-e995df0b2f4b">Punctuation marks that are associated with each semantic function</p>
</li>
<li><p id="_79adfa58-df79-e5d4-767f-48b531432461">A collection of predictable punctuation rules that govern their usage</p>
</li>
</ul>

<p id="_54776868-8e6f-f821-ae0f-218821fea996">Given a punctuation profile, a document rendering with appropriate punctuation that suits the target audience can be achieved—provided that the punctuation rules can be automated. Not all punctuation rules described here can be so automated, and they will be addressed by being applied manually in authored text.</p>
</clause>

<clause id="_b7a47375-1930-d72b-d32c-0adc57897194" obligation="normative">
<title id="_25b4a44c-a9f2-ea2f-b09c-5e0102961a44">Punctuation semantic functions</title>
<p id="_499ad4ba-44a8-b4c5-350f-3393a7635052">Punctuation marks are assigned semantic functions  by their primary functional usage rather than their linguistic origin.</p>

<p id="_01305387-eac8-34c4-1049-82507011e6f5">This approach enables consistent implementation across different languages, while accommodating language-specific variations within each usage category.</p>

<p id="_c31cbe8f-fbcc-54e2-4422-bf53be7b0238">Under each usage category of semantic functions, each distinct function in the framework is given, along with its typical corresponding marks in Latin (exemplified by English), Cyrillic, and CJK.</p>

<p id="_3f26f348-dd9f-d792-c785-f2fbbb1fb9f6">Each usage category and each individual function defines one of more of the following:</p>

<ul id="_0a8b3c9d-e475-5b8d-7651-dd5f30fe5bbb"><li><p id="_d9c18803-1913-6c1c-620c-4b7efc7c9872">Primary function and purpose</p>
</li>
<li><p id="_42328186-a1ab-6055-0f0f-25e0b6b07906">Range of semantic functions covered, including potential ambiguity with other usage categories</p>
</li>
<li><p id="_810fd44a-c67e-3bc5-0306-a8a3316c6b68">Common punctuation mark variations across languages for each function</p>
</li>
<li><p id="_86a73f68-75f0-4fd4-d87e-0b6e4c010f68">Spacing requirements</p>
</li>
<li><p id="_bef9c3d2-7f26-7d17-4b62-37839dcb50af">Special handling rules</p>
</li>
</ul>

<p id="_8f5240fe-815b-3b42-21ab-873367512a22">The semantic functions described here reflect usage, and punctuation usage does not follow rigorously differentiated functions: similar functions are routinely conflated in punctuation marks, and the same function is routinely represented by different punctuation marks, with little rigour. This framework is concerned with contexts where the intended meaning of punctuation can be controlled by the publishing system, in deriving punctuated, template-generated text from underlying semantic markup. Such templates can specify the intended function of punctuation more rigorously than it is reasonable to expect of a human author.</p>

<p id="_7e18a2e5-bc0c-35b1-d338-9cb4b25d549d">The mapping of semantic functions to punctuation marks is often idiosyncratic, regional, and subject to fashions, as well as to disagreements between authorities as fashions change. This is particularly notable with ongoing changes in English punctuation noted in this document, as well as with the differences between American English and British English practice.</p>

<p id="_2ad5315b-d55f-b410-444b-f647043c41d5">Differences in practice between languages often reflect lags in change; for instance, Greek uses the same ditto mark as Quebec French (<xref target="repetition-mark"/>), not because Greece was in contact with Canada, but because both have preserved older France French practice, which has since been abandoned in France itself. This is also reflected in the formerly more widespread practice of French spacing (<xref target="sentence-stop-spacing"/>), and in Japanese practice matching Traditional Chinese practice rather than Simplified Chinese practice.</p>

<p id="_eaea10fb-0a7b-9429-9b59-b5b693fcc225">Not all semantic functions described here are expected in the kinds of documents that Metanorma processors, but they are included for completeness. Semantic functions that are not expected to be supported by Metanorma are flagged in the following as “(out of scope)”.</p>
</clause>
</clause>

<clause id="_5de37cff-4b51-32b0-8dbe-e671a9eaca33" obligation="normative">
<title id="_712868df-4c6f-52f8-0bef-29c9db47dbdc">Functions: phrase-level structure</title>
<clause id="_5546e780-e415-70cf-cfdd-ea0cd7b58b26" obligation="normative">
<title id="_cc5dc0eb-9d85-3d8f-5f4c-732d486479f4">Sentence stops</title>
<clause id="_3fd916e1-b101-ff43-d98a-6109ef60594f" obligation="normative">
<title id="_634c60ac-a601-38a8-cbaf-d817c32d2423">General</title>
<clause id="_23717f3c-dec2-9fce-0db8-6f8be0d98c6e" obligation="normative">
<title id="_c73cb0c2-e789-7375-371f-f3906008b5ce">Primary function and purpose</title>
<p id="_15bed9ad-7671-5e45-cc1d-c5a18b020c05">Sentence stops delimit a full grammatical sentence.</p>
</clause>

<clause id="_d9c8f578-5d57-add2-8a70-99709fdc205d" obligation="normative">
<title id="_2f869747-1d78-ba5a-e122-d6b1ae81a05d">Range of semantic functions</title>
<p id="_659f0ac4-007a-88a1-eece-936bf3f333a1">Writing systems vary as to whether they also terminate a standalone sentence, and therefore act as a sentence terminator. That is the case in formal English (though often not in texting), but it is not the case in Japanese.</p>
</clause>

<clause id="_61cf672f-4e07-32fe-18e4-c73ed7ca62d6" anchor="sentence-stop-spacing" obligation="normative">
<title id="_80fc99bd-aaaf-cf16-be9d-5cca10b3fd5d">Spacing rules</title>
<ul id="_74c7b907-78ae-2df2-eff6-92ac04197599"><li><p id="_36142257-4db5-291a-358d-8f36b6e0ebe3">Latin and Cyrillic require space after sentence stops as delimiters between sentences, as does Korean.</p>
</li>
<li><p id="_f9ff9ea1-5e49-e0b5-2ec5-7ca9c4a4636c">Writing systems do not require space after the final sentence stop in a paragraph.</p>
</li>
<li><p id="_2275cbb0-f48e-d121-cf2b-e7b2928e3780">Chinese and Japanese by default do not use space after sentence stops.</p>
</li>
<li><p id="_68517c78-f9dd-8131-8e57-f8ac147fc745">None of the writing systems in scope of this framework has space before sentence stops.</p>
</li>
<li><p id="_14140732-4bad-7385-da1d-b9cf30e9d78e">In French in France, Switzerland and Belgium, some punctuation marks, including some sentence stops, are preceded by a non-breaking thin space (U+202F) (“French spacing”). In common practice, a full non-breaking space (U+00A0) is used instead. French spacing is not used for most punctuation marks in Canada for French.</p>
</li>
</ul>
</clause>

<clause id="_d659aa3c-9218-7a7b-fd0b-75e48c6aba93" anchor="cjk-fullwidth-punctuation" obligation="normative">
<title id="_31290eb8-2dfc-d77c-739d-6698e5b1119a">Special handling</title>
<ul id="_b879bf36-8ce3-afe1-4b8d-4278082d9284"><li><p id="_73b27d12-171e-b889-574a-cd8030d21506">Korean sentence stops are half-width.</p>
</li>
<li><p id="_6aed8ba0-aea7-69a3-5f8b-c353847fd5e1">Chinese and Japanese sentence stops are full-width.</p>
</li>
<li><p id="_f25e644a-a6a0-22ee-fba3-7ea6ca0dc7f0">In text mixed between Latin and Chinese or Japanese, usual practice is to follow the document main language. Fine typography will apply kerning in such contexts so that the switch in width does not look obtrusive.</p>
<example id="_856c1165-275f-424f-d565-8e4cc4d36667">
<name id="_b181ab55-aa00-ae00-a1fe-3d235da9e78c">Script switch with Chinese as main language</name>
<p id="_2fc83a6b-ad59-0714-7b1d-3bb65ac03ea6">现在很多人都在用 iPhone。(with full-width punctuation in a Chinese text after English words)</p>
</example>

<example id="_8f321651-9e27-76d1-17e3-e0340c6474a8">
<name id="_ada47604-c3ce-7454-d354-f44d45bf1840">Script switch with English as main language</name>
<p id="_181f9ed0-9a83-b55d-a4d1-636f7729ff5b">This app 很好用.</p>
</example>
</li>
<li><p id="_2ecbed36-4996-920d-9d4e-193ad533b9a6">Some desktop publishing applications in Japanese and CJK OpenType fonts allow switching contextually between full-width and half-width punctuation (欧文混在時の約物処理 “treat punctuation when mixed with Western text”).</p>
</li>
</ul>
</clause>
</clause>

<clause id="_4181a436-2eec-14a9-0203-47e44b66ccca" anchor="declarative-sentence-stop" obligation="normative">
<title id="_904910bb-0b51-cb7d-ffca-c2e7e01333d6">Declarative stop (<em>period</em>)</title>
<clause id="_22de146b-1bfa-8469-0d89-37a0d73dfa3b" obligation="normative">
<title id="_4590c4be-01d6-0ded-8a4c-eb3da87fd7f0">Primary function and purpose</title>
<p id="_ca86b0ec-e6ea-91f2-8807-9defbf976d30">Mark that indicates the end of a complete declarative grammatical statement. This function is represented in Metanorma i18n files as  <tt>punct.period</tt>.</p>

<example id="_715a28d8-96a6-02d9-8a35-65ee654ebdcf"><p id="_4651593c-641e-f30d-be37-76b0bfb6b9d4">English: the period in <em>This is a sentence.</em></p>
</example>

<example id="_e6adb260-8711-d63a-7c67-bdfc810d3435"><p id="_598e6c46-3348-0bfb-4169-2ae9a170c98f">Traditional Chinese: the ideographic period in 這是一句句子。</p>
</example>
</clause>

<clause id="_220d7999-0865-23e3-d681-9ebf60cc2431" obligation="normative">
<title id="_998e22d7-a5d3-2852-8d0b-8b70a82a1229">Punctuation mark in scripts, languages, and locales</title>
<ul id="_5c4f08b5-a119-7c92-7bd0-67c25aa4c34a"><li><p id="_b901dc8b-711e-5296-f2ca-f15ee46c0931">Latin, Cyrillic: FULL STOP <tt>&lt;.&gt;</tt> (U+002E)</p>
</li>
<li><p id="_36eda427-9f67-4758-54a7-d479cdcc5236">Traditional Chinese: IDEOGRAPHIC FULL STOP <tt>&lt;。&gt;</tt> (U+3002)</p>
</li>
<li><p id="_90a96629-0f9d-764d-6009-baed5046440b">Simplified Chinese: IDEOGRAPHIC FULL STOP <tt>&lt;。&gt;</tt> (U+3002)</p>
</li>
<li><p id="_dc50daee-1006-e252-9ede-cd6cf0187367">Japanese: IDEOGRAPHIC FULL STOP <tt>&lt;。&gt;</tt> (U+3002)</p>
</li>
<li><p id="_ab0794dc-458a-ab07-6c64-ba350ff35dde">Korean: FULL STOP <tt>&lt;.&gt;</tt> (U+002E)</p>
</li>
</ul>
</clause>

<clause id="_0b983153-9712-fdf9-499c-560e9dd1722a" obligation="normative">
<title id="_b5df9de5-34bf-37db-0f68-d25b7dc801da">Special handling</title>
<ul id="_b7c2df9c-20f8-fa2a-9a7b-b0253c780e46"><li><p id="_1570c7f0-2437-a94b-0bd9-be1a009e3daa">French spacing does <strong>NOT</strong> apply (<xref target="sentence-stop-spacing"/>).</p>
</li>
<li><p id="_acc2e8de-59bd-60b4-c802-0385e78abdd4">The placement of period in CJK is different by directionality, but this does not involve different Unicode codepoints, so the browser/operating system is assumed to handle positioning appropriately. (While there is a PRESENTATION FORM FOR VERTICAL IDEOGRAPHIC FULL STOP  <tt>&lt;︒&gt;</tt> (U+FE12), this is only included in Unicode as a compatibility character.)</p>
<ul id="_7b69e32d-d3f2-2e23-f412-53a6bbef5ea6"><li><p id="_e865973a-c80d-d8bd-780d-64c7637fbeae">In Japanese and Simplified Chinese horizontal text, the period appears at the bottom right. In Japanese and Simplified Chinese vertical text, the period appears below and to the right of the character.</p>
</li>
<li><p id="_bceea658-0147-73c6-9127-41af6fc4071f">In Traditional Chinese, the period appears at mid-height in both horizontal and vertical text orientations.</p>
</li>
</ul>
</li>
</ul>
</clause>
</clause>

<clause id="_71e51d2b-4da1-5f8e-c7ed-d3da1d512903" anchor="interrogative-stop" obligation="normative">
<title id="_aa082de3-d570-ee33-435e-3f67e0aeb379">Interrogative stop (<em>question mark</em>)</title>
<clause id="_08210eb4-8fcf-86b9-5541-9264f69c6b9b" obligation="normative">
<title id="_ea88ad15-0178-56df-56e2-22f6d8883bab">Primary function and purpose</title>
<p id="_40433937-db88-c956-44c6-861ebfb3f5c3">Mark that indicates this grammatical statement is a question. This function is represented in Metanorma i18n files as  <tt>punct.question-mark</tt>.</p>

<example id="_f4311290-12f7-da3f-6660-d9b0b7ba37bb"><p id="_fbc6fe5b-bbb7-bcc7-d8f9-4450132dc6a2">English: the question mark in <em>Is this a question?</em></p>
</example>

<example id="_d00b1026-350c-d887-8602-bca4bf24f1a5"><p id="_524fd11d-3683-9fdb-850c-355e41097fde">Traditional Chinese: the ideographic question mark in 這是問題嗎？</p>
</example>
</clause>

<clause id="_3417d7c3-e258-560e-e444-34ea2fb8b595" obligation="normative">
<title id="_c201b252-dde9-3929-8ddd-9d98b2212615">Punctuation mark in scripts, languages, and locales</title>
<ul id="_8bd6b7d2-8a6d-2b07-df37-fd97a3e158af"><li><p id="_d5a0b152-d3ee-4e64-3533-4399e731e0ed">Latin, Cyrillic: QUESTION MARK <tt>&lt;?&gt;</tt> (U+003F)</p>
</li>
<li><p id="_ced2887c-1152-37c7-7f29-a71215091b89">Traditional Chinese: FULLWIDTH QUESTION MARK <tt>&lt;？&gt;</tt> (U+FF1F)</p>
</li>
<li><p id="_9eebbc88-90f0-37ac-fe18-d793bbe1dfd7">Simplified Chinese: FULLWIDTH QUESTION MARK <tt>&lt;？&gt;</tt> (U+FF1F)</p>
</li>
<li><p id="_a91bbc78-c6c3-395c-c13b-3d095f7716de">Japanese: FULLWIDTH QUESTION MARK <tt>&lt;？&gt;</tt> (U+FF1F)</p>
</li>
<li><p id="_8c6dfbd7-1887-e024-bb13-95d77f17ea3b">Korean: QUESTION MARK <tt>&lt;?&gt;</tt> (U+003F)</p>
</li>
</ul>
</clause>

<clause id="_cfc1e0b0-c04c-bf3c-6ed6-8b6fc1c420e3" obligation="normative">
<title id="_511578e4-e10d-b0a5-fa09-0b8fd42e0b9c">Spacing rules</title>
<ul id="_7ee97c0f-bda4-7bca-a589-4f5e4d378ce9"><li><p id="_302afe67-f7db-d394-a68a-8d57dd4b2130">French spacing applies (<xref target="sentence-stop-spacing"/>).</p>
</li>
</ul>
</clause>

<clause id="_832c62d4-3b50-5dbb-9cbd-a4eab22d0c6d" obligation="normative">
<title id="_45eb943d-179f-f269-823c-26bf605f844c">Special handling</title>
<ul id="_7def32b3-6f81-c9dc-3291-e19b0f04c5ac"><li><p id="_cc29e769-af59-9c6f-ede2-8db11d3b3be1">In Spanish and languages under Spanish cultural influence (e.g. Catalan), INVERTED QUESTION MARK <tt>&lt;¿&gt;</tt> (U+00BF) is used at the start of an interrogative sentence or phrase. If a declarative sentence contains an  interrogative phrase, only the interrogative phrase is so delimited:</p>
<example id="_a2191b6e-3434-fe03-e11f-6076e1f52d5b"><p id="_340abf0d-7832-9a4c-9c56-862e27fe008e"><em>Si no puedes ir con ellos, ¿quieres ir con nosotros?</em> “If you cannot go with them, ¿would you like to go with us?”</p>
</example>

<ul id="_1d6279b8-8609-ad76-f11d-c6d42a92c07d"><li><p id="_85599bbd-3073-47aa-f4d6-ce4f34293b83">There is some variation by locale in usage: short questions can omit the inverted question mark in Galician; Catalan in Catalonia does not use inverted question marks; Catalan in Valencia uses them optionally.</p>
</li>
</ul>
</li>
</ul>

<admonition id="_a89a3272-6cbe-c0f1-67b5-75f265ae0785" type="tip"><p id="_30445b2c-e45c-b51b-73a9-5ab55870fbc7">Metanorma does not currently implement inverted question marks.</p>
</admonition></clause>
</clause>

<clause id="_0cd94461-b134-9de2-3450-d8621598daa0" anchor="exclamatory-stop" obligation="normative">
<title id="_3a9e43f7-8262-2fef-66da-26fe0089e53b">Exclamatory stop (<em>exclamation mark</em>) (out of scope)</title>
<clause id="_6498fb58-6ad5-c9ce-56b4-81fce4fb3b9b" obligation="normative">
<title id="_b007a488-9803-22a0-a042-6898ffed9b50">Primary function and purpose</title>
<p id="_5bd63187-0905-a79d-27d5-29608578a28e">Mark that indicates this grammatical statement is an exclamation. This function is represented in Metanorma i18n files as  <tt>punct.exclamation-mark</tt>.</p>

<example id="_f5365eef-0ab5-c141-efa8-f929869384be"><p id="_e6539d43-0892-438b-bea4-f3daba5e3f98">English: the exclamation mark in <em>What a great day!</em></p>
</example>

<example id="_1f106eed-b6fb-3beb-1da3-7e1791de9890"><p id="_6bfeb173-09d9-24fa-faf2-3d90fd7bcb6e">Traditional Chinese: the ideographic exclamation mark in 多麼美好的一天！</p>
</example>
</clause>

<clause id="_d286596e-1a9e-1da7-3fce-70c66042e806" obligation="normative">
<title id="_06d02b19-9c7b-b327-7e4b-0fcccd0ed0c8">Punctuation mark in scripts, languages, and locales</title>
<ul id="_9d4dd6c5-e703-06b0-cccf-75da0303d3f7"><li><p id="_4c2c9cd4-8eb2-8e4e-2c66-2e73b4ec04d1">Latin, Cyrillic: EXCLAMATION MARK <tt>&lt;!&gt;</tt> (U+0021)</p>
</li>
<li><p id="_47fc5324-eb15-8abb-5eb3-d7655aa79cf7">Traditional Chinese: FULLWIDTH EXCLAMATION MARK <tt>&lt;！&gt;</tt> (U+FF01)</p>
</li>
<li><p id="_3fbc3d51-4695-dd06-d7a8-1f7b5a482647">Simplified Chinese: FULLWIDTH EXCLAMATION MARK <tt>&lt;！&gt;</tt> (U+FF01)</p>
</li>
<li><p id="_2b716021-59b7-25f8-3cdd-ac9cdb801132">Japanese: FULLWIDTH EXCLAMATION MARK <tt>&lt;！&gt;</tt> (U+FF01)</p>
</li>
<li><p id="_cfa5b790-ee70-6f22-57d9-8b2a0e3b28e6">Korean: EXCLAMATION MARK <tt>&lt;!&gt;</tt> (U+0021)</p>
</li>
</ul>
</clause>

<clause id="_b93d657b-032e-e3f3-4f21-02a1f4cc572a" obligation="normative">
<title id="_dfe4ef36-b022-c4ec-c5bc-96040dbd2576">Spacing rules</title>
<ul id="_db3aa0fd-3f58-dc4c-10c7-1101a5f435d9"><li><p id="_f0b4ea3b-bbf0-230d-c840-97fbe478ba1a">French spacing applies (<xref target="sentence-stop-spacing"/>).</p>
</li>
</ul>
</clause>

<clause id="_c94ebc23-7f4e-7316-58ef-bd848114e686" obligation="normative">
<title id="_b8005b47-1d1a-b509-ef14-d4c1179e9314">Special handling</title>
<ul id="_46553b23-8f22-e579-fbab-00c3e312c040"><li><p id="_92a36076-dea7-0356-f036-52e0b8ba0fd0">In Spanish and languages under Spanish cultural influence (e.g. Catalan), INVERTED EXCLAMATION MARK <tt>&lt;¡&gt;</tt> (U+00A1) is used at the start of an exclamatory sentence or phrase.</p>
</li>
<li><p id="_fd186032-d382-86f5-e41e-46af35c9a783">The same locale considerations apply for Catalan as for inverted question mark.</p>
</li>
</ul>

<admonition id="_888f4aca-4da9-80f5-0328-1d7b89406edf" type="tip"><p id="_86bb2f39-2299-a63a-258a-7144c9100d1d">Metanorma does not currently implement inverted exclamation marks.</p>
</admonition></clause>
</clause>
</clause>

<clause id="_06675681-6bd0-ceb4-7296-13d19fca91a6" obligation="normative">
<title id="_39be568a-5881-b22d-cbaf-311bef27e589">Phrase stops</title>
<clause id="_4a0504a3-90a5-c162-4fdd-385977529d05" obligation="normative">
<title id="_1eacdd25-bd0e-c4cc-8a5f-20cb85cdf39f">General</title>
<clause id="_f8bc9866-be11-b591-9986-364f37edd3a8" obligation="normative">
<title id="_2eaeb88b-4bf8-dd64-e053-91ff65bf89f6">Primary function and purpose</title>
<p id="_350fd98b-23d6-16df-e78d-794b6774b859">Phrase stops delimit phrases within a sentence.</p>
</clause>

<clause id="_2244558d-61e4-a777-c0ad-e701459a7798" obligation="normative">
<title id="_5cd438ec-70c3-7fc9-9289-74129caf2900">Special handling</title>
<p id="_e2d198c2-c076-db5e-a0b2-29a9623a10f4">CJK full-width punctuation (<xref target="cjk-fullwidth-punctuation"/>) applies.</p>
</clause>
</clause>

<clause id="_ee588094-168d-430a-f17b-dae745a5cea8" anchor="minor-phrase-separator" obligation="normative">
<title id="_65e21ab4-bc38-57d0-d79d-1a568b57da7f">Minor phrase separator (<em>comma</em>)</title>
<clause id="_3f0989db-5a62-a046-c38f-a5ad8c0f724c" obligation="normative">
<title id="_67a8be14-04f2-a967-9940-2d6c4eb3604d">Primary function and purpose</title>
<p id="_c8b9cc07-f2a0-54b1-b5ea-f88f95a92fa9">Mark that delimits a minor break between phrases within a sentence. This function is represented in Metanorma i18n files as  <tt>punct.comma</tt>.</p>

<example id="_9a4bbf4c-4354-d445-e330-b0c28b899afa"><p id="_320550ba-cf81-4164-6fac-fc55900ad309">English: the comma in <em>This is a sentence, with a pause.</em></p>
</example>

<example id="_1f7cc32f-a4c9-2ecb-5d43-1911ed785579"><p id="_92078e5a-414c-b0f3-57e6-6884d2a68262">Traditional Chinese: the full-width comma in 這是一句句子，有停頓。</p>
</example>
</clause>

<clause id="_9510fa62-432e-bc39-96b1-e42fd3eaed5e" obligation="normative">
<title id="_d135d18a-0d6e-98f4-fb3c-49ea703f4c6f">Range of semantic functions</title>
<ul id="_4d95b5cf-b807-7d92-f5d0-ecba974f3397"><li><p id="_18c4707b-c3c5-492a-66db-61458385aa06">The contexts in which the minor break is marked between phrases vary significantly by language and by style.</p>
</li>
<li><p id="_6f0bf2d8-227b-be52-0853-fd8c1b66eee6">The types of phrase eligible to be so marked also vary significantly by language and by style; it usually includes both clauses (which express a complete predicate, including both a subject and a verb) and smaller units such as noun phrases, or successive adjectives.</p>
<example id="_859137c6-b2a7-c364-fa64-615bddb3f9cd"><p id="_789001ca-55bc-69ba-9227-7e92e350510a"><em>Ich weiß, dass du lügst</em> “I know, that you’re lying”, with comma separating a complement clause from the main clause, is correct punctuation in German, but not English</p>
</example>
</li>
<li><p id="_0b43762e-5d3e-66c0-db69-5647cf0b1e7f">In many writing systems, the same mark (comma) is used for minor phrase separators and other separating functions, such as enumerator delimiters (<xref target="enumeration-delimiter"/>), and decimal point (<xref target="decimal-point"/>).</p>
</li>
</ul>
</clause>

<clause id="_d8400f13-0766-9c99-2169-3a744eb470a6" obligation="normative">
<title id="_8376d74d-6341-7794-0062-04191f124ccf">Punctuation mark in scripts, languages, and locales</title>
<ul id="_b00037ee-ff41-f179-852a-b185c4bdd75a"><li><p id="_8f2bcc08-3dc6-e8b4-e48c-fc085615632f">Latin, Cyrillic: COMMA <tt>&lt;,&gt;</tt> (U+002C)</p>
</li>
<li><p id="_c70dc73d-e4e1-0fdd-6c61-f4c0df655f69">Traditional Chinese: FULLWIDTH COMMA <tt>&lt;，&gt;</tt> (U+FF0C)</p>
</li>
<li><p id="_705e0ce5-24f4-b942-07cb-2997c3ea9d1c">Simplified Chinese: FULLWIDTH COMMA <tt>&lt;，&gt;</tt> (U+FF0C)</p>
</li>
<li><p id="_d2400412-b271-f44a-dd0d-645704431d7f">Japanese: IDEOGRAPHIC COMMA <tt>&lt;、&gt;</tt> (U+3001)</p>
<ul id="_54561c80-788b-4c67-a31b-25c55e37e58e"><li><p id="_2faa8be2-1279-5f1d-6b8a-b826135fcde9">In mixed Japanese-Western text, FULLWIDTH COMMA <tt>&lt;，&gt;</tt> (U+FF0C) can be used instead to maintain visual consistency</p>
</li>
<li><p id="_4344c18d-78d2-2d15-53ad-7f89765cb645">IDEOGRAPHIC SPACE <tt>&lt;　&gt;</tt> (U+3000) can be used in Japanese corresponding to English comma or colon usage in certain contexts.</p>
</li>
</ul>
</li>
<li><p id="_79813973-5054-9bb1-beec-0ad41d3bd1dc">Korean: COMMA <tt>&lt;,&gt;</tt> (U+002C)</p>
</li>
</ul>
</clause>

<clause id="_56443a91-0d77-3717-a987-af32137bbc40" obligation="normative">
<title id="_c4667d82-39b4-f076-d280-fe7238c657bb">Special handling</title>
<p id="_395a87f1-9f5e-e300-99da-61569e1ba2f1">The placement of comma in CJK is different by directionality, but this does not involve different Unicode codepoints, so the browser/operating system is assumed to handle positioning appropriately. (While there is a PRESENTATION FORM FOR VERTICAL COMMA  <tt>&lt;︐&gt;</tt> (U+FE10) and a PRESENTATION FORM FOR VERTICAL IDEOGRAPHIC COMMA  <tt>&lt;︑&gt;</tt> (U+FE11), these are only included in Unicode as a compatibility character.)</p>

<ul id="_d27b23c5-bdcc-39c5-26ed-5a929941bfe5"><li><p id="_f156f12a-9b0d-7e3d-51d2-4b598f0bc41f">In Japanese and Simplified Chinese horizontal text, the comma appears at the bottom right. In Japanese and Simplified Chinese vertical text, the comma appears below and to the right of the character.</p>
</li>
<li><p id="_4c05a325-0e2e-2601-ddab-b6eb0dceea17">In Traditional Chinese, the comma appears at mid-height in both horizontal and vertical text orientations.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_bed1eda8-6a7f-cbff-d5db-8d67abb6857d" anchor="major-phrase-separator" obligation="normative">
<title id="_d4c0bd32-5700-4254-66aa-7f9655760e34">Major phrase separator (<em>semicolon</em>)</title>
<clause id="_fd7b6aa4-063a-59de-76c2-a443f0e347a4" obligation="normative">
<title id="_91586be3-48a3-ebc0-0f85-b07c65b1bbdf">Primary function and purpose</title>
<p id="_38fe6530-9432-c35e-7a4e-0cb164ed0ad4">Mark that delimits a major break between phrases within a sentence. This function is represented in Metanorma i18n files as  <tt>punct.semicolon</tt>.</p>

<example id="_59ee0c85-5993-5f7f-75cc-3212edc479bb"><p id="_7577539f-6599-94ae-024a-a91645c46175">English: the semicolon in <em>This is a sentence; with a pause.</em></p>
</example>

<example id="_b3d58145-5d03-fb88-e302-b2442890d358"><p id="_06467bbb-5e25-a6aa-52d1-118c0ea2d8cd">Traditional Chinese: the full-width semicolon in 這是一句句子；有停頓。</p>
</example>
</clause>

<clause id="_b7043d29-5d67-20ff-b455-e84df8fc961b" obligation="normative">
<title id="_d14049f0-7551-6906-9a9e-b5229da12cff">Range of semantic functions</title>
<ul id="_f7f6da8f-b449-3939-eefb-7779a651b432"><li><p id="_3fc466d0-d6a7-8641-5b99-8b4ff5865e7e">The contexts in which the major break is marked between phrases varies significantly by language and by style. In many styles, it is avoided as an overly fine distinction from the minor break (comma).</p>
</li>
<li><p id="_9da88d50-a3e6-794c-5b8c-5483aa28e873">The phrases separated by a major phrase separator are typically independent clauses grammatically (i.e. complete predicates, with both a subject and a verb).</p>
</li>
</ul>
</clause>

<clause id="_8f73a937-0e3d-9ee0-a804-f6a307018c5f" obligation="normative">
<title id="_b9ed5694-9749-b007-da92-886ea41b2b67">Punctuation mark in scripts, languages, and locales</title>
<ul id="_cdb3d915-dd88-a972-9498-9efaa010363f"><li><p id="_0be58239-6206-c98d-4255-c19aa0397931">Latin, Cyrillic: SEMICOLON <tt>&lt;;&gt;</tt> (U+002C)</p>
</li>
<li><p id="_4ff1a30b-4154-6d3e-8225-d57afa88a729">Traditional Chinese: FULLWIDTH SEMICOLON <tt>&lt;；&gt;</tt> (U+FF1B)</p>
</li>
<li><p id="_6038f488-b3aa-8a40-30b4-21349071638d">Simplified Chinese: FULLWIDTH SEMICOLON <tt>&lt;；&gt;</tt> (U+FF1B)</p>
</li>
<li><p id="_70332059-2fb2-5507-9cda-35467d908922">Japanese: FULLWIDTH SEMICOLON <tt>&lt;；&gt;</tt> (U+FF1B)</p>
</li>
<li><p id="_52c853de-4d56-fea0-16c7-d96765ad2c92">Korean: SEMICOLON <tt>&lt;;&gt;</tt> (U+002C)</p>
</li>
</ul>
</clause>

<clause id="_b6b1022e-b554-e7c9-4c2f-e353eb38ac17" obligation="normative">
<title id="_e580e985-f0f2-fb0a-58eb-1226d1f7dcc2">Spacing rules</title>
<ul id="_0de33016-71c6-b3af-e1e1-ed8d7d8d4c4c"><li><p id="_db166fc0-cd9f-ccf4-914e-ff7f75ba9387">French spacing applies (<xref target="sentence-stop-spacing"/>).</p>
</li>
</ul>
</clause>

<clause id="_10806d94-b47b-9116-82f3-d16086f4d91d" obligation="normative">
<title id="_b802798b-d8b8-a075-9d7c-52e4f5315bc6">Special handling</title>
<p id="_2c26939c-5698-2998-c2c0-14ef86c23b3c">The placement of semicolon in CJK is different by directionality, but this does not involve different Unicode codepoints, so the browser/operating system is assumed to handle positioning appropriately. (While there is a PRESENTATION FORM FOR VERTICAL SEMICOLON  <tt>&lt;︔ &gt;</tt> (U+FE14), this is only included in Unicode as a compatibility character.)</p>
</clause>
</clause>

<clause id="_43c4e135-49b5-5472-6973-1b20b88eb5ce" anchor="introductory-phrase-separator" obligation="normative">
<title id="_c82c4197-a72f-aa27-c92f-11872cafce20">Introductory phrase separator (<em>colon</em>)</title>
<clause id="_fcfafd12-083a-27d8-c519-7430899b58d6" obligation="normative">
<title id="_871a81bb-09b3-5b50-8d70-9be120e85a60">Primary function and purpose</title>
<p id="_634ed6e2-edb3-7f52-4a7b-8111367cef56">Mark that delimits phrases within a sentence, where the first phrase introduces the second. This function is represented in Metanorma i18n files as  <tt>punct.colon</tt>.</p>
</clause>

<clause id="_84e59540-7932-f7dd-7e08-b0e00e1d00a6" obligation="normative">
<title id="_0509bfaf-36fe-a46f-9039-0abdd03d115c">Range of semantic functions</title>
<ul id="_ec1e609e-1b5e-9e7a-3735-b528db574e82"><li><p id="_5d4ac44c-a4bd-b673-755f-75a1375b85da">Sometimes punctuation is used to separate a term from a description in a definition list, although the default is to use only indented space. This function can be regarded as an extension of the introductory phrase separator. In Metanorma Presentation XML, this is notated as  <tt>&lt;span class="fmt-dt-delim"&gt;</tt>.</p>
</li>
</ul>

<example id="_8da003ec-877b-183e-ed0c-842b4559164d"><dl id="_6c5a6246-f7cf-0e9b-5733-2f60e14ee1d9"><dt><em>Framework</em></dt>
<dd id="_4f8f544b-bfcd-187e-1e3f-1f2e2d099129"><p id="_8e2dbdd7-a9f1-bef9-3933-b7d444ea7aa9"><em>basic structure underlying a system, concept, or text</em></p>
</dd>
<dt><em>Framework:‌</em></dt>
<dd id="_4d656607-a4f3-c778-7cac-ac394a3f46f6"><p id="_3a1e52ab-e316-2576-baf3-fa4e2de557dd"><em>basic structure underlying a system, concept, or text</em></p>
</dd>
</dl>
</example>
</clause>

<clause id="_299fd05c-1575-7ebd-ad75-91621f95e355" obligation="normative">
<title id="_3ec0f5f2-aeb5-57f5-2a91-3fbc5dedfba3">Punctuation mark in scripts, languages, and locales</title>
<ul id="_90c90b10-e4ca-5b49-bef8-a3efed4e80c2"><li><p id="_e5a77eb5-33b2-b93c-d2e4-118e87cce9a4">Latin: COLON <tt>&lt;:&gt;</tt> (U+003A)</p>
</li>
<li><p id="_f515b549-2911-ecca-7c52-8acadf577284">Cyrillic: COLON <tt>&lt;:&gt;</tt> (U+003A)</p>
</li>
<li><p id="_33a96a09-0593-7ccd-3fd6-fc75f0fcd35e">Traditional Chinese: FULLWIDTH COLON <tt>&lt;：&gt;</tt> (U+FF1A)</p>
</li>
<li><p id="_e2a3b0d2-cb25-9986-c61e-d365574d81f0">Simplified Chinese: FULLWIDTH COLON <tt>&lt;：&gt;</tt> (U+FF1A)</p>
</li>
<li><p id="_98679027-94a5-53e3-f430-98993e438faf">Japanese: FULLWIDTH COLON <tt>&lt;：&gt;</tt> (U+FF1A)</p>
<ul id="_1754d3c4-ecb6-0380-6e57-991eb679d00d"><li><p id="_80d13830-cf11-82ff-3df5-7ff0a07f91ca">IDEOGRAPHIC SPACE <tt>&lt;　&gt;</tt> (U+3000) can be used in Japanese corresponding to English comma or colon usage in certain contexts.</p>
</li>
</ul>
</li>
<li><p id="_ee9f9899-0301-6de7-c8e5-89ba6f462eaf">Korean: COLON <tt>&lt;:&gt;</tt> (U+003A)</p>
</li>
</ul>

<clause id="_72b7b575-aa90-f1a6-f7cf-c58004550fc0" obligation="normative">
<title id="_1c6bf03f-765d-b79c-ae4c-9e043f30dc7e">Spacing rules</title>
<ul id="_9e70642d-ba6e-c623-2a71-d97331722b8f"><li><p id="_9d51cdad-c1bc-96de-459c-a95df838091c">In French, colon is preceded by a non-breaking space. There is more variation by locale of this spacing rule than for other punctuation marks, for which French spacing applies (<xref target="sentence-stop-spacing"/>).</p>
<ul id="_6535cfca-6f91-6ce6-6657-e4b240dc6fcf"><li><p id="_36f4fbda-81d8-fda6-4ac9-30002524f18a">In Switzerland, it is thin space (U+202F).</p>
</li>
<li><p id="_23b5a233-542d-cf07-d9f1-13abf3958118">In Canada, colon is the only punctuation mark where French spacing is expected, and it is a full space (U+00A0).</p>
</li>
<li><p id="_eb51da9f-7240-6bea-cd40-377036112b14">In France, a full space (U+00A0) is usual.</p>
</li>
</ul>
</li>
</ul>
</clause>
</clause>

<clause id="_fdfcad6f-db8a-769f-57d4-e685da4ee485" obligation="normative">
<title id="_aca6a920-3cb2-0d6d-acae-7ce546c94764">Special handling</title>
<p id="_c766cb01-1b44-f6f0-6d6c-89e8ef2daabe">The placement of colon in CJK is different by directionality, but this does not involve different Unicode codepoints, so the browser/operating system is assumed to handle positioning appropriately. (While there is a PRESENTATION FORM FOR VERTICAL COLON  <tt>&lt;︓ &gt;</tt> (U+FE13), this is only included in Unicode as a compatibility character.)</p>

<p id="_774bd80d-1978-8ff3-84d0-50289a9f53e1">The interpunct (<xref target="interpunct"/>) is used instead of hyphen, dash, or colon in Japanese vertical text.</p>
</clause>
</clause>

<clause id="_9e9c72b0-6966-2aeb-dc2e-ec9ef5c8d704" anchor="breaking-phrase-separator" obligation="normative">
<title id="_3c91b386-f869-7558-c18d-63d05562dc7e">Breaking phrase separator (<em>em-dash</em>)</title>
<clause id="_469921e9-76b3-ccae-611f-20338337874c" obligation="normative">
<title id="_ce91e74a-18f6-b269-351b-c403a57017df">Primary function and purpose</title>
<p id="_2fd95ee7-a5ae-c3ad-8b52-f35dcb99f45b">Mark that delimits phrases within a sentence, where there is a conceptual break of some sort between the first phrase and the second. This function is represented in Metanorma i18n files as  <tt>punct.em-dash</tt>.</p>
</clause>

<clause id="_9bbe63f0-7724-8221-ec29-821c1ce5bdc8" obligation="normative">
<title id="_a5cb8d19-e1f6-2e5b-c417-46c8dc4298af">Range of semantic functions</title>
<ul id="_3f07ea28-47c7-9fda-ca20-902228452dcc"><li><p id="_dbab7a5d-b2fc-9313-e522-415908ca215b">An interrupted ending to a sentence can be indicated by a breaking phrase separator. Similarly, a sentence start which counts as a resumption from a previous interruption can be indicated by a breaking phrase separator.</p>
<example id="_aaeddd13-9dd1-a88a-1c47-84216059aafb"><p id="_118c244b-517d-faed-5446-a9df485691fa"><em>He was the miracle ingredient Z-147. He was—</em><br/> <em>“Crazy!” Clevinger interrupted, shrieking. “That’s what you are! Crazy!”</em><br/> <em>“—immense. I’m a real, slam-bang, honest-to-goodness, three-fisted humdinger. I’m a bona fide supraman.”</em> —  Joseph Heller,  <em>Catch-22</em></p>
</example>

<ul id="_78e18fb7-c243-f6bc-289c-87dd9656f000"><li><p id="_bf961f6f-44a8-d01c-b61f-0d55061cb885">Interrupted and resumed sentences are characteristic of literary prose, but not formal prose, such as is in scope of Metanorma.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_813c4e17-7390-02cf-429e-d4aa1f0b8bf2" obligation="normative">
<title id="_d19444ad-385d-d93e-7d48-7b8fc19f0b31">Punctuation mark in scripts, languages, and locales</title>
<ul id="_650ebc4a-04b9-c508-5b54-78ef17e16995"><li><p id="_23e1cc99-a677-ac4b-c5bb-6a00e4bd85fc">Latin, Cyrillic: EM DASH <tt>&lt;—&gt;</tt> (U+2014)</p>
<ul id="_ad71d2fc-3e8c-a66c-d44f-ffffebaf83c8"><li><p id="_64fdcb0d-84ee-e05f-b627-79c2fa71eee3">The EN DASH <tt>&lt;–&gt;</tt> (U+2013) is also used in this function</p>
</li>
<li><p id="_27671a36-093c-d9be-4925-8e3f27299247">Double and triple hyphens are typewriter approximations of em-dashes, and are commonly used in word processing as easy ways to data enter em-dashes through auto-text; they are not normally expected to display as such in finished documents, although they remain a convention of comic strips.</p>
</li>
<li><p id="_ad324696-45b3-cb4a-adc2-0b0e0dac1f34">In some style guides (e.g. the <em>Australian Government Style Manual</em>), interrupted and resumed sentence breaks are notated with two em-dashes, as a distinct function from the breaking phrase separator.</p>
</li>
</ul>
</li>
<li><p id="_4ac2230e-ea26-4875-66d6-b6ba6bc421be">Traditional Chinese: TWO EM DASH <tt>&lt;⸺&gt;</tt> (U+2E3A)</p>
</li>
<li><p id="_0256c9a1-c3df-d00d-9116-41103b13039e">Simplified Chinese: TWO EM DASH <tt>&lt;⸺&gt;</tt> (U+2E3A)</p>
</li>
<li><p id="_b7f91b05-0c00-bced-278b-b9d206887f3f">Japanese: TWO EM DASH <tt>&lt;⸺&gt;</tt> (U+2E3A)</p>
<ul id="_630fe687-1673-55b7-aea5-549fd4bd3b79"><li><p id="_80533c4d-16ae-86e4-2188-2bce1aa77f82">Informally in CJK, twice em-dash (U+2014 U+2014) is used instead of the two em-dash.</p>
</li>
</ul>
</li>
<li><p id="_719736ea-7c85-90a2-8d69-771f4bfeb396">Korean:  EM DASH <tt>&lt;—&gt;</tt> (U+2014)</p>
</li>
</ul>

<clause id="_a2afd72f-161c-a70e-0245-4fad2a061c5e" obligation="normative">
<title id="_4379e409-c94b-71b5-546d-457546b3d0cf">Spacing rules</title>
<ul id="_05215622-d7cd-75f0-31c5-147058a593b5"><li><p id="_b527bc6c-30c1-df29-07b8-64fb24df457f">There is variation between languages and locales as to whether em-dash or en-dash is used. Spaces surrounding the dash are required for en-dash, and may or may not be required for em-dash. The spaces are thin spaces in fine typography, but may be normal spaces in common practice.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_9f3af2fd-8005-e7c1-2e3c-13058963d0ca" obligation="normative">
<title id="_502278a1-174c-a82d-c66d-5a14730592ec">Special handling</title>
<ul id="_59aaf7bc-ae72-b1ab-c2d1-b7261ad24d09"><li><p id="_c28a9a4e-ad03-f9d4-cb18-a4747951a4a5">The placement of em-dash in CJK is different by directionality, but this does not involve different Unicode codepoints, so the browser/operating system is assumed to handle positioning appropriately. (While there is a PRESENTATION FORM FOR VERTICAL EM DASH  <tt>&lt;︱&gt;</tt> (U+FE31), this is only included in Unicode as a compatibility character.)</p>
</li>
<li><p id="_47ef4614-4ec6-2841-10dd-d70726808009">The interpunct (<xref target="interpunct"/>) is used instead of hyphen, dash, or colon in Japanese vertical text.</p>
</li>
<li><p id="_980b3833-3498-141b-8a3c-792312506925">An interrupted ending to a sentence can be indicated by a breaking phrase separator. In that case, the breaking phrase separator replaces the sentence stop.</p>
<example id="_ef25c1ad-4204-0338-d2bb-91a9821e0a52"><p id="_32896f40-4135-9f89-0031-95315157059e"><em>He was the miracle ingredient Z-147. He was—</em><br/> <em>“Crazy!”</em></p>
</example>
</li>
</ul>
</clause>
</clause>

<clause id="_c760edac-d326-63db-e319-cfd2aedf2710" anchor="hesitancy-phrase-separator" obligation="normative">
<title id="_28e49f80-3546-aaf9-367d-30cc82169d62">Hesitancy phrase separator (out of scope)</title>
<clause id="_0038b775-995f-1740-d9c5-44f53e6307b9" obligation="normative">
<title id="_ed78be2c-9843-ffb1-1505-f4bcf2ca7858">Primary function and purpose</title>
<p id="_981d2619-6fc2-25e1-729d-4e0ffa084d86">Mark that delimits phrases within a sentence, where there is some sort of hesitation between them.</p>
</clause>

<clause id="_1707bb79-298a-fef3-2031-849663ee7de0" obligation="normative">
<title id="_45098059-2ecb-4c36-297c-544ed806dc81">Range of semantic functions</title>
<ul id="_d397f0da-1920-2b81-21b0-d24f714090b1"><li><p id="_ff9b8613-6ae2-ed1f-a1ad-76bdae745c21">The hesitancy phrase separator is closely related to the breaking phrase separator, and in past practice was conflated with it.</p>
</li>
<li><p id="_51f24005-d2d2-ec5a-d1c9-3b80cb06b591">The hesitancy phrase separator is routinely conflated with the missing text mark (<xref target="missing-text-mark"/>), but the two interact differently with other punctuation.</p>
</li>
<li><p id="_e4b6e2c3-6b57-c922-38e4-43c2780e5b38">“Hesitancy” is to be broadly understood, and it includes pauses, interruption, speechlessness, deliberate silence, longing, and surprise. Different languages place different expectations on the punctuation mark.</p>
</li>
<li><p id="_07cbb6d3-eb1d-d7d6-466c-a460792725a0">The hesitancy phrase separator is associated with emotion, and is therefore avoided in formal writing, such as is in scope of Metanorma. The missing text mark, on the other hand, is entirely consistent with formal writing.</p>
</li>
</ul>
</clause>

<clause id="_1672f241-950e-aa46-3e32-7472dee75b50" obligation="normative">
<title id="_09666d7b-9a09-bc7e-9251-755261f4b29a">Punctuation mark in scripts, languages, and locales</title>
<ul id="_ba51c297-86b9-c59a-34a0-f7aaf3dc9380"><li><p id="_12f930b0-5e06-07b8-cedd-2f23c32ae32b">Latin, Cyrillic: in fine typography, a single HORIZONTAL ELLIPSIS <tt>&lt;…&gt;</tt> (U+2026) is used. In informal practice, three periods in succession are used as well.</p>
<ul id="_6f1ed9b7-cb22-b2ef-5035-e3b601c31f3e"><li><p id="_4389a583-7ec9-c95e-1c70-7d6192c0ab10">In some fine typographic practice, the em dash for the breaking phrase separator is used instead.</p>
</li>
<li><p id="_4c0be55c-b48c-00e5-7b9c-a9aa0724a2a6">In some fine typographic practice, the three periods are interpolated with non-breaking spaces, or thin non-breaking spaces.</p>
</li>
</ul>
</li>
<li><p id="_0488b9d3-3c7b-ae6c-baf5-192553b9a502">CJK: the ellipse can be presented as three dots, or six dots.</p>
<ul id="_8446eb6b-1175-19e9-d87f-9c4129caa025"><li><p id="_a2c41e96-3bbc-7c27-7993-5f6eda6d333a">The six dot form is entered as twice the full-width three-dot form.</p>
</li>
<li><p id="_4448df87-28d2-a541-4bde-6e5bde8076c5">The CJK form is either MIDLINE HORIZONTAL ELLIPSIS <tt>&lt;⋯&gt;</tt> (U+22EF), as explicit centered markup, or the half-width HORIZONTAL ELLIPSIS (U+2026) where centering is inexplicit, rendered in CJK fonts as full-width.</p>
</li>
<li><p id="_f5900bc6-f7e1-fc8e-354f-446c1a661fd8">Japanese rarely also uses a two-dot ellipse (<em>rīdā</em>).</p>
</li>
</ul>
</li>
</ul>

<clause id="_c319216a-4f8b-b5ed-745a-f5720e08d498" obligation="normative">
<title id="_b738d1ac-a233-b3b5-0fb7-adb26ded35c5">Spacing rules</title>
<ul id="_e0a1ec67-ba5f-5c86-5a1c-f07cf8b54b1b"><li><p id="_8fcb00ec-4d1d-8636-4fbd-81a30138f834">Languages and style guides vary as to whether they put spaces before or after the hesitancy phrase separator, and between the ellipse dots within the hesitancy phrase separator—and when. For example, the Modern Language Association styleguide has recently changed its recommendation from space before in all contexts, to no space before in the phrase separator function.</p>
</li>
<li><p id="_c9a9b39f-3adf-9283-2b89-a897cf90b3b6">In French, French spacing applies (<xref target="sentence-stop-spacing"/>).</p>
</li>
</ul>
</clause>
</clause>

<clause id="_236fd536-df39-7876-155d-ac36a6771f72" obligation="normative">
<title id="_64cd3c1e-1204-b6b5-0b51-58ce64b35802">Special handling</title>
<ul id="_9ab5d520-c100-98d4-ca0d-09f9bb49abb1"><li><p id="_74ec5f90-dcd7-6c46-edfc-4601b0ed4392">If the hesitation follows the final phrase in a sentence, some practice has the hesitancy mark replace the sentence stop (e.g. common British English practice). Other practice appends the sentence stop to the hesitancy mark, as a fourth dot (e.g.  <em>Chicago Manual of Style</em>).</p>
<example id="_18b1b7f9-b20f-c3ab-38a9-7667789b3926"><p id="_2b604063-bef5-f60a-175f-2dbbde940e74"><em>I like traffic lights…</em><br/> <em>I like traffic lights… .</em></p>
</example>
</li>
<li><p id="_78647771-fe78-f4a2-5eae-9f9c71ee9c32">Russian combines not only declarative but interrogative and exclamatory sentence stops with the hesitancy mark and missing text mark:  <tt>&lt;?..&gt;</tt>, <tt>&lt;!..&gt;</tt>.</p>
</li>
<li><p id="_f1113479-23e7-8276-658f-38cccbfe8657">Unlike other stops, the hesitation phrase separator can appear at the start of a sentence.</p>
</li>
<li><p id="_5ac49626-e346-a2f9-bf4b-46896a526cb5">In horizontal directonality in Traditional Chinese and Japanese, the ellipse is vertically centered; in vertical directionality, it is horizontally centered.</p>
</li>
<li><p id="_0cdd2cf0-b7d0-d997-a82b-fb8b160cfeb1">In Simplified Chinese, the ellipse is usually aligned to the baseline in horizontal directionality; in vertical directionality, it is still horizontally centered.</p>
</li>
<li><p id="_130bcfb7-81a9-3e4c-35cf-5b6eadd27240">In vertical directionality in CJK, Unicode has a codepoint for VERTICAL ELLIPSIS   <tt>&lt;⋮&gt;</tt> (U+22EE), and it is not designated as a compatibility character. However as with other punctuation, the browser/operating system is assumed to handle positioning appropriately, so MIDLINE HORIZONTAL ELLIPSIS would still be expected to be entered.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_9b452761-bf28-5e74-47ee-2031d151ee15" obligation="normative">
<title id="_66479770-fa26-fcf4-a1c4-2a0e36696f61">Verse separator (out of scope)</title>
<clause id="_73232189-0daa-22b2-76e4-b7beea847bde" obligation="normative">
<title id="_c9f3ff5c-d173-38b9-e00b-c7892e2e06fa">Primary function and purpose</title>
<p id="_3361399f-ee90-5147-6131-b8b8fb6b7515">Mark that delimits verses in poetic writing.</p>
</clause>

<clause id="_be8c6533-04b5-ad44-b792-5597a273e137" obligation="normative">
<title id="_0cda213d-9ceb-b766-21c5-b1c9cb285f3b">Punctuation mark in scripts, languages, and locales</title>
<ul id="_7d2acc8b-6879-f61b-b297-6e4d08ffe1d8"><li><p id="_41c804fc-ed1d-d91f-ec6e-7103acef4c4f">In verses presented as poetry, verses are globally separated by line breaks, which are not regarded as punctuation.</p>
</li>
<li><p id="_f3e2670c-0c39-d722-3461-37379b8661a4">In prose transcription of poetry, verses are often separated by a slash:  SOLIDUS <tt>&lt;/&gt;</tt> (U+002F).</p>
<ul id="_6861d098-6fa5-36bf-c2ca-3a9b55f03557"><li><p id="_624a8bf0-8bae-6f42-05d4-b341932e0f10">There is some usage of VERTICAL LINE <tt>&lt;|&gt;</tt> (U+007C) instead.</p>
</li>
</ul>
</li>
</ul>

<example id="_77f66566-90a4-4a0a-1006-5f1ccdecd41b">
<name id="_306fefdf-6ec7-0a6a-79d0-1a6333987c80">Poetic typesetting</name>
<p id="_c4f4fd90-2cd8-2c53-3cec-b0d6f4f6a684" align="left"><em>To be, or not to be, that is the question:</em><br/> <em>Whether ’tis Nobler in the mind to suffer</em><br/> <em>The Slings and Arrows of outrageous Fortune,</em><br/> <em>Or to take Arms against a Sea of troubles,</em><br/> <em>And by opposing end them…​</em></p>
</example>

<example id="_6b40275e-c047-f509-240a-3182157b8580">
<name id="_361dd057-4382-7340-fbfb-0e4b7180485b">Prose typesetting</name>
<p id="_596de82e-b02c-627f-381e-d4df8db65f75"><em>To be, or not to be, that is the question: / Whether ’tis nobler in the mind to suffer / The slings and arrows of outrageous Fortune, / Or to take arms against a sea of troubles, / And by opposing end them…​</em></p>
</example>
</clause>

<clause id="_f1beade3-9440-3fc6-516a-4ea70753d043" obligation="normative">
<title id="_84f426c5-d31c-8c43-4d91-65ec82b7e894">Spacing rule</title>
<ul id="_b6454dad-80d9-ebf4-c27c-9bda5be580aa"><li><p id="_71614c8a-b27d-f93d-14b3-f1b6627306c7">When slash is used to separate verses, there is a space either side of the slash.</p>
</li>
</ul>
</clause>

<clause id="_e7b1f574-5db8-05a2-5fde-ff96de7b6e84" obligation="normative">
<title id="_311501b4-8653-28de-4dca-64fc688ac90f">Special handling</title>
<p id="_20764637-e1a7-489f-5192-4d22f5e72037">In poetic presentation (one verse per line), separate verses must not be right-justified at the line-break.</p>
</clause>
</clause>

<clause id="_66e27bf0-aef7-a69e-8ee6-da0687783936" anchor="section-separator" obligation="normative">
<title id="_5371d744-ffde-1631-1b92-ec9a1cd10d3f">Section separator (out of scope)</title>
<clause id="_b3f87a06-d32a-09a6-81a7-83de057d654f" obligation="normative">
<title id="_3789e1f4-180a-3dea-ae26-7a41d68948ca">Primary function and purpose</title>
<p id="_d38c46c7-37b1-58e6-215a-ea79be4d5cdf">The section separator includes a break in a document, at a higher level than a sentence or paragraph. This is distinct from a clause heading, which introduces a new section of text, with a number and/or a title.</p>

<example id="_4ea69c35-6973-c963-c4cf-64bba7eb99e1"><p id="_60b0c7fa-a162-0872-3cf3-d0f7296acdde"><em>…Randy looked at this watch. He was sweating buckets.</em></p>

<p id="_b917a5ce-a900-1b59-b176-b6be2d52b82e"><em>“If the otter police don’t get here soon, we’re in deep trouble,” he said.</em></p>

<p id="_299d631e-1d1b-5565-af08-dbb6b35f972a"><em>James nodded. “I’m almost out of kibble. And the bits are running low too.”</em></p>

<p id="_2b2239a0-2473-0219-35b9-8af7f390a8f3" align="center"><tt>*         *         *</tt></p>

<p id="_c4e3eac1-32a9-ebff-22dc-17c9916dfe4f"><em>In the blimp floating high over Ferretsburg, Captain Crandle looked down at the unfolding battle with growing annoyance….</em></p>

<p id="_46ccd724-20a9-4ebb-8c8d-3040df55f87a">— <link target="https://greenwalledtreehouse.com/2022/03/05/writing-corner-the-dinkus/"/></p>
</example>
</clause>

<clause id="_62229bfb-dc95-0595-bac7-145aedeffc25" obligation="normative">
<title id="_9a3b89b1-a1fb-37e3-7216-f816614c117b">Range of semantic functions</title>
<ul id="_cca1c498-118e-e109-93d7-c8582dee1aa5"><li><p id="_5aab250f-365e-7f54-0e5a-e2932d467064">In formal documents of the type considered by Metanorma, the only permitted breaks at a document level higher than a paragraph are clauses, and new clauses are explicitly indicated by clause headings. Section separators are characteristic of extended literary prose, such as novels; even though novels have chapters, they do not have subchapters, and breaks in a chapter are indicated by a section separator instead.</p>
<ul id="_4dd62c58-7c18-75ef-0d29-411c3a67a145"><li><p id="_115a7c58-8207-d46f-e78f-01763722f910">In literary use, the section separator is intended to convey a logical or emotional break.</p>
</li>
</ul>
</li>
<li><p id="_006ba9af-f78d-784b-15f2-5e30f274deea">There is overlap between the section separator and the missing text mark (<xref target="missing-text-mark"/>), when the scope of the missing text mark is at the paragraph level.</p>
</li>
</ul>
</clause>

<clause id="_3859beae-25fb-f990-5c1a-6d66d68df82b" obligation="normative">
<title id="_fc47b17c-f572-487f-34a2-d5307c91ece5">Punctuation mark in scripts, languages, and locales</title>
<ul id="_39f7536a-48e1-b1e6-e2b9-49af89e67fe4"><li><p id="_b613092b-cf52-d714-de35-fa2ad83f6139">The cover term for the traditional punctuation mark for a section separator, used in literary writing, is the dinkus. The usual contemporary form of the dinkus is three asterisks or three bullets in a row, with space between them.</p>
<ul id="_46455a03-280c-2c12-1e6b-2c1de7a60ca0"><li><p id="_f4d59629-1b4e-0420-5ada-14e55681fc75">Older practice used other decorative symbols, including ASTERISM <tt>&lt;⁂&gt;</tt> (U+2042) and various fleurons—such as ROTATED FLORAL HEART BULLET  <tt>&lt;❧&gt;</tt> (U+2767) and NORTH WEST POINTING LEAF <tt>&lt;🙐&gt;</tt> (U+1F650).</p>
</li>
</ul>
</li>
<li><p id="_61802e49-e651-ea4c-c8f2-fabd8e5ba426">In word processing and HTML documents, this function is conveyed by the horizontal rule (<tt>&lt;hr/&gt;</tt>), which is not regarded as punctuation.</p>
</li>
<li><p id="_ab250e35-fd36-d263-d4db-3fbb71c4e324">The Japanese PART ALTERNATION MARK <tt>&lt;〽&gt;</tt> (U+303D) has narrower application, being used in the Renga genre of poetry to indicate the start of a song. The LEFT CORNER BRACKET  <tt>&lt;「&gt;</tt> (U+300C)  may also be used.</p>
</li>
</ul>
</clause>

<clause id="_a2d653d2-5c01-2186-196f-da1db6fdd206" obligation="normative">
<title id="_46d9329b-be6b-9725-5304-f2650e21498c">Spacing rule</title>
<ul id="_8bfd3750-ff75-6e01-ea3b-e2c036bb455a"><li><p id="_3fa234a9-4f62-7e29-c890-07124dae9e6b">The dinkus typically appears centrally aligned, on a line of its own, with vertical spacing before and after it.</p>
</li>
</ul>
</clause>

<clause id="_af22fde3-d40d-518f-788b-9ee0440d4111" obligation="normative">
<title id="_b1412ae7-69db-c993-d157-dad6df2df3a2">Special handling</title>
<ul id="_bbf2423c-d873-5092-4562-d5cae1285e71"><li><p id="_4bc4c52f-f2f8-5ef1-2828-a4e093711aef">In contemporary practice, the dinkus is mutually exclusive with clause headings; in older usage a dinkus can appear before a new clause heading, especially when it conveys an emotional break.</p>
</li>
</ul>
</clause>
</clause>
</clause>

<clause id="_e9918e31-eded-6921-ef11-2344d11b33f5" obligation="normative">
<title id="_47934fd3-0fa9-dc67-2403-5d3268676ff5">Listing stops</title>
<clause id="_6a7dffec-0afa-dbf0-5773-b7bbee354423" obligation="normative">
<title id="_215c4bf9-d886-70e3-a8f8-5493975e022d">General</title>
<clause id="_d2e77f93-2531-7bdf-c465-05e663e0eec7" obligation="normative">
<title id="_62812341-0feb-9110-027a-552b2b53e2c2">Primary function and purpose</title>
<p id="_9da7d98d-805f-cf0b-9b09-5d4f50b82841">Listing stops are used to delimit multiple items in a listing, other than phrases.</p>
</clause>

<clause id="_56849c04-723b-25e7-6c9a-16faf571da1c" obligation="normative">
<title id="_7a49a0b5-258a-0ed8-6890-8e2c00d1b8de">Range of semantic functions</title>
<p id="_be92981e-a48a-83de-8f8c-18584301e893">Because of the conceptual similarity between phrase stops and listing stops, as joining multiple items, punctuation marks for the two are often conflated. In fact, if the definition of “phrase” is liberal enough, listing stops are phrase stops. This framework considers punctuation separating noun or adjective phrases to be listing stops, and not phrase stops.</p>

<example id="_18b6a5f6-b1f7-fa61-9cd5-afff9d4d8b88"><p id="_5db827ff-65d2-edd0-2c6b-000a7e7e5618"><em>I went to the market, and I bought some beans</em>: comma as phrase stop (it is separating two phrases that are complete sentences)<br/> <em>I bought some beans, cheese, and a nice bottle of Chianti</em>: comma as listing stop (it is separating noun phrases, which can include articles, adjectives, and quantifiers)</p>
</example>
</clause>
</clause>

<clause id="_a11dc07a-e0b6-f273-8e5b-dfc7934d6018" anchor="enumeration-delimiter" obligation="normative">
<title id="_309dd2c8-056d-3f0f-92a7-83a7aab27005">Enumeration delimiter (<em>enumeration comma</em>)</title>
<clause id="_172a04e6-6979-5193-6a0f-14444ede32ff" obligation="normative">
<title id="_1335ecf5-16f8-d94b-8850-e9b585c599be">Primary function and purpose</title>
<p id="_2635e349-1886-d00b-3795-693fe3d47f67">The enumeration delimiter separates items in a list. This function is represented in Metanorma i18n files as  <tt>punct.enum-comma</tt>, and in Metanorma Presentation XML as  <tt>&lt;span class="fmt-enum-comma"&gt;</tt>.</p>

<p id="_75591a6d-336a-498d-84e3-149ddb7fde89">In CJK, both comma-like punctuation marks and interpuncts are used as enumeration delimiters. There is no consistent semantic distinction between the two, so no such distinction is made here.</p>

<example id="_38f54fe3-7cdc-f1a4-7d38-b1defb2eef61"><p id="_c3e607f1-39b4-bf83-c409-f38b22926b71">Japanese: 小・中学校 or  小、中学校 “elementary, [and] middle school”</p>
</example>
</clause>

<clause id="_317bdcd3-48cb-816f-7f15-788fd440720d" obligation="normative">
<title id="_8d6c52f5-352e-39ca-c819-631a4322ecde">Range of semantic functions</title>
<ul id="_148b11cd-2a80-c4bc-1ba3-c222cb605d43"><li><p id="_00b6c2a0-17fb-6e39-c7f5-ef58e1dfefe0">There is variation in whether the enumeration delimiter is used in a list of two items.</p>
</li>
<li><p id="_e89657f9-db21-57f6-08be-d760959295cc">There is (linguistic) variation in whether a conjunction is used before the last item in a list, and (punctuation) variation in whether the enumeration delimiter is used before the last item. Thus English allows both  <em>A, B and C</em> and <em>A, B, and C</em> as style variants (the latter is known as the “Oxford comma”). Chinese allows both   <em>A、B及C</em> and <em>A、B、C</em>.</p>
</li>
<li><p id="_b8d411ee-17a4-7e92-e79f-d8a01a8b480e">The punctuation mark for the enumeration delimiter is often the same as that for the minor phrase separator (comma).</p>
</li>
<li><p id="_6158ebd9-2329-ff65-85c4-708b4903248c">The punctuation mark for the enumeration delimiter is often the same as that for other separators; for example Japanese uses the interpunct as an enumeration delimiter, as a decimal point (<xref target="decimal-point"/>), and to separate professional titles, names, and positions (<xref target="name-separator"/>).</p>
</li>
</ul>
</clause>

<clause id="_378c14c1-4aa1-bc20-52e6-ff425b85cfe4" anchor="interpunct" obligation="normative">
<title id="_d61d0b25-3b91-1f74-556e-e928363dbf52">Punctuation mark in scripts, languages, and locales</title>
<ul id="_3045cf87-de5a-d1ab-0a30-11d441612b1e"><li><p id="_3297d772-9fed-7622-2664-1a4206b6214c">Latin, Cyrillic: COMMA <tt>&lt;,&gt;</tt> (U+002C)</p>
</li>
<li><p id="_bec0e5ad-7ce7-8a56-bd56-3990be8caf11">Traditional Chinese: IDEOGRAPHIC COMMA <tt>&lt;、&gt;</tt> (U+3001)</p>
</li>
<li><p id="_3060b167-f8b4-e47d-25ca-37f789c19a23">Simplified Chinese: IDEOGRAPHIC COMMA <tt>&lt;、&gt;</tt> (U+3001)</p>
</li>
<li><p id="_468f0b53-729d-a64b-060c-ded9dc4ca0f6">Japanese: IDEOGRAPHIC COMMA <tt>&lt;、&gt;</tt> (U+3001)</p>
<ul id="_0fdeb43e-03cb-dd36-9535-5b95cf2e2147"><li><p id="_8675b1a3-a9b7-a8a4-9e8d-e475e6143b07">Japanese uses the interpunct for short lists instead of comma in some contexts. This is rendered as KATAKANA MIDDLE DOT   <tt>&lt;・&gt;</tt> (U+30FB)</p>
</li>
<li><p id="_9b1b0f0c-7545-785c-fa71-07d10f53cc95">In mixed Japanese-Western text, FULLWIDTH COMMA <tt>&lt;，&gt;</tt> (U+FF0C) can be used instead to maintain visual consistency</p>
</li>
</ul>
</li>
<li><p id="_019dbf20-1de4-ec95-8a15-011a193be140">Korean: COMMA <tt>&lt;,&gt;</tt> (U+002C)</p>
<ul id="_424d0e8d-85ee-8d27-80e7-7526e5d9eb25"><li><p id="_1c234dc2-0c30-471c-246b-4d664e1961c6">Korean uses the interpunct for short lists instead of comma in some contexts. This is rendered as HANGUL LETTER ARAEA  <tt>&lt;ㆍ&gt;</tt> U+318D.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_f667de12-3b03-87e3-9761-475c517eeeda" obligation="normative">
<title id="_448dc622-e470-cacf-6103-53ae55750f77">Special handling</title>
<ul id="_56d3bfe5-d3a6-6af3-9d4b-25f80b75d08a"><li><p id="_e9de5422-11b3-5d40-d143-f07424ae141f">When lists contain mixed scripts in CJK, follow the punctuation convention of the list’s primary language while maintaining readability.</p>
</li>
<li><p id="_b7e67a24-4556-7d16-6d4f-cca0de432fc3">Japanese also supports HALFWIDTH KATAKANA MIDDLE DOT <tt>&lt;･&gt;</tt> (U+FF65) for the interpunct.</p>
</li>
<li><p id="_3912be52-6df0-5305-2787-c05b56a2bc8b">In Japanese vertical text, the interpunct appears centered rather than at a specific corner position.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_c5976ba5-ce9e-68fd-a23e-65235d71fd49" obligation="normative">
<title id="_f75ef03d-f4ea-ed35-5493-6b0af7452664">List itemisation mark</title>
<clause id="_49f859ff-dbd0-25fb-1daa-1c3576b996a4" obligation="normative">
<title id="_67589a04-fc99-a323-194c-9f881f6a636c">Primary function and purpose</title>
<p id="_e9c49acc-8bf3-fbcf-69ee-4387bf2dbdee">List itemisation marks are used at the start of list items, when they are rendered as separate lines in a list paragraph.</p>

<p id="_ade26eb9-acfd-72a4-7f68-c09ff7f69b5a">List items may be ordered or unordered; if they are ordered, the list itemisation mark is an ordered numeral or letter, optionally followed by a caption number delimiter (<xref target="caption-number-delimiter"/>). In the case of unordered lists, a single typographic symbol is used.</p>
</clause>

<clause id="_515f96cc-fcc8-4c71-907c-0dd8262d1d88" obligation="normative">
<title id="_19a1abb7-6e9c-b390-4329-f02921df72ef">Punctuation mark in scripts, languages, and locales</title>
<ul id="_e89a74e2-f746-0bfe-9a2f-af96fe926bd1"><li><p id="_f86fa458-44d2-d064-d523-8b61ece1fdef">The default list itemisation mark for unordered list items is BULLET <tt>&lt;•&gt;</tt> (U+2022). Alternatives include the em dash, en dash, and WHITE BULLET  <tt>&lt;◦&gt;</tt> (U+25E6).</p>
</li>
</ul>
</clause>

<clause id="_e405aeca-4f56-1410-f2e9-0b112f4c7d22" obligation="normative">
<title id="_6f337474-5673-7244-6cc2-92c8f211c223">Spacing rules</title>
<ul id="_823f0d2a-f0f6-2b73-02fe-2e1919e12e6b"><li><p id="_eed424a2-3df3-b824-3fe9-167969f6251b">List items of different levels in a list are typically indented to differing degrees, so as to indicate that level.</p>
</li>
<li><p id="_35a3a555-7da6-4c3d-5ef8-09c9502e9720">The list itemisation mark is typically separated from the list item content by a tab (a horizontal space of consistent width between different list items).</p>
</li>
<li><p id="_27cfdc1e-8140-dd9f-4437-7535c14cfb09">List items are typically rendered with hanging indentation, so that their list itemisation marks and content lines up across multiple-line list items.</p>
</li>
</ul>
</clause>

<clause id="_d57c0559-f965-f723-5b12-6df6d1ba80bb" obligation="normative">
<title id="_daa635a0-3026-b82c-1add-110b09669e4b">Special handling</title>
<ul id="_f1d244cf-4e7a-d22c-2717-e955ebbd0309"><li><p id="_26c2d3b3-2085-6cac-7992-f43a19016553">In word processing and HTML, list itemisation marks are not entered directly by the author, but are indicated to be rendered via list markup. The selection of list itemisation mark in unordered lists is almost never specified in markup, but in the document configuration/document stylesheet.</p>
</li>
</ul>
</clause>
</clause>
</clause>

<clause id="_8b5a65ef-0478-4694-aa1d-087f52d44c5a" anchor="quotation-marker" obligation="normative">
<title id="_1d38b421-b24f-27e9-5e5e-175b5b2dd38b">Quotation markers</title>
<clause id="_9c604cec-f58f-b0fa-3646-dd2b77be8841" obligation="normative">
<title id="_3bd04871-3c7f-9f29-5c03-f08473daf73a">General</title>
<clause id="_25c29f6c-4217-ab33-ced2-d180c3d148cf" obligation="normative">
<title id="_19bd9633-283b-c150-829f-cb64c290dff8">Primary function and purpose</title>
<p id="_334846ea-5ec2-2dad-bcf1-3728e135c06c">Quotation markers indicate that a span of text constitutes direct speech, or otherwise attribute it to  some third party.</p>
</clause>

<clause id="_600af16e-ed71-dfe6-7328-0df3293bdf39" obligation="normative">
<title id="_15e90c72-b039-c8fc-b054-830f7d17ea8d">Spacing rules</title>
<ul id="_cd79beb7-bf03-cedb-8f3d-69ab8780b05b"><li><p id="_d2c19f67-15e1-a7c6-1e6e-8a68521fe0c6">In French in France, Switzerland and Belgium, for paired quotation delimiters, the opening delimiter (left guillemet, left single guillemet) is followed by a non-breaking thin space (U+202F), as an instance of French spacing (<xref target="sentence-stop-spacing"/>); the closing delimiter (right guillemet, right single guillemet) is preceded by a non-breaking thin space, as the mirror counterpart of French spacing. As with other French spacing, in common practice, a full non-breaking space (U+00A0) is used instead.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_30f1ecfc-ea57-5f47-f15c-12d445edb377" anchor="paired-quotation-delimiter" obligation="normative">
<title id="_eef7d681-210d-9b44-a5f1-85b4539a936c">Paired quotation delimiters (<em>double quotes</em>)</title>
<clause id="_53bc1c4f-91d0-17aa-3c5a-0564747adbc8" obligation="normative">
<title id="_7c805931-bec5-e15d-b2e4-84805f263898">Primary function and purpose</title>
<p id="_e1ce6a4b-425a-5745-37e1-efe55f49719e">Paired quotation delimiters indicate the start and end of quoted text. This function is represented in Metanorma i18n files as  <tt>punct.open-quote</tt> and <tt>punct.close-quote</tt>.</p>
</clause>

<clause id="_0a2a6c64-84ba-8256-1e64-a7f1a85106d6" obligation="normative">
<title id="_f3c7f467-33bb-97dd-3107-91469e2902ad">Range of semantic functions</title>
<ul id="_bbe210e8-6abb-ae1c-14df-ba74d80b9c11"><li><p id="_596a1ff4-8c4b-fc99-8a82-a4bc171d8fcd">Paired quotation markers are often conflated with title marks (<xref target="title-mark"/>).</p>
</li>
</ul>
</clause>

<clause id="_de8c278f-f987-7a96-3178-0cc9d2d67db4" obligation="normative">
<title id="_09c4a96f-5fd3-91b0-a392-019c1dfd6a65">Punctuation mark in scripts, languages, and locales</title>
<ul id="_672fbd4f-6627-c233-1003-ca25d1296b99"><li><p id="_2a72e6d1-485e-42ff-d0ed-853f8d738b50"><bookmark id="_9bc99b22-2996-3889-2a65-580629dadf71" anchor="_c9ab23ea-fc60-422e-b0cf-786cd213b4db"/>Latin, Cyrillic: There is significant variation among Latin and Cyrillic script languages on their choice of paired quotation delimiter and their orientation, and different languages and locales draw from 15 Unicode codepoints.</p>
<ul id="_ec1f4a4e-e042-40be-1b85-aa104b8e2ae1"><li><p id="_649bcf06-f182-56fa-681e-46057b4d1d75">In American English, good typographical practice uses LEFT DOUBLE QUOTATION MARK <tt>&lt;“&gt;</tt> (U+201C) and RIGHT DOUBLE QUOTATION MARK  <tt>&lt;”&gt;</tt> (U+201D) as opening and closing marks. In British English, some publishers use double quotation marks, and others use single quotation marks, LEFT SINGLE QUOTATION MARK  <tt>&lt;‘&gt;</tt> (U+2018) and RIGHT SINGLE QUOTATION MARK  <tt>&lt;’&gt;</tt> (U+2019).</p>
</li>
<li><p id="_f465fd55-b942-74c4-afc0-fd17b1c317b5">Finnish uses the RIGHT DOUBLE QUOTATION MARK <tt>&lt;”&gt;</tt> (U+201D) as both opening and closing marks.</p>
</li>
<li><p id="_8c660668-75d0-0dfc-25f1-6d383e21a342">French uses guillemets, LEFT-POINTING DOUBLE ANGLE QUOTATION MARK <tt>&lt;«&gt;</tt> (U+00AB) and RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK  <tt>&lt;»&gt;</tt> (U+00BB) as opening and closing marks.</p>
</li>
</ul>
</li>
<li><p id="_1f54e591-e1fd-0168-9e4e-80f844f3bc26">Traditional Chinese: LEFT CORNER BRACKET <tt>&lt;「&gt;</tt> (U+300C) and RIGHT CORNER BRACKET <tt>&lt;」&gt;</tt> (U+300D)</p>
</li>
<li><p id="_947c5522-0154-d306-b6e9-07096b4635ac">Simplified Chinese: LEFT DOUBLE QUOTATION MARK <tt>&lt;“&gt;</tt> (U+201C) and RIGHT DOUBLE QUOTATION MARK  <tt>&lt;”&gt;</tt> (U+201D).</p>
<ul id="_e975544e-3330-4f58-5337-1a02eb8bfe34"><li><p id="_3319501f-e4ed-188e-001f-9f29e58c1959">The corner brackets of Traditional Chinese are also in common use.</p>
</li>
</ul>
</li>
<li><p id="_3c3f3ac7-59c4-285b-d7a4-e2ca3cf08e6f">Japanese: LEFT CORNER BRACKET <tt>&lt;「&gt;</tt> (U+300C) and RIGHT CORNER BRACKET <tt>&lt;」&gt;</tt> (U+300D).</p>
<ul id="_0aa2178b-3676-1b0f-c51d-0a09634d8c48"><li><p id="_c240de38-9303-db04-2d7c-4791619b86f3">Japanese also uses lenticular brackets, LEFT BLACK LENTICULAR BRACKET <tt>&lt;【&gt;</tt> (U+3010) and RIGHT BLACK LENTICULAR BRACKET  <tt>&lt; 】&gt;</tt> (U+3011).</p>
</li>
</ul>
</li>
<li><p id="_2ec4ad08-db62-2acd-abef-77743e77d13e">Korean: South Korea uses the same punctuation marks as English. North Korea uses full-width guillemets, LEFT DOUBLE ANGLE BRACKET  <tt>&lt;《&gt;</tt> (U+300A) and RIGHT DOUBLE ANGLE BRACKET <tt>&lt;》&gt;</tt> (U+300B).</p>
<ul id="_bf162499-b7ff-e4eb-ec2a-117fe53b19ec"><li><p id="_e097cb51-ae9a-0dc3-e6be-d6bd589fda43">Corner brackets and white corner brackets are often used in practice.</p>
</li>
</ul>
</li>
</ul>

</clause>

<clause id="_dee71d45-61c5-1a60-4be1-250755949455" obligation="normative">
<title id="_1d665dfd-13af-6154-40e8-5221ba8ffc26">Special handling</title>
<ul id="_8c380b4c-2554-48c3-4629-681a8368025d"><li><p id="_0aa24abc-c84b-2d03-c87d-b4f23e23a56a">The placement of quotation marks in CJK is different by directionality, but this does not involve different Unicode codepoints, so the browser/operating system is assumed to handle positioning appropriately. (While there is e.g. a PRESENTATION FORM FOR VERTICAL LEFT CORNER BRACKET  <tt>&lt;﹁&gt;</tt> (U+FE41) and PRESENTATION FORM FOR VERTICAL RIGHT CORNER BRACKET  <tt>&lt;﹂&gt;</tt> (U+FE42), these are only included in Unicode as a compatibility character.)</p>
</li>
<li><p id="_f7209266-4813-9fc2-b821-7e9d453ebdbb">Quotation marks in English are routinely typed as straight quotes, QUOTATION MARK <tt>&lt;"&gt;</tt> (U+0022), with the expectation that software will transform them contextually into paired quotation marks (“smart quotes”).</p>
<admonition id="_5adb1e6a-d7a3-ce51-3b6d-2611d55390b7" type="tip"><p id="_e6b4809f-3a45-d375-30a3-965b50904305">Metanorma transforms straight quotes in Asciidoc source into smart quotes following English conventions.</p>
</admonition></li>
<li><p id="_f66d4071-8b2f-f5eb-6aea-cfba28cec927">Simplified Chinese uses the font to make Western quotation marks (U+201C, U+201D) full-width, instead of deploying distinct codepoints: REVERSED DOUBLE PRIME QUOTATION MARK `&lt;〝&gt;, (U+301D) DOUBLE PRIME QUOTATION MARK  <tt>&lt;〞&gt;</tt> (U+301E).</p>
</li>
<li><p id="_1245f32d-2793-31e5-7118-1cb47ed7890d">In vertical directionality, Traditional and Simplified Chinese use presentation variants of the codepoints LEFT WHITE CORNER BRACKET  <tt>&lt;『&gt;</tt> (U+300E) and RIGHT WHITE CORNER BRACKET <tt>&lt; 』&gt;</tt> (U+300F).</p>
</li>
</ul>
</clause>
</clause>

<clause id="_8a5235e1-8b14-b52b-8387-1ddd7de67c31" anchor="single-quotes" obligation="normative">
<title id="_2f4d521e-38ba-ad3f-5586-57f7fd68d537">Nested paired quotation delimiters (<em>single quotes</em>)</title>
<clause id="_8302ba5a-ded8-a6aa-c57d-4ce5ef00361b" obligation="normative">
<title id="_e99c4262-2474-f673-979a-4bf56895f770">Primary function and purpose</title>
<p id="_c3bb0686-31d6-0dee-9445-5cbbe2198d1f">Nested paired quotation delimiters indicate the start and end of quoted text within another delimited quoted text, and attributed to a different speaker from that of the nesting quoted text. This function is represented in Metanorma i18n files as  <tt>punct.open-nested-quote</tt> and <tt>punct.close-nested-quote</tt>.</p>

<example id="_d64451af-4759-7652-c97a-5cfe668b0357"><p id="_694d62cc-2a4b-e2c0-7937-023b7c754d5c"><em>“Didn’t she say ‘I like red best’ when I asked her wine preferences?” he asked his guests.</em></p>
</example>
</clause>

<clause id="_181e4e7b-dc79-e5f0-4e19-6a4e8a153fd9" obligation="normative">
<title id="_6e8c6b91-ef6e-236d-081f-45e4ff8b3cbc">Range of semantic functions</title>
<ul id="_7a6ef59d-a2a5-bbdd-cd2b-e281d48cb38f"><li><p id="_f744042d-a03e-feb6-7561-5bdb14a8a4f4">The English closing nested paired quotation delimiter is often conflated with the elision mark (<xref target="elision-mark"/>).</p>
</li>
</ul>
</clause>

<clause id="_2e7f2aeb-cb80-fb04-119c-00a42d310095" obligation="normative">
<title id="_b86c5547-c06e-079a-9e04-782388135b8e">Punctuation mark in scripts, languages, and locales</title>
<ul id="_333dcd6a-8b77-5b64-c484-c0d02949301a"><li><p id="_f38a73de-9cb8-dce7-c551-2d50d908892d">Latin, Cyrillic: There is significant variation among Latin and Cyrillic script languages on their choice of paired quotation delimiter, and different languages and locales draw from 15 Unicode codepoints.</p>
<ul id="_78ce941d-b273-afe1-439f-2b09d94c88f3"><li><p id="_13e380cc-1665-fbe9-2597-23cf4af348b5">In American English, good typographical practice uses LEFT SINGLE QUOTATION MARK <tt>&lt;‘&gt;</tt> (U+2018) and RIGHT SINGLE QUOTATION MARK  <tt>&lt;’&gt;</tt> (U+2019) as opening and closing marks. In British English, some publishers use single quotation marks, and others use double quotation marks, LEFT DOUBLE QUOTATION MARK  <tt>&lt;“&gt;</tt> (U+201C) and RIGHT DOUBLE QUOTATION MARK  <tt>&lt;”&gt;</tt> (U+201D).</p>
</li>
<li><p id="_1d9fcf08-f08c-8e25-48f8-ad889ece49cf">Finnish uses the RIGHT SINGLE QUOTATION MARK <tt>&lt;’&gt;</tt> (U+2019) as both opening and closing marks.</p>
</li>
<li><p id="_9268a2d5-2fa0-c404-4791-e8bb865db58d">French uses single guillemets, LEFT-POINTING SINGLE ANGLE QUOTATION MARK <tt>&lt;«&gt;</tt> (U+2039) and RIGHT-POINTING SINGLE ANGLE QUOTATION MARK  <tt>&lt;»&gt;</tt> (U+203A).</p>
</li>
</ul>
</li>
<li><p id="_acd15350-aa7a-a633-6603-0729e02bf645">Traditional Chinese: LEFT WHITE CORNER BRACKET <tt>&lt;『&gt;</tt> (U+300E) and RIGHT WHITE CORNER BRACKET <tt>&lt;』&gt;</tt> (U+300F).</p>
</li>
<li><p id="_19926054-3ea3-1052-6a98-cc26bcb82d03">Simplified Chinese: LEFT SINGLE QUOTATION MARK <tt>&lt;‘&gt;</tt> (U+2018) and RIGHT SINGLE QUOTATION MARK  <tt>&lt;’&gt;</tt> (U+2019).</p>
<ul id="_4df6aa0f-48f9-dabd-7ac3-282bd13a4b6a"><li><p id="_0a0bf751-bfa7-33f9-3367-258abd80ab2b">The white corner brackets of Traditional Chinese are also in common use.</p>
</li>
</ul>
</li>
<li><p id="_9637e1fc-d8b1-6c9b-1755-3c732f90bff8">Japanese: LEFT WHITE CORNER BRACKET <tt>&lt;『&gt;</tt> (U+300E) and RIGHT WHITE CORNER BRACKET <tt>&lt;』&gt;</tt> (U+300F).</p>
</li>
<li><p id="_1c01a566-624b-edbc-a070-8a99d0312ccb">Korean: South Korea uses the same punctuation marks as English. North Korea uses full-width guillemets, LEFT  ANGLE BRACKET  <tt>&lt;〈&gt;</tt> (U+3008) and RIGHT  ANGLE BRACKET <tt>&lt;〉&gt;</tt> (U+3009).</p>
<ul id="_34d40cfa-f357-30c4-5e79-bffedecac6ac"><li><p id="_bd023704-0443-577e-3425-5c4608757e3b">Corner brackets and white corner brackets are often used in practice.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_a1893864-44f7-eac5-cf26-34b7146df1ff" obligation="normative">
<title id="_1caa48fe-142b-9bf1-d877-b346d721d242">Special handling</title>
<ul id="_8e854b12-2de7-791b-6413-ca93d5aa1968"><li><p id="_d7c4aeed-d90c-d0ba-ec99-a8128e31c5ad">The placement of quotation marks in CJK is different by directionality, but this does not involve different Unicode codepoints, so the browser/operating system is assumed to handle positioning appropriately. (While there is e.g. a PRESENTATION FORM FOR VERTICAL LEFT WHITE CORNER BRACKET  <tt>&lt;﹃&gt;</tt> (U+FE43) and PRESENTATION FORM FOR VERTICAL RIGHT WHITE CORNER BRACKET  <tt>&lt;﹄&gt;</tt> (U+FE44), these are only included in Unicode as a compatibility character.)</p>
</li>
<li><p id="_1b9edfea-aa06-d10e-386c-48760c896215">Nested quotation marks in English are routinely typed as straight quotes, APOSTROPHE <tt>&lt;'&gt;</tt> (U+0027), with the expectation that software will transform them contextually into paired quotation marks (“smart quotes”).</p>
<admonition id="_1d19ce8d-3df7-28fa-4d09-f18bffed144f" type="tip"><p id="_61afbba0-bdc0-4704-8b35-0220918b1ca6">Metanorma transforms straight quotes in Asciidoc source into smart quotes following English conventions.</p>
</admonition></li>
<li><p id="_717a35d7-c2b2-9043-4b34-06d422b2d577">Simplified Chinese uses the font to make Western quotation marks (U+2018, U+2019) full-width, instead of deploying distinct codepoints</p>
</li>
<li><p id="_2a6f42b5-c2c9-7238-5116-df857ba551e8">In vertical directionality, Traditional and Simplified Chinese use presentation variants of the codepoints LEFT CORNER BRACKET  <tt>&lt;「&gt;</tt> (U+300C) and RIGHT CORNER BRACKET <tt>&lt;」&gt;</tt> (U+300D).</p>
</li>
</ul>
</clause>
</clause>

<clause id="_45d65c19-b812-821e-a94e-52f6aaabd79f" obligation="normative">
<title id="_790a48bc-c5b6-7b43-e75e-c18f42eb6273">Single quotation delimiters (<em>quotation dash</em>) (out of scope)</title>
<clause id="_a49fe4d4-f1dd-8e76-7d6c-a553778c691b" obligation="normative">
<title id="_43fb3001-4fe9-2191-348e-b780c2530bbf">Primary function and purpose</title>
<p id="_10a63f0c-10c4-1899-dcd3-6db6eabd74c9">A single initial marker used to represent one turn in an alternation of direct speech.</p>

<example id="_d2950781-2f85-d878-49d8-f2ca31fab10c"><p id="_a4c45fcd-2e35-5581-c041-7b6890e6affd">― <em>O saints above! Miss Douce said, sighed above her jumping rose. I wished I hadn’t laughed so much. I feel all wet.</em></p>

<p id="_64f43d8a-d706-32b2-4d8d-c00d0e0dcc81">― <em>O Miss Douce! Miss Kennedy protested. You horrid thing!</em></p>

<p id="_550130d6-dc77-8bfd-bed0-fa552ca1178c">—James Joyce, <em>Ulysses</em></p>
</example>
</clause>

<clause id="_894226d4-edca-dc1e-db1f-f47a285c5057" obligation="normative">
<title id="_c22192c6-961d-b211-33e8-b5e47ae48d36">Punctuation mark in scripts, languages, and locales</title>
<ul id="_88b205c2-166b-a5f6-ac46-c9cf26044771"><li><p id="_8576585e-fa79-cade-80a0-f4a25fbe730d">Latin, Cyrillic: Properly HORIZONTAL BAR <tt>&lt;―&gt;</tt> (U+2015) is used; in practice EM DASH <tt>&lt;—&gt;</tt> (U+2014) is usually used.</p>
<ul id="_391be6b0-a550-579f-0cc0-fd34babae078"><li><p id="_bbdd312a-6dcc-5fb9-3723-0a5384727026">The quotation dash is almost unknown in English, but is commonplace in other European languages, such as French.</p>
</li>
</ul>
</li>
<li><p id="_b3bc101f-b2fd-7a95-36fd-ffab0e7dc960">The Japanese PART ALTERNATION MARK <tt>&lt;〽&gt;</tt> (U+303D) has narrower application, being used in Noh drama to indicate the start of a speaker’s or the chorus’ part. The opening square quotation mark  <tt>&lt;「&gt;</tt> may also be used.</p>
</li>
</ul>
</clause>

<clause id="_cc95b982-e697-8982-1ef0-aa3c43c191f0" obligation="normative">
<title id="_e7bda8e9-ce1e-60bd-317d-c60f3021b030">Spacing rules</title>
<p id="_27d5eddb-8c2f-93a1-15fa-ca543e9f0537">There is a thin space after the quotation dash.</p>
</clause>
</clause>
</clause>
</clause>

<clause id="_52520983-b179-6e11-d59d-f6e36077ad12" obligation="normative">
<title id="_4fe7cbf9-f6d0-7daf-da40-ea53f3beca07">Functions: word-level structure</title>
<clause id="_a6973408-be4b-2879-24cc-13dbf4fe20d0" obligation="normative">
<title id="_c295fd26-bf3d-c253-a722-6237d3d7ffa1">Conjunctors</title>
<clause id="_c7a1e012-4251-1a64-6375-f24bc8645775" obligation="normative">
<title id="_9b4d7bd0-d71d-eba4-bbca-8c13ed1eb57f">General</title>
<p id="_77e232cf-9df9-52c2-baf9-90777b142a32">Connection indicators link related elements, show relationships between parts, or indicate continuation across boundaries.</p>
</clause>

<clause id="_f37d0408-d755-7de6-83c1-98602e194d4d" obligation="normative">
<title id="_957b1883-6272-25a1-25f9-718ee01c4d68">Conjunctive mark</title>
<clause id="_10cb5e21-ce38-7a18-01d2-284a4eb7312f" obligation="normative">
<title id="_e924e040-9c8e-9fec-0b7e-06c0723fa01c">Primary function and purpose</title>
<p id="_d6eb9aba-9762-f496-4f35-2d1632faa5e7">The conjunctive mark presents two or more words or morphemes as both applicable. It is a punctuation counterpart to “and”.</p>
</clause>

<clause id="_ac8ed7f8-838d-bfbd-2798-64f85483e752" obligation="normative">
<title id="_bfe79d1a-47b4-b85e-99d9-2296b13c4086">Range of semantic functions</title>
<ul id="_f89398c4-f044-d68c-77ec-66c4106c8ed8"><li><p id="_ab331fd7-e653-0692-c707-499213537d1f">In formal usage, ampersand is restricted to citations of multiple authors, and to disambiguate scope of conjunction (items in a list joined by “and”, some of which are themselves joined by “and”).</p>
<example id="_c3c67660-5926-db86-762d-78ddff2b9e84">
<name id="_0476a8a6-b2d3-3375-cf3f-07ff772fe862">Citation of multiple authors</name>
<p id="_93472003-7f67-41de-ea87-a94d2c3d0f85"><em>Jones &amp; Jones (2005)</em></p>
</example>

<example id="_cea35415-aba7-ec88-cef3-5c2b022b215b">
<name id="_2893c904-1ff1-cd5b-e426-978cb8072bf6">Items in a list joined by “and”, some of which are themselves joined by “and”</name>
<p id="_33dfc73d-720b-b3ad-a722-df93d1001b15">Rock, pop, rhythm &amp; blues and hip hop</p>
</example>
</li>
</ul>
</clause>

<clause id="_1685bda5-67ed-b236-6437-b67f4332cdcf" obligation="normative">
<title id="_5d4bfc36-8de8-388e-c51a-eccd71b4efdd">Punctuation mark in scripts, languages, and locales</title>
<ul id="_7038e1de-4f8c-5fd1-36f5-3392e418c114"><li><p id="_35a4ce5c-d955-43bf-1146-0025fe0d1ab4">In Latin script, the default conjunctive mark is AMPERSAND <tt>&lt;&amp;&gt;</tt> (U+0026).</p>
<ul id="_21d89037-100e-c50e-afc6-398ca42e2a69"><li><p id="_dc853eb3-7c9b-ca53-5d5d-2d923f185c82">In Irish and Scots Gaelic, TIRONIAN SIGN ET <tt>&lt;⁊&gt;</tt> (U+204A) is used traditionally.</p>
</li>
<li><p id="_816613df-3f5f-3368-b734-c1d60366629f">In Swedish, underlined <em>o</em> is also used.</p>
</li>
<li><p id="_12380e1a-7247-4c57-d0b0-e2a11427d8ea">In informal usage, the plus sign may be used.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_dfa1ff03-851c-d970-f32b-664a5bd1ecfa" obligation="normative">
<title id="_0e7f5dc6-e14c-d525-de5f-efd1c14e1417">Spacing rules</title>
<ul id="_6d8f36f5-f2e6-62de-b681-630d07719020"><li><p id="_fdd64b92-8a55-1c3b-225a-93c2da8e43c4">By default the ampersand is consider to stand in for “and” as a word, and is spaced either side as a word. It is printed without spaces when it is part of an acronym, e.g.  <em>R&amp;D</em> = “Research and Development”.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_4f7d74d4-a72e-41e2-210d-dd94da2f24ae" obligation="normative">
<title id="_66412093-d4f7-53a1-6e22-824e02f64d67">Disjunctive mark</title>
<clause id="_c17bc8b7-0d37-d1e6-be5f-0ab389a31e64" obligation="normative">
<title id="_3359fd59-21ee-cecb-08a4-02a3425ddb70">Primary function and purpose</title>
<p id="_3f99a533-644c-96c0-c118-b59e8019566b">The disjunctive mark presents two or more words or morphemes as alternatives. It is a punctuation counterpart to “or”.</p>

<example id="_70047ad8-aba2-a355-a8d7-d06012d15b96"><p id="_5fdc56d0-5005-b626-a21c-5b1cfa165b06"><em>Iran/Persia</em> (place may be designated as either)<br/> <em>is/are</em><br/> <em>he/she</em><br/> <em>s/he</em> (truncated version of <em>she/he</em>)</p>
</example>
</clause>

<clause id="_76cbd6c2-0a2e-47f4-b5d1-d8f80887e08f" obligation="normative">
<title id="_fbc46170-2ba4-621f-1fbb-43853eefa660">Range of semantic functions</title>
<ul id="_9db43d84-b311-67bd-1b4c-89a9857eada6"><li><p id="_ac109759-8de6-2731-6e10-f83529071d2d">The disjunctive mark can be used to express inclusive “or”, or “and”; in that case it overlaps with the conjunctive mark and the range mark.</p>
</li>
<li><p id="_17599cfb-9f93-44da-fcca-ba05841b8eac">English uses both a disjunctive mark and range mark to express points on an itinerary; e.g. <em>Shanghai/Nanjing/Wuhan/Chongqing</em> or <em>Shanghai–Nanjing–Wuhan–Chongqing</em></p>
</li>
</ul>
</clause>

<clause id="_1333ab5e-3dff-d8ef-0cf9-35c357f45235" obligation="normative">
<title id="_2553475a-4c8a-1d53-0212-2fb4b8ab4a3c">Punctuation mark in scripts, languages, and locales</title>
<ul id="_621575cd-4a0f-c2d0-ae18-58b72f976c89"><li><p id="_5379da94-cc5c-79ad-2adc-0dd1f7b62ef9">In English, the expression of the disjunctive mark is the slash, SOLIDUS <tt>&lt;/&gt;</tt> (U+002F).</p>
</li>
</ul>
</clause>

<clause id="_36f9860d-9a0c-ef98-a2e7-7c4799584996" obligation="normative">
<title id="_6e289822-0be6-00e3-8d38-91da1c3f7d06">Spacing rules</title>
<ul id="_c732a0ae-819f-3a74-187c-66e1b4bff999"><li><p id="_e047ca6e-a09b-8fac-a088-d2f8e01b0a6e">Normally there is no space either side of the slash. Some style guides require space when the phrase being joined contains a space:</p>
<example id="_1baef4b5-6f44-adcb-ae11-5350b3cdf339"><p id="_779fc7be-7e00-2816-122c-8b6ee7a48f62"><em>and/or</em><br/> <em>New Zealand / Western Australia</em></p>
</example>
</li>
</ul>
</clause>
</clause>

<clause id="_06f55729-82ae-7c7e-96a3-5cea7b084e7e" anchor="range-mark" obligation="normative">
<title id="_6fe74aaa-6e4f-63fb-7371-497521119905">Range mark (<em>en-dash</em>)</title>
<clause id="_ca823ac0-0d78-bf0b-dcc5-f0138d4d8ba9" obligation="normative">
<title id="_1bd5ec28-7551-8fbe-6ea1-1d9f997feed7">Primary function and purpose</title>
<p id="_312ac63f-286f-2b05-52a6-c2d6c8a438a3">A marker between two items, used to convey a range between the two. The items can be verbal values (<em>Paris–New York</em>), numerals (<em>3</em>–<em>5</em>), dates (<em>Jan–Oct</em>), quantities, etc. This function is represented in Metanorma i18n files as  <tt>punct.en-dash</tt>.</p>
</clause>

<clause id="_33f1e27f-e6b2-f0b3-f7d1-689ad9921107" obligation="normative">
<title id="_a5b87ed3-989c-276f-e2e8-aea6cb66bfcc">Range of semantic functions</title>
<ul id="_df828bfc-c34c-4906-eeec-c859070124bf"><li><p id="_3a6a6822-4b74-df73-3f21-85a98cbbfea8">Latin script conflates the punctuation marks for verbal and numeric ranges. CJK uses distinct punctuation marks for verbal and numeric ranges. The latter function is represented in Metanorma i18n files as  <tt>punct.numeric-en-dash</tt>.</p>
</li>
<li><p id="_8c19a77d-66a9-1175-6f56-41400ef9286d">The range mark is also used to contrast two items, or convey a relationship between them: <em>Mother–daughter relationship</em>,</p>
</li>
</ul>
</clause>

<clause id="_2e430645-3e78-450c-6291-5aab5cd9743f" obligation="normative">
<title id="_ab205fa5-c004-0640-02ca-d13eae1a87cd">Punctuation mark in scripts, languages, and locales</title>
<ul id="_b81d2eb5-54c9-be29-04c1-a8839bbc5616"><li><p id="_ded0788f-84de-9735-8df0-c2fdb31e6e89">Latin, Cyrillic: In good typography, EN DASH <tt>&lt;–&gt;</tt> (U+2013) is used. Informal use typically uses the hyphen, and some style guides prescribing formal use prefer the hyphen when conveying a relationship, in its role as a word divider (<xref target="word-divider"/>).</p>
<ul id="_1893aa00-a102-43f2-0ede-4ccfe9a300f7"><li><p id="_d0062f02-d916-fbb7-a33c-637803c057c1">In French, TILDE <tt>&lt;~&gt;</tt> (U+007E) is used: <em>3~5 m</em>.</p>
</li>
</ul>
</li>
<li><p id="_bcca97c8-a6fd-7b4d-6860-5b2ea7217a54">Traditional Chinese, Simplified Chinese, Japanese, Korean: EN DASH <tt>&lt;–&gt;</tt> (U+2013), WAVE DASH <tt>&lt;〜&gt;</tt> (U+301C), FULLWIDTH TILDE  <tt>&lt;～&gt;</tt> (U+FF5E).</p>
</li>
</ul>
</clause>

<clause id="_dfff5d5d-6e3f-deca-92a6-29fcb67ac425" obligation="normative">
<title id="_cc02749a-5444-d9cd-816a-f2fb9680f1d4">Spacing rules</title>
<ul id="_e9416be3-3635-39de-84c4-a11161eec9fb"><li><p id="_e0e9d080-4e78-3b41-895b-0d64fe795bf7">Typically in Latin script there is no spacing around the en-dash. This differentiates it from the phrase stop use of the en-dash. Some style guides recommend spacing where it would avoid ambiguity in scope, e.g.  <em>12 June – 3 July</em>; others do not, e.g.  <em>12 June–3 July</em>.</p>
</li>
</ul>
</clause>

<clause id="_3fe5ed83-edfb-98ff-3d8c-7cb08bb08438" obligation="normative">
<title id="_ef199eb2-ef4d-b478-04bb-c96f62f6d21e">Special handling</title>
<ul id="_cb16eab7-449f-2ecb-f86d-6d9ca85fa310"><li><p id="_aab050b5-14bc-d454-85d4-72980d96e34a">In French, the range mark can be open on either side of the interval: <em>~3</em> means “up to 3”, <em>100~</em> means “100 or more”.</p>
</li>
<li><p id="_3bd60437-cfec-d265-4d13-96be83f0f398">In CJK, verbal range is conveyed through en-dash. Tilde and single em-dash can also be used for verbal range.</p>
</li>
<li><p id="_616cd7e3-a52b-dcbb-6c86-79f3b5eac8af">Numeric range in CJK is normally wave dash. Some Japanese academic writing uses colons instead of wave dash, though this is not universal.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_938d7767-5fa8-75bf-c28a-06c412e04e03" anchor="name-separator" obligation="normative">
<title id="_f1b46c66-9247-f4d8-871b-dd1cb5f975e9">Name separator</title>
<clause id="_ab8c0b54-f827-5b24-c53f-a8d1a59ca779" obligation="normative">
<title id="_d30cdcc4-4d8c-172b-36e7-6fcb442eba73">Primary function and purpose</title>
<p id="_b9f27904-d8c3-1e34-60ba-564ec518ecb1">Particularly in CJK, components of a name are separated from each other using a punctuation mark where necessary for clarity. This applies to names in the broadest sense, including personal names (particularly foreign names), professional titles and positions next to names, and names of works (i.e. titles, separating the title from the subtitle).</p>

<example id="_9ad14bec-5b2d-26a0-520e-27dd38850353"><p id="_92544e79-e29d-a680-645a-66ee5ec76ed6">Simplified Chinese: 李奧納多·達·文西 “Leonardo·da·Vinci”</p>
</example>

<example id="_cda68f09-2d75-e3af-af63-64b245f388bf"><p id="_a04e41e6-cc6b-9a8b-60f5-592ce294ba42">Japanese: 部長補佐・鈴木 “Assistant Department Head·Suzuki”</p>
</example>
</clause>

<clause id="_438fa997-7f88-f159-1510-dba4b93346d7" obligation="normative">
<title id="_52346a4d-2d78-1e08-eb30-b6e53e142479">Range of semantic functions</title>
<ul id="_f8e92282-e690-9a17-5f58-484647337109"><li><p id="_ed1c36ef-53af-de86-0a0a-351ad94283d4">There is a continuity of function between the name separator and the word divider in CJK, particularly as CJK uses ideographs for words (so words are not consistently broken down), and it uses word dividers only sparingly.</p>
</li>
<li><p id="_fa9ac210-3794-94f1-a8d4-10039311e7aa">The following are the more refined classes of name separator; because of the fluidity of classes, they are enumerated here rather than being broken down into separate semantic functions in the framework.</p>
<ul id="_8f1e7d17-4a15-b6a3-1472-4bbf4a6edf71"><li><p id="_e8800887-f7c5-b7ca-2d6b-3f97a497473e">Components of foreign names (Chinese, Japanese)</p>
</li>
<li><p id="_671298ea-d08b-65c7-44ff-8c30a5b0bdea">Components of an organsiation name</p>
</li>
<li><p id="_834d71d5-60ee-0cd1-2234-b3cc5edfcf05">Title and subtitle of a work</p>
</li>
<li><p id="_f5a2ca05-ce5e-6dc5-0640-76369663710b">Professional title, professional position, personal name</p>
</li>
<li><p id="_8425b1b5-5cf6-937a-d572-69b85ba00947">Components of a bibliographic reference entry (e.g. <em>Smith, J. 1989. The passage of time. New York: Wiley.</em>)</p>
</li>
</ul>
</li>
<li><p id="_a476703a-f8aa-13b7-50b7-4d1c85447854">Caption markers (<xref target="caption-markers"/>) include a subset of name separators, but these are discussed separately, as a core concern of Metanorma configuration.</p>
</li>
</ul>
</clause>

<clause id="_5a55fe67-f9e8-21c6-a26a-74a3984dbb05" obligation="normative">
<title id="_b95b2a23-9733-cf7c-fbce-016c67cebb6e">Punctuation mark in scripts, languages, and locales</title>
<ul id="_47da4c0e-d8ea-f0b6-4fff-753c39e6c265"><li><p id="_f9008984-b2c4-d4ba-876d-781d67cd5f0b">Latin, Cyrillic: In Western scripts, this function is conflated, with the normal word separator (<xref target="word-separator"/>) (space), with phrase stops (comma by default (<xref target="minor-phrase-separator"/>), colon for title/subtitle (<xref target="introductory-phrase-separator"/>), both for organisation names), or with word divider (<xref target="word-divider"/>) (hyphen, used in personal names).</p>
<ul id="_4b9d92a0-3f1f-e52d-cd38-2a6d732bb6c7"><li><p id="_ca501482-0fd6-be36-261a-3c4cdf798f3d">The colon or em-dash is used for title/subtitle: <em>Star Trek V: The Final Frontier</em>, <em>Star Trek V—The Final Frontier</em></p>
</li>
<li><p id="_5ecebb6f-92c4-95fb-fbc5-8b7aaeddb6bb">The comma, colon, or em-dash is used for organsiation name: <em>Yamato Bank: Osaka Branch</em></p>
</li>
<li><p id="_d5bf9b0e-0d3b-4b11-883a-a236022cdb6f">The hyphen is used within a single component of a personal name, a surname or a given name: <em>Jean-Jacques</em>, <em>Zeta-Jones</em></p>
</li>
</ul>
</li>
<li><p id="_788a84fa-1724-f735-e398-0ed00472d486">CJK: Various forms of interpunct (<xref target="interpunct"/>): MIDDLE DOT <tt>&lt;·&gt;</tt> (U+OOB7) in China, HYPHENATION POINT <tt>&lt;‧&gt;</tt> (U+2027) in Taiwan, KATAKANA MIDDLE DOT  <tt>&lt;・&gt;</tt> (U+30FB) to separate Katakana words in Japanese.</p>
<ul id="_3bdbf7c5-e05b-6521-0e51-4d060f9e4f59"><li><p id="_d883f029-ab1a-c2e7-fc06-2674c878e8b5">Japanese also uses WAVE DASH <tt>&lt;〜&gt;</tt> (U+301C), to separate title from subtitle.</p>
</li>
<li><p id="_fe685cc0-b879-7782-37fb-5f915f33bea8">Japanese also uses the KATAKANA-HIRAGANA DOUBLE HYPHEN <tt>&lt;゠&gt;</tt> (U+U+30A0) and the FULLWIDTH EQUALS SIGN <tt>&lt;＝&gt;</tt> &lt;U+FF1D&gt;. This double hyphen is used to render Latin hyphen in transliteration of foreign names, i.e. in the function of separating single components of a Western name. That function occasionally uses the interpunct instead. More rarely, the double hyphen also is used instead of the interpunct to delimit names and titles in Western names, e.g. サー゠アーサー゠コナン゠ドイル “Sir=Arthur=Conan=Doyle”</p>
</li>
<li><p id="_1e21fef3-c138-717e-45b9-8cfd23bfc18f">Japanese occasionally uses the interpunct for Japanese names, particularly when there would otherwise be confusion as to where one name ends and another begins.</p>
</li>
<li><p id="_4aefbe3e-a70b-58e9-ead9-1b474afd37c1">Japanese can use ideographic space to delimit components of an organisation name: 大和銀行　大阪支店 “Yamato Bank, Osaka Branch”.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_258e7cf4-ca57-1aa9-f5ea-fa497042860b" obligation="normative">
<title id="_81c5c7fc-cfef-aadb-999b-8e6ec1a3b3bc">Special handling</title>
<ul id="_e55476d0-6e7a-f37e-19bf-82d7d3913987"><li><p id="_fbe78895-fd6a-1bcf-90f7-8b9d389ee9a8">The interpunct is half-width in Chinese in print, but full-width in online material.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_230a5bbf-2c62-06ac-f34e-7467d025ac5b" obligation="normative">
<title id="_755c5d18-1594-4dbf-85ab-dc7971ca8e9f">Attribution mark</title>
<clause id="_9af95b18-102d-c8eb-dbef-fd0594866cdf" obligation="normative">
<title id="_b96276fe-813a-847b-c679-e35ff135ca59">Primary function and purpose</title>
<p id="_0ac84bc9-9590-9d1a-7c8b-e670f9ed4854">The attribution mark is used  to delimit a quotation from its source.</p>

<example id="_7655354e-ff59-3812-cae1-276634e92cdf"><quote id="_c937be08-d7ec-00ea-b3db-825d74253946"><p id="_83c6c438-966a-15ac-bb05-624eb8f50817"><em>To be or not to be, that is the question.</em></p>
</quote>

<p id="_9b05226c-2885-3a5f-12b6-fda9b5bebc42">— William Shakespeare</p>
</example>

<example id="_2685458b-6a62-6034-74bb-e18292e188e8"><p id="_28efe391-c21c-f874-a6d6-73b3735df9f6">To be or not to be, that is the question” — William Shakespeare</p>
</example>
</clause>

<clause id="_5f6c46e1-1db8-14d6-47cc-16d588df0cea" obligation="normative">
<title id="_fdc0af36-b2a6-8c01-0a9c-06475e41a238">Range of semantic functions</title>
<ul id="_e99dcea9-9eca-ee5e-9f11-975d359a03fc"><li><p id="_6a7d3fdf-9975-507a-fd7d-3636891f1839">The attribution mark is comparable to the caption separator (<xref target="caption-separator"/>) and the breaking phrase separator (<xref target="breaking-phrase-separator"/>). It accordingly shares punctuation with them.</p>
</li>
</ul>
</clause>

<clause id="_d79f07e5-d2fa-66a4-6b74-d24648d2ce66" obligation="normative">
<title id="_5ee27911-3982-6f81-f0da-4d431f909362">Punctuation mark in scripts, languages, and locales</title>
<ul id="_caf10397-eb32-ce32-eb85-3ac5236cdb32"><li><p id="_4595b8ed-4d6d-1cd5-4780-7bf671f9f67d">The em-dash is typically used. In less formal writing, the colon and the comma are also used.</p>
</li>
</ul>
</clause>

<clause id="_be5e83dd-1d5d-5adc-e5c4-ada09c48beda" obligation="normative">
<title id="_beb83bd3-a20b-557b-a506-b8e6c37f716c">Spacing rules</title>
<ul id="_e405dc2c-bc6c-0855-add0-1daf8eddaa9c"><li><p id="_5f7fa39e-fee1-0e38-4442-361fc32f052e">When applied to a block quote, the attribution starts on a separate line, with the attribution mark dash. The separate line is typically indented.</p>
</li>
<li><p id="_3c8ebd20-40da-3cd6-b704-3fea1a1ca23a">When used inline, the attribution mark dash follows the quotation directly.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_7c5bee36-c1a5-6cab-acf7-7976b7b4afd5" anchor="word-separator" obligation="normative">
<title id="_1147f68b-3051-6808-2a15-f78386bb731e">Word separator (<em>space</em>)</title>
<clause id="_ff10e0c6-f9d5-105a-af1d-a2dc90de2c67" obligation="normative">
<title id="_053dfc24-a1ed-ac44-4eb0-473182161a3e">Primary function and purpose</title>
<p id="_218d021f-9307-b42a-0c7f-f7e8ff887e1f">The word separator is used to separate words from each other.</p>
</clause>

<clause id="_2d8f76e5-7564-42ca-e2cd-9321d2d4d03c" obligation="normative">
<title id="_5bcffd17-ae10-0651-1a84-23906dbbe604">Punctuation mark in scripts, languages, and locales</title>
<ul id="_f1f4475f-edc5-6e75-af92-dbd91b6f6c49"><li><p id="_ca3c4412-9d21-5476-dc6d-105d343ffd14">In Latin and Cyrillic, this function is fulfilled by the space, which is not regarded as punctuation at all. The space is applied universally as a word separator.</p>
<ul id="_11c6c986-750f-3bcc-b2da-4f39a4a26ac4"><li><p id="_28342e05-4745-c7a9-abca-b3e46aef4777">This was not the case in antiquity. Roman inscriptions used an interpunct (<xref target="interpunct"/>) as a word separator; Greek and Roman manuscripts did not use word separators. (The latter practice is known as  <em>scriptio continua</em>, “continuous writing”)</p>
</li>
</ul>
</li>
<li><p id="_d33aa6ed-16c9-f1e4-f4d0-283a2f2bb825">CJK by contrast defaults to not using word separators, outside of special contexts (here considered as name separators). CJK therefore has  <em>scriptio continua</em>.</p>
</li>
<li><p id="_339003e9-a220-761b-3dfa-d855eaf9da03">There are circumstances in which a word separator is necessary in careful text in CJK. Japanese specifically uses the interpunct to separate ordinary Japanese words, outside of the special cases of name separators (<xref target="name-separator"/>), where the intended meaning would be unclear if the characters were written side-by-side. It is more commonly used to separate foreign words and names when written in kana: パーソナル・コンピューター (<em>pāsonaru·konpyūtā</em> “personal computer”).</p>
</li>
</ul>
</clause>
</clause>

<clause id="_742adf0c-9dc2-9f04-e335-a59d81dba402" anchor="word-divider" obligation="normative">
<title id="_e888b990-840d-6957-54ea-f5985336efa6">Word divider</title>
<clause id="_a65bbba5-f524-396d-4737-2774cd0a3f89" obligation="normative">
<title id="_5a055ace-a22b-da8b-e863-c566fa8846ac">Primary function and purpose</title>
<p id="_3a103cdb-d7ec-567e-6f9e-ac2ac5c63d69">The word divider indicates the compound structure of a word, dividing it into pieces smaller than a word.</p>
</clause>

<clause id="_acfb9043-dd35-2efd-2613-108d089f3186" obligation="normative">
<title id="_346132a3-caef-b891-3f31-90245fa981f5">Range of semantic functions</title>
<ul id="_505dd9fb-eba6-7545-9985-d2f7a5d4b47a"><li><p id="_236d6777-89c7-98a3-cd19-54c17872e479">The word divider differs from the name separator in scope: name dividers operate on groupings of words, the word divider operates within a word.</p>
</li>
<li><p id="_c24aec47-6187-8133-38c6-1f18ddca9b81">The grammatical word divider (<xref target="grammatical-word-divider"/>) is a special case of the word divider.</p>
</li>
<li><p id="_f9c424e3-72b4-67de-b5a5-809e6c7f81e3">The hyphen (<xref target="hyphen"/>) is a special case of the word divider.</p>
</li>
<li><p id="_57dac0e6-ef77-f192-50b1-6aba73eb4ea9">The divisions that a word divider makes can vary in scope. What is divided up may be a compound consisting of meaningful units: independent words, or morphemes (e.g. prefixes:  <em>de-emphasise</em>). Or, what is divided up may be a single meaningful unit, broken up into phonetic units (syllables, or letters: syllabification or spelling out of a word).</p>
<example id="_99b5669b-836f-80e1-0d07-7e76d680f658">
<name id="_2e3b05df-1a62-5113-a606-ee3aa89caafc">Meaningful units</name>
<p id="_1c9f4043-7071-5c27-242d-58392c9f3385"><em>post-war</em><br/> <em>Indo-European</em></p>
</example>

<example id="_86c59e21-f474-2709-48c3-2c612955dff6">
<name id="_25b0f7b1-3ef7-d013-08b0-3875c732adac">Phonetic units</name>
<p id="_1e469733-ecb8-a94a-13ee-0910d0100fd6"><em>R-E-S-P-E-C-T</em> (spelling out)<br/> <em>in-cre-di-ble</em> (syllabification)</p>
</example>
</li>
<li><p id="_3165288e-dec7-e47f-6ef6-8f5de3157ef2">The extent to which the word divider is used in compound words varies by language and by style. The use of hyphen to indicate compound words (e.g.  <em>pigeon-hole</em>, <em>craftily-constructed chair</em>) is on the decline in English.</p>
</li>
<li><p id="_0bca543f-a035-31b6-1796-8847951d4165">There may be two levels of division represented, with different dividers used to differentiate between them. This applies because here are two actual levels of grouping, or because a component being connected is a multi-word expression with space in it</p>
<example id="_68c57780-1937-064f-cb61-64dc6ac5f896">
<name id="_fb895c7e-9995-2196-d2d2-9bf11112da89">Two levels of division</name>
<p id="_fe8b31a4-1333-a6dd-8330-fc7832e47039"><em>Pre–Indo-European</em><br/> <em>San Francisco–area</em></p>
</example>
</li>
</ul>
</clause>

<clause id="_75a70b56-0590-8ea8-83d2-f2d40ded8514" obligation="normative">
<title id="_eb3ef344-9e0c-d876-8872-17ac66b600c4">Punctuation mark in scripts, languages, and locales</title>
<ul id="_b0a12efc-7d63-4fe2-cf4f-d6451e0f1d97"><li><p id="_cc8298c0-9afd-467b-b1a9-0d0d5b76f00f">In Latin and Cyrillic, the default word divider is the hyphen, HYPHEN-MINUS <tt>&lt;-&amp;#x200c;&gt;</tt> (U+002D). Unicode also has HYPHEN  <tt>&lt;‐&gt;</tt> (U+2010) to disambiguate it from the minus sign (<xref target="minus-sign"/>), but this “Unicode hyphen” is little used.</p>
<ul id="_2747c498-aef0-7303-6de7-d487ef5603e2"><li><p id="_cd2855cf-35e8-63ff-90a8-389684513084">The EN DASH <tt>&lt;–&gt;</tt> (U+2013) is used as a higher level of division in careful typesetting (<em>Pre–Indo-European</em>, <em>San Francisco–area residents</em>).</p>
</li>
<li><p id="_00519dbf-4ba8-20c8-db2e-9ac2eb79364e">In lexicography, interpunct is also used for syllabification.</p>
</li>
<li><p id="_24429282-0b05-f750-65a2-a116bd1421f0">In some transcription practice, e.g. for Arabic, Japanese and Chinese  into English. the apostrophe is used to indicate syllabification, as disambiguation (مصحف transcribed as  <em>mus’haf</em>, to avoid the pronunciation “moo-shaf”; しんいち transcribed as  <em>Shin’ichi</em> to indicate the syllabification is “Shi-n-i-chi” rather than “Shi-ni-chi”).</p>
</li>
<li><p id="_5d3fafb8-f3dc-b833-a99d-e628b431df8c">This is also done in Pinyin: <em>Xi’an</em> is two syllables, <em>Xī-ān</em>, whereas <em>xian</em> would be read as a single syllable.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_f2bf9e96-389e-32f7-d3b1-a035dfd0ce0a" obligation="normative">
<title id="_31246360-0408-030f-ced5-95bae2bd14e7">Spacing rules</title>
<p id="_e0c0b3c5-fec0-b9bd-06ad-806928432e7a">Space is not meant to appear after word dividers normally, as any word separators would contradict the intent of the word divider as showing divisions within a single word.</p>
</clause>

<clause id="_8c606071-c256-e312-2542-61eafc988e00" obligation="normative">
<title id="_ffc57c30-205e-8b0b-8534-e694c490e59a">Special handling</title>
<p id="_a889bcc8-6a0a-f961-8060-867b9bb081d0">Some instances of word divider  are not meant to be conflated with the hyphen, and  a line break between such word divisions is inappropriate. For such cases, NON-BREAKING HYPHEN  <tt>&lt;‑&gt;</tt> (U+2011) is used.</p>
</clause>
</clause>

<clause id="_bca9342f-f99c-bc15-e1d0-f230ee17ecf9" anchor="grammatical-word-divider" obligation="normative">
<title id="_27d44ebd-0ca3-91c6-b3fa-a42f2e5ec88a">Grammatical word divider</title>
<clause id="_477c518b-9116-44cf-baeb-742d5e617015" obligation="normative">
<title id="_5c36e4c5-8d8e-4264-d1aa-63d78ebe30c2">Primary function and purpose</title>
<p id="_b6d3db78-23c0-3496-0afc-346a3c9ae7fa">The grammatical word divider, like the word divider, indicates the compound structure of a word, dividing it into pieces smaller than a word.</p>

<p id="_11ef42be-63cd-7540-66f1-b176ac13d86c">The word divider can indicate the compound structure of any compound word, and is not a normal part of conventional orthography. The grammatical word divider, by contrast, is used to designate specific grammatical functions of morphemes, and is part of the conventional orthography of a language.</p>
</clause>

<clause id="_6f8d8489-edc9-b673-5f21-c2406bb40e40" obligation="normative">
<title id="_66810c37-ceb7-c239-884f-64a5845e979d">Range of semantic functions</title>
<ul id="_e46622ac-09c8-4667-4f53-502dac682639"><li><p id="_7df6684a-cb94-5f64-56b2-b0c7333df548">The use of a  grammatical word divider distinct from the general word divider is idiosyncratic, and inconsistent between languages.</p>
</li>
<li><p id="_61b2c4ec-0c70-b30a-d90c-b94efe09767c">The use of the grammatical word divider is also less widespread than the elision mark, with which English conflates it.</p>
<ul id="_712f0619-b900-018b-57c8-4f4daa013655"><li><p id="_03a6b4d4-fe5f-da52-cbf8-f3e0a1d4c8cc">Wikipedia lists instances in Danish, Estonian, Finnish, Polish, Turkish, and Welsh. In the first four it is restricted to foreign words, where the inflection would be hard to parse as distinct from the unfamiliar word; in Turkish it is restricted to proper nouns, for similar reasons; and in Welsh it is used to disambiguate infixed pronouns. None of them use it regularly for every instance of the grammatical function, the way English does for possessive  <em>-’s</em>.</p>
</li>
<li><p id="_4951fc9c-d20a-c0b0-5eca-a4df2715fd58">English attaches possessive <em>-s</em> to nouns using a grammatical word divider. No other Germanic language does.</p>
<example id="_a2cf9d12-37de-814b-189f-a10db0251164"><p id="_4ee2f373-cad6-29be-1f44-2a565541fcfd">English: <em>Julia’s</em><br/> German:  <em>Julias</em></p>
</example>
</li>
<li><p id="_c7131192-c823-020e-4715-aec00d9e880d">Current practice in English uses a grammatical word divider for apostrophes, but a normal word divider for unexpected verb inflections:</p>
<example id="_9fa8be3f-15be-31af-8e27-303b0b1dd859"><p id="_c583f520-d7d3-4dcb-540c-51aafc91e72f"><em>Julia’s</em><br/> <em>to-ing and fro-ing</em></p>
</example>
</li>
<li><p id="_72f38cf1-8863-278f-47fb-b506556f6b19">Practice in English is in flux for particular functions: unexpected plurals, and verb inflections after vowels, used to be separated by a grammatical word divider; increasingly, that is not used at all.</p>
<example id="_de9f5152-8920-4c89-8ec2-d6ee9ab49df8">
<name id="_3c30a4e2-2188-80fb-0f76-0c70369e42d7">Older practice using grammatical word dividers</name>
<p id="_fb945f2a-fd74-60a1-b26a-57e85c130fff"><em>bastinado’d</em><br/> <em>KO’d</em><br/> <em>B’s and C’s</em></p>
</example>

<example id="_b454908d-ead8-c97d-e10a-a95fec28e5e2">
<name id="_92bcb658-d037-8689-d49b-c33f06313bd6">Newer practice avoiding grammatical word dividers</name>
<p id="_f0faa796-3bd0-f48a-726b-c88285048690"><em>bastinadoed</em><br/> <em>KOed</em><br/> <em>Bs and Cs</em></p>
</example>
</li>
<li><p id="_743ef32c-9a9b-e327-f680-951708160e75">Grammatical word dividers are also increasingly avoided in formal labels, such as geographical place names</p>
<example id="_30d6bf40-5e39-0700-105a-08d63e3c0ac8"><p id="_25dfb9c4-35df-ad74-260f-bf8e80106de9"><em>Coffs Harbour</em> (town in Australia, originally Korff’s Harbour)<br/> <em>Earl’s Court, Barons Court</em> (adjacent London Underground stations)</p>
</example>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_64e67082-f70c-9443-a0c9-6fd3dbbc7f78" obligation="normative">
<title id="_0415265f-6bb7-333b-bb25-d0a055db5ba6">Punctuation mark in scripts, languages, and locales</title>
<ul id="_930f085d-fa24-7ed5-9a63-f36e5e738dfb"><li><p id="_c6a78f9e-c30a-6a74-158c-5fb473ea63f2">In Latin and Cyrillic, the grammatical word divider is usually the apostrophe.</p>
<ul id="_7423e0b1-7656-5be9-ceb2-b700efbb9d6a"><li><p id="_4e180359-5278-5249-2b55-04fc1369a6e6">In fine typography, RIGHT SINGLE QUOTATION MARK <tt>&lt;’&gt;</tt> (U+2019) is used as the apostrophe. In typewriter usage, which is inherited in online usage,  APOSTROPHE  <tt>&lt;'&gt;</tt> (U+0027) is used.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_ba0bbc6c-e9c7-73ea-48ef-151e1f4847e0" obligation="normative">
<title id="_dae03d84-4317-03f7-0d5a-aabc969e7f3a">Special handling</title>
<p id="_59e2c4b1-7530-8bbb-3dd5-84dfe8bcfd79">The grammatical word divider function of the apostrophe has the same special handling as the elision mark function (<xref target="elision-mark"/>).</p>
</clause>
</clause>

<clause id="_9ecc39d8-1464-30ea-67dd-e21b3f6cf1fa" anchor="hyphen" obligation="normative">
<title id="_9d560f30-2013-ad80-518a-7ce813e554c6">Hyphen</title>
<clause id="_475082cb-128a-e3b4-057f-cdaa622b65ab" obligation="normative">
<title id="_ec20e677-a343-8ff0-ac74-e6ff8ba8cadd">Primary function and purpose</title>
<p id="_2871c48d-049a-8b6f-2d0c-1b40f0675e13">The hyphen is a special case of word divider (<xref target="word-divider"/>). It is used to divide a word at a line-break, so that the amount of empty space in a line is reduced.</p>

<example id="_1f70372e-8495-c65b-37c6-3708bf9a1bd9"><p id="_5b61e7a3-f5ab-233d-724b-3899ed63fc96">We, therefore, the represen-<br/> tatives of the United States<br/> of America …​</p>
</example>
</clause>

<clause id="_5b9b5dc4-4ba7-2153-907c-b56b95c8813b" obligation="normative">
<title id="_7cda1d19-46cc-b184-0500-f00bb469254e">Punctuation mark in scripts, languages, and locales</title>
<ul id="_25e572fd-8ae4-5ef2-1a2d-355e6f752c7e"><li><p id="_cd8e918c-4478-32a8-0e0d-d3433bd784ed">The hyphen is in routine use in Latin and Cyrillic.</p>
</li>
<li><p id="_b1a595f0-dc76-2c9b-1886-5cd53fa4b249">The word delimiter is alien to CJK; accordingly, the hyphen is also alien to CJK.</p>
</li>
</ul>
</clause>

<clause id="_5ff43250-f96d-33ae-d10c-1ff342607d6a" obligation="normative">
<title id="_9d15ccef-c09b-b823-607e-18e8d771faf2">Spacing rules</title>
<p id="_ec26237e-e478-a207-b760-e0071c097799">The hyphen is only meaningful in that function at the end of a line, and no characters are meant to appear after it.</p>
</clause>

<clause id="_99cde53d-8e35-555e-c392-c4456c99708e" obligation="normative">
<title id="_40ea83ae-d77e-cbba-1aec-85174478de55">Special handling</title>
<ul id="_6cc3ad8e-47d6-1089-9880-e6a88e39d070"><li><p id="_8a9b2e51-006e-4de5-02a9-651f75c555eb">An optional hyphen, SOFT HYPHEN (U+00AD) is often used in word processing, which is only rendered when near a line break.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_35230c9b-221a-1bd7-3141-2e2d2c8c3532" anchor="identifier-divider" obligation="normative">
<title id="_d5eab05b-9305-fa85-8a82-dae6e4e24217">Identifier divider</title>
<clause id="_319c092d-71af-669e-88b3-bb790be2fcb6" obligation="normative">
<title id="_49ba7670-a410-6a39-9e78-06ecc52ca271">Primary function and purpose</title>
<p id="_b5b28cc3-828e-d6f8-c0b0-681534d4a6a9">The identifier divider is used to break up a token that is not a linguistic expression.</p>

<example id="_1b91df09-853a-5159-97f8-7da5e5502136"><p id="_510dfc43-c809-715f-a518-d478bc852fcd">Phone number: <em>555-8787</em><br/> Date:  <em>2000-01-01</em><br/> Document identifier:  <em>ISO 639-2</em><br/> Document entity identifier:  <em>Table 3.1</em>, <em>Clause 4.1.4</em></p>
</example>
</clause>

<clause id="_cf317124-fdde-8781-f3d9-265db0764a3f" obligation="normative">
<title id="_f9572ebb-27ea-0881-87be-b56ca87a6b21">Range of semantic functions</title>
<ul id="_5f0d5ad5-adc8-51e9-9e0a-95b9c686f489"><li><p id="_0e290a25-41c3-c687-7e34-837704ca5f14">The function of the identifier divider and the word divider are quite similar: they both are breaking up a token and showing its internal structure. They differ in that one divides a linguistic word, and the other divides a non-linguistic token.</p>
</li>
<li><p id="_9ce08467-3afb-4d37-2790-57f76b0d2828">The function of the identifier divider is also similar to the decimal point, as a number token divider; however decimal points are dealt with separetely, as numeric formatting.</p>
</li>
<li><p id="_0c5eee0d-48af-7e4b-4ef1-1e000e978965">Identifier dividers can apply to numbers as identifiers, but are distinct from decimal points in that they don’t have an arithmetic function. So when separating groups of digits in a phone number or a date, the hyphen is distinct from a decimal point.</p>
</li>
<li><p id="_626b1fe2-1b0d-4521-c8d8-c7711e8f05ce">The components of a numeric date are also split by identifier divider.</p>
</li>
<li><p id="_db2b320d-8a5e-6c97-7d4c-e30f3bfb86cf">In the case of hierarchical identifiers of entities in a document, such as clauses, Metanorma Presentation XML notates this as  <tt>&lt;span class="fmt-autonum-delim"&gt;</tt>.</p>
</li>
</ul>
</clause>

<clause id="_ff6dc609-e0b1-adef-1f81-addbd5a32aef" obligation="normative">
<title id="_cfd89269-d559-69c6-c57a-82f657f7fd57">Punctuation mark in scripts, languages, and locales</title>
<ul id="_cdfa9bbb-0b14-1ba7-e2b3-c09bb2d0de7b"><li><p id="_dec17bb4-df3a-5969-1545-234c55d91ae0">The usual identifier divider is the hyphen. In Unicode, the identifier divider function is properly indicated with FIGURE DASH  <tt>&lt;‒&gt;</tt> (U+2012), as that symbol is designed to have the same width as Arabic numerals.</p>
</li>
<li><p id="_e9fc9d35-3663-13d5-7242-b92fdda91a94">Period, slash, colon and parentheses are also used idiosyncratically, through analogy with their core meanings (hyphen as a word divider; sentence stop as delimiter of a meaningful unit; slash as a disjunctive mark; colon as an introductory stop; parentheses as additional material).</p>
<ul id="_e97dbaf2-53ef-b86f-8089-9281a8e73856"><li><p id="_4f4965da-23ee-8435-9f5a-a3edc107967c">Period is the most common for hierarchical identifiers of document entities; colon is the most common for delimiting a following date.</p>
</li>
</ul>
</li>
</ul>
</clause>
</clause>

<clause id="_adc17013-0ff3-eef8-4ab3-a4c920c56f5d" obligation="normative">
<title id="_94986a65-40ec-413d-9dc1-754222d603b0">Identifier delimiter</title>
<clause id="_756389e4-ee43-5bd3-3fea-647c66756834" obligation="normative">
<title id="_7785bb18-182a-c686-0b1b-8b8ea39c7faa">Primary function and purpose</title>
<p id="_09a9afe4-7991-98e5-02f5-05752854cede">The identifier divider is used to separate an identifier from surrounding text, whether at the start, the end, or both.</p>

<example id="_142821ff-87db-11ad-93bd-794605dc4ca3"><p id="_8dcee4e4-c99b-12ae-64dc-702fdc397c53"><em>Formula (1)</em><br/> <em>Figure 1 a)</em></p>
</example>
</clause>

<clause id="_561620a2-8b81-63e9-eefb-daa7094bdcca" obligation="normative">
<title id="_6fa79821-b3bf-d5cd-2cc1-40bf75b71bdf">Range of semantic functions</title>
<ul id="_1a1efb85-2985-afb5-4835-bb48dc703643"><li><p id="_e2f06c41-4809-760b-bc38-3fd032483627">Identifier delimiters distinct from word delimiters are very rare. The most common use of them is in structured documents such as under Metanorma, for subfigures and formulas. Whether an identifier delimiter is used is a matter of style convention.</p>
</li>
<li><p id="_f414300e-a187-02b6-ca2e-f70b7b1f6b85">The identifier delimiter is similar in function to title marks (<xref target="title-mark"/>) and emphasis marks (<xref target="emphasis-mark"/>).</p>
</li>
<li><p id="_106a5e5d-bbe4-7430-9d98-648fd4d0d4d8">Metanorma Presentation XML currently notates this function as <tt>&lt;span class="fmt-autonum-delim"&gt;</tt>, although this is properly the notation for identifier dividers.</p>
</li>
</ul>
</clause>

<clause id="_262f54ea-3b2e-e682-013f-0075ca100299" obligation="normative">
<title id="_c05e3bbb-caec-360c-b9ca-e156fbfdc4ae">Punctuation mark in scripts, languages, and locales</title>
<ul id="_f85bd5c2-4a2d-3cf0-96a8-ddb987e39ef4"><li><p id="_f80f2b1f-5a9f-0af9-e259-4676f58d1652">The usual identifier delimiter is the close parenthesis, or surrounding parentheses.</p>
</li>
</ul>
</clause>
</clause>
</clause>

<clause id="_d5b75d19-e2a7-04e9-271f-8a50350421b6" anchor="caption-markers" obligation="normative">
<title id="_66b1c0b6-42d3-c88a-f502-db010603a197">Caption markers</title>
<clause id="_9b8deec7-09f7-968b-2d36-2b6cf1931d45" obligation="normative">
<title id="_1772d070-ae11-4e1a-e0f9-d3c78d3198e5">General</title>
<clause id="_1ac719a5-1546-4cf6-f551-8b6db4428938" obligation="normative">
<title id="_595be0f6-b1cd-8c1e-ea06-86e301c524ac">Primary function and purpose</title>
<p id="_90c3f03d-2f40-982f-cfde-21b0d6ac5bf2">In formal documents (particularly the standards in scope of Metanorma), titles of cross-referencable entities within the document (figures, tables, lists, list items, footnotes, clauses, etc.) are labelled in such a way as to isolate the identifier of the entity. This is done both in labelling the entity, and in cross-referencing that entity.</p>
</clause>
</clause>

<clause id="_75baa74c-bea8-fb03-8c7e-725cf36e1b47" anchor="caption-number-delimiter" obligation="normative">
<title id="_0ade8cfe-7800-d175-159f-f932290c4616">Caption number delimiter</title>
<clause id="_035c20b5-46f8-710b-8628-97e61cf3ebec" obligation="normative">
<title id="_fe412c31-61b9-1342-c3aa-2688d54cce99">Primary function and purpose</title>
<p id="_e48cc9bd-90b0-1e68-b8bd-c7a34d126f39">The identifier of the entity may be signalled with punctuation acting as a delimiter. In Metanorma Presentation XML, this is notated as  <tt>&lt;span class="fmt-label-delim"&gt;</tt>.</p>

<example id="_d8ced9fc-af14-0353-a0bd-b9e3dc963e2c"><p id="_0a88069e-f5e1-c202-505c-f8164bb2bfbc"><em>Table 1.</em></p>
</example>

<example id="_e05289f3-b55d-e280-4b44-9ef8418f3a14"><p id="_1b9e105b-c67e-6583-450b-630789cbb18b"><em>3)</em></p>
</example>
</clause>

<clause id="_9ac783c6-6c20-26c7-fe45-8e45ecb98b31" obligation="normative">
<title id="_f1402f28-004e-bf54-b134-f2317240c8a9">Range of semantic functions</title>
<ul id="_4c002534-b6f9-2ead-3f6e-569def31fe8a"><li><p id="_2915896d-7d17-28fd-d5fc-8e5868aced6f">Different kinds of entity can take different punctuation. Ordered list items are commonly delimited with a closing parenthesis instead of a period.</p>
</li>
</ul>
</clause>

<clause id="_fb2a1a04-d87a-497f-be20-160caaf838b1" obligation="normative">
<title id="_91fb7f4e-8e3e-072b-b420-c5afc53d98ff">Punctuation mark in scripts, languages, and locales</title>
<ul id="_3f5fa7b7-b03c-6695-e093-6515693d57e5"><li><p id="_de499cf3-1520-0a07-205c-9a359be23fb6">Latin, Cyrillic: Period is the most common caption number delimiter, if a delimiter is used at all. Closing parentheses are common for ordered list items and footnotes.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_1e84c1d6-eed8-892e-c80f-d45b0a635fdf" anchor="caption-separator" obligation="normative">
<title id="_da0d0bb4-b9bd-ff5e-2009-55f998789710">Caption separator</title>
<clause id="_f037c3db-00c3-6b91-a9ef-2cf3156779e1" obligation="normative">
<title id="_916a9f12-392d-be49-c797-9a5feca63907">Primary function and purpose</title>
<p id="_b964b17e-c47d-edef-cb9e-cfb58d74a8d9">If the number of the entity appears together with a caption or title, giving more information about the entity, punctuation is usually used to separate the two. In Metanorma Presentation XML, this is notated as  <tt>&lt;span class="fmt-caption-delim"&gt;</tt></p>

<example id="_5e7d7f5a-187c-4154-1672-63a2ed2570e7"><p id="_83eea019-d310-7f6e-e50a-559c23a22951"><em>Table 1. Distribution of rice yields</em></p>
</example>

<example id="_57680570-997e-d6e2-9cde-01755ba498f0"><p id="_33af798d-32e4-3c92-63d1-dead13bf8bea"><em>2.1: Soil erosion</em></p>
</example>
</clause>

<clause id="_58086b87-5a58-b492-6382-08b2adb2ceca" obligation="normative">
<title id="_2957359d-a84f-e970-ec2d-12323ab315bf">Range of semantic functions</title>
<ul id="_f81e6432-0536-b5b8-7434-6329d48551df"><li><p id="_617be5ce-bc03-ce58-a57e-98f3624fac8f">Different kinds of entity can take different punctuation. For example, a document may use period as a caption separator for clauses, but dash for tables and figures.</p>
</li>
<li><p id="_eac43d28-e6ff-e773-73a3-e4f96117d4d2">This function overlaps with the caption separator. If a caption number delimiter is used, a distinct separator is usually not used after it. The following illustrates different possible configurations.</p>
<example id="_b07128ad-d365-bf41-ffbf-4e3159270d11">
<name id="_27e4f17d-d654-ef3e-806b-d16562a8ea07">No caption number delimiter, colon as caption separator</name>
<p id="_d48b46bf-0405-ecec-38d8-98757e709c25"><em>Table 1</em><br/> <em>Table 1: Distribution of rice yields</em></p>
</example>

<example id="_4c4bdbdf-07ee-ea69-7c62-f9e391e4c214">
<name id="_ec93dfcb-1bae-f5bc-7992-a38222ff7c83">No caption number delimiter, period as caption separator</name>
<p id="_b6a75b91-38f1-dfd2-c7b2-c445ee62becf"><em>Table 1</em><br/> <em>Table 1. Distribution of rice yields</em></p>
</example>

<example id="_fffb5ac7-4ede-4b58-5f16-da5ca1e05e61">
<name id="_47bd81b9-5fa9-7d35-2fac-74ba0dd55c1e">Period as caption number delimiter, caption delimiter blocks distinct caption separator</name>
<p id="_b584fc22-4f49-9800-6795-743d614637b1"><em>Table 1.</em><br/> <em>Table 1. Distribution of rice yields</em><br/> NOT:  <em>Table 1.: Distribution of rice yields</em></p>
</example>
</li>
</ul>
</clause>

<clause id="_04fedea4-fc11-0fce-2592-345c3128adc1" obligation="normative">
<title id="_c46b51df-6353-a2bf-7415-70d6128e84e5">Punctuation mark in scripts, languages, and locales</title>
<ul id="_08e7cd4e-e0e7-d545-bcfa-82ad65e3711e"><li><p id="_db8b8914-472a-3fb0-5c3d-b5e312a45b9d">Latin, Cyrillic: All of the following may appear in this function: space (i.e. no special punctuation), colon, comma, em-dash, period</p>
</li>
</ul>
</clause>
</clause>

<clause id="_87808753-27fa-50b6-7f8f-0df46116e715" obligation="normative">
<title id="_183a379d-b0be-2658-b1d7-7a2aab4a2776">Caption stop</title>
<clause id="_68149386-f085-db88-3e67-8d6f1cea82d9" obligation="normative">
<title id="_0a7bc83c-c430-2e13-5c7c-cf780a02be39">Primary function and purpose</title>
<p id="_81576340-cec7-0bb9-efec-b8d631a9cc8f">The caption or title of an entity in a document may be terminated with a punctuation mark. In Metanorma Presentation XML, this is notated as  <tt>&lt;span class="fmt-label-delim"&gt;</tt> (conflating it with the Caption number delimiter.)</p>

<example id="_46904d52-c0fc-0721-308f-da52c51aab24"><p id="_6b377d6f-c3e7-8882-b51b-6fe22e442847"><em>Table 1: Distribution of rice yields.</em></p>
</example>
</clause>

<clause id="_a6954e9c-0fa7-aa28-407e-b026c03cb9ff" obligation="normative">
<title id="_ddab68d1-24d6-3064-d171-63d558ef81c6">Range of semantic functions</title>
<ul id="_ece12c5a-5608-c71e-0074-13db263bf029"><li><p id="_57d66014-9b17-5258-a60e-9ceaea50ecde">This function is an extension of the sentence stop, since captions can be seen as sentences. Whether it is used or not depends on the publisher’s style conventions.</p>
</li>
</ul>
</clause>

<clause id="_876ab0fb-7f0f-2267-8f9d-8763d2ea361b" obligation="normative">
<title id="_5b276e3f-95f5-be20-f9c3-09d5839a20d4">Punctuation mark in scripts, languages, and locales</title>
<ul id="_e88adf57-e8ad-4536-a381-6a75f0fcddd5"><li><p id="_a9f24380-814a-4b12-8651-f29db2d58165">Latin, Cyrillic: if a caption stop is provided, it is a period.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_16b18373-badd-3b72-3da4-c25ba2828aa5" obligation="normative">
<title id="_0099f032-c538-854e-1972-1c05e0bdf18f">Hierarchical caption separator</title>
<clause id="_78807e1d-f7a0-1b38-1a17-70c32e37fb54" obligation="normative">
<title id="_d45df1c0-2c19-4570-44b5-b06f2826176b">Primary function and purpose</title>
<p id="_dfecf96d-3bbd-f648-d240-ac3e125373d8">The hierarchical caption separator separates hierarchical components of a cross-reference to entity in a document (e.g.  <em>Clause 5, Note 1</em>). This is used when the entity cross-reference by itself is ambiguous (e.g. note numbering restarts each clause, so “Note 1” on its own is ambiguous between the first note of clause 4 and of clause 5.) In Metanorma Presentation XML, this is notated as  <tt>&lt;span class="fmt-comma"&gt;</tt>.</p>
</clause>

<clause id="_4bccebef-7b05-b816-43ed-30c46f612803" obligation="normative">
<title id="_534cc069-9e35-4219-8969-778fac8dda08">Range of semantic functions</title>
<ul id="_4e49935b-2b76-34b3-554c-401d3e742c1f"><li><p id="_05c7e090-35f6-3901-8eaf-8a90c3153063">This is a special case of a name separator (<xref target="name-separator"/>), and shares punctuation with it: comma in Latin script.</p>
</li>
</ul>
</clause>

<clause id="_244ccdb9-9f8b-0e5e-402f-c9e61a8552b6" obligation="normative">
<title id="_fa6e3c8e-5867-5da9-e089-ccc2075381c5">Punctuation mark in scripts, languages, and locales</title>
<ul id="_3c7ff90f-6968-bc3c-9117-aa181bcf637a"><li><p id="_f2439051-7ae6-2c0f-be76-97063ff43f42">Latin, Cyrillic: if a caption stop is provided, it is a period.</p>
</li>
<li><p id="_937e9416-eba2-61aa-c1ff-069880a0978a">In some languages and styles, this function is conveyed by linguistic words instead of punctuation; e.g. in Japanese, the particle の “of” is used instead.</p>
</li>
</ul>
</clause>
</clause>
</clause>
</clause>

<clause id="_be580c07-6094-6b49-7af7-8bd9b82da56f" obligation="normative">
<title id="_8b621d48-91e6-f11c-d255-a7a2d1913b08">Functions: adding meaning</title>
<clause id="_7cabab3e-d10a-2838-582f-f5a94e056869" obligation="normative">
<title id="_2294873a-5a40-7237-147e-ca5236c71ced">Annotation markers</title>
<clause id="_fce7e358-58f4-1e4d-2e88-d64de1561184" obligation="normative">
<title id="_9dd6109e-3c79-f47e-db10-f3558609d0e4">General</title>
<clause id="_9018a974-f4ed-3e0e-0fa5-2e0ab9c31862" obligation="normative">
<title id="_e96f96bd-fec3-1ca9-5cfa-9da70675072b">Primary function and purpose</title>
<p id="_0b504d14-091a-adc9-417e-8855a05be12b">Annotation markers provide supplementary information or references related to the main text content.</p>
</clause>

<clause id="_838a2201-9eba-2432-a385-dc1b823c273c" obligation="normative">
<title id="_f596567a-2459-4b35-8ca6-1d24f40ed71f">Range of semantic functions</title>
<ul id="_bf17c5cd-d358-bdeb-fecb-3d99e9914e4f"><li><p id="_0bec3ca8-6772-d618-47eb-5e879293b8f9">Annotation markers are routinely conflated with grouping markers (<xref target="grouping-marker"/>), which enclose, separate, or highlight specific text elements.</p>
</li>
<li><p id="_fce9e706-14dd-54ac-f937-cf411833850d">Different kinds of annotation are indicated by different punctuation conventions, as described below, but these are usually not rigorously differentiated.</p>
</li>
</ul>

<example id="_268ddea9-a15f-76f0-981d-d6ec061bc019" anchor="leiden"><p id="_ddad184c-3f63-8586-dad6-d2b963c257f0">The Leiden conventions for publishing ancient inscriptions and papyri use a wide range of brackets with quite distinct meanings, in order to convey editorial approaches to a text. (They are a form of machine readable text changes.) This is the upper limit of distinct semantic functions in annotation markers, and most use of annotation markers is semantically much more ad hoc:</p>

<ul id="_954fc97d-f708-ed0f-0a5a-65d2800db803"><li><p id="_72d25f6f-d877-b5c2-96f0-404065b4f1a1">ạḅ: letter is unclear in original</p>
</li>
<li><p id="_86841391-15cc-be00-837f-975047cccc28">[abc]: letters missing from original (because text is broken off), restored by editor</p>
</li>
<li><p id="_804a6d30-7f01-c315-b925-f6021049281c">⸤ abc⸥ : letters missing from original, but restored from another source, e.g. a mediaeval manuscript of the same text</p>
</li>
<li><p id="_34bbe3c4-1311-a4d0-2c31-e5d7b91ab88b">⟨abc⟩: letters left out from original text (because the scribe never wrote them), restored by editor</p>
</li>
<li><p id="_3f528b15-8211-1700-ded8-280f7ac570b7">a(bc): abbreviation in original, letters expanded by editor</p>
</li>
<li><p id="_a378bed0-6e91-1a4a-08ec-9f8640575f95">{abc}: letters written in the original by the scribe, deleted as errors by the editor</p>
</li>
<li><p id="_33d65742-badc-7c13-06cb-0cdb457d4354">⟦abc⟧: letters deleted in the original by the scribe, restored by the editor</p>
</li>
<li><p id="_a390541d-e5cc-dc32-3f93-39a47ce77257">\abc/: letters interpolated in the original by the scribe (typically between lines)</p>
</li>
</ul>
</example>
</clause>

<clause id="_0cccff45-24dc-cb56-df55-e673e7fbe0eb" obligation="normative">
<title id="_b7657768-6f49-3462-3b33-c20b614b0674">Special handling</title>
<p id="_3c0880ff-735e-5117-f2ce-0b5815032757">CJK full-width punctuation (<xref target="cjk-fullwidth-punctuation"/>) applies.</p>
</clause>
</clause>

<clause id="_a19a8203-a722-49a0-94ba-3089a7e182a7" anchor="parenthetical-annotation" obligation="normative">
<title id="_e6113db2-9dc9-ba71-827f-0a456c2178bd">Parenthetical annotation  (<em>parentheses</em>)</title>
<clause id="_46db1f67-2b6f-7750-7ee3-0850137cc294" obligation="normative">
<title id="_d591dab4-2d54-9c8e-82ff-638f38b218c9">Primary function and purpose</title>
<p id="_b08256c9-657c-b0d0-6ee9-864f0570428b">Parenthetical annotation marks enclose supplementary or explanatory information. This function is represented in Metanorma i18n files as  <tt>punct.open-paren</tt> and <tt>punct.close-paren</tt>.</p>
</clause>

<clause id="_b17498e8-3cbb-f433-4417-feee23f7882f" obligation="normative">
<title id="_5c9f2ad2-65a3-7915-e76f-6cbcc3707f00">Range of semantic functions</title>
<ul id="_97553ff2-0f5b-7cd5-89d9-40a5f6bd4e16"><li><p id="_b993694f-4b0c-8cd5-a55f-1b1eca1eea74">Parenthetical annotations can appear either within a sentence, or as a group of one or more sentences, between sentences.</p>
</li>
<li><p id="_6451d853-9e76-af18-9a6b-0e3057d817b9">Parenthetical annotations can be conflated with grouping markers (<xref target="grouping-marker"/>), although they are less common in that function than for other paired punctuation marks.</p>
</li>
<li><p id="_807d344b-a5ee-a483-3387-09caa0120cd6">As an extension of their role, parenthetical annotations can also occur within a word, to indicate that a part of the word is optional in some sense. This is a special case of a word divider. Examples include indication of singular and plural, or masculine and plural; both give the letter distinguishing those grammatical categories in parentheses, as optional:</p>
<example id="_558e8e78-670d-abc4-322e-fff2ffd27819"><p id="_af1539b3-0f54-98a8-8261-c48daed1085e"><em>(s)he</em><br/> <em>plan(s)</em></p>
</example>
</li>
<li><p id="_6bd93b9f-0d08-d45e-fd7a-8ff8e96f768b">Within a sentence, paired breaking phrase (em-dashes) separators (<xref target="breaking-phrase-separator"/>) can overlap in function with parenthetical annotations: the parenthetical information is presented as a break from the main sentence, and another breaking phrase separators resumes the main sentence.</p>
<example id="_05eaf542-b377-5ae8-57c5-b9be67699912"><p id="_73448a34-55db-f55c-91db-6b4e2fdbc7be"><em>The red-nosed reindeer (Rudolph was his name) had a very shiny nose.</em></p>

<p id="_e320c1b9-ef19-3067-22e0-08139c0e11ef"><em>The red-nosed reindeer—Rudolph was his name—had a very shiny nose.</em></p>
</example>
</li>
</ul>
</clause>

<clause id="_b66ace6f-1279-b847-6348-79850f1fe8ac" obligation="normative">
<title id="_8a3ffc47-3099-3bca-da3e-69f60c4d66ac">Punctuation mark in scripts, languages, and locales</title>
<ul id="_ec60d41f-c229-acc9-5f61-71cd79f0b630"><li><p id="_daa4a0d8-b165-e779-2fa3-09d51b26af20">Latin, Cyrillic: By default, parenthetical annotations are rendered as LEFT PARENTHESIS <tt>&lt;(&gt;</tt> (U+0028) and RIGHT PARENTHESIS  <tt>&lt;)&gt;</tt> (U+0029)</p>
</li>
<li><p id="_310cf235-be61-aa32-a5b3-da355cbbe553">Paired em dashes are used within a sentence, when the parenthetic annotation can be presented as a sentence break and resumption. This is associated with less formal style.</p>
</li>
<li><p id="_a737b22b-fca3-161a-e0d4-1621c163a499">CJK:  FULLWIDTH LEFT PARENTHESIS <tt>&lt;（&gt;</tt> (U+FF08) and  FULLWIDTH RIGHT PARENTHESIS <tt>&lt;）&gt;</tt> (U+FF09)</p>
<ul id="_f645a751-9340-9345-ef04-c5656c12518d"><li><p id="_ef132e83-5a4a-81ad-a977-cb4add9753e6">Use of a paired em dash equivalent is rare in CJK.</p>
</li>
<li><p id="_e13d11ee-da66-46fa-425f-91774cd18d22">Japanese: Japanese in addition uses double wave dash, WAVE DASH <tt>&lt;〜&gt;</tt> (U+301C)</p>
<example id="_35b2a505-ad2a-3da4-854e-db309500b6b9"><p id="_2a46734b-6d51-ee1f-1a0f-367a2ee3664d">〜〜答え〜〜</p>
</example>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_4a0d8d74-76be-220c-cff6-d924ed508feb" obligation="normative">
<title id="_68d640dc-0e09-e35a-6d1e-939d067d8211">Special handling</title>
<ul id="_ec483d84-0270-1f38-79c5-b63b5dbf8a91"><li><p id="_07bf99ad-e773-d563-0add-843f24496f16">Languages differ as to whether parentheses enclosing italicised text should themselves be in italics. In German, they are expected to; in English, they are expected not to.</p>
</li>
<li><p id="_b84da94a-be4a-a75a-a564-177391e93d2b">Parenthetical annotations can be nested within other parenthetical annotations. In informal writing, parentheses are used for both nesting and nested annotations. In formal writing, concern for ambiguity drives many style guides to require that the nested annotation be in brackets instead of parentheses, with any third level of nesting  in curly brackets.</p>
<example id="_84eee9a0-7f3c-dc25-022d-fb71c2184ebf"><p id="_aee080ec-b003-e8e0-c1ad-2eef9b833212">From Wikipedia:</p>

<quote id="_9c21eaf8-3eb5-d7cd-661b-52408029f8ca"><p id="_b03f5e17-ebb6-d49f-22ad-bbbe39eb6f6a"><em>Parentheses may be nested (generally with one set (such as this) inside another set). This is not commonly used in formal writing (though sometimes other brackets [especially square brackets] will be used for one or more inner set of parentheses [in other words, secondary {or even tertiary} phrases can be found within the main parenthetical sentence]).</em></p>
</quote>
</example>
</li>
</ul>
</clause>
</clause>

<clause id="_0a2c8a80-5540-4189-5537-5ee0db236aec" obligation="normative">
<title id="_bfd42eb0-858d-efc1-7eff-e64bef9a381a">Footnote annotations (<em>footnote marks</em>)</title>
<clause id="_0cdf2456-668c-cc08-f93f-75a6d2e79ac8" obligation="normative">
<title id="_dbd2a860-5b0f-51bc-b09c-cfafa513fbf1">Primary function and purpose</title>
<p id="_411c5a71-a342-5f25-b218-a2f85807e50a">Footnote annotations are text annotation marks that provide supplementary information or references related to the main text content, like parenthetical annotations. Unlike parenthetical annotations, the annotation does not appear inline with the text it is annotating, but in a separate place: either the bottom of a page (<strong>footnote</strong>), the end of a chapter or book (<strong>endnote</strong>), or, in older practice, the margin of a text (<strong>marginalia</strong>). A footnote mark is used to cross-reference the place annotated in the text (where it is a  <strong>footnote reference</strong>), to the annotation content (where it is a <strong>footnote label</strong>).</p>
</clause>

<clause id="_f4ae44c1-a8c0-ed47-5b06-6605b3a7237e" obligation="normative">
<title id="_0e8e3739-96e3-c0f6-18c7-2706b9c2965b">Punctuation mark in scripts, languages, and locales</title>
<ul id="_f8d13150-dd79-6a62-9f21-3309945aff05"><li><p id="_4b5e25c7-6b1a-741b-dd24-ea16ecd11286">Latin, Cyrillic: there are two repertoires of marks drawn on for footnote marks</p>
<ul id="_8f149cee-1711-f6d4-74ff-44cc3bcdcfa6"><li><p id="_e99cf3e6-5baa-d4ee-788b-e40672e7b2f6">Where a small repertoire of footnote marks is required (e.g. footnotes are cycled through once for each page), and in older practice, footnote marks are drawn from a set of typographical symbols, in the traditional order  <tt>&lt;* † ‡ § ‖ ¶&gt;</tt>, supplemented in ad hoc function by other symbols.</p>
</li>
<li><p id="_72a83c46-c3d7-c4d5-7906-c3105e58c902">Where a large repertoire of footnote marks is required (e.g. footnotes are cycled through once per chapter or document), and in newer practice, footnote marks are drawn from an ordered sequence of numerals or letters. Arabic numbers are the most commonly used, but Roman numbers and letters of the alphabet also appear.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_fb0f2767-5bf9-ddcd-9749-332277ded3ef" obligation="normative">
<title id="_666e73f4-6771-71a3-935a-4ea140d26c20">Spacing rules</title>
<ul id="_e1f680e9-5aef-f6a5-a077-edd526f1b65f"><li><p id="_98ecc5a2-8b82-c2db-cfd2-a0d5fddb598a">There is normally no space between text being annotated and the footnote reference.</p>
</li>
<li><p id="_4cd171f1-5cc2-f013-a1ce-8674f8799d64">There may be space between the footnote label and the annotation.</p>
</li>
</ul>
</clause>

<clause id="_f7aba08e-2e23-9e13-6b6a-5686d0a8157c" obligation="normative">
<title id="_21ec1f82-6204-beda-21f3-769ea9bd5a3c">Special handling</title>
<ul id="_d3491bf5-363b-c756-87ab-4f5ec6771830"><li><p id="_4a8fa434-3c59-fe17-e07a-9999eaa26fbb">Footnote marks are normally superscripts, both as footnote references and as footnote labels.</p>
</li>
<li><p id="_9829ef38-329a-aef0-4064-629019a4f90b">Footnote references normally appear after sentence and phrase stops.</p>
</li>
<li><p id="_f9feb49f-4f26-2218-dbe4-8543b8192322">There are different conventions on whether the repertoire of footnote symbols is cycled through (i.e. restarted from  <tt>1</tt> or <tt>*</tt>) each page, each chapter, or once in a document.</p>
</li>
<li><p id="_3f5f856d-a149-e686-8ba8-dc124e7c8f2b">There may be a caption number delimiter after the footnote mark. Documents may differ in whether they place a caption number delimiter after footnote references and after footnote labels.</p>
</li>
<li><p id="_f84b17d0-e8b7-0b53-a873-1ae6a7d2e8d4">In some documents, a semantic distinction is made between different footnote mark sequences.</p>
</li>
</ul>
</clause>
</clause>
</clause>

<clause id="_91151bc9-9052-0467-6e51-ff49672ebdd7" anchor="grouping-marker" obligation="normative">
<title id="_87daccab-a0c4-cf5d-7531-9e3cdd5264cb">Grouping markers</title>
<clause id="_3b55857a-5d5a-9ab7-ca46-1df91966671d" obligation="normative">
<title id="_274a7230-5401-7430-2ed4-bb5af8c0ed35">General</title>
<p id="_fbb069cb-8403-4753-896a-4415e55d60d1">Grouping markers include a range of paired punctuation markers, used to indicate that the enclosed items or word belong together in some sense. While grouping markers have some semantic functions associated with editorial interventions, the association is loose, and the markers are instead differentiated by visual form.</p>

<p id="_a6e259b6-fb9f-1e07-3245-0f2d9313d253">The listing of grouping markers here is limited to those in use in normal language. Grouping markers that only appear in formal notation systems, e.g. double brackets (MATHEMATICAL LEFT/RIGHT WHITE SQUARE BRACKET  <tt>&lt;⟦ ⟧&gt;</tt> U+27E6/U+27E7) and floor brackets (LEFT/RIGHT FLOOR  <tt>&lt;⌊ ⌋&gt;</tt> U+230A/U+230B) are out of scope of this document.</p>

<clause id="_b51a5c43-7181-86f1-be64-710f90fbe17c" obligation="normative">
<title id="_9c4ff70a-21f9-78b3-2e74-2c52667e2fc7">Range of semantic functions</title>
<ul id="_46657b75-fa74-9d69-c9f2-2475884ec263"><li><p id="_1606c6a4-b35d-17fc-c901-95742b4eb962">Grouping markers overlap with parenthetical annotations (<xref target="parenthetical-annotation"/>).</p>
</li>
<li><p id="_1702ba60-2161-47d4-21cb-ae9844fa7d8f">Grouping markers are used to indicate editorial interventions in text; the Leiden conventions (<xref target="leiden"/>) are a very formalised equivalent of the less granular conventions expressed by grouping markers. Editorial interventions are not here treated as a distinct semantic function.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_01d15234-1a93-c396-9ca8-548795c98e65" anchor="bracket" obligation="normative">
<title id="_787006d9-ab4a-eb92-a4e1-22df23e02237">Bracket</title>
<clause id="_85ddeed5-3ee1-2f47-3d7f-a15eb3b8133a" obligation="normative">
<title id="_bdccb69e-8c6c-2c3f-1ab4-98a0dc0678de">Range of semantic functions</title>
<ul id="_63a8f646-d2f2-4eb0-dfe3-8939647a9254"><li><p id="_69d03b9e-d864-8dc6-f072-5a3835493e39">Brackets can be used to insert explanatory material, instead of parentheses. Typically  the brackets represent an editorial intervention, rather than the authorial voice.</p>
</li>
</ul>

<example id="_b15cdd39-6439-2336-b088-e3b289ad3f68">
<name id="_d9fecebf-e6b8-5dcc-b7cc-d0043996e714">Use of brackets to indicate editorial change of a text’s case</name>
<p id="_981bdc9b-dab5-684a-9f08-18c98b1ec066"><em>[m]y cause is just</em></p>
</example>

<example id="_c5c558f0-aaeb-1a21-5637-7aeb2b2aa186">
<name id="_f81fe307-1988-8bc4-36af-b9566c4f334c">Use of brackets to indicate an editorial explanatory interpolation</name>
<p id="_425d5d9c-543c-d250-d290-d832462af4d1"><em>I appreciate it [the honor], but I must refuse</em></p>
</example>

<example id="_631196b3-98aa-36bf-4a99-da85ad8fcc37">
<name id="_8a9e13fe-ccc6-56ef-d12c-bcd5c6ed0374">Use of brackets to interpolate the original language word in a translation</name>
<p id="_607cac44-0fe8-0730-cc7f-7976fd9abccf"><em>He is trained in the way of the open hand</em> [karate].</p>
</example>
</clause>

<clause id="_56d0c312-d085-c223-52d2-f4396ab8c05f" obligation="normative">
<title id="_5606d293-c387-fca0-755d-baebced2702f">Punctuation mark in scripts, languages, and locales</title>
<ul id="_a5a8a01f-07c6-1ef8-a03c-1fa5a0787420"><li><p id="_83b07569-a16b-1e6b-955a-5b697f1826e0">Latin, Cyrillic: LEFT SQUARE BRACKET <tt>&lt;[&gt;</tt> (U+005B), RIGHT SQUARE BRACKET <tt>&lt;]&gt;</tt> (U+005D)</p>
</li>
<li><p id="_c6b5f0fb-fb11-2722-4e88-dfa98c7c0e66">CJK: FULLWIDTH RIGHT SQUARE BRACKET <tt>&lt;［&gt;</tt> (U+FF3B), FULLWIDTH RIGHT SQUARE BRACKET <tt>&lt;］&gt;</tt> (U+FF3D)</p>
</li>
</ul>
</clause>
</clause>

<clause id="_10a6c2a2-dd28-ac23-81ac-712b35e2b0f0" obligation="normative">
<title id="_3f90cc08-68a7-e46e-c5b6-69a948feab09">Brace</title>
<clause id="_ab75e41c-dbf4-c9a3-dc73-8c31a361df77" obligation="normative">
<title id="_b1f06c98-ca90-bad8-16ac-fbccd5317a07">Range of semantic functions</title>
<ul id="_26b68098-5587-c60c-5345-cd14d1700b24"><li><p id="_96e7a8a7-c20a-ba61-8517-5c6ebde6496c">The main use of braces in English normal text is to indicate editorial additions and interpolations. They are overwhelmingly used in formal notation systems instead.</p>
</li>
</ul>
</clause>

<clause id="_d26965aa-18eb-cbc1-ac00-0d3efc8a6f3a" obligation="normative">
<title id="_91b46838-2be7-4578-5609-6c2416870ea8">Punctuation mark in scripts, languages, and locales</title>
<ul id="_ad922b76-b65c-c4c3-d423-b8d07bea9888"><li><p id="_c7c9d4df-aa90-6bb0-d3da-7d1dd864e02d">Latin, Cyrillic: LEFT CURLY BRACKET <tt>&lt;{&gt;</tt> (U+007B), RIGHT CURLY BRACKET <tt>&lt;}&gt;</tt> (U+007D)</p>
</li>
<li><p id="_d7785f5b-0301-eb47-aa09-dfbd8a5f993e">CJK: FULLWIDTH RIGHT CURLY BRACKET <tt>&lt;｛ &gt;</tt> (U+FF5B), FULLWIDTH RIGHT CURLY BRACKET <tt>&lt;｝&gt;</tt> (U+FF5D)</p>
</li>
</ul>
</clause>
</clause>

<clause id="_dbab3b63-fad1-325b-0a46-a35f07835aaf" obligation="normative">
<title id="_6b806bf8-77c8-2401-79a0-2538d5553911">Angle bracket</title>
<clause id="_1be5da2a-baa6-cf04-34a7-0a5d819ce2d8" obligation="normative">
<title id="_e1baa611-9d64-c4e3-be12-dea99f046742">Range of semantic functions</title>
<ul id="_cae255db-fa0e-2204-0314-12f4fb2e8303"><li><p id="_e429e1a8-72e0-344c-a481-f95d91be67fc">Angle brackets have limited use to indicate editorial interpolation, or to indicate that a text was thought by a character instead of spoken. They are overwhelmingly used in formal notation systems instead.</p>
</li>
</ul>
</clause>

<clause id="_009bf7b7-1664-bdb5-7ae4-6fc5e78db731" obligation="normative">
<title id="_837441cf-4c6f-dbf4-2610-6ad28df18a08">Punctuation mark in scripts, languages, and locales</title>
<ul id="_f2ff8251-7c93-dc11-c6b7-662435fd3642"><li><p id="_c252c701-3d59-6c6c-d7a4-724b0a378f02">Latin, Cyrillic: Good typography expects MATHEMATICAL LEFT ANGLE BRACKET <tt>&lt;⟨&gt;</tt> (U+27E8), MATHEMATICAL RIGHT ANGLE BRACKET  <tt>&lt; ⟩ &gt;</tt> (U+27E9) for mathematical and normal text usage. In informal usage, and in many formal notation schemes such as computer programming, LESS-THAN SIGN  <tt>&lt;&amp;#x3c;&gt;</tt> (U+003C) and GREATER-THAN SIGN <tt>&lt;&amp;#x3e;&gt;</tt> (U+003E) are used instead.</p>
</li>
<li><p id="_cb978044-bd1b-f8cc-6087-d78577c5aef6">CJK: LEFT ANGLE BRACKET <tt>&lt;〈 &gt;</tt> (U+3008), RIGHT ANGLE BRACKET <tt>&lt; ⟩ &gt;</tt> (U+3009).</p>
</li>
</ul>
</clause>
</clause>
</clause>

<clause id="_824c7693-962a-89be-7700-e715d6accdfd" obligation="normative">
<title id="_c3cf656e-ddd9-7e3f-097b-05f24b494673">Semantic identification</title>
<clause id="_934dbb3c-c9d7-b945-639a-db2f5281b06a" obligation="normative">
<title id="_2ba2f2b6-9869-8a71-fc35-752cd3796612">General</title>
<clause id="_e5997a1d-9e0b-15a2-4c3e-3c2fda2e9335" obligation="normative">
<title id="_6cceba62-47e4-dc3e-0642-d2eecc6ecc70">Primary function and purpose</title>
<p id="_7a687220-92c7-a28c-c032-7e152ca2cbca">Semantic identification punctuation identifies a span of text as conveying a specific semantics, as distinct from the structural information conveyed by punctuation marks in the foregoing usage categories.</p>
</clause>

<clause id="_c369ef56-dd9f-9362-a6a7-c73e5f77c6ce" obligation="normative">
<title id="_8fe7ac0d-e803-86c6-3c5f-5ea0a9821369">Range of semantic functions</title>
<ul id="_7bed3bad-a670-9cad-74fb-46763abe27ab"><li><p id="_24d5f30f-3063-782c-b232-334d5e822685">Semantic identification overlaps routinely with emphasis marks (<xref target="emphasis-mark"/>), and with quotation markers (<xref target="quotation-marker"/>).</p>
</li>
</ul>
</clause>

<clause id="_070328ff-4bbf-77ae-20c3-28b5b8a9f28f" obligation="normative">
<title id="_318423e1-cf61-f156-a929-bf57a60e0f00">Punctuation mark in scripts, languages, and locales</title>
<ul id="_58c1f216-587e-7ea2-a610-79a51bf716f5"><li><p id="_13ed2671-7bd0-0999-0f07-b5c32ca5bd79">Latin, Cyrillic: Punctuation marks for most semantic identification, other than abbreviation marks, are not used in contemporary Latin and Cyrillic practice—although number marks were commonplace in ancient and mediaeval versions of those writing systems.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_6f0e1da4-9e9f-8fd0-301b-881ace42ca0d" anchor="abbreviation-mark" obligation="normative">
<title id="_6606ac78-8767-88c8-1a4e-b3619fdf4e99">Abbreviation mark</title>
<clause id="_742c2f56-fb9f-7596-72e6-b2ddf6a7e3bc" obligation="normative">
<title id="_73601948-366a-5fd4-13a5-1515e8ad1482">Primary function and purpose</title>
<p id="_f302be34-7839-fe68-d59d-4b6f627e4ad8">Abbreviation marks are used to indicate that a word is an abbreviation of another word, and is to be understood as such rather than as a phonetically intact word.</p>
</clause>

<clause id="_c5c41e78-9410-d559-811a-41acc9787610" obligation="normative">
<title id="_ef90d744-6825-d6b6-14b0-14e765b92992">Punctuation mark in scripts, languages, and locales</title>
<ul id="_fa4b72cf-1a51-6832-8394-8edf35a4b4df"><li><p id="_6a894deb-2560-6cf0-231c-49a728767a40">Latin, Cyrillic: the usual abbreviation mark is the period.</p>
<ul id="_fa2086b3-fb47-c3ba-8250-50170243f65f"><li><p id="_c7fb3458-971c-50e7-6b98-f6d9a391aa2f">The ambiguity of abbreviation mark and declarative sentence stop (<xref target="declarative-sentence-stop"/>) is particularly pernicious, and is a pressing issue for Metanorma converting between Latin and CJK punctuation.</p>
</li>
<li><p id="_adf3e609-74f8-d08f-bbdd-cf11bff48601">The slash, SOLIDUS <tt>&lt;/&gt;</tt> (U+002F), is used for some abbreviations in English, especially involving initials of separate words or morphemes (<em>w/o</em> = “<strong>w</strong>ith<strong>o</strong>ut”)</p>
</li>
<li><p id="_8969dcf1-283b-2aab-7eba-95bb5ce9ab0a">The apostrophe, as an elision mark (<xref target="elision-mark"/>), is also used in some abbreviations: <em>gov’t</em> &lt; <em>government</em>.</p>
</li>
</ul>
</li>
<li><p id="_fb60f1d8-33a4-5e38-1bd1-043eae3ebe0a">CJK: while CJK languages do form truncated expressions (e.g. <em>Běidà</em> 北大 for <em>Běijīng Dàxué</em> 北京大学 “Peking University”), abbreviation marks are not used explicitly.</p>
</li>
</ul>
</clause>

<clause id="_5ed7aa3c-547a-f438-0458-cde565118ba1" obligation="normative">
<title id="_312abc3c-320e-c950-d5ae-be758f51dc2d">Spacing rules</title>
<ul id="_972e6f8e-ac39-650f-c03f-1dc8c0c4b190"><li><p id="_37f894de-2f72-65b6-033d-413310c86bed">There is variation as to whether an abbreviation of a multi-word phrase retains the spaces of its source phrase (<em>U. S.</em> vs <em>U.S.</em>).</p>
</li>
</ul>
</clause>

<clause id="_c650b2a5-5b91-21af-3eec-cecd63ceb234" obligation="normative">
<title id="_7d8a96ce-18bb-85e6-fe76-b7fc5104e91a">Special handling</title>
<ul id="_3fb7591d-873a-ca28-bf8d-05956c680e09"><li><p id="_ad85e880-07c7-ae6a-5837-e824229fbc2c">There is variation by language, style, and instance as to when to use the abbreviation mark, and whether to use abbreviation marks within an acronym (<em>N.A.T.O.</em> vs <em>NATO</em>, <em>etc.</em> vs <em>etc</em>).</p>
</li>
</ul>
</clause>
</clause>

<clause id="_5eb50acc-5df7-18d7-c0ea-52c270c3e000" anchor="elision-mark" obligation="normative">
<title id="_cc689f26-cd60-c046-91c1-5b2ad24de2d4">Elision mark</title>
<clause id="_ffb964f1-a687-1567-754e-4fa2a8b0b104" obligation="normative">
<title id="_0b1a8143-3c4b-ea1b-440c-8619e41fc691">Primary function and purpose</title>
<p id="_91494f08-8a93-d11a-8026-4d89fdd557a1">The elision mark is used to indicate that a word is derived from a word of the same meaning in an older, more formal or more standard version of the language, through the deletion of letters or numbers in the base form.</p>
</clause>

<clause id="_cbf04c4b-6788-fda2-74c5-c2d309bd1104" obligation="normative">
<title id="_b1987c96-95dc-27e1-9767-d15d0a180897">Range of semantic functions</title>
<ul id="_d142c534-22f8-84dd-94b5-a14b37d5074b"><li><p id="_ebb26e74-4b33-a4fe-fbb0-ae6f000e9fee">Letters may be deleted from the beginning, the middle, or the end of the base form.</p>
<example id="_45fa46ab-33de-5711-e19a-72b663538dc2"><p id="_3d8c4143-7633-148f-6d8f-ba72efb2074b"><em>’tis &lt; it is</em><br/> <em>shootin’ &lt; shooting</em><br/> <em>’n’ &lt; and</em><br/> <em>bo’sun &lt; boatswain</em></p>
</example>
</li>
<li><p id="_fba22533-8933-59c8-294b-f43969471549">Letters may be deleted from a single word derived from a phrase; the resulting word is called a contraction.</p>
<example id="_9473b191-4c8b-cfb9-330f-9baa9b4fb262"><p id="_c03e996c-3e8e-d304-689b-635404fb4e04"><em>isn’t &lt; is not</em><br/> <em>won’t &lt; woll not</em> (Middle English variant of <em>will not</em>)</p>
</example>
</li>
<li><p id="_4764b84d-0f05-8c7b-0ad1-88e9b76c49d1">Numbers may also be deleted, specifically in expressions for decades (this is an English-specific convention):</p>
<example id="_b53eb346-84fc-1290-ae0b-510bf28a60c9"><p id="_98d18d14-2702-30b5-1147-a7088109d1aa">’70s &lt; 1970s</p>
</example>
</li>
<li><p id="_9de52d89-85fe-74c9-7f3e-bfe75dce4b8a">Elision marks often differentiate colloquial forms from formal forms, and therefore words using elision marks are often avoided in formal style.</p>
</li>
<li><p id="_7af1f87d-6a69-a72f-76bb-8bbed722a14b">Elision marks prioritise the formal form of a language, deriving elided forms from it; that can make its use politically contentious, if the prioritisation of that form becomes controversial.</p>
<example id="_312c44da-8228-e96d-a9f9-d1577d2a8362"><p id="_b6ff9462-5ee1-2a0b-b4ef-a4f9a466584a">In the 19th century, Scots forms were derived from Standard English forms in spelling, using elision marks (e.g.  <em>a’ &lt; all, gi’e &lt; give</em>); this was rejected in the 20th century, as Scots was increasingly regarded as a distinct language from English (with the words now spelled  <em>aw, gie</em>), rather than as a corrupt form of London English; the older use of the elision mark is dismissed as the “apologetic apostrophe”.</p>
</example>

<p id="_b602f321-543f-52df-e56f-d2289deff0a5">A similar backlash has occured in the Anglosphere against other such transcription of non-standard English (“eye dialect”).</p>
</li>
</ul>
</clause>

<clause id="_974af0a2-d0da-450e-735f-4db05c05095b" obligation="normative">
<title id="_a8be9669-550c-21ee-3e6b-dd266d2d29bf">Punctuation mark in scripts, languages, and locales</title>
<ul id="_8c83e0e9-e3d8-027c-ead0-fdc8a7bab9f8"><li><p id="_2494b230-cce6-c48b-7e34-f8922840f452">Latin, Cyrillic: in fine typography, RIGHT SINGLE QUOTATION MARK <tt>&lt;’&gt;</tt> (U+2019) is used as the elision mark. In typewriter usage, which is inherited in online usage,  APOSTROPHE  <tt>&lt;'&gt;</tt> (+0027) is used.</p>
<ul id="_cb6affba-3d4b-c3d0-aadd-ee4b280779e6"><li><p id="_b1a58319-ca74-71c7-6b58-c22f3482ad07">Both forms of the punctuation mark are called apostrophe.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_46f3dd9c-ecaf-4643-b32c-8d919c404502" obligation="normative">
<title id="_95dbae96-a92f-1cc5-9db8-1dbbd5ef2b3b">Spacing rules</title>
<ul id="_76ee824d-539f-81f7-eabe-2b98d7701894"><li><p id="_fbfdba45-06c5-af38-fe29-31d3e561cbdc">There is variation as to whether an abbreviation of a multi-word phrase retains the spaces of its source phrase (<em>U. S.</em> vs <em>U.S.</em>).</p>
</li>
<li><p id="_d354c30f-c9db-da54-d4a1-68643a054578">There is no space before an elision mark in a contraction, even if the elision mark denotes the start of a new day (<em>it’s</em> &lt; <em>it is</em>.)</p>
</li>
</ul>
</clause>

<clause id="_a7a1c6bd-b215-b1cd-8505-9f5ca7cf8daa" obligation="normative">
<title id="_83c4e146-bcb3-c3e1-7e66-901c4e6311fd">Special handling</title>
<ul id="_0c1bbc23-dc5f-efe1-d460-068cdff79de9"><li><p id="_0c8ea267-f2d9-3211-8db8-db46d239cdc9">Data-entry of the straight APOSTROPHE character is automatically corrected by word processors to the curved RIGHT SINGLE QUOTATION MARK character. The conversion uses the identical mechanism as smart quotes for quotation marks (<xref target="single-quotes"/>).</p>
</li>
<li><p id="_9a24ef37-2c1f-b1ab-b928-26c9e877b6a3">The RIGHT SINGLE QUOTATION MARK punctuation mark is ambiguous between  a quotation mark and an elision mark, as indeed its Unicode name indicates. That means that initial elision marks are incorrectly corrected from the straight quote: it is treated as an initial quotation mark, and changed to LEFT SINGLE QUOTATION MARK, whereas initial elision marks are always RIGHT SINGLE QUOTATION MARK.</p>
<example id="_dece7b01-3a4e-8646-3de6-e61dab9d8576"><p id="_1fa6510d-06ca-092f-2843-e14e2f56db63"><tt>'n'</tt> (data entry)<br/> <em>’n’</em> (correct rendering)<br/> <em>‘n’</em> (incorrect smart quotes conversion, treating elision mark as quotation mark)</p>
</example>
</li>
</ul>
</clause>
</clause>

<clause id="_83103ff2-4bfe-edcd-9317-531c5d3a891e" obligation="normative">
<title id="_ffe69425-5b0f-47d1-f33c-0feb01473310">Cardinal number mark (out of scope)</title>
<clause id="_5ce48a2d-68c4-920d-1aef-357a566556ca" obligation="normative">
<title id="_769d2300-31c2-073e-1995-2b16230aedf4">Primary function and purpose</title>
<p id="_da0659b9-3e0f-7300-ca79-f976e563acc0">In writing systems where number symbols are ambiguous with letters of the script, it is routine to highlight the numeric use of letters to prevent ambiguity, through a cardinal number mark.</p>

<example id="_a00cbc18-d53f-20d5-0234-88acb74122b0"><p id="_549e7265-542a-e9ac-13eb-5f028838d6b3">Latin <em>VI</em> “by power”<br/> Roman numeral  <em>V͞I</em> “6”</p>
</example>
</clause>

<clause id="_c9f82ffd-37dd-0668-d2d5-31fa01598022" obligation="normative">
<title id="_6aa03774-652a-d614-0d77-97c837e75cc8">Punctuation mark in scripts, languages, and locales</title>
<ul id="_4495637c-8c25-cbfe-61f5-e3b2bba4bcb1"><li><p id="_6c5d3a36-f81d-f9d3-6bbe-ec75a3982c96">Hebrew and Greek have distinct cardinal number marks (<em>gershayim</em> and <em>geresh</em> in Hebrew, <em>keraia</em> in Greek), including disambiguating marks for counts of thousands (quote mark in Hebrew,  <em>lower keraia</em> in Greek) and for reciprocal fractions (double  <em>keraia</em> in Greek).</p>
<example id="_e35674b3-30da-0ee2-603c-47cb1ccfd2d9">
<name id="_1544a30e-23b2-58b9-dcd7-9124eaa1de37">Greek numerals</name>
<p id="_5622d092-f5a3-14ff-ecd1-7417823eea05">δʹ “4” (Greek letter delta, used as a number)<br/> ͵δ “4000”<br/> δ″ “1/4”</p>
</example>
</li>
<li><p id="_71ed69e4-a294-353e-6925-8f1b1b828bc6">Roman numbers used an overbar in antiquity to indicate that they were numbers; as it happens, an overbar (<em>vinculum</em>) was also used in the same period, to indicate that the number was to be multiplied by a thousand (so  <em>V͞I</em> was used for both “6” and “6,000”). The number mark is rare in contemporary usage of Roman numbers.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_609a307e-efcd-95e9-5a3a-4a76684f0e0c" obligation="normative">
<title id="_a28ee0e7-007c-bb2b-c157-02ffe130c714">Ordinal number mark (out of scope)</title>
<clause id="_3defe02d-c0b5-d487-b956-a9090b53c3f1" obligation="normative">
<title id="_b86844f0-3959-9edc-b334-6662d33f929c">Primary function and purpose</title>
<p id="_941c2c77-41bd-4402-65b3-80ef2264408b">In some languages, ordinal numbers are preceded by a mark indicating that this is an ordinal, and which is often derived from an abbreviation of the spoken word for “number”.</p>

<example id="_7a44a160-931d-98de-64f5-30fb9733702f"><p id="_b0d730e8-1490-9604-39eb-6eba2efd54fa">№ 29 Acacia Rd<br/> #29 Acadia Rd</p>
</example>
</clause>

<clause id="_ab070af2-9093-0451-f1cc-4181ecdb82e4" obligation="normative">
<title id="_9697f7ea-f621-f51c-d355-bafc22372a8d">Punctuation mark in scripts, languages, and locales</title>
<ul id="_1f9edc94-7683-7056-dd6f-7ca4e808483f"><li><p id="_2f63e77a-6409-a971-feaa-2aa7dfa2da94">In Romance languages such as French and Spanish, an abbreviation of a word for “number” is used, usually an abbreviation of Italian  <em>numero</em>. In French and Spanish, this is <em>n<sup>o</sup></em>, with the <em>o</em> superscript. In British English,  <em>No.</em> is used. In German, <em>Nr.</em> is used. Such abbreviations are not to be regarded as punctuation.</p>
<ul id="_81bf609f-d886-2534-e699-62e125cfcc56"><li><p id="_3764145e-8c63-c9d0-3bc8-325371327124">In informal use in the French- and Spanish-speaking world, DEGREE SIGN <tt>&lt;°&gt;</tt> (U+00B0) is used, as a truncation of <em>n<sup>o</sup></em>.</p>
</li>
<li><p id="_d5750755-473f-cf34-4303-68820416b1f1">Some languages, such as Portuguese and Italian, use the masculine ordinal indicator <tt>&lt;º&gt;</tt> (U+00BA) instead of a superscript <em>o</em>.</p>
</li>
</ul>
</li>
<li><p id="_accc7328-452a-8a26-4ab2-e996aff733fd">The number sign NUMERO SIGN <tt>&lt;№&gt;</tt> (U+2116) is very common in use in Russian and Bulgarian; it is derived from the Latin script abbrevation.</p>
</li>
<li><p id="_d1c5bffb-9772-07ba-c43e-2894833f9525">In American English, NUMBER SIGN <tt>&lt;#&gt;</tt> (U+0023) (hash) is used.</p>
</li>
</ul>
</clause>

<clause id="_ca2dd256-8e5f-816a-7761-42ca4384c186" obligation="normative">
<title id="_3b083d2a-b1e0-f9e9-4474-60b337ce8b1e">Spacing rules</title>
<ul id="_be090005-78e9-2604-6bc4-ae069bc5cde3"><li><p id="_ad4c8949-4c9b-475a-18a5-f84ef50d87ce">The abbreviations of “number” and their derivatives, including the Numero sign, are followed by space.</p>
</li>
<li><p id="_0a975393-0d2c-bf2a-d787-a885c22e22c9">The number sign (hash) is not followed by a space.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_d3062bf9-6ad3-6b0c-b67b-a03496eaab49" anchor="title-mark" obligation="normative">
<title id="_36a6d44e-5b75-a567-fc12-146934ee1c36">Title mark</title>
<clause id="_688c7804-3856-c56b-b5ae-2c089fe34124" obligation="normative">
<title id="_cfc03a03-e64c-7319-dcdd-12905e2665ef">Primary function and purpose</title>
<p id="_551aa3ea-8a78-8f35-f9d9-619baaee27d7">The title mark is used to indicate the title of a document. This is a core function in bibliographic rendering, but it is also applied outside of formal bibliographic rendering, in running text. This function is represented in Metanorma i18n files as  <tt>punct.open-title</tt> and <tt>punct.close-title</tt>.</p>
</clause>

<clause id="_7bc37217-1e34-b2f6-d8ca-c0e56fc8001c" obligation="normative">
<title id="_9e9e76c5-935c-a8f5-6a66-1bb3c3ac2bec">Punctuation mark in scripts, languages, and locales</title>
<ul id="_bd68939a-d171-edd8-c219-c1a9e1d8fcf3"><li><p id="_52d257e0-f1a9-811a-2bef-9cc3c8d4e4c0">Latin, Cyrillic: this is by default handled through italics rather than a punctuation mark. Quotation marks are often used instead, although in more formal referencing, quotation marks are used as secondary title marks instead.</p>
</li>
<li><p id="_3c9fc402-35d3-0a05-bd3e-b1870aa92a46">Traditional Chinese: WAVY LOW LINE (U+FE4F) is used as official title markup, particularly in texts that also use the proper name mark.</p>
<ul id="_c5b5807f-b75f-8537-c1b8-81dcc55d126f"><li><p id="_ab77dddd-74b1-131f-69e0-bbed1ecdf74a">Square brackets 【】and double quotation marks『』are also used.</p>
</li>
</ul>
</li>
<li><p id="_39b62d48-edd1-f654-4071-6b302e58006d">Simplified Chinese: uses《…​》for titles.</p>
<ul id="_9793aef0-753f-fe21-4a75-18a4019a2496"><li><p id="_e1c9e884-bb11-5f78-253a-f785b2ace0fb">Square brackets【】and double quotation marks『』are also used for song titles.</p>
</li>
</ul>
</li>
<li><p id="_09396b45-e3d2-4aba-41c4-412eb2150b46">Japanese: 『…​』(double quotes) are used for book titles.</p>
<ul id="_3af0d43d-db76-61d5-f489-8a177624528d"><li><p id="_1f8339cb-f41c-70e4-bec2-0dfdc70aa092">Western quotes are unofficially used in press for titles in Traditional Chinese, Japanese, and Korean.</p>
</li>
</ul>
</li>
</ul>
</clause>

<clause id="_b7c09505-bd25-3d7f-f780-6f2042739f31" obligation="normative">
<title id="_7c63da48-7bc2-e72c-4f39-48668ffde84b">Special handling</title>
<ul id="_53787e13-e646-bb03-ccda-15950219e1b5"><li><p id="_28b44fed-ec08-92dc-3961-1075e549736f">The title mark is associated with the name separator (<xref target="name-separator"/>), to separate components of a bibliographic reference entry.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_4c00c3d9-cfaa-67cd-d825-0fede69d86b7" obligation="normative">
<title id="_7daa334e-d4ac-04f8-4fcd-ef6d208ff6df">Subsidiary title mark</title>
<clause id="_f79dee83-4593-c2b1-6463-f1455b807a3c" obligation="normative">
<title id="_3b67d680-56e3-f1c1-35e3-3c7ef870fd0f">Primary function and purpose</title>
<p id="_ce33fe0a-3584-670e-d5c6-5a878a86ea24">The subsidiary title mark is used to indicate the subtitle of a document.</p>
</clause>

<clause id="_5f255ec7-937f-1a54-fe65-af876a742b15" obligation="normative">
<title id="_e5c9155d-9ac7-9276-4032-99e099dc91ee">Range of semantic functions</title>
<ul id="_8ad25cbd-2787-be7c-e0b1-72ff7c570005"><li><p id="_042d6f06-f9fd-ba1d-4ed8-423272bd36fc">The title mark is associated with the name separator (<xref target="name-separator"/>), to delimit titles from subtitles.</p>
</li>
</ul>
</clause>

<clause id="_97a75054-0e65-cf0f-bc75-f72284622b49" obligation="normative">
<title id="_c9431b44-2bc4-364d-8972-d71f407cadbb">Punctuation mark in scripts, languages, and locales</title>
<ul id="_20ed34e6-35ad-ab6c-d516-66c079a6999b"><li><p id="_4edb0912-63b9-72d0-47b9-9055c7217625">Latin, Cyrillic: subtitles are not marked up as a separate span from titles, and Western script referencing relies instead on the name separator to differentiate titles from subtitles.</p>
</li>
<li><p id="_d1af179b-e90e-3ed9-dac8-5391988a0890">Japanese: WAVE DASH <tt>&lt;〜&gt;</tt> (U+301C) can be used to mark subtitles: 〜概要〜</p>
</li>
</ul>
</clause>
</clause>

<clause id="_b8a3c991-7d86-42f4-9e40-a3b9689fdae1" anchor="secondary-title-mark" obligation="normative">
<title id="_f0c271f7-82ee-c0a2-faea-e4daf34175a1">Secondary title mark</title>
<clause id="_790b813e-a21d-d6d3-4a03-99b080f7c6c4" obligation="normative">
<title id="_4663ddb3-cd69-bad5-d793-a37d362af3d3">Primary function and purpose</title>
<p id="_40dc238a-97cc-b35a-fa9f-58afa801224c">The secondary title mark is used to indicate the title of a subsidiary document in bibliographic referencing. This applies to article and chapter titles, as distinct from book and journal titles. This function is represented in Metanorma i18n files as  <tt>punct.open-secondary-title</tt> and <tt>punct.close-secondary-title</tt>.</p>
</clause>

<clause id="_598a6953-632f-26b4-f4f1-19d7d48e61e6" obligation="normative">
<title id="_58781266-420e-a03a-9a09-d9fa6f25ca3f">Punctuation mark in scripts, languages, and locales</title>
<ul id="_2c23ea32-2651-69e7-c0bb-61cd2c3b7ff5"><li><p id="_177fb578-8146-9793-6d78-3a11aeadb0d9">Latin, Cyrillic: this is by default handled through quotation marks.</p>
</li>
<li><p id="_f35693e3-81f0-359d-2c19-851ddcf0bea4">Traditional Chinese, Simplified Chinese: Single title marks 〈…​〉() are used for article and chapter titles (LEFT  ANGLE BRACKET  <tt>&lt;〈&gt;</tt> (U+3008) and RIGHT  ANGLE BRACKET <tt>&lt;〉&gt;</tt> (U+3009).)</p>
</li>
</ul>
</clause>
</clause>

<clause id="_5de77c5a-6ada-9273-f62f-eb1a015eff09" obligation="normative">
<title id="_646087f6-f4f8-9c26-1661-881262adeaf9">Proper name mark</title>
<clause id="_e08f47ed-a4c6-dbf8-16bb-bffc79c83135" obligation="normative">
<title id="_cebb60e1-7fb0-ea41-895e-50413b3684e4">Primary function and purpose</title>
<p id="_4bc94f33-3383-ff1d-e47f-b16b7faff1a8">The proper name mark is used to indicate a proper name within a document.</p>
</clause>

<clause id="_3d5dcb9c-b705-b5f5-f1c4-56ebe7f657f1" obligation="normative">
<title id="_b75785c7-55c2-c744-cf8a-afbb08aceff6">Range of semantic functions</title>
<ul id="_0b95dc59-f2c1-71b2-570a-f599fa08688e"><li><p id="_f7df81b9-5845-fb17-5521-fdfdab19367f">Writing systems can use the name separator instead (<xref target="name-separator"/>), to differentiate names from surrounding text.</p>
</li>
</ul>
</clause>

<clause id="_fdb205e2-8eba-ba3d-2499-b54e36e72b72" obligation="normative">
<title id="_7dfd661c-8e78-6892-2cd8-592d9e4bd43d">Punctuation mark in scripts, languages, and locales</title>
<ul id="_fad4d358-bb55-6bb9-0582-9c7328ae7440"><li><p id="_129eabf5-9ff2-9862-b27b-8bb7eea8c7e4">Traditional Chinese: an underline is occasionally used, in didactic and ambiguous contexts (teaching materials, movie subtitles).</p>
</li>
</ul>
</clause>
</clause>

<clause id="_8c734044-8565-8dfd-194f-a3e10f3661d0" obligation="normative">
<title id="_7ba2374a-8ace-6362-1d2a-e2493a2b152c">Clause mark  (out of scope)</title>
<clause id="_45f76f65-0e46-cf00-5552-fb1a8282af9c" obligation="normative">
<title id="_f313679d-3390-ec03-e53f-d1201816b606">Primary function and purpose</title>
<p id="_1e111c99-3e37-eb32-d37f-3f55a2184db2">A clause mark is used to indicate that an identifier is a cross-reference to a clause in a document.</p>
</clause>

<clause id="_969f20cf-19a2-6cd0-eaec-037772b19410" obligation="normative">
<title id="_28a45ac5-53fa-e003-6659-4ebd186bec14">Range of semantic functions</title>
<ul id="_03f99d6e-deed-4529-cac4-b7f38f4c429c"><li><p id="_b5d39681-f8f7-7d1c-8233-f4d185476898">Use of the clause mark is now infrequent outside of legal documents, with the word for “clause” typically supplied instead. In ISO documents, a dot-delimited numeral on its own (i.e. featuring an &lt;identifier-divider&gt;&gt;) is understood to be a clause reference, without an explicit indication of the cross-reference scope (“clause”).</p>
</li>
</ul>
</clause>

<clause id="_2fd1c91d-3059-4114-1ab3-563d2f16d3c8" obligation="normative">
<title id="_96f40ce8-32ee-4bda-ba90-182929b4b844">Punctuation mark in scripts, languages, and locales</title>
<ul id="_66b58abf-b619-d163-4d8d-cff543ddd6c1"><li><p id="_2ced5405-60cc-7c6c-f002-e93c5676a5c4">Latin: SECTION SIGN <tt>&lt;§&gt;</tt> (U+00A7)</p>
</li>
</ul>
</clause>

<clause id="_a9607872-d9fc-f473-3d17-0458648bbdd5" obligation="normative">
<title id="_e6b5a58e-bd46-f37c-8137-b53c5187071a">Spacing rules</title>
<ul id="_68961372-b569-c57e-28d0-4f4ff0e587c7"><li><p id="_b1a52bb9-98b6-2180-0b23-b1926e0255e3">The clause mark is linked to the following identifier with a non-breaking space.</p>
</li>
</ul>
</clause>

<clause id="_23fb2d72-a580-a52f-2b00-b13326c23640" obligation="normative">
<title id="_422ddd53-3fba-9136-e379-41b0d28f15cf">Special handling</title>
<ul id="_d2636138-1119-e286-76e5-f6b28a2edabb"><li><p id="_a6e80fdc-db97-a248-fff0-3c7f981c6d20">When multiple clauses are referenced, the section sign may be duplicated: “§§ 13–21”. This is analogous to cross-reference abbreviations of reference locality types, such as “pp.” for “pages”.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_d83b5006-dbdd-43a1-8abc-3d3f2e4388ea" obligation="normative">
<title id="_a6957cb1-0cac-59b0-4804-bd063f786c0a">Paragraph mark (out of scope)</title>
<clause id="_f475514b-1836-5ba2-3d95-4ed722110155" obligation="normative">
<title id="_108ad07b-fd9d-3a8f-6d1c-f4c59aa8fcdf">Primary function and purpose</title>
<p id="_8e69c098-2676-4800-748e-a42a8dc4acf8">A paragraph mark is used to indicate that an identifier is a cross-reference to a paragraph in a document.</p>

<example id="_154e8fd1-29eb-493d-6c5c-2ec03112ac06"><p id="_6e68d8e6-74d0-74b5-bbc7-9bf280c78749"><em>17 U.S.C. § 411 ¶ 5</em> “Title 17 of the United States Code, section 411, paragraph 5”</p>
</example>
</clause>

<clause id="_78c5ee53-6689-347d-ea59-75cd67cabe6f" obligation="normative">
<title id="_8737c775-9887-b7dc-3025-ce71dbf2f30b">Range of semantic functions</title>
<ul id="_6aa33b35-3468-5314-37b8-da73cd2fd159"><li><p id="_453ba27a-f39d-f8f5-3960-ad218c071f96">Use of the paragraph mark is infrequent outside of legal documents, with the word for “paragraph” typically supplied instead.</p>
</li>
<li><p id="_cb602903-19bc-cd94-a9ed-abeab47f830a">There is limited use of the paragraph mark to represent carriage return at the end of a paragraph, or the concept of a paragraph: that use is not properly punctuation.</p>
</li>
</ul>
</clause>

<clause id="_7c1593b4-dd35-5e1f-60ca-7acb448ac12f" obligation="normative">
<title id="_c2718a4e-e0e4-3453-fb8b-78c569e27d69">Punctuation mark in scripts, languages, and locales</title>
<ul id="_88ffc6df-83eb-41af-1cfb-efdb667d7115"><li><p id="_18101e5e-eda2-2614-e205-7ddbd6193712">Latin: PILCROW SIGN <tt>&lt;¶&gt;</tt> (U+00B6).</p>
</li>
</ul>
</clause>

<clause id="_9c2c0d05-d3e9-7cd6-b16a-da69d65fb5e5" obligation="normative">
<title id="_d86e82a3-7d8a-6f47-1e0a-86371f489f37">Spacing rules</title>
<ul id="_cc9c2221-076d-5ab5-7119-64e1be7b9a5f"><li><p id="_4edb3682-3ca3-a9f6-38af-51a8f0815161">The paragraph mark is linked to the following identifier with a non-breaking space.</p>
</li>
</ul>
</clause>
</clause>
</clause>

<clause id="_e901fbc4-7ccb-5652-f281-2d13e32cf03b" obligation="normative">
<title id="_142ef24a-a46f-e4e0-98d6-f23656bb23d7">Highlight markers</title>
<clause id="_d8d2a33f-2cc9-0159-6b6f-1f73ed3e4a61" obligation="normative">
<title id="_fa06c69a-5956-f331-574c-275a1d544266">General</title>
<clause id="_39306cd7-55b0-08d4-8db5-e499f3ba6626" obligation="normative">
<title id="_44f3643f-1393-a4c2-8b22-57462f5bc1c3">Primary function and purpose</title>
<p id="_145e621b-8268-dbd7-c166-1e3ec65105aa">Highlight markers highlight and draw attention to specific text elements through visual modification or annotation, for a range of functions.</p>
</clause>

<clause id="_7f1efdfe-66a5-6232-3d7e-1ae64c1c4a63" obligation="normative">
<title id="_954817f4-9bb2-306a-1945-20c04cc0bbb1">Range of semantic functions</title>
<ul id="_a3b52d10-9d2f-a95f-7314-8e101d140a3f"><li><p id="_005cefeb-8f43-a5f7-3561-188eca7f556e">The range of functions for which highlight markers are used is open-ended, and often overlaps with other semantic functions. This includes emphasis on the part of the author; emphasis on the part of a speaker in direct speech; use–mention distinction (so citation of words as subjects of discussion, as opposed to use of words in language); titles and names of entities; and foreign words.</p>
</li>
<li><p id="_600147ca-25c5-b8df-5a68-28f29b7f4a50">The extent of use of highlight markers varies by language and style.</p>
</li>
</ul>
</clause>

<clause id="_46da4a82-b572-25c3-10fe-eef318a0aa63" obligation="normative">
<title id="_712efdc6-1aa3-023f-d11c-22e9f4985e39">Punctuation mark in scripts, languages, and locales</title>
<ul id="_b105181c-23be-3b81-8b58-b7dca79d14de"><li><p id="_0aa9bacb-7120-8285-5f4c-81dc1c122f3e">Latin and Cyrillic do not use punctuation in this function, and resort instead to typographical styling, including italics, boldface, and underlining. These are not in scope of this framework, except where Metanorma needs to alternate between typographical styling in Latin/Cyrillic, and punctuation marks in CJK.</p>
<ul id="_b5bfb637-f0d1-964d-7208-bec64a316d55"><li><p id="_33d9bec6-97be-4ac8-4f70-54d746b93e0b">While some documents make meaningful distinctions between italics, boldface, and underlining, they are idiosyncratic to the document, and cannot be generalised readily. Italics is the default highlight marking device in English.</p>
</li>
</ul>
</li>
<li><p id="_58fa2868-12ff-9430-65bc-ee9acc039485">CJK does not use italics, although it does use boldface.</p>
<ul id="_c514613b-b623-a62d-18b3-86fe184187e5"><li><p id="_f508959f-514b-c366-11a1-4d1db5f03491">Instead of italics, CJK uses a range of explicit punctuation, including single or double quotes, brackets, lenticular brackets, or emphasis marks.</p>
</li>
<li><p id="_e750f392-903d-edb0-0ef5-a91372557800">For example,  Japanese uses lenticular brackets in dictionaries for quoting Chinese characters and Sino-Japanese loanwords.</p>
</li>
</ul>
</li>
</ul>
</clause>
</clause>

<clause id="_b605e1f9-cc5a-7c4a-315b-dcc8b6c965cc" anchor="emphasis-mark" obligation="normative">
<title id="_ac21e202-110d-5494-9968-073d63feb647">Emphasis marks</title>
<clause id="_c4888aef-6be5-6e9d-bd42-cb3916be5643" obligation="normative">
<title id="_cab11c86-9635-2140-4aad-980cad14a398">Punctuation mark in scripts, languages, and locales</title>
<ul id="_5e0b4be9-631f-3c23-73b8-3d4195b9986b"><li><p id="_0afcf358-f2b2-cbc9-7981-820f7016cbcc">CJK emphasis marks are a diacritic applied to every character in the text span to be emphasised. Chinese is usually restricted to using an underdot. Japanese uses a much wider range of emphasis marks: filled or hollow dot, circle, double circle, triangle, and “sesame” marks.</p>
</li>
</ul>
</clause>

<clause id="_499a16ad-885a-feda-9c35-05c26e48e62d" obligation="normative">
<title id="_f86e1f93-f822-ea07-af2e-c0a2ac952010">Special handling</title>
<ul id="_8d67ca22-3c60-8d51-04c6-6ff30f3fa8b2"><li><p id="_e2856bb3-4d91-b823-e7b2-10a4ca8a1966">While the underdot emphasis mark could be realised as a distinct Unicode character, CJK emphasis marks are treated in computer typesetting as markup. They are realised in CSS using the  <tt>text-emphasis-style</tt> attribute. This means that Western and CJK emphasis marks are both treated as markup rather than as punctuation.</p>
</li>
<li><p id="_d3f14155-9492-2036-a8b7-9e1fc692e348">CJK emphasis marks are rare online and unsupported in many Word processors. (Microsoft Word also supports a smaller range of emphasis marks in Japanese than does HTML CSS or XSL:FO.)</p>
</li>
</ul>

<admonition id="_8f0c0b7e-61f7-f7e4-6d8a-5ad3f1225036" type="tip"><p id="_34752414-09f1-2f94-2bfd-431cbd5883e2">Metanorma does not currently support emphasis marks. When it does, it will be as a discretionary expansion of  <tt>&lt;em&gt;</tt> markup in Semantic Metanorma XML.</p>
</admonition></clause>
</clause>
</clause>
</clause>

<clause id="_d9980ccb-c986-640b-a7df-84c5aca90a24" obligation="normative">
<title id="_a52b0392-b491-6bc5-429d-b135500b485f">Functions: other</title>
<clause id="_0ced139d-1eed-59d1-5c02-86211a996ea3" anchor="numeric-punctuation" obligation="normative">
<title id="_6d3ad7cb-cf84-36f9-c014-958fcb74a2d9">Numeric punctuation</title>
<clause id="_beaf1906-ea79-29be-84c9-dd0d582692f5" obligation="normative">
<title id="_16be971e-d27d-1ff2-fae8-7a298d9f42f2">General</title>
<p id="_e703f06f-5063-dbf0-5a0e-531888e03ae7">Punctuation used to convey different types of number overlaps with other punctuation discussed here; Metanorma handles it with distinct mechanisms (document attributes and  <tt>number:[]</tt> macro parameters: see  <link target="https://www.metanorma.org/author/topics/inline_markup/semantic-elements/#encoding-numbers-as-formulas">Metanorma documentation</link>). It is briefly outlined here for completeness, and to identify potential points of ambiguity.</p>

<p id="_7e3cc299-d622-ed77-8d57-7380a9aa9634">The punctuation used to convey different types of number also overlaps with some  symbols for mathematical functions (notably plus and minus signs); mathematical functions are out of scope of this framework.</p>
</clause>

<clause id="_fa02887a-7f33-b75a-90d3-9b66daaf014f" anchor="decimal-point" obligation="normative">
<title id="_56912707-3d45-054f-cbc4-69b953a1dfe4">Decimal point</title>
<clause id="_44e61421-36ec-93be-470a-a9325bf5c36c" obligation="normative">
<title id="_0c67f8de-c17f-10b0-cb6d-23f9cf2b5ec3">Primary function and purpose</title>
<p id="_e19c294f-ec99-df43-1f09-04ffd01adacb">The decimal point delimits integer and decimal portions of a number.</p>
</clause>

<clause id="_8b114270-6ec0-1d29-7e2d-959be655e322" obligation="normative">
<title id="_28c7ce68-e2ec-9f6b-1caa-1f773b0cd02f">Range of semantic functions</title>
<ul id="_81272044-8408-ced6-1573-26c223c6b0d6"><li><p id="_fb65ca1a-e28f-2e59-daa8-f3ecf8129b88">The decimal point is a special case of an identifier divider (<xref target="identifier-divider"/>).</p>
</li>
</ul>
</clause>

<clause id="_8ccf5c35-dcba-18b7-9394-fadcbf26fd30" obligation="normative">
<title id="_2f8599d5-2a2d-c6a0-e5f1-8e51a85c2e74">Punctuation mark in scripts, languages, and locales</title>
<ul id="_bb85d6e0-b366-2a59-296c-e94c696ae545"><li><p id="_c785730f-e81b-5447-cb5b-59377f427b43">Latin, Cyrillic: there is variation among Western script languages: the Anglosphere uses a period, while Continental Europe uses a comma. In the case of ISO, even English-language texts adhere to Continental norms in using comma as a decimal point.</p>
</li>
<li><p id="_c5ad4288-aff1-5cb6-cb1c-30ca5013cd3a">Traditional Chinese: the HYPHENATION POINT <tt>&lt;‧&gt;</tt> (U+2027) (interpunct) is used as a decimal point in Chinese numbers: 三‧五 “3.5”.</p>
</li>
<li><p id="_7ed1afeb-77ff-c694-faca-3b16bf15a059">Japanese: the same practice is followed, using the Japanese version of the interpunct, KATAKANA MIDDLE DOT   <tt>&lt;・&gt;</tt> (U+30FB): 三・一四 “3.14”.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_94e9683f-14ef-3354-852c-8b3546ece815" anchor="minus-sign" obligation="normative">
<title id="_fa5eff62-40c4-f03f-e6b3-393bbf626498">Minus sign</title>
<clause id="_c15b5acb-d774-ba0c-6925-6440ee0f2032" obligation="normative">
<title id="_9963f4a2-4e28-b943-6449-c085cda32cc3">Primary function and purpose</title>
<p id="_0430cb68-80b1-eb17-0b5e-a534c7f3c90c">The minus sign indicates negative numbers.</p>
</clause>

<clause id="_30465a18-adc7-4ac4-8e58-40b9e7e35bdf" obligation="normative">
<title id="_e02ec825-fba1-9532-ba23-dc09cc30525b">Range of semantic functions</title>
<ul id="_4e9326fe-9e61-ec2b-98c6-04014b2163c4"><li><p id="_e4e87169-5e0d-9ff0-fb94-985f8152a0d6">The same sign is used for negative numbers and for the arithmetic subtraction operator; the former is in scope of this framework, as negative numbers can appear outside the context of mathematical typesetting, inserted into normal text.</p>
</li>
</ul>
</clause>

<clause id="_a86e107b-05a0-4e1a-8195-5432f32d9079" obligation="normative">
<title id="_c4438a19-80d4-d366-6600-d0ae10524b1e">Punctuation mark in scripts, languages, and locales</title>
<ul id="_53759225-37ef-91da-2b19-919a79fcacad"><li><p id="_af7dcd07-c265-1836-894e-d9a2fc677bd3">Fine typography prefers to use the distinct MINUS SIGN <tt>&lt;−&gt;</tt> (U+2212) in mathematical use. Informal use uses HYPHEN-MINUS  <tt>&lt;</tt><tt>-</tt><tt>&gt;</tt> (U+002D).</p>
</li>
</ul>
</clause>
</clause>

<clause id="_24509521-4b83-152d-2201-e97823293930" obligation="normative">
<title id="_d763014a-716b-1a14-1d8b-faec03fd66e5">Ratio sign</title>
<clause id="_d7991b00-9930-b16e-5ef6-84f145fe11ed" obligation="normative">
<title id="_3ab6217d-3d8f-0d4a-075e-b60987b8add5">Primary function and purpose</title>
<p id="_43e7c087-510c-7509-485d-7d3170973895">Indicates a ratio or proportion of two numbers.</p>
</clause>

<clause id="_638ac85b-e914-9d0e-778c-f542b5401573" obligation="normative">
<title id="_40d53408-29ac-034e-dfc2-130451e697fc">Range of semantic functions</title>
<ul id="_ba3f515e-f8f7-213a-bf0e-fc73a7c0f132"><li><p id="_bb8e1b25-c833-fefd-bb4b-a1c12469ca10">The ratio function is a generalisation of both the fraction sign and the division sign in mathematics.</p>
</li>
<li><p id="_aee41785-460f-4201-b63d-f24c5cd53370">Proportions can include a proportion of completion, e.g. <em>Page 17/35</em>, indicating how many pages have been traversed out of a total of 35.</p>
</li>
</ul>
</clause>

<clause id="_81dea2f5-b0fb-b80c-c276-d59dedb2d940" obligation="normative">
<title id="_dce4fd43-bb15-142a-f110-ee2a57b1a184">Punctuation mark in scripts, languages, and locales</title>
<ul id="_f8650c85-b6d9-b196-b56c-92ac6eb62d9e"><li><p id="_b8033f89-d8d3-d1dd-e4d6-e3408c9767a7">In English, both colon and slash are used: <em>1:7</em>, <em>1/7</em>.</p>
<ul id="_f227fb11-1a41-6025-0524-570bf649e656"><li><p id="_574c61b3-bd51-215e-43d6-fe326c598141">Unicode differentiates the FRACTION SLASH <tt>&lt;⁄&gt;</tt> (U+2044), the division sign DIVISION SLASH <tt>&lt;∕&gt;</tt> (U+2215), and the non-mathmetical use of slash.</p>
</li>
</ul>
</li>
</ul>
</clause>
</clause>

<clause id="_64da1697-f84a-12c6-bdc8-06ba9bf9e8b2" anchor="approximation-sign" obligation="normative">
<title id="_dcc9697a-0a95-5dac-8bce-f3053ca7d796">Approximation sign</title>
<clause id="_2b547920-241f-d887-5aa3-0f1f44a8112c" obligation="normative">
<title id="_f0be1d58-58ee-3fb6-9e23-b5ea9afe5fbe">Primary function and purpose</title>
<p id="_bf27c984-aa6a-71c0-c002-88f082575de9">Indicates that a numeric value is approximate.</p>

<example id="_b1801e41-dae9-ede1-cb94-75cb9197c44c"><p id="_4b5f1aba-e343-004f-c63d-e0d82f7d11e9">~40 metres</p>
</example>
</clause>

<clause id="_8a6d865b-cded-01a0-ca44-94fa0266ce63" obligation="normative">
<title id="_496721d7-1c22-58c8-f0b5-9a7abcadcb91">Punctuation mark in scripts, languages, and locales</title>
<ul id="_2e92c651-9bdf-3d6f-2502-526656c3066b"><li><p id="_1618e028-1a08-8f1e-4dd6-235115b07ad6">TILDE <tt>&lt;~&gt;</tt> (U+007E) is used by default</p>
<ul id="_e65ef80b-78c2-e4df-c0af-6d2093bfbbba"><li><p id="_887cc446-4c49-8ee2-e7ce-bf6014e2ec99">Some languages such as French also use ALMOST EQUAL TO <tt>&lt;≈&gt;</tt> (U+2248).</p>
</li>
</ul>
</li>
</ul>
</clause>
</clause>
</clause>

<clause id="_ce01c0e7-b743-92ba-d382-44d25651dbf4" obligation="normative">
<title id="_f1572367-7687-72d0-9004-64086822df28">Miscellaneous</title>
<clause id="_a938cf72-77d4-8828-9941-0b4ad8bfa0b4" anchor="missing-text-mark" obligation="normative">
<title id="_a74e1d30-e9e9-44de-130e-1bf13cbdbd19">Missing text mark</title>
<clause id="_901a4750-f831-486d-16bb-316e814c4f14" obligation="normative">
<title id="_035063a8-b728-d01d-4a02-e4540bcd50f7">Primary function and purpose</title>
<p id="_92faa6bc-4f0f-9a0f-7188-f77e79546412">The missing text mark represents omitted text. This function is represented in Metanorma i18n files as  <tt>punct.ellipse</tt>.</p>
</clause>

<clause id="_7932b430-6534-4415-7a73-ad7ba26a984b" obligation="normative">
<title id="_f7f87390-4129-949c-f1a3-2fe4c7169925">Range of semantic functions</title>
<ul id="_3ab5059a-5f2e-88ad-60ff-a6e3995a2dfd"><li><p id="_5714b858-d9f8-18d5-95c6-8713374956f1">The ellipse is conflated with the hesitancy phrase separator (<xref target="hesitancy-phrase-separator"/>), but the two interact differently with other punctuation.</p>
</li>
</ul>
</clause>

<clause id="_0419ed48-7291-670f-25f5-9bcdabea0fa6" obligation="normative">
<title id="_24faaf89-8cb8-e749-45a9-8c2a0b55a5c1">Punctuation mark in scripts, languages, and locales</title>
<ul id="_a992a17f-005f-10ea-f3c9-f591f1e8d1e7"><li><p id="_68bdb89f-e9cd-e113-0e9b-f26c4eba9108">The same mark, the elllipse, is used as for the hesitancy phrase separator.</p>
<ul id="_7a1e1c71-8ddf-20f5-627b-77b0070c0af1"><li><p id="_b6fc49f9-ba2d-af86-e5a0-b0655b4a9262">Occasionally triple asterisks, <tt>&lt;* * \*&gt;</tt> or <tt>&lt;***&gt;</tt>, are used as an explicit missing text mark. This is done in some legal writing in English. In this regard, the missing text mark usually has scope at paragraph-level rather than sentence-level, and it is a variant of the section separator (<xref target="section-separator"/>).</p>
</li>
</ul>
</li>
<li><p id="_56d9a8bd-705f-49c7-c208-fac30f594642">When the omitted material is part of a word, e.g. out of religious or social taboo, or anonymisation, one or two em dashes are used traditionally. For taboo deletion, asterisk is also used; for more expressive or jocular deletion, a range of symbols is used.</p>
<example id="_902b2a11-f72a-d06d-7a5f-01b93268d804">
<name id="_ab710501-49d8-94b9-c172-7cf8be64c08a">Anonymisation</name>
<p id="_64b7558f-5a1e-89ef-bfef-5b42f3db6f75"><em>It was alleged that D—— had been threatened with blackmail.</em></p>
</example>

<example id="_58d51d49-bef8-f973-edf4-2f433e53e85c">
<name id="_4cbdf3bd-6b6f-956a-21e9-8a9a8db691bb">Religious taboo</name>
<p id="_d49442de-b72d-401a-9004-8660f773f212"><em>In the name of G–d</em></p>
</example>

<example id="_30a03ed3-f0a9-94c2-d04e-873eec068857">
<name id="_e6f88b90-c7a5-caa1-ba0f-7b05d20ded6d">Social taboo</name>
<p id="_5b081769-5e07-cd02-daf4-5104d8591aa7"><em>F—— you!</em><br/> <em>F*ck you!</em><br/> <em>F*@# you!</em></p>
</example>
</li>
</ul>
</clause>

<clause id="_a927e209-f735-b26b-c0b2-5d41a279e230" obligation="normative">
<title id="_ae029652-1026-f3cb-c72b-0a10ce265934">Spacing rules</title>
<ul id="_5688338d-c242-6fd3-52a6-6c1627150b8c"><li><p id="_e49ec0bc-715f-c01b-473e-a5a671685e48">When the missing text mark represents one or more missing words,  it is usually treated for spacing as a separate word, rather than as punctuation. Therefore unlike the hesitancy phrase separator, the missing text mark is preceded by space as a word separator, just as a word would. This extends to treating the missing text mark as a distinct sentence.</p>
<p id="_07240f1a-fc10-e52f-d3bf-3704238a2393">So British practice, as reflected in the <em>Oxford Style Guide</em>, has the hesitancy mark replace the sentence stop, but the missing text mark appear after a sentence stop. It also has space before both the missing text mark and the hesitancy mark.</p>

<example id="_75cde55c-ae3b-a31b-ef84-1a9c664bfc57"><p id="_4793a9e0-e31b-d5cc-a228-7c0d04f5878a"><em>The …​ fox jumps …​</em><br/> _The quick brown fox jumps over the lazy dog. …​ And if they have not died, they are still alive today.<br/> <em>It is not cold …​ it is freezing cold.</em></p>
</example>
</li>
<li><p id="_045240ac-7ed3-c938-3eb5-bcb95ca5b9ef">But as an illustration of the flux around spacing rules: the <em>University of Oxford Style Guide</em> (which applies to the university rather than to the commercial printer) requires no space around the missing text mark, and space after and not before the hesitancy mark:</p>
<example id="_1f18dfdf-e644-1439-2bc1-73ec24d53d2c"><p id="_6c6e69a5-4578-d10d-06d3-d39394a0868c"><em>The…​fox jumps…​</em><br/> _The quick brown fox jumps over the lazy dog…​And if they have not died, they are still alive today.<br/> <em>It is not cold…​ it is freezing cold.</em></p>
</example>
</li>
</ul>
</clause>

<clause id="_e071d2a8-589d-7f4d-0bb1-102200aa4d41" obligation="normative">
<title id="_0b3cc48d-6032-9429-ddcc-bfe1ac429abb">Special handling</title>
<ul id="_08dc0116-2368-2aa7-e32b-6a9c3ec64077"><li><p id="_b336b36c-eaae-3b63-ede7-6817c59c413e">The same special handling applies as for the hesitancy phrase separator.</p>
</li>
<li><p id="_afd42123-47cc-e6c4-286e-9d85d3f9768f">As a sign of editorial intervention, the missing text mark is often put inside brackets (<xref target="bracket"/>) in English, to make the editorial intervention explicit, and to disambiguate it from the hesitancy phrase separator. In Spanish, parentheses are preferred in that role.</p>
<example id="_df201208-4755-2936-d5b7-7e67a8b9d287"><p id="_6087d178-d651-7642-2458-ad22a48b821f">Original text: <em>The President said that, for as long as this situation continued, he would not be satisfied</em><br/> Reported text:  <em>The President said that […​] he would not be satisfied</em></p>
</example>
</li>
</ul>
</clause>
</clause>

<clause id="_8e47c5ec-7c9c-db8a-d409-9b2b794397b1" anchor="repetition-mark" obligation="normative">
<title id="_64ed0c46-cdb8-2018-5112-78f0b33b750c">Repetition mark</title>
<clause id="_f3278d5d-45db-5739-54dc-d5525bc7188b" obligation="normative">
<title id="_4bd818c9-7364-f5ab-1e6e-d1a9f72dbe5a">Primary function and purpose</title>
<p id="_9ec268b5-c99c-d0c6-a852-058495e17b72">The repetition mark indicates a place where text is repeated from a previous passage, and it is obvious visually what the repeated text is.</p>
</clause>

<clause id="_76035841-765f-4796-282c-302aa9839f52" obligation="normative">
<title id="_e203092e-2b6c-f14e-0634-fdfa149c76e5">Range of semantic functions</title>
<ul id="_632bbed6-0078-bde2-c8f3-b1b5e632f61f"><li><p id="_eedf045f-1ab5-9866-6330-1180d6c8729d">Repetition marks are infrequent in contemporary use outside of specific contexts, to avoid ambiguity. Space saving is not now as pressing a concern as it was in the past in texts.</p>
</li>
</ul>
</clause>

<clause id="_d93e4dae-f453-e925-119e-270993f1f38b" obligation="normative">
<title id="_da328b25-f21b-a567-e880-59f538c1c176">Punctuation mark in scripts, languages, and locales</title>
<ul id="_22a38486-0649-8988-6852-d381fbcf7f19"><li><p id="_ff6bfa31-c1cd-dc5e-c6c6-026416ca116c">English traditionally uses a ditto mark under each word to be repeated from a previous line; these can take the form of straight quotes, right smart quotes, or apostrophe.</p>
<figure id="_e2a71687-8f3a-6142-d4e4-642bda8c94ca"><pre id="_27831627-a4f7-358a-455f-a18729fdb8cf">Black pens, box of twenty ... $2.10 +
Blue  "     "   "  "      ... $2.35</pre></figure>

<ul id="_65dbf1da-e701-901b-13ba-7eb3beab39ad"><li><p id="_c5c03ed8-7136-0be5-4604-94f39c3f2452">In Quebec French and Greek, a right guillemet is used. In other European languages (e.g. Italian), a double prime is used; the English use of apostrophes is an approximation of this. In yet others (e.g. Swedish), the double prime ditto mark is set on the baseline, and surrounded by em-dashes.</p>
</li>
<li><p id="_9eb3180e-303d-1a42-c2b7-0bf68423dece">In CJK, DITTO MARK <tt>&lt;〃&gt;</tt> (U+3003) is  used.</p>
</li>
<li><p id="_3a583148-e36f-4a5d-658a-33603be81029">These are clearly visual variants of each other, that have been conflated historically with other punctuation in the same local writing systems.</p>
</li>
</ul>
</li>
<li><p id="_093d84ad-d238-7de1-ce5b-3914076d3693">In some citation conventions, if two consecutive reference entries in a bibliography have the same author(s), a repetition mark is used instead of repeating the author, consisting of two or three  em-dashes.</p>
<example id="_24d6026c-966a-f35e-16ed-4db89651cdab"><p id="_062ee082-7db5-c68b-fbac-1837f68c83b4">Smith, J. &amp; J. Doe. 1990. <em>The elements of style</em>. New York: Wiley.<br/> ——— 1991.  <em>The rudiments of style</em>. New York: Wiley.</p>
</example>
</li>
</ul>
</clause>
</clause>

<clause id="_a48fe026-0142-12a3-95b1-0047399b6afc" obligation="normative">
<title id="_d40d6e8c-1661-1098-a9e7-b8b1771a653a">Iteration mark</title>
<clause id="_34bb99e8-c68b-86ac-c09b-43d2ee1f72aa" obligation="normative">
<title id="_e60a884b-f94d-558a-bb25-1f1bd1a6f8c4">Primary function and purpose</title>
<p id="_95f521fc-e6e5-6cb3-ebd3-3d16c57526c0">The iteration mark indicates the repetition of a word or a component of a word.</p>
</clause>

<clause id="_7be021f1-a178-8081-fea8-bbf1d474b51e" obligation="normative">
<title id="_5d70584c-b90e-c4e5-fc48-63efa5cf95e3">Punctuation mark in scripts, languages, and locales</title>
<ul id="_b43609d4-18a1-e262-6b49-6704fbcd7fc9"><li><p id="_e6573e5d-f27c-2b22-248e-3c553ee6e32f">In Chinese, IDEOGRAPHIC ITERATION MARK <tt>&lt;々&gt;</tt> (U+3005) is used in casual usage to repeat a character, but is no longer used in formal usage.</p>
</li>
<li><p id="_f0f9e566-5cff-d4a8-5d8c-07cfb70cd564">In Japanese, IDEOGRAPHIC ITERATION MARK <tt>&lt;々&gt;</tt> (U+3005) remains in common use for repeating a single kanji, and follows different norms from the Chinese instance of the punctuation mark.</p>
<ul id="_0d650d4a-82f1-a142-8445-9d50c9304a0a"><li><p id="_56dc2ed4-2ef7-35cf-ea0c-7bc5e28748f6">Japanese also has repeat marks for repeating the preceding word or phrase of two or more characters: VERTICAL KANA REPEAT MARK  <tt>&lt;〱&gt;</tt> (U+3031) for exact repetition, VERTICAL KANA REPEAT WITH VOICED SOUND MARK <tt>&lt;〲&gt;</tt> (U+3032) for repetition with the first letter voiced. The repeat marks are restricted to vertical directionality, and are no longer in common use.</p>
<example id="_4eecaddd-6624-1306-6121-8a2f7dd85ffe"><p id="_7f72c22f-7578-660f-7cde-499481618cc0">ところ <em>tokoro</em> “place”<br/>ところ〲;  <em>tokorodokoro</em> “in places”</p>
</example>
</li>
<li><p id="_7ddf625b-fc85-61b4-af44-848ad27f60da">Hiragana and Katakana have distinct iteration marks. They are no longer in common use, but they still appear in names.</p>
<example id="_9483cf1d-0613-840d-f857-22b27c77fa32"><p id="_46bfe161-6629-ce9c-8f31-cf7fe6f4a4c9"><em>Isuzu</em> in Japanese is いすゞ, using a voiced iteration mark: I-su-{repeat, voiced}</p>
</example>

<example id="_2070d5c3-cc48-fc69-b1a1-f46221fda008"><p id="_b04db5ca-a2fc-ac71-7f7e-987ec747f4a2">Japanese Wikipedia refers to “heart” in Kanji: <link target="https://ja.wikipedia.org/wiki/%E5%BF%83">心</link>. Its Hiragana entry <link target="https://ja.wikipedia.org/wiki/%E3%81%93%E3%81%93%E3%82%8D">こころ</link> includes a dozen literary works titled  <em>kokoro</em> “heart”. There is a distinct reference <link target="https://ja.wikipedia.org/wiki/%E3%81%93%E3%82%9D%E3%82%8D">こゝろ</link> to the 1914 novel by Soseki; being a much older work than the others, it has retained the Hiragana repetition mark, “ko-{repeat}-ro”.</p>
</example>
</li>
</ul>
</li>
<li><p id="_59a38360-99ff-c843-192e-b176056e8f2a">Among Latin-script languages, a normal or superscript number <tt>&lt;2&gt;</tt> is used as an iteration mark in Filipino, Malay, and Indonesian, although in Indonesian this is no longer official practice.</p>
</li>
</ul>
</clause>
</clause>
</clause>
</clause>

<clause id="_f9d06f1f-84c1-e2b6-15b7-866f29dda005" obligation="normative">
<title id="_4732d283-d6a4-3e47-ea87-8b9f723ea532">Whitespace handling</title>
<clause id="_565949a5-1a87-f183-f933-5c8971c635e7" obligation="normative">
<title id="_d0fe7de5-6e1e-b142-ea53-7c3704ee5df1">General</title>
<p id="_a1b3895f-2ca2-fd85-1b1d-61c3c441e038">Rules about whitespace handling specific to various punctuation marks have already been given inline in the foregoing discussion. The following is general discussion about whitespace handling in paragraphs, and specific to CJK writing systems—which are in  <em>scriptio continua</em>, and rarely use whitespace at all typographically.</p>
</clause>

<clause id="_eb99cc3a-df7e-b3e7-46d9-3aec3bd422e2" obligation="normative">
<title id="_c395d6d0-dcc4-c396-c102-7d7c9aed94c2">Paragraphing</title>
<p id="_1e05d499-c7ad-ec79-4b0e-07f49fe23aa5">Paragraphs may be indented in Western typography. If they are, this done both in word processing and HTML as document configuration, setting the indentation of the first line in a paragraph, rather than by inserting a spacing character.</p>

<p id="_e622d708-cc14-6aef-09a4-c20f563150ff">In Japanese, it is common to indent the first line of a paragraph using a full-width space (U+3000).</p>
</clause>

<clause id="_5fe4aeed-7637-ef46-bfb4-a906090c281f" obligation="normative">
<title id="_9bfbc72e-df9c-d17e-46d4-0cea08b26781">Alternation between scripts</title>
<p id="_856eaf69-554f-e80a-9c5c-183f63a9141f">When alternating between CJK and Latin scripts, Chinese does not insert space at the boundary: it preserves the non-spacing nature of CJK. The word delimiter within spans of Latin text is still preserved. The same applies to Korean.</p>

<example id="_96ec4331-235d-dfc8-986e-c7433f29e2cb"><p id="_4b3758f4-a8a6-358f-749f-618d54aad4c9">她唱的I dreamed a dream(我曾有夢)，唱得肝腸寸斷 “She sang <em>I dreamed a dream</em>, so heartbreakingly”</p>
</example>

<p id="_1d8d6038-3d87-fab6-93bb-707eaa1ad46f">In Japanese, however, spacing is required at the boundary between Japanese text and Latin characters in fine typography. This takes the form of a quarter-em space (U+2005), and it applies to any Latin characters, including numbers, and even full-width punctuation marks that are not Japanese in origin, such as exclamation marks and question marks.</p>

<p id="_cc3ea482-159a-0251-0f57-235cb570c1c0">The whitespace to be applied between runs of CJK and Latin text can be configured in Metanorma i18n files, as  <tt>punct.cjk-latin-separator</tt>. In Chinese and Korean, it is set by default to the empty string <tt>""</tt>. In Japanese, it is set to <tt>\u2005</tt>.</p>
</clause>

<clause id="_2fcbdb07-6306-22f2-ff24-814b4203924f" obligation="normative">
<title id="_9aeb30ed-3114-069b-262e-49af5d2ab20c">CJK use of whitespace</title>
<p id="_4614c16c-7d19-1f31-6186-d04d1945e90f">In Chinese, use of full-width space (U+3000) is very rare, and is only used in specific contexts. For example, it is used as an honorific spacing preceding certain names (such as that of Chang Kai-shek in Taiwan).</p>

<p id="_a6b3d723-de4d-f658-108d-d4f90f06350b">Japanese uses full-width space (U+3000) more commonly, as an optional disambiguating word divider, especially in text that mostly consists of hiragana or katakana and not kanji. There is also some usage of full-width space as a name separator (<xref target="name-separator"/>).</p>
</clause>
</clause>

<clause id="_4f7964a7-6beb-26f3-e74f-1244ff5f2f18" obligation="normative">
<title id="_86f424ce-0c71-3bbc-3fe0-49b7f4197c61">Metanorma Implementation</title>
<clause id="_76e71b33-69bf-8f71-ebf2-da1cbeca90b7" obligation="normative">
<title id="_a8e27f1b-1bd5-7fa7-d824-b825e96c6247">Classes of punctuation localisation</title>
<p id="_cb088250-e8e9-195c-1d1f-f1f3b492c7d2">Metanorma applies different types of punctuation localisation in different contexts, which provide different levels of semantic context for the punctuation to be applied; the implemented approaches are described here. The approaches are liable to change in the near future, and this document was authored in order to provide a framework for such changes, improving the quality and consistency of punctuation localisation.</p>

<p id="_a0987ebf-6980-f2cf-717e-d35ad4e94ec9">The different approaches are, in order of increasingly rich semantic context:</p>

<ul id="_134c5ad8-fd48-83b2-ded0-84defae5051b"><li><p id="_aeec071e-2bfb-1e5e-7045-b595286415bf">Smart quotes translation</p>
</li>
<li><p id="_67fbb22f-37be-e679-291e-226057bd4802">Auto-text punctuation translation</p>
</li>
<li><p id="_978f4705-3e84-c593-3c2b-49a90ad4676e">Direct i18n configuration values</p>
</li>
<li><p id="_a4074519-eb96-dded-0860-55fb6d485fe4">Number localisation</p>
</li>
<li><p id="_a74e2d39-32b8-f121-7711-053127520bd9">Bibliographic punctuation</p>
</li>
</ul>

<clause id="_1d5e9b7c-57a6-d85e-4965-27f5733a2830" obligation="normative">
<title id="_ebc069ec-b8de-41d0-157c-d491797ad595">Smart quotes translation</title>
<p id="_60abac93-4e9d-918c-9fb5-966999a6b987">Like other word processing systems, Metanorma translates ASCII-based input of punctuation marks to Unicode-based punctuation marks as a post-processing step. While Metanorma input uses Asciidoctor, Metanorma does not use the native capability of Asciidoctor to do smart quotes translation; it instead does so at the end of Semantic XML processing, using the  <link target="https://github.com/pbhogan/sterile"><tt>sterile</tt></link> gem. This translation step is applied to all user-provided text in the document.</p>

<p id="_765efcd8-22b3-b05e-bd4e-cfcd66f98576">The main class of punctuation handled in this way is quotation marks; <tt>sterile</tt> has contextual mechanisms to differentiate between apostrophe as quotation mark and apostrophe as elision mark (left curly vs right curly single quote at the start of a word), and Metanorma adds to the configured contexts for translation (e.g. converting  <tt>'70s</tt> to <em>’70s</em>)</p>

<p id="_1337b1c9-302e-6a20-034e-d983eceb67a8">Metanorma implements the English smart quotes equivalents to the straight quotes <tt>'</tt> and <tt>"</tt>; for other languages, users are expected to enter the correct Unicode punctuation marks directly in the document, rather than expect Metanorma to translate the straight quotes correctly.</p>
</clause>

<clause id="_e555d5b8-2e0c-a108-3430-870ec01d8086" obligation="normative">
<title id="_2ce91dfe-82e6-c006-5840-677a72592297">Auto-text punctuation via <tt>l10n()</tt></title>
<p id="_2030f0e7-a8df-0ef0-ae17-82d3ad8a6b15">Metanorma implements a generic mechanism for translating text with English punctuation and spacing into other languages and scripts; as of this writing, it supports Simplified Chinese, Traditional Chinese, Korean, and French. This translation is done in the  <tt>Isodoc::I18n::l10n()</tt> function, implemented in the <tt>isodoc-i18n</tt> gem.</p>

<p id="_a955572a-ba23-51a5-1003-210856c20274">The <tt>l10n()</tt> function performs the following conversions:</p>

<ul id="_1793d85a-1ace-8333-4c63-27aa3fc0b395"><li><p id="_f0b5a464-c5ae-fcc4-1028-99747f22d72d">Introduce French spacing for French punctuation.</p>
</li>
<li><p id="_cba7724a-6335-9593-e380-146a394fd65f">Translate Latin punctuation to full-width CJK punctuation.</p>
</li>
<li><p id="_61f8b479-7d25-30ad-f04b-6c5c6524c393">Remove spacing between CJK characters.</p>
</li>
<li><p id="_ebe7d366-3ff8-b884-6f6a-bd5f34dd3fba">Introduce space between CJK and Latin text in Japanese.</p>
</li>
</ul>

<p id="_8b5fa354-8158-e0f9-f07d-a6883100d3c3">The text passed to <tt>l10n()</tt> is automatically generated text in Metanorma: this is for the most part document element captions and cross-references, such as “Figure 1”, “Table 2”, “Section 3.4”, etc. Bibliographic entries are also passed to  <tt>l10n()</tt>, to normalise their punctuation to language expectations. Such text is typically generated by templates, using Latin word delimiters and punctuation between template slots. Rather than define distinct templates for English, French, Chinese and Japanese, the  <tt>l10n()</tt> function allows the one template for auto-text to be applied to multiple languages.</p>

<p id="_98c35f42-bb11-2d48-04fe-a1869c42897f">The text passed to <tt>l10n()</tt> can be a string of text, or a fragment of XML. If it is a fragment of XML,  <tt>l10n()</tt> is able to traverse the XML tree, and identify preceding and following context in adjacent nodes, for the purposes of punctuation and spacing localisation. For example, in a fragment like—</p>

<example id="_064de45d-0347-bb48-f84b-4ec8f98c3d68"><sourcecode id="_62196d06-a61c-11d1-d118-2f0d18f9b35d" lang="xml"><body>&lt;p&gt;&lt;strong&gt;你想&lt;/strong&gt; &lt;strong&gt;去吗&lt;/strong&gt;
&lt;strong&gt;Do you want&lt;/strong&gt; &lt;strong&gt;to go&lt;/strong&gt;&lt;/p&gt;</body></sourcecode> </example>

<p id="_369bf4ce-e51e-e317-1c71-9af498ebaa6c">—the <tt>l10n()</tt> method  works out that the first space occurs between two spans of CJK text, despite them being inside XML elements, and  deletes the first space; it will leave the second space alone, because the method also works out that it occurs in a Latin text context.</p>

<p id="_00356237-41ff-5661-de5b-2fe04df8d04b">Often  the text entered into the template cells for automatically generated text is in Latin script, and must not be subject to the same localisation as the surrounding template; for example, a Japanese bibliographic citation may contain a Latin script author, whose punctuation should not be translated into Japanese.</p>

<p id="_a083d39e-87ae-0746-1687-b3a43389015b">(The particular problem with authors is the use of period as an abbreviation mark for initials, which should not be conflated with the sentence stop, and translated into fullwidth period:  <em>Simpson, W.</em> should not become <em>Simpson、W。</em> in Japanese bibliographic entries.) In order to prevent translation in a subspan of the string, that subspan is passed wrapped in  <tt>&lt;esc&gt;&lt;/esc&gt;</tt>.</p>

<p id="_f8de3e81-a939-351e-c74b-6982dfee422b">While this approach works some of the time, the ambiguity of English punctuation, well-documented in this framework, limits the accuracy of such mappings; occurrences of period are particularly fraught. The punctuation of normal English text does not contain all distinctions needed in other languages: the English comma, for instance, conflates the Chinese enumeration delimiter and the Chinese minor phrase separator.</p>

<p id="_be3a4077-b01e-ba28-e4c0-1102505fd918">This issue will be addressed in two ways:</p>

<ul id="_0882da57-c1e9-2e2f-3ddd-6b40f13033f9"><li><p id="_a8a89335-f509-c728-5990-65e9aa280134">Use of <tt>l10n()</tt> for punctuation translation will be reduced, in favour of the more well-controlled direct use of i18n configuration values: the correct punctuation for the language will where practical be looked up and inserted into the input string, so that the role of  <tt>l10n()</tt> is reduced to dealing with spacing rules.</p>
</li>
<li><p id="_db204dfd-209e-18e2-366a-5fae7386abcd"><tt>l10n()</tt> will reduce the ambiguity of its input by assigning only one semantic function to input punctuation. (So  <tt>&lt;,&gt;</tt> will never be interpreted as an enumeration delimiter.) Disambiguating punctuation markup may also be introduced.</p>
</li>
</ul>
</clause>

<clause id="_d6355059-472b-e4f2-59b3-8447ec2f2c5c" obligation="normative">
<title id="_405907de-c193-c15d-04fc-79cd8cbb3fd0">Direct i18n configuration values</title>
<clause id="_2b8d246d-fd9a-5c3c-57d6-cce04121a031" obligation="normative">
<title id="_c0bd1024-4d48-7ec1-1506-70be118498c6">General</title>
<p id="_2ba86ddd-5b40-64e4-9c2e-54e36763f24c">The internationalisation configuration files for Metanorma, managed in YAML format, include configuration values for punctuation marks, under the  <tt>punct:</tt> heading. These values can be invoked directly in the templates for automatically generated text, and filled in with language-specific values, matching the requested semantic function.</p>

<p id="_9052456f-afbd-2036-3f88-72f840c225f4">The configuration files are set globally per language in the <tt>isodoc</tt> gem; their values are overridden in the configuration for a Metanorma flavour (and/or a Metanorma taste), and can  optionally be overridden further in a configuration file supplied with the document. There is no mechanism for providing multiple configuration values for a document, and selecting which of the values to apply for a particular instance: once the overrides have been worked out, there is one configuration value applied per punctuation mark per document.</p>

<p id="_153d99cd-54cc-7f9b-9e89-dcf6e9e512f0">The overrides per flavour allow Metanorma to deal with SDO-specific alterations in punctuation; JIS for example uses punctuation more closely aligned with Western practice, whereas Plateau uses traditional Japanese punctuation.</p>
</clause>

<clause id="_c06d7bca-6ac6-9ca2-0974-43c51c30c75c" obligation="normative">
<title id="_0d7246f2-895c-04df-a3c2-0994e9dd2749">Configurable punctuation marks</title>
<p id="_0afd93a8-7491-83c4-a32c-53e1b32679aa">As of this writing, the following punctuation values can be configured in internationalisation files. While the names correspond to English punctuation marks, the intention of the configuration is to support punctuation semantic functions; the specific semantic functions involves are named in the foregoing.</p>

<ul id="_0bb8955f-4445-3e1e-dec3-2885f9eb9632"><li><p id="_3c58d329-f592-6b4c-2f01-a11dfb7129f1">colon (<xref target="introductory-phrase-separator"/>)</p>
</li>
<li><p id="_3109c171-c2b4-6960-1118-5a036e5e05e1">comma (<xref target="minor-phrase-separator"/>)</p>
</li>
<li><p id="_14c8a982-73c1-fba4-7470-c6f21e6fc58e">enum-comma (<xref target="enumeration-delimiter"/>)</p>
</li>
<li><p id="_9a430210-8a6e-f48d-b093-adad346f3583">semicolon (<xref target="major-phrase-separator"/>)</p>
</li>
<li><p id="_a9cb8988-0697-ef17-605d-d5f12703e8a3">period (<xref target="declarative-sentence-stop"/>)</p>
</li>
<li><p id="_650ca88c-a904-add9-9051-5a906f5a9629">close-paren (<xref target="parenthetical-annotation"/>)</p>
</li>
<li><p id="_6683759c-43d0-5f9f-f64f-de68e6e69bc4">open-paren (<xref target="parenthetical-annotation"/>)</p>
</li>
<li><p id="_2fcd5f23-e0fc-41c7-d936-0b51275f6b17">close-bracket (<xref target="bracket"/>)</p>
</li>
<li><p id="_ba371813-7f36-9052-a7b2-da8c451ee882">open-bracket (<xref target="bracket"/>)</p>
</li>
<li><p id="_398d68bd-c57b-7493-d266-37dfb2f5c11c">question-mark (<xref target="interrogative-stop"/>)</p>
</li>
<li><p id="_6934e5a7-9c4e-99bb-5d47-f0d7475d592e">exclamation-mark (<xref target="exclamatory-stop"/>)</p>
</li>
<li><p id="_05b5e7be-e534-211a-7567-18a10ad0eefb">emphasis-mark (<xref target="emphasis-mark"/>)</p>
</li>
<li><p id="_aed52df0-04ff-1af1-b0bf-0d88078f60c5">em-dash (<xref target="breaking-phrase-separator"/>)</p>
</li>
<li><p id="_a9694e38-ecf1-2c4c-9d18-d32fc9691187">en-dash (<xref target="range-mark"/>)</p>
</li>
<li><p id="_894f16a2-3874-db09-c440-5701b58fa300">number-en-dash (<xref target="range-mark"/>)</p>
</li>
<li><p id="_ee6cf740-8ec1-29a2-2456-d273a31509d3">open-quote (<xref target="paired-quotation-delimiter"/>)</p>
</li>
<li><p id="_629b7456-fa57-abbd-a9a3-64ea723e4006">close-quote (<xref target="paired-quotation-delimiter"/>)</p>
</li>
<li><p id="_14c9ce5a-1482-d089-a10d-676cd5ae6ac7">open-nested-quote (<xref target="single-quotes"/>)</p>
</li>
<li><p id="_f11bd899-6da3-8763-ca2a-a70170bb3197">close-nested-quote (<xref target="single-quotes"/>)</p>
</li>
<li><p id="_b57fb655-76b8-fcea-32e4-f31d57e42ac5">ellipse (<xref target="missing-text-mark"/>)</p>
</li>
<li><p id="_678948e8-7445-bfcb-deb0-deb09d6cea12">open-title (<xref target="title-mark"/>)</p>
</li>
<li><p id="_af480993-4bd8-868a-ec32-1655f662d24d">close-title (<xref target="title-mark"/>)</p>
</li>
<li><p id="_f6fc6013-4918-3eaf-d54f-f8967b4f5faa">open-secondary-title (<xref target="secondary-title-mark"/>)</p>
</li>
<li><p id="_1d14616c-2e16-2b83-8585-ecec10b2420e">close-secondary-title (<xref target="secondary-title-mark"/>)</p>
</li>
</ul>

<p id="_f507b9a2-0195-c9aa-d7b5-dab282f1e67b">A subset of the foregoing is be translated from Latin punctuation in automatically generated text, via  <tt>l10n()</tt>:</p>

<ul id="_d6636eb2-ddc2-1d74-dd08-c0249496b633"><li><p id="_0400dfc0-723e-5164-3f52-2c949d9a5efd">colon: <tt>:</tt></p>
</li>
<li><p id="_a9f6eef9-20ff-441c-8569-99c48a18d0e4">comma: <tt>,</tt></p>
</li>
<li><p id="_51bcdaf4-15f9-ea9e-4a58-aaab46e3ddc6">semicolon: <tt>;</tt></p>
</li>
<li><p id="_924d4f25-727a-b029-d173-95e53a33ce53">period: <tt>.</tt></p>
</li>
<li><p id="_a0cbb736-8615-b8d3-a246-cad8cf79181c">close-paren: <tt>)</tt></p>
</li>
<li><p id="_55610251-4cc9-d0bc-a89b-80b0571408b6">open-paren: <tt>(</tt></p>
</li>
<li><p id="_7c6b7200-6d69-c897-a325-59d3a958afd2">close-bracket: <tt>]</tt></p>
</li>
<li><p id="_523c1970-57ba-68a3-3ae0-28072fb88e16">open-bracket: <tt>[</tt></p>
</li>
<li><p id="_139641d0-ffc6-2db0-bd41-840491b8d8ad">question-mark: <tt>?</tt></p>
</li>
<li><p id="_cf255fab-c582-74e6-ddf9-34f6a7dfc343">exclamation-mark: <tt>!</tt></p>
</li>
<li><p id="_2b36b2fa-2085-bb62-6326-48e3c54faeab">em-dash: <tt>—</tt></p>
</li>
<li><p id="_483987c2-9e39-3d3e-4e15-3a89454d5d95">en-dash: <tt>–</tt></p>
</li>
<li><p id="_6baf6c0c-85a6-b993-4bd8-4ce649d392a1">number-en-dash: <tt>–</tt> (invoked depending on context — both surrounding characters need to be Unicode numbers)</p>
</li>
<li><p id="_7de26772-e858-80d3-0fd4-f2aa5723edfc">open-quote: <tt>"</tt></p>
</li>
<li><p id="_378c26c0-a144-5d3b-180f-cb2d587573c4">close-quote: <tt>"</tt></p>
</li>
<li><p id="_88694cd9-3673-ca80-04ac-7d6f007cccfa">ellipse: <tt>…</tt></p>
</li>
</ul>

<p id="_9ec63aef-f728-6a54-a1cc-e866a87eee32">In this list,</p>

<ul id="_d960ad49-d13e-8451-b02b-63124c1cafd5"><li><p id="_6a76e965-d82a-9d1c-0b07-8035fb7962be">Quotation marks are out of scope, because of the ambiguity of apostrophe, and the high variability of quotation marks between languages of  <tt>l10n()</tt> translation.</p>
</li>
<li><p id="_75e47e2a-aefa-bca6-c35b-04a3bd46cd84">Enumeration delimiters are not supported directly in <tt>l10n()</tt>, because of the ambiguity of the comma. They are handled instead through the  <tt>multiple_and</tt> i18n YAML value.</p>
</li>
<li><p id="_0f0cca00-0bac-b974-3d31-59d63c2659b0">Title marks require explicit semantics to drive them, which are not available in the <tt>l10n()</tt> context, and introducing them is deferred to bibliographic processing.</p>
</li>
</ul>
</clause>

<clause id="_1d6383c5-ae2b-961c-51c8-62d45dbdff44" obligation="normative">
<title id="_eeb82e78-d141-7d93-78bd-55a0054a50d7">Self-references in YAML configuration</title>
<p id="_afc55d60-442d-f10e-0e02-0abd2243008a">Values in the internationalisation configuration files can reference other entries in the configuration (including values overridden downstream), using the Ruby-derived syntax  <tt>#{ self.label }</tt>, where <tt>label</tt> is the key of the value to be referenced. These values can include punctuation. For example, the following is how a YAML configuration value references the current rendering of the enumeration comma:</p>

<example id="_e8548d2d-fce0-bc65-96b2-087ed0e36593"><sourcecode id="_07b0b65e-d55a-08bc-2983-4e487d8ba047" lang="yaml"><body>#{ self["punct"]["enum-comma"] }</body></sourcecode> </example>
</clause>
</clause>

<clause id="_4f3f5511-9473-cb01-3475-9c2ad0a10b2a" obligation="normative">
<title id="_3a38c07c-f76f-8772-c819-25ecf8a96f09">Number localisation</title>
<p id="_187bf72b-ac3a-c39f-0dcb-9366f5bbdb9d">Punctuation associated with numerals (<xref target="numeric-punctuation"/>) is handled separately from other punctuation, as part of the localisation of numbers in Metanorma, which separates the semantic value of the number from how it is rendered. This currently allows the decimal point to be configured.</p>

<example id="_99b2db9e-c83b-252e-e567-e8a02db82c4f">
<name id="_f07b7507-a2a5-e8d3-f03f-336369583c85">Document attributes specifying decimal point and minus sign choices</name>
<sourcecode id="_259e6514-a3a2-2477-5733-9298f8293ff2" lang="asciidoctor"><body>:number-presentation-profile: notation=scientific,exponent_sign=nil,decimal=","</body></sourcecode>

</example>

<example id="_7449b85c-ee46-18c4-4644-9734b0d4c1e3">
<name id="_198cf45e-0114-7b93-1d5e-be54f41a508b">Configuration of number rendering inline</name>
<sourcecode id="_bc8abfe7-e100-b540-4f63-d67e9e18a733" lang="asciidoctor"><body>number:327428.7432878432992[decimal=".",notation=exponential]</body></sourcecode>

</example>
</clause>

<clause id="_3b2e9dee-8865-d973-b856-7e40a35d7519" obligation="normative">
<title id="_ec0b15b2-cf71-168e-9e51-68e5e1fd39de">Bibliographic punctuation</title>
<p id="_39639be8-b694-baf1-6767-1abed7bf4042">Bibliographic punctuation is distinct from auto-text punctuation, and is catered for in the <tt>relaton-render</tt> gem. The  <tt>relaton-render</tt> gem is passed full details of the bibliographic entry to be rendered, including what the primary and secondary title are, and therefore it is the right place for title marks to be rendered, whether as punctuation or as italics.</p>

<p id="_e731af91-219b-deef-9da2-3d948ca28f81">The handling of punctuation has been overhauled in <tt>relaton-render</tt>`. In particular, the use of punctuation to separate bibliographic fields has ceased being treated as sentence and phrase stops, since they are handled in CJK as tabs instead, and needs to avoid conflation with the abbreviation usage of period. Bibliographic rendering thus adds two new values to i18n configuration:</p>

<ul id="_ee1b5dac-cf23-61e0-4d8c-a6c4b3622d47"><li><p id="_e3e53dab-a312-623a-ada6-edac9488ffea"><tt>biblio-field-delimiter</tt> is the main delimiter between (groupings of) bibliographic fields in a citation; e.g. in “Smith, J. (ed.) $ 1980 $ The smell of success $ New York: Doubleday”, it is indicated by pass:c,q,a,m,p[`$`]. Note that some fields are grouped together with different publication, to indicate more tight coupling; e.g. “Smith, J” and “(ed.)”, and “New York” and “Doubleday”, are distinct bibliographic fields, but they are grouped together more tightly. In Western practice, the bibliographic field delimiter is usually period, though in some styles it is comma. In CJK practice, it is traditionally horizontal spacing.</p>
</li>
<li><p id="_1b919c2d-fa7f-ceb9-daaa-896f1d073510"><tt>biblio-terminator</tt> is the final punctuation of a bibliographic entry. In some styles, it is supplied in a bibliography (e.g. NIST); in some, it is absent (e.g. ISO); in some, its use depends on the content of the entry (e.g. for BIPM, home standards vs. other standards). The bibliographic terminator is typically identified with the declarative stop (period in Western use), since a bibliographic entry is treated as a sentence. The bibliographic terminator is not used in in-document citations (citations given in running text), since they appear there as part of a sentence of running text.</p>
</li>
</ul>
</clause>
</clause>

<clause id="_f59583cf-7063-9d6f-189f-189cf441c074" obligation="normative">
<title id="_8f02df7f-cb73-7e2a-82d6-500df08f6f63">Writing mode parameterization</title>
<p id="_d08ccb31-2626-ea38-96be-aa59a0854079">Punctuation in CJK is handled differently in vertical and horizontal directionality. Currently there is no provision for different punctuation configuration for vertical and horizontal: the same punctuation is used in both cases, and rotating the punctuation glyphs as required is left up to the rendering engine.</p>

<p id="_66b20825-4f4d-11f6-6871-2ef38df590f2">If it turns out that this is not adequate, and separate configuration is needed for vertical directionality, directionality will be a separate parameter passed to  <tt>l10n()</tt>; we propose to use the CSS <tt>writing-mode</tt> style values, <tt>vertical-rl</tt>, <tt>vertical-lr</tt>, <tt>horizontal-tb</tt>. (There is no standard encoding of directionality.)</p>
</clause>
</clause>


</sections><bibliography><references id="_49be3bc2-8658-03af-415f-9224d287a76a" normative="true" obligation="informative">
<title id="_270c5ee6-077e-f285-ff95-287984a30140">Normative references</title><p id="_49996d2b-65c1-916b-9bbf-42b933aa0025">The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.</p>
<bibitem anchor="MN112" id="_8e99d23f-712d-797d-52f0-567a093ca3a3"><formattedref format="application/x-isodoc+xml">MN 112: <em>Label Auto-assignment Definition Language (LADL) specification</em></formattedref><docidentifier>MN 112</docidentifier><docnumber>112</docnumber><language>en</language><script>Latn</script></bibitem>
<bibitem id="_b1a7068f-1e8a-1178-0114-6a48d315b240" type="standard" schema-version="v1.5.6" anchor="ISO10646">
  <fetched>2026-06-02</fetched>
  
<title language="en" script="Latn" type="title-intro">Information technology</title>

  
<title language="en" script="Latn" type="title-main">Universal coded character set (UCS)</title>

  
<title language="en" script="Latn" type="main">Information technology — Universal coded character set (UCS)</title>

  
<title language="fr" script="Latn" type="title-intro">Technologies de l’information</title>

  
<title language="fr" script="Latn" type="title-main">Jeu universel de caractères codés (JUC)</title>

  
<title language="fr" script="Latn" type="main">Technologies de l’information — Jeu universel de caractères codés (JUC)</title>

  <uri type="src">https://www.iso.org/standard/76835.html</uri>
  <uri type="obp">https://www.iso.org/obp/ui/en/#!iso:std:76835:en</uri>
  <uri type="rss">https://www.iso.org/contents/data/standard/07/68/76835.detail.rss</uri>
  <docidentifier type="ISO" primary="true">ISO/IEC 10646:2020</docidentifier>
  <docidentifier type="iso-reference">ISO/IEC 10646:2020(E)</docidentifier>
  <docidentifier type="URN">urn:iso:std:iso-iec:10646:stage-90.92</docidentifier>
  <docnumber>10646</docnumber>
  <date type="published">
    <on>2020-12-21</on>
  </date>
  <contributor>
    <role type="publisher"/>
    <organization>
      
<name>International Organization for Standardization</name>

      <abbreviation>ISO</abbreviation>
      <uri>www.iso.org</uri>
    </organization>
  </contributor>
  <contributor>
    <role type="publisher"/>
    <organization>
      
<name>International Electrotechnical Commission</name>

      <abbreviation>IEC</abbreviation>
      <uri>www.iec.ch</uri>
    </organization>
  </contributor>
  <contributor>
    <role type="author">
      <description>committee</description>
    </role>
    <organization>
      
<name>International Organization for Standardization</name>

      <subdivision type="technical-committee" subtype="IEC">
        
<name>Coded character sets</name>

        <identifier>ISO/IEC JTC 1/SC 2</identifier>
      </subdivision>
      <abbreviation>ISO</abbreviation>
    </organization>
  </contributor>
  <edition>6</edition>
  <language>en</language>
  <script>Latn</script>
  <abstract language="en" script="Latn">This document specifies the architecture of the UCS; defines terms used for the UCS; describes the general structure of the UCS codespace; specifies the assigned planes of the UCS: the Basic Multilingual Plane (BMP) of the UCS, the Supplementary Multilingual Plane (SMP), the Supplementary Ideographic Plane (SIP), the Tertiary Ideographic Plane (TIP), and the Supplementary Special-purpose Plane (SSP); defines a set of graphic characters used in scripts and the written form of languages on a world-wide scale; specifies the names for the graphic characters and format characters of the BMP, SMP, SIP, TIP, SSP and their coded representations within the UCS codespace; specifies the coded representations for control characters and private use characters; specifies three encoding forms of the UCS: UTF-8, UTF-16, and UTF-32; specifies seven encoding schemes of the UCS: UTF-8, UTF-16, UTF-16BE, UTF-16LE, UTF-32, UTF-32BE, and UTF-32LE; specifies the management of future additions to this coded character set. NOTE The determination of suitability of these characters for use as identifiers in programming languages is not specified by this document but can be found in an external reference. See Annex U.</abstract>
  <status>
    <stage>90</stage>
    <substage>92</substage>
  </status>
  <copyright>
    <from>2020</from>
    <owner>
      <organization>
        
<name>ISO/IEC</name>

      </organization>
    </owner>
  </copyright>
  <relation type="obsoletes">
    <bibitem>
      <formattedref>ISO/IEC 10646:2017</formattedref>
      <docidentifier type="ISO" primary="true">ISO/IEC 10646:2017</docidentifier>
      <date type="published">
        <on>2017-12-20</on>
      </date>
    </bibitem>

  </relation>
  <relation type="obsoletes">
    <bibitem>
      <formattedref>ISO/IEC 10646:2017/Amd 2:2019</formattedref>
      <docidentifier type="ISO" primary="true">ISO/IEC 10646:2017/Amd 2:2019</docidentifier>
      <date type="published">
        <on>2019-06-14</on>
      </date>
    </bibitem>

  </relation>
  <relation type="obsoletes">
    <bibitem>
      <formattedref>ISO/IEC 10646:2017/Amd 1:2019</formattedref>
      <docidentifier type="ISO" primary="true">ISO/IEC 10646:2017/Amd 1:2019</docidentifier>
      <date type="published">
        <on>2019-01-31</on>
      </date>
    </bibitem>

  </relation>
  <relation type="obsoletedBy">
    <bibitem>
      <formattedref>ISO/IEC CD 10646.4</formattedref>
      <docidentifier type="ISO" primary="true">ISO/IEC CD 10646.4</docidentifier>
    </bibitem>

  </relation>
  <relation type="updatedBy">
    <bibitem>
      <formattedref>ISO/IEC 10646:2020/Amd 1:2023</formattedref>
      <docidentifier type="ISO" primary="true">ISO/IEC 10646:2020/Amd 1:2023</docidentifier>
      <date type="published">
        <on>2023-07-17</on>
      </date>
    </bibitem>

  </relation>
  <place>
    <city>Geneva</city>
  </place>
</bibitem>
<bibitem anchor="Unicode15" id="_564f6624-fca9-73ac-7ce1-638ebf71622b"><formattedref format="application/x-isodoc+xml"><em>Unicode</em> Edition 15.1. <link target="https://www.unicode.org"/></formattedref><docidentifier>Unicode 15.1</docidentifier><docnumber>15.1</docnumber><language>en</language><script>Latn</script></bibitem>
</references><references id="_b2ff123c-dd9d-a489-c8db-3e05daf412e1" normative="false" obligation="informative">
<title id="_50ceb1e1-516f-2673-d73d-4f0c58b4d023">Bibliography</title><bibitem id="_4c4ffa64-6705-a3f6-77ad-8c8a5ac038cf" type="standard" schema-version="v1.5.6" anchor="re_PunctuationMarks">
  <fetched>2026-06-02</fetched>
  
<title language="zh" script="Hans" type="title-main">标点符号用法</title>

  
<title language="zh" script="Hans" type="main">标点符号用法</title>

  
<title language="en" script="Latn" type="title-main">General rules for punctuation</title>

  
<title language="en" script="Latn" type="main">General rules for punctuation</title>

  <uri type="src">http://openstd.samr.gov.cn/bzgk/gb/newGbInfo?hcno=22EA6D162E4110E752259661E1A0D0A8</uri>
  <docidentifier type="Chinese Standard" primary="true">GB/T 15834-2011</docidentifier>
  <date type="published">
    <on>2011-12-30</on>
  </date>
  <contributor>
    <role type="publisher"/>
    <organization>
      
<name language="en">General Administration of Quality Supervision, Inspection and Quarantine; Standardization Administration of China</name>

      
<name language="zh">中华人民共和国国家质量监督检验检疫总局 中国国家标准化管理委员会</name>

    </organization>
  </contributor>
  <language>zh</language>
  <script>Hans</script>
  <status>
    <stage>activated</stage>
  </status>
</bibitem><bibitem anchor="tw_punct" id="_0ddd88c7-9b59-7c56-8a30-9f74d7aa7ac6">
  <formattedref format="application/x-isodoc+xml">Taiwan Ministry of Education. <em>Revised Handbook of Punctuation</em> (Second Edition). Ministry of Education. 2017.</formattedref>
  <docidentifier type="metanorma">[2]</docidentifier>
  <language>en</language>
  <script>Latn</script>
</bibitem><bibitem anchor="bunka_guidelines" id="_c55dcb33-929a-532b-f0b8-8bd959e12246">
  <formattedref format="application/x-isodoc+xml">Japan Cultural Affairs Agency. <em>Guidelines for Creating Public Documents (Cultural Affairs Council Recommendation)</em>. Cultural Affairs Council. 2022.</formattedref>
  <docidentifier type="metanorma">[3]</docidentifier>
  <language>en</language>
  <script>Latn</script>
</bibitem><bibitem anchor="kumihan-en-2" id="_0e02b4ce-e6ad-8ffa-b017-79ba20d72217">
  <formattedref format="application/x-isodoc+xml">Japan Electronic Publishing Association. <em>Requirements for Japanese Text Layout</em>. W3C Working Group Note. 2012.</formattedref>
  <docidentifier type="metanorma">[4]</docidentifier>
  <language>en</language>
  <script>Latn</script>
</bibitem>




</references></bibliography>
<annotation-container><annotation id="_c1e89b07-4708-3cb6-3c78-08b8dca02d19" reviewer="(Unknown)" type="todo" date="2026-06-02T00:00:00Z" from="_c9ab23ea-fc60-422e-b0cf-786cd213b4db" to="_c9ab23ea-fc60-422e-b0cf-786cd213b4db"><p id="_3a3830cd-96c9-cf2a-b111-090c76448a47">Are lenticular brackets quotation markers, title marks, or both?</p>
</annotation></annotation-container></metanorma>
