github-markup 6.0.0 → 6.1.1

data/test/markups/README.mediawiki.html

@@ -1,9 +1,9 @@
-<p><a href="Home">» JRuby Project Wiki Home Page</a>
-</p><h1>Embedding JRuby</h1>
+<p><a>» JRuby Project Wiki Home Page</a>
+<h1>Embedding JRuby</h1>
 Using Java from Ruby is JRuby's best-known feature---but you can also go in the other direction, and use Ruby from Java.  There are several different ways to do this. You can execute entire Ruby scripts, call individual Ruby methods, or even implement a Java interface in Ruby (thus allowing you to treat Ruby objects like Java ones).  We refer to all these techniques generically as "embedding."  This section will explain how to embed JRuby in your Java project.
-
-<p></p><table summary="Contents"><tr><td>
-<div><h2>Table of Contents</h2></div>
+</p>
+<p><table id="toc" summary="Contents"><tr><td>
+<div id="toctitle"><h2>Table of Contents</h2></div>
 <ul>
 <li>
 <a href="#Red_Bridge_JRuby_Embed">Red Bridge (JRuby Embed)</a><ul><li><a href="#Features_of_Red_Bridge">Features of Red Bridge</a></li></ul>
@@ -12,53 +12,53 @@ Using Java from Ruby is JRuby's best-known feature---but you can also go in the
 <li><a href="#References">References</a></li>
 </ul>
 </td></tr></table>
-
+</p>
 
 <h1>
-<a name="Red_Bridge_JRuby_Embed"></a>Red Bridge (JRuby Embed)
+<a name="Red_Bridge_JRuby_Embed"></a><span id="Red_Bridge_JRuby_Embed">Red Bridge (JRuby Embed)</span>
 </h1>
 
 
 
 <p><tt>one-&lt;two</tt>
-</p><pre>a-b</pre>
-
-<p>JRuby has long had a private embedding API, which was closely tied to the runtime's internals and therefore changed frequently as JRuby evolved. Since version 1.4, however, we have also provided a more stable public API, known as Red Bridge or JRuby Embed. Existing Java programs written to the <a href="DirectJRubyEmbedding">legacy API</a> should still work, but we strongly recommend Red Bridge for all new projects.
+<pre>a-b</pre>
+</p>
+<p>JRuby has long had a private embedding API, which was closely tied to the runtime's internals and therefore changed frequently as JRuby evolved. Since version 1.4, however, we have also provided a more stable public API, known as Red Bridge or JRuby Embed. Existing Java programs written to the <a>legacy API</a> should still work, but we strongly recommend Red Bridge for all new projects.
 </p>
 
 <h2>
-<a name="Features_of_Red_Bridge"></a>Features of Red Bridge
+<a name="Features_of_Red_Bridge"></a><span id="Features_of_Red_Bridge">Features of Red Bridge</span>
 </h2>
 
 
-<p>Red Bridge consists of two layers: Embed Core on the bottom, and implementations of <a href="http://www.jcp.org/en/jsr/detail?id=223" target="_blank">JSR223</a> and <a href="http://jakarta.apache.org/bsf/" target="_blank">BSF</a> on top. Embed Core is JRuby-specific, and can take advantage of much of JRuby's power. JSR223 and BSF are more general interfaces that provide a common ground across scripting languages.
+<p>Red Bridge consists of two layers: Embed Core on the bottom, and implementations of <a href="http://www.jcp.org/en/jsr/detail?id=223">JSR223</a> and <a href="http://jakarta.apache.org/bsf/">BSF</a> on top. Embed Core is JRuby-specific, and can take advantage of much of JRuby's power. JSR223 and BSF are more general interfaces that provide a common ground across scripting languages.
 </p>
 <p>Which API should you use? For projects where Ruby is the only scripting language involved, we recommend Embed Core for the following reasons:
 </p>
 
 
 
-<p></p><ol>
+<p><ol>
 <li>With Embed Core, you can create several Ruby environments in one JVM, and configure them individually (via <code>org.jruby.RubyInstanceConfig</code>. With the other APIs, configuration options can only be set globally, via the <code>System</code> properties.</li>
 <li>Embed Core offers several shortcuts, such as loading scripts from a <code>java.io.InputStream</code>, or returning Java-friendly objects from Ruby code. These allow you to skip a lot of boilerplate.</li>
 </ol>
 For projects requiring multiple scripting languages, JSR223 is a good fit. Though the API is language-independent, JRuby's implementation of it allows you to set some Ruby-specific options. In particular, you can control the threading model of the scripting engine, the lifetime of local variables, compilation mode, and how line numbers are displayed.
-
-<p>The full <a href="http://jruby-embed.kenai.com/docs/" target="_blank">API documentation</a> has all the gory details. It's worth talking about a couple of the finer points here.
+</p>
+<p>The full <a href="http://jruby-embed.kenai.com/docs/">API documentation</a> has all the gory details. It's worth talking about a couple of the finer points here.
 </p>
 
 <h1>
-<a name="Previous_Embedding_JRuby_Page"></a>Previous Embedding JRuby Page
+<a name="Previous_Embedding_JRuby_Page"></a><span id="Previous_Embedding_JRuby_Page">Previous Embedding JRuby Page</span>
 </h1>
 
 
-<p>We recommend using Embed Core; however, if you're maintaining code that uses the old API, you can find its documentation on the <a href="JavaIntegration">legacy embedding</a><sup>[<a href="#cite_note-1">1</a>]</sup> page.
+<p>We recommend using Embed Core; however, if you're maintaining code that uses the old API, you can find its documentation on the <a>legacy embedding</a><sup id="cite_ref-1-0">[<a href="#cite_note-1">1</a>]</sup> page.
 </p>
 
 <h1>
-<a name="References"></a>References
+<a name="References"></a><span id="References">References</span>
 </h1>
 
 
-<p></p><ol><li>
-<b><a href="#cite_ref-1-0">^</a> </b> This link goes nowhere.</li></ol>
+<p><ol><li id="cite_note-1">
+<b><a href="#cite_ref-1-0">^</a> </b> This link goes nowhere.</li></ol></p>

data/test/markups/README.org.html

@@ -1,28 +1,19 @@
 <h1>org-ruby</h1>
 <table>
-  <tr>
-<td>Status:</td>
-<td>Under Development</td>
-</tr>
-  <tr>
-<td>Location:</td>
-<td><a href="http://github.com/wallyqs/org-ruby">http://github.com/wallyqs/org-ruby</a></td>
-</tr>
-  <tr>
-<td>Version:</td>
-<td>0.9.0</td>
-</tr>
+  <tr><td>Status:</td><td>Under Development</td></tr>
+  <tr><td>Location:</td><td><a href="http://github.com/wallyqs/org-ruby">http://github.com/wallyqs/org-ruby</a></td></tr>
+  <tr><td>Version:</td><td>0.9.0</td></tr>
 </table>
-<h1>1 Description</h1>
+<h1><span>1</span> Description</h1>
 <p>Helpful Ruby routines for parsing orgmode files. The most
   significant thing this library does today is convert orgmode files
   to textile. Currently, you cannot do much to customize the
   conversion. The supplied textile conversion is optimized for
-  extracting “content” from the orgfile as opposed to “metadata.”</p>
-<h1>2 History</h1>
-<h2>2.1 2014-02-08: Version 0.9.0</h2>
+  extracting &#8220;content&#8221; from the orgfile as opposed to &#8220;metadata.&#8221;</p>
+<h1><span>2</span> History</h1>
+<h2><span>2.1</span> 2014-02-08: Version 0.9.0</h2>
 <ul>
-  <li>Let’s make sure <code>#+INCLUDE:</code> is not supported</li>
+  <li>Let&#8217;s make sure <code>#+INCLUDE:</code> is not supported</li>
 </ul>
 <ul>
   <li>And confirm that syntax highlight is supported</li>
@@ -30,18 +21,18 @@
 <pre lang="ruby">
 module GitHub
   module Markup
-    VERSION = 'test'
+    VERSION = &#39;test&#39;
     Version = VERSION
   end
 end
 </pre>
-<h2>2.2 2009-12-30: Version 0.5.1</h2>
+<h2><span>2.2</span> 2009-12-30: Version 0.5.1</h2>
 <ul>
-  <li>Minor enhancement: Recognize lines starting with “:” as examples.</li>
+  <li>Minor enhancement: Recognize lines starting with &#8220;:&#8221; as examples.</li>
   <li>Minor enhancement: Recognize #+BEGIN_SRC as source blocks</li>
-  <li>Minor enhancement: Add “src” and “example” classes to &lt;pre&gt; blocks.</li>
+  <li>Minor enhancement: Add &#8220;src&#8221; and &#8220;example&#8221; classes to &lt;pre&gt; blocks.</li>
 </ul>
-<h2>2.3 2009-12-30: Version 0.5.0</h2>
+<h2><span>2.3</span> 2009-12-30: Version 0.5.0</h2>
 <ul>
   <li>Parse (but not necessarily <b>use</b>) in-buffer settings. The following
     in-buffer settings <b>are</b> used:
@@ -56,7 +47,7 @@ end
         the tree to export</li>
     </ul>
   </li>
-  <li>Rewrite “file:(blah).org” links to “http:(blah).html” links. This
+  <li>Rewrite &#8220;file:(blah).org&#8221; links to &#8220;http:(blah).html&#8221; links. This
     makes the inter-links to other org-mode files work.</li>
   <li>Uses &lt;th&gt; tags inside table rows that precede table separators.</li>
   <li>Bugfixes:
@@ -65,7 +56,7 @@ end
     </ul>
   </li>
 </ul>
-<h2>2.4 2009-12-29: Version 0.4.2</h2>
+<h2><span>2.4</span> 2009-12-29: Version 0.4.2</h2>
 <ul>
   <li>Got rid of the extraneous newline at the start of code blocks.</li>
   <li>Everything now shows up in code blocks, even org-mode metadata.</li>
@@ -76,59 +67,59 @@ end
     </ul>
   </li>
 </ul>
-<h2>2.5 2009-12-29: Version 0.4.1</h2>
+<h2><span>2.5</span> 2009-12-29: Version 0.4.1</h2>
 <ul>
   <li>HTML is now escaped by default</li>
   <li>org-mode comments will show up in a code block.</li>
 </ul>
-<h2>2.6 2009-12-29: Version 0.4</h2>
+<h2><span>2.6</span> 2009-12-29: Version 0.4</h2>
 <ul>
-  <li>The first thing output in HTML gets the class “title”</li>
+  <li>The first thing output in HTML gets the class &#8220;title&#8221;</li>
   <li>HTML output is now indented</li>
   <li>Proper support for multi-paragraph list items.
     <p>See? This paragraph is part of the last bullet.</p>
   </li>
   <li>Fixed bugs:
     <ul>
-      <li>“rake spec” wouldn’t work on Linux. Needed “require ‘rubygems’”.</li>
+      <li>&#8220;rake spec&#8221; wouldn&#8217;t work on Linux. Needed &#8220;require &#8216;rubygems&#8217;&#8221;.</li>
     </ul>
   </li>
 </ul>
-<h2>2.7 2009-12-27: Version 0.3</h2>
+<h2><span>2.7</span> 2009-12-27: Version 0.3</h2>
 <ul>
-  <li>Uses rubypants to get better typography (smart quotes, ellipses, etc…).</li>
+  <li>Uses rubypants to get better typography (smart quotes, ellipses, etc&#8230;).</li>
   <li>Fixed bugs:
     <ul>
       <li>Tables and lists did not get properly closed at the end of file</li>
-      <li>You couldn’t do inline formatting inside table cells</li>
+      <li>You couldn&#8217;t do inline formatting inside table cells</li>
       <li>Characters in PRE blocks were not HTML escaped.</li>
     </ul>
   </li>
 </ul>
-<h2>2.8 2009-12-26: Version 0.2</h2>
+<h2><span>2.8</span> 2009-12-26: Version 0.2</h2>
 <ul>
   <li>Added <code>to_html</code> output on the parser.</li>
   <li>Added support for the full range of inline markup: <b>bold</b>,
-    <i>italic</i>, <code>code</code>, <code>verbatim</code>, underline, <del>strikethrough</del>.</li>
+    <i>italic</i>, <code>code</code>, <code>verbatim</code>, <span>underline</span>, <del>strikethrough</del>.</li>
   <li>Lots of refactoring to make the code more maintainable.</li>
 </ul>
-<h2>2.9 2009-12-23: Version 0.1</h2>
+<h2><span>2.9</span> 2009-12-23: Version 0.1</h2>
 <ul>
   <li>Added support for block code, like this:
     <pre>
   def flush!
-  @logger.debug "FLUSH ==========&gt; #{@output_type}"
+  @logger.debug &quot;FLUSH ==========&gt; #{@output_type}&quot;
   if (@output_type == :blank) then
-    @output &lt;&lt; "\n"
+    @output &lt;&lt; &quot;\n&quot;
   elsif (@buffer.length &gt; 0) then
     if @cancel_modifier then
-      @output &lt;&lt; "p. " if @output_type == :paragraph
+      @output &lt;&lt; &quot;p. &quot; if @output_type == :paragraph
       @cancel_modifier = false
     end
     @output &lt;&lt; @paragraph_modifier if (@paragraph_modifier and not sticky_modifier?)
-    @output &lt;&lt; @buffer.textile_substitution &lt;&lt; "\n"
+    @output &lt;&lt; @buffer.textile_substitution &lt;&lt; &quot;\n&quot;
   end
-  @buffer = ""
+  @buffer = &quot;&quot;
 end
     </pre>
   </li>

data/test/markups/README.pod.html

@@ -1,46 +1,42 @@
-<h1>Matrixy</h1>
+<h1 id="Matrixy">Matrixy</h1>
 
-<h2>INTRODUCTION</h2>
+<h2 id="INTRODUCTION">INTRODUCTION</h2>
 
 <p>This is a port of the MATLAB/Octave programming language to Parrot. See the ROADMAP file for more information on the status of this project, and what else needs to be done.</p>
 
-<h2>ABOUT</h2>
+<h2 id="ABOUT">ABOUT</h2>
 
 <p>Primary goals are:</p>
 
 <ul>
 
-<li>
-<p>Create a working compiler that understands the majority of the MATLAB/Octave programming language.</p>
+<li><p>Create a working compiler that understands the majority of the MATLAB/Octave programming language.</p>
 
 </li>
 </ul>
 
-<h2>IMPLEMENTATION</h2>
+<h2 id="IMPLEMENTATION">IMPLEMENTATION</h2>
 
 <p>This project is broken into three primary components:</p>
 
 <ul>
 
-<li>
-<p>The first is the parser, located in the <code>src/parser/</code> directory. The parser proper is composed of three source files, <i>grammar.pg</i> which is a Perl6Grammar file, and <i>actions.pm</i> which is the associated actions file written in NQP, and <i>grammar-oper.pm</i> which is the operator precedence parser. In addition, several helper functions used by the parser are located in <code>src/internals</code>.</p>
+<li><p>The first is the parser, located in the <code>src/parser/</code> directory. The parser proper is composed of three source files, <i>grammar.pg</i> which is a Perl6Grammar file, and <i>actions.pm</i> which is the associated actions file written in NQP, and <i>grammar-oper.pm</i> which is the operator precedence parser. In addition, several helper functions used by the parser are located in <code>src/internals</code>.</p>
 
 </li>
-<li>
-<p>The second component is the library of builtin functions in the <code>src/builtins/</code> directory. These functions are, currently, written primarily in PIR. Function names prefixed with an underscore are "private" functions for use with the parser. Other functions should have names which are the same as names for regular MATLAB or Octave functions, since they will be available to the HLL. These are also separated into different namespaces depending on visibility and utility.</p>
+<li><p>The second component is the library of builtin functions in the <code>src/builtins/</code> directory. These functions are, currently, written primarily in PIR. Function names prefixed with an underscore are &quot;private&quot; functions for use with the parser. Other functions should have names which are the same as names for regular MATLAB or Octave functions, since they will be available to the HLL. These are also separated into different namespaces depending on visibility and utility.</p>
 
 </li>
-<li>
-<p>A number of library functions are written in M, or mostly M with some inline PIR code in <code>toolbox/</code>.</p>
+<li><p>A number of library functions are written in M, or mostly M with some inline PIR code in <code>toolbox/</code>.</p>
 
 </li>
 </ul>
 
-<h2>DEPENDENCIES</h2>
+<h2 id="DEPENDENCIES">DEPENDENCIES</h2>
 
 <p>Matrixy depends on these dependencies:</p>
 
-<h3>Parrot</h3>
+<h3 id="Parrot">Parrot</h3>
 
 <p>To get a proper version of Parrot to build Matrixy, you will need to check out and build Parrot from source:</p>
 
@@ -49,28 +45,28 @@ cd parrot
 perl Configure.pl
 make &amp;&amp; make test &amp;&amp; make install-dev</code></pre>
 
-<h3>Parrot-Linear-Algebra</h3>
+<h3 id="Parrot-Linear-Algebra">Parrot-Linear-Algebra</h3>
 
 <p>The linear algebra package for Parrot is available separately and provides functionality required by Matrixy. This includes matrix data types and matrix manipulation libraries</p>
 
-<h2>BUILDING</h2>
+<h2 id="BUILDING">BUILDING</h2>
 
 <p>Once all dependencies are in place, you can build Matrixy using this sequence of commands:</p>
 
 <pre><code>perl Configure.pl
 nmake test</code></pre>
 
-<h2>TODO</h2>
+<h2 id="TODO">TODO</h2>
 
 <pre><code>* Parser
 * Standard Builtins
 * Test against Octave Test Suite.</code></pre>
 
-<h2>BUGS</h2>
+<h2 id="BUGS">BUGS</h2>
 
 <p>Lots!</p>
 
-<h2>CONTACT</h2>
+<h2 id="CONTACT">CONTACT</h2>
 
 <p>If you need to contact the Matrixy team, go to the project home page at:</p>
 

data/test/markups/README.rdoc.html

@@ -1,12 +1,9 @@
-<ul>
-<li>
+<ul><li>
 <p>One</p>
-</li>
-<li>
+</li><li>
 <p>Two</p>
-</li>
-</ul>
+</li></ul>
 
 <p>This is an <a href="http://github.com">absolute link</a>.  So is this: <a href="http://github.com">github.com</a></p>
 
-<p>This is a <a href="rawr.html">relative link</a>.  So is this: <a href="rawr.html">rawr.html</a></p>
+<p>This is a <a>relative link</a>.  So is this: <a>rawr.html</a></p>

data/test/markups/README.rst.html

@@ -1,16 +1,16 @@
 <h1>Header 1</h1>
-<h2>Subtitle</h2>
+<h2 id="subtitle">Subtitle</h2>
 <p>Example text.</p>
-<div>
+<div id="table-of-contents">
 <p><a href="#top">Table of Contents</a></p>
 <ul>
-<li><a href="#header-2">Header 2</a></li>
-<li><a href="#field-list">Field list</a></li>
+<li><a href="#header-2" id="id1">Header 2</a></li>
+<li><a href="#field-list" id="id2">Field list</a></li>
 </ul>
 </div>
 <a name="header-2"></a>
 <a name="label-for-header-2"></a>
-<h2><a href="#toc-entry-1">Header 2</a></h2>
+<h2><a href="#id1">Header 2</a></h2>
 <ol>
 <li>Blah blah <code>code</code> blah</li>
 <li>More <code>code</code>, hooray</li>
@@ -19,42 +19,34 @@
 </ol>
 <p>The UTF-8 quote character in this table used to cause python to go boom. Now docutils just silently ignores it.</p>
 <table>
-Things that are Awesome (on a scale of 1-11)
+<caption>Things that are Awesome (on a scale of 1-11)</caption>
 
 
 
 
 <tbody valign="top">
-<tr>
-<td>Thing</td>
+<tr><td>Thing</td>
 <td>Awesomeness</td>
 </tr>
-<tr>
-<td>Icecream</td>
+<tr><td>Icecream</td>
 <td>7</td>
 </tr>
-<tr>
-<td>Honey Badgers</td>
+<tr><td>Honey Badgers</td>
 <td>10.5</td>
 </tr>
-<tr>
-<td>Nickelback</td>
+<tr><td>Nickelback</td>
 <td>-2</td>
 </tr>
-<tr>
-<td>Iron Man</td>
+<tr><td>Iron Man</td>
 <td>10</td>
 </tr>
-<tr>
-<td>Iron Man 2</td>
+<tr><td>Iron Man 2</td>
 <td>3</td>
 </tr>
-<tr>
-<td>Tabular Data</td>
+<tr><td>Tabular Data</td>
 <td>5</td>
 </tr>
-<tr>
-<td>Made up ratings</td>
+<tr><td>Made up ratings</td>
 <td>11</td>
 </tr>
 </tbody>
@@ -82,24 +74,19 @@ python.code('hello world')
 
 
 <tbody valign="top">
-<tr>
-<td>Travis</td>
+<tr><td>Travis</td>
 <td><a href="http://travis-ci.org/tony/pullv">http://travis-ci.org/tony/pullv</a></td>
 </tr>
-<tr>
-<td>Docs</td>
+<tr><td>Docs</td>
 <td><a href="http://pullv.rtfd.org">http://pullv.rtfd.org</a></td>
 </tr>
-<tr>
-<td>API</td>
+<tr><td>API</td>
 <td><a href="http://pullv.readthedocs.org/en/latest/api.html">http://pullv.readthedocs.org/en/latest/api.html</a></td>
 </tr>
-<tr>
-<td>Issues</td>
+<tr><td>Issues</td>
 <td><a href="https://github.com/tony/pullv/issues">https://github.com/tony/pullv/issues</a></td>
 </tr>
-<tr>
-<td>Source</td>
+<tr><td>Source</td>
 <td><a href="https://github.com/tony/pullv">https://github.com/tony/pullv</a></td>
 </tr>
 </tbody>
@@ -109,31 +96,23 @@ python.code('hello world')
 </a>
 <img alt="Coverity Scan Build Status" src="https://scan.coverity.com/projects/621/badge.svg">
 <a name="field-list"></a>
-<h2><a href="#toc-entry-2">Field list</a></h2>
+<h2><a href="#id2">Field list</a></h2>
 <table frame="void" rules="none">
 
 
 <tbody valign="top">
 <tr><th colspan="2">123456789 123456789 123456789 123456789 123456789 1:</th></tr>
-<tr>
-<td> </td>
-<td>Uh-oh! This name is too long!</td>
+<tr><td>&nbsp;</td><td>Uh-oh! This name is too long!</td>
 </tr>
-<tr>
-<th>123456789 123456789 123456789 123456789 1234567890:</th>
-<td>this is a long name,
+<tr><th>123456789 123456789 123456789 123456789 1234567890:</th><td>this is a long name,
 but no problem!</td>
 </tr>
-<tr>
-<th>123456789 12345:</th>
-<td>this is not so long, but long enough for the default!</td>
+<tr><th>123456789 12345:</th><td>this is not so long, but long enough for the default!</td>
 </tr>
-<tr>
-<th>123456789 1234:</th>
-<td>this should work even with the default :)</td>
+<tr><th>123456789 1234:</th><td>this should work even with the default :)</td>
 </tr>
 </tbody>
 </table>
-<p><a href="mailto:someone@somewhere.org">someone@somewhere.org</a></p>
+<p><a href="mailto:someone@somewhere.org">someone&#64;somewhere.org</a></p>
 <p>Press <kbd>Ctrl+C</kbd> to quit</p>
-<p><strong>RAW HTML!</strong></p> p {color:blue;} 
+<p><strong>RAW HTML!</strong></p>

data/test/markups/README.rst.txt.html

@@ -13,24 +13,19 @@
 
 
 <tbody valign="top">
-<tr>
-<td>Travis</td>
+<tr><td>Travis</td>
 <td><a href="http://travis-ci.org/tony/pullv">http://travis-ci.org/tony/pullv</a></td>
 </tr>
-<tr>
-<td>Docs</td>
+<tr><td>Docs</td>
 <td><a href="http://pullv.rtfd.org">http://pullv.rtfd.org</a></td>
 </tr>
-<tr>
-<td>API</td>
+<tr><td>API</td>
 <td><a href="http://pullv.readthedocs.org/en/latest/api.html">http://pullv.readthedocs.org/en/latest/api.html</a></td>
 </tr>
-<tr>
-<td>Issues</td>
+<tr><td>Issues</td>
 <td><a href="https://github.com/tony/pullv/issues">https://github.com/tony/pullv/issues</a></td>
 </tr>
-<tr>
-<td>Source</td>
+<tr><td>Source</td>
 <td><a href="https://github.com/tony/pullv">https://github.com/tony/pullv</a></td>
 </tr>
 </tbody>

data/test/markups/README.toc.asciidoc.html

@@ -1,16 +1,14 @@
 <h1>Document Title</h1>
-<div>
-<div>Contents</div>
+<div id="toc">
+<div id="toctitle">Contents</div>
 <ul>
-<li>
-<a href="#section-a">Section A</a>
+<li><a href="#section-a">Section A</a>
 <ul>
 <li><a href="#subsection-a-1">Subsection A-1</a></li>
 <li><a href="#subsection-a-2">Subsection A-2</a></li>
 </ul>
 </li>
-<li>
-<a href="#section-b">Section B</a>
+<li><a href="#section-b">Section B</a>
 <ul>
 <li><a href="#subsection-b-1">Subsection B-1</a></li>
 <li><a href="#subsection-b-2">Subsection B-2</a></li>
@@ -19,27 +17,27 @@
 </ul>
 </div>
 <div>
-<h2>Section A</h2>
+<h2 id="section-a">Section A</h2>
 <div>
 <div>
-<h3>Subsection A-1</h3>
+<h3 id="subsection-a-1">Subsection A-1</h3>
 
 </div>
 <div>
-<h3>Subsection A-2</h3>
+<h3 id="subsection-a-2">Subsection A-2</h3>
 
 </div>
 </div>
 </div>
 <div>
-<h2>Section B</h2>
+<h2 id="section-b">Section B</h2>
 <div>
 <div>
-<h3>Subsection B-1</h3>
+<h3 id="subsection-b-1">Subsection B-1</h3>
 
 </div>
 <div>
-<h3>Subsection B-2</h3>
+<h3 id="subsection-b-2">Subsection B-2</h3>
 
 </div>
 </div>

data/test/markups/README.toc.rst.html

@@ -1,23 +1,22 @@
-<div>
+<div id="contents">
 <p><a href="#top">Contents</a></p>
 <ul>
-<li>
-<a href="#introduction">1   Introduction</a><ul>
-<li><a href="#what-is-pycparser">1.1   What is pycparser?</a></li>
-<li><a href="#what-is-it-good-for">1.2   What is it good for?</a></li>
+<li><a href="#introduction" id="id1">1&nbsp;&nbsp;&nbsp;Introduction</a><ul>
+<li><a href="#what-is-pycparser" id="id2">1.1&nbsp;&nbsp;&nbsp;What is pycparser?</a></li>
+<li><a href="#what-is-it-good-for" id="id3">1.2&nbsp;&nbsp;&nbsp;What is it good for?</a></li>
 </ul>
 </li>
 </ul>
 </div>
 <a name="introduction"></a>
-<h2>1   Introduction</h2>
+<h2>1&nbsp;&nbsp;&nbsp;Introduction</h2>
 <a name="what-is-pycparser"></a>
-<h3>1.1   What is pycparser?</h3>
+<h3>1.1&nbsp;&nbsp;&nbsp;What is pycparser?</h3>
 <p><strong>pycparser</strong> is a parser for the C language, written in pure Python. It is a
 module designed to be easily integrated into applications that need to parse
 C source code.</p>
 <a name="what-is-it-good-for"></a>
-<h3>1.2   What is it good for?</h3>
+<h3>1.2&nbsp;&nbsp;&nbsp;What is it good for?</h3>
 <p>Anything that needs C code to be parsed. The following are some uses for
 <strong>pycparser</strong>, taken from real user reports:</p>
 <ul>

data/test/test_helper.rb

@@ -0,0 +1,29 @@
+require "simplecov"
+
+SimpleCov.start do
+  enable_coverage :branch
+  add_filter "/test/"
+  add_filter "/spec/"
+  add_filter "/features/"
+  track_files "lib/**/*.rb"
+  command_name "MarkupTests"
+  minimum_coverage line: 100, branch: 100
+end
+
+module ConstantStubbing
+  private
+
+  def with_stub_const(path, value)
+    parts = path.split("::")
+    name = parts.pop
+    parent = parts.inject(Object) { |mod, part| mod.const_get(part) }
+    had_const = parent.const_defined?(name, false)
+    original = parent.const_get(name) if had_const
+    parent.send(:remove_const, name) if had_const
+    parent.const_set(name, value)
+    yield
+  ensure
+    parent.send(:remove_const, name) if parent.const_defined?(name, false)
+    parent.const_set(name, original) if had_const
+  end
+end