Update fixtures

Author: kenyonj

Diff for: test/markups/README.asciidoc.html

@@ -59,4 +59,4 @@ <h2>Another Section</h2>
 <p>content</p>
 </div>
 </div>
-</div>
+</div>

Diff for: test/markups/README.hidetitle.asciidoc.html

@@ -1,3 +1,3 @@
 <div>
 <p>This test verifies the author can disable the document title by adding <code>:!showtitle:</code> to the document header.</p>
-</div>
+</div>

Diff for: test/markups/README.litcoffee.html

@@ -3,37 +3,37 @@ <h2>Literate CoffeeScript Test</h2>
 <p>Taken from <a href="https://github.com/jashkenas/coffee-script/blob/master/test/literate.litcoffee">https://github.com/jashkenas/coffee-script/blob/master/test/literate.litcoffee</a></p>
 </blockquote>
 <p>comment comment</p>
-<pre><code>test "basic literate CoffeeScript parsing", -&gt;
-  ok yes
-</code></pre>
+<pre><code><span>test "basic literate CoffeeScript parsing", -&gt;
+</span><span>  ok yes
+</span></code></pre>
 <p>now with a...</p>
-<pre><code>test "broken up indentation", -&gt;
-</code></pre>
+<pre><code><span>test "broken up indentation", -&gt;
+</span></code></pre>
 <p>... broken up ...</p>
-<pre><code>  do -&gt;
-</code></pre>
+<pre><code><span>  do -&gt;
+</span></code></pre>
 <p>... nested block.</p>
-<pre><code>    ok yes
-</code></pre>
+<pre><code><span>    ok yes
+</span></code></pre>
 <p>Code must be separated from text by a blank line.</p>
-<pre><code>test "code blocks must be preceded by a blank line", -&gt;
-</code></pre>
+<pre><code><span>test "code blocks must be preceded by a blank line", -&gt;
+</span></code></pre>
 <p>The next line is part of the text and will not be executed.
 fail()</p>
-<pre><code>  ok yes
-</code></pre>
+<pre><code><span>  ok yes
+</span></code></pre>
 <p>Code in <code>backticks is not parsed</code> and...</p>
-<pre><code>test "comments in indented blocks work", -&gt;
-  do -&gt;
-    do -&gt;
-      # Regular comment.
-
-      ###
-        Block comment.
-      ###
-
-      ok yes
-</code></pre>
+<pre><code><span>test "comments in indented blocks work", -&gt;
+</span><span>  do -&gt;
+</span><span>    do -&gt;
+</span><span>      # Regular comment.
+</span><span>
+</span><span>      ###
+</span><span>        Block comment.
+</span><span>      ###
+</span><span>
+</span><span>      ok yes
+</span></code></pre>
 <p>Regular <a href="http://example.com/markdown">Markdown</a> features,
 like links and unordered lists, are fine:</p>
 <ul>
@@ -52,4 +52,4 @@ <h2>Literate CoffeeScript Test</h2>
 </ul>
 <p>Tabs work too:</p>
 <p>test "tabbed code", -&gt;
-ok yes</p>
+ok yes</p>

Diff for: test/markups/README.org.html

@@ -13,14 +13,17 @@ <h1>org-ruby</h1>
 <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>
+<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>
 </ul>
@@ -35,13 +38,15 @@ <h2>2.1 2014-02-08: Version 0.9.0</h2>
   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 #+BEGIN_SRC as source blocks</li>
   <li>Minor enhancement: Add “src” and “example” 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:
@@ -65,7 +70,8 @@ <h2>2.3 2009-12-30: Version 0.5.0</h2>
     </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,12 +82,14 @@ <h2>2.4 2009-12-29: Version 0.4.2</h2>
     </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>HTML output is now indented</li>
@@ -94,7 +102,8 @@ <h2>2.6 2009-12-29: Version 0.4</h2>
     </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>Fixed bugs:
@@ -105,14 +114,16 @@ <h2>2.7 2009-12-27: Version 0.3</h2>
     </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>

Diff for: test/markups/README.pod.html

@@ -10,7 +10,8 @@ <h2>ABOUT</h2>
 
 <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>
@@ -21,13 +22,16 @@ <h2>IMPLEMENTATION</h2>
 
 <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 &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>
+<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>
-<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>

Diff for: test/markups/README.rst.html

@@ -2,7 +2,7 @@ <h1>Header 1</h1>
 <h2>Subtitle</h2>
 <p>Example text.</p>
 <div>
-<p>Table of Contents</p>
+<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>
@@ -17,7 +17,7 @@ <h2><a href="#toc-entry-1">Header 2</a></h2>
 </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>
 
 
 
@@ -102,7 +102,8 @@ <h2><a href="#toc-entry-1">Header 2</a></h2>
 </tr>
 </tbody>
 </table>
-<a href="https://scan.coverity.com/projects/621"><img alt="Coverity Scan Build Status" src="https://scan.coverity.com/projects/621/badge.svg">
+<a href="https://scan.coverity.com/projects/621">
+<img alt="Coverity Scan Build Status" src="https://scan.coverity.com/projects/621/badge.svg">
 </a>
 <img alt="Coverity Scan Build Status" src="https://scan.coverity.com/projects/621/badge.svg">
 <a name="field-list"></a>
@@ -133,5 +134,4 @@ <h2><a href="#toc-entry-2">Field list</a></h2>
 </table>
 <p><a href="mailto:[email protected]">[email protected]</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> p {color:blue;} 

Diff for: test/markups/README.toc.asciidoc.html

@@ -43,4 +43,4 @@ <h3>Subsection B-2</h3>
 
 </div>
 </div>
-</div>
+</div>

Diff for: test/markups/README.toc.rst.html

@@ -1,5 +1,5 @@
 <div>
-<p>Contents</p>
+<p><a href="#top">Contents</a></p>
 <ul>
 <li>
 <a href="#introduction">1   Introduction</a><ul>
@@ -29,4 +29,4 @@ <h3>1.2   What is it good for?</h3>
 </ul>
 <p><strong>pycparser</strong> is unique in the sense that it's written in pure Python - a very
 high level language that's easy to experiment with and tweak. To people familiar
-with Lex and Yacc, <strong>pycparser</strong>'s code will be simple to understand.</p>
+with Lex and Yacc, <strong>pycparser</strong>'s code will be simple to understand.</p>