fix: Fix an edge case in the table of contents in text output (#735)

* chore: Update tests
* fix: Fix an edge case in the table of contents in text output

Author: kesara

tests/input/draft-miek-test.xml

@@ -986,6 +986,9 @@ draft-gieben-writing-rfcs-pandoc-00.txt -> draft.txt
             <t>
                Test a very long title.  
             </t>
+            <section title="S/MIME encrypted and signed over a simple message, Injected Headers with hcp_minimal (+ Legacy Display)" toc="default">
+              <t>Test long title edge case</t>
+            </section>
          </section>
          <section title="Markup in heading" anchor="markup-in-heading" toc="default">
             <t>

tests/valid/docfile.py36.html

@@ -4,15 +4,15 @@
 <meta charset="utf-8">
 <meta content="Cherokee,Common,Greek,Latin" name="scripts">
 <meta content="initial-scale=1.0" name="viewport">
-<title>Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.12.1</title>
+<title>Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.12.3</title>
 <meta content="xml2rfc(1)" name="author">
 <meta content="
        
        This document provides information about the XML schema implemented in this release of xml2rfc, and the individual elements of that schema.  The document is generated from the RNG schema file that is part of the xml2rfc distribution, so schema information in this document should always be in sync with the schema in actual use.  The textual descriptions depend on manual updates in order to reflect the implementation.
        
     " name="description">
-<meta content="xml2rfc 3.12.1" name="generator">
-<meta content="xml2rfc-docs-3.12.1" name="ietf.draft">
+<meta content="xml2rfc 3.12.3" name="generator">
+<meta content="xml2rfc-docs-3.12.3" name="ietf.draft">
 <link href="tests/out/docfile.xml" rel="alternate" type="application/rfc+xml">
 <link href="#copyright" rel="license">
 <link href="xml2rfc.css" rel="stylesheet">
@@ -45,7 +45,7 @@
 </dd>
 </dl>
 </div>
-<h1 id="title">Xml2rfc Vocabulary Version 3 Schema<br>xml2rfc release 3.12.1</h1>
+<h1 id="title">Xml2rfc Vocabulary Version 3 Schema<br>xml2rfc release 3.12.3</h1>
 <section id="section-abstract">
       <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
 <p id="section-abstract-1">
@@ -367,7 +367,7 @@ <h2 id="name-introduction">
 <p id="section-1-5">
        The latest version of this documentation is available in HTML form at <span><a href="https://xml2rfc.ietf.org/xml2rfc-doc">https://xml2rfc.ietf.org/xml2rfc-doc</a></span>.<a href="#section-1-5" class="pilcrow">¶</a></p>
 <p id="section-1-6">
-            This documentation applies to xml2rfc version 3.12.1.<a href="#section-1-6" class="pilcrow">¶</a></p>
+            This documentation applies to xml2rfc version 3.12.3.<a href="#section-1-6" class="pilcrow">¶</a></p>
 </section>
 <section id="section-2">
       <h2 id="name-schema-version-3-elements">
@@ -2882,7 +2882,7 @@ <h4 id="name-name-attribute-2">
 <a href="#section-2.53.3" class="section-number selfRef">2.53.3. </a><a href="#name-name-attribute-2" class="section-name selfRef">"name" Attribute</a>
           </h4>
 <p id="section-2.53.3-1">
-       A filename suitable for the contents (such as for extraction to a local file).  This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code).  Note that the "name" attribute does not need to be unique for &lt;artwork&gt; elements in a document.  If multiple &lt;sourcecode&gt; elements have the same "name" attribute, a formatter might assume that the elements are all fragments of a single file, and such a formatter can collect those fragments for later processing.<a href="#section-2.53.3-1" class="pilcrow">¶</a></p>
+       A filename suitable for the contents (such as for extraction to a local file).  This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code).  Note that the "name" attribute does not need to be unique for &lt;sourcecode&gt; elements in a document.  If multiple &lt;sourcecode&gt; elements have the same "name" attribute, a formatter might assume that the elements are all fragments of a single file, and such a formatter can collect those fragments for later processing.<a href="#section-2.53.3-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="attrib-sourcecode-src">
@@ -6342,7 +6342,7 @@ <h2 id="name-xml2rfc-documentation-templ">
 <p id="appendix-D-1">
 
             The following variables are available for use in an xml2rfc
-            manpage Jinja2 template, as of xml2rfc version 3.12.1:<a href="#appendix-D-1" class="pilcrow">¶</a></p>
+            manpage Jinja2 template, as of xml2rfc version 3.12.3:<a href="#appendix-D-1" class="pilcrow">¶</a></p>
 <span class="break"></span><dl class="dlNewline" id="appendix-D-2">
         <dt id="appendix-D-2.1">{{ bare_latin_tags }}:</dt>
         <dd style="margin-left: 1.5em" id="appendix-D-2.2"></dd>

tests/valid/docfile.py37.html

@@ -4,15 +4,15 @@
 <meta charset="utf-8">
 <meta content="Cherokee,Common,Greek,Latin" name="scripts">
 <meta content="initial-scale=1.0" name="viewport">
-<title>Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.12.1</title>
+<title>Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.12.3</title>
 <meta content="xml2rfc(1)" name="author">
 <meta content="
        
        This document provides information about the XML schema implemented in this release of xml2rfc, and the individual elements of that schema.  The document is generated from the RNG schema file that is part of the xml2rfc distribution, so schema information in this document should always be in sync with the schema in actual use.  The textual descriptions depend on manual updates in order to reflect the implementation.
        
     " name="description">
-<meta content="xml2rfc 3.12.1" name="generator">
-<meta content="xml2rfc-docs-3.12.1" name="ietf.draft">
+<meta content="xml2rfc 3.12.3" name="generator">
+<meta content="xml2rfc-docs-3.12.3" name="ietf.draft">
 <link href="tests/out/docfile.xml" rel="alternate" type="application/rfc+xml">
 <link href="#copyright" rel="license">
 <link href="xml2rfc.css" rel="stylesheet">
@@ -45,7 +45,7 @@
 </dd>
 </dl>
 </div>
-<h1 id="title">Xml2rfc Vocabulary Version 3 Schema<br>xml2rfc release 3.12.1</h1>
+<h1 id="title">Xml2rfc Vocabulary Version 3 Schema<br>xml2rfc release 3.12.3</h1>
 <section id="section-abstract">
       <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
 <p id="section-abstract-1">
@@ -367,7 +367,7 @@ <h2 id="name-introduction">
 <p id="section-1-5">
        The latest version of this documentation is available in HTML form at <span><a href="https://xml2rfc.ietf.org/xml2rfc-doc">https://xml2rfc.ietf.org/xml2rfc-doc</a></span>.<a href="#section-1-5" class="pilcrow">¶</a></p>
 <p id="section-1-6">
-            This documentation applies to xml2rfc version 3.12.1.<a href="#section-1-6" class="pilcrow">¶</a></p>
+            This documentation applies to xml2rfc version 3.12.3.<a href="#section-1-6" class="pilcrow">¶</a></p>
 </section>
 <section id="section-2">
       <h2 id="name-schema-version-3-elements">
@@ -2882,7 +2882,7 @@ <h4 id="name-name-attribute-2">
 <a href="#section-2.53.3" class="section-number selfRef">2.53.3. </a><a href="#name-name-attribute-2" class="section-name selfRef">"name" Attribute</a>
           </h4>
 <p id="section-2.53.3-1">
-       A filename suitable for the contents (such as for extraction to a local file).  This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code).  Note that the "name" attribute does not need to be unique for &lt;artwork&gt; elements in a document.  If multiple &lt;sourcecode&gt; elements have the same "name" attribute, a formatter might assume that the elements are all fragments of a single file, and such a formatter can collect those fragments for later processing.<a href="#section-2.53.3-1" class="pilcrow">¶</a></p>
+       A filename suitable for the contents (such as for extraction to a local file).  This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code).  Note that the "name" attribute does not need to be unique for &lt;sourcecode&gt; elements in a document.  If multiple &lt;sourcecode&gt; elements have the same "name" attribute, a formatter might assume that the elements are all fragments of a single file, and such a formatter can collect those fragments for later processing.<a href="#section-2.53.3-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="attrib-sourcecode-src">
@@ -6342,7 +6342,7 @@ <h2 id="name-xml2rfc-documentation-templ">
 <p id="appendix-D-1">
 
             The following variables are available for use in an xml2rfc
-            manpage Jinja2 template, as of xml2rfc version 3.12.1:<a href="#appendix-D-1" class="pilcrow">¶</a></p>
+            manpage Jinja2 template, as of xml2rfc version 3.12.3:<a href="#appendix-D-1" class="pilcrow">¶</a></p>
 <span class="break"></span><dl class="dlNewline" id="appendix-D-2">
         <dt id="appendix-D-2.1">{{ bare_latin_tags }}:</dt>
         <dd style="margin-left: 1.5em" id="appendix-D-2.2"></dd>

tests/valid/docfile.py38.html

@@ -4,15 +4,15 @@
 <meta charset="utf-8">
 <meta content="Cherokee,Common,Greek,Latin" name="scripts">
 <meta content="initial-scale=1.0" name="viewport">
-<title>Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.12.1</title>
+<title>Xml2rfc Vocabulary Version 3 Schema xml2rfc release 3.12.3</title>
 <meta content="xml2rfc(1)" name="author">
 <meta content="
        
        This document provides information about the XML schema implemented in this release of xml2rfc, and the individual elements of that schema.  The document is generated from the RNG schema file that is part of the xml2rfc distribution, so schema information in this document should always be in sync with the schema in actual use.  The textual descriptions depend on manual updates in order to reflect the implementation.
        
     " name="description">
-<meta content="xml2rfc 3.12.1" name="generator">
-<meta content="xml2rfc-docs-3.12.1" name="ietf.draft">
+<meta content="xml2rfc 3.12.3" name="generator">
+<meta content="xml2rfc-docs-3.12.3" name="ietf.draft">
 <link href="tests/out/docfile.xml" rel="alternate" type="application/rfc+xml">
 <link href="#copyright" rel="license">
 <link href="xml2rfc.css" rel="stylesheet">
@@ -45,7 +45,7 @@
 </dd>
 </dl>
 </div>
-<h1 id="title">Xml2rfc Vocabulary Version 3 Schema<br>xml2rfc release 3.12.1</h1>
+<h1 id="title">Xml2rfc Vocabulary Version 3 Schema<br>xml2rfc release 3.12.3</h1>
 <section id="section-abstract">
       <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
 <p id="section-abstract-1">
@@ -367,7 +367,7 @@ <h2 id="name-introduction">
 <p id="section-1-5">
        The latest version of this documentation is available in HTML form at <span><a href="https://xml2rfc.ietf.org/xml2rfc-doc">https://xml2rfc.ietf.org/xml2rfc-doc</a></span>.<a href="#section-1-5" class="pilcrow">¶</a></p>
 <p id="section-1-6">
-            This documentation applies to xml2rfc version 3.12.1.<a href="#section-1-6" class="pilcrow">¶</a></p>
+            This documentation applies to xml2rfc version 3.12.3.<a href="#section-1-6" class="pilcrow">¶</a></p>
 </section>
 <section id="section-2">
       <h2 id="name-schema-version-3-elements">
@@ -2882,7 +2882,7 @@ <h4 id="name-name-attribute-2">
 <a href="#section-2.53.3" class="section-number selfRef">2.53.3. </a><a href="#name-name-attribute-2" class="section-name selfRef">"name" Attribute</a>
           </h4>
 <p id="section-2.53.3-1">
-       A filename suitable for the contents (such as for extraction to a local file).  This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code).  Note that the "name" attribute does not need to be unique for &lt;artwork&gt; elements in a document.  If multiple &lt;sourcecode&gt; elements have the same "name" attribute, a formatter might assume that the elements are all fragments of a single file, and such a formatter can collect those fragments for later processing.<a href="#section-2.53.3-1" class="pilcrow">¶</a></p>
+       A filename suitable for the contents (such as for extraction to a local file).  This attribute can be helpful for other kinds of tools (such as automated syntax checkers, which work by extracting the source code).  Note that the "name" attribute does not need to be unique for &lt;sourcecode&gt; elements in a document.  If multiple &lt;sourcecode&gt; elements have the same "name" attribute, a formatter might assume that the elements are all fragments of a single file, and such a formatter can collect those fragments for later processing.<a href="#section-2.53.3-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="attrib-sourcecode-src">
@@ -6342,7 +6342,7 @@ <h2 id="name-xml2rfc-documentation-templ">
 <p id="appendix-D-1">
 
             The following variables are available for use in an xml2rfc
-            manpage Jinja2 template, as of xml2rfc version 3.12.1:<a href="#appendix-D-1" class="pilcrow">¶</a></p>
+            manpage Jinja2 template, as of xml2rfc version 3.12.3:<a href="#appendix-D-1" class="pilcrow">¶</a></p>
 <span class="break"></span><dl class="dlNewline" id="appendix-D-2">
         <dt id="appendix-D-2.1">{{ bare_latin_tags }}:</dt>
         <dd style="margin-left: 1.5em" id="appendix-D-2.2"></dd>