github-markup 1.3.1 → 1.3.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f884921d84f6c8e654ce8e27b3aa486c3a1e8a3f
-  data.tar.gz: 2a9ac570aa7d6b80fd6a9021c365f03dc78f224a
+  metadata.gz: a9e1194fe2c1586d23a61b036d048d4abf5e7502
+  data.tar.gz: 42776f3011796cad915a90ecb98ef1d48f1b95d1
 SHA512:
-  metadata.gz: 76e8ebe3c9a8d872eaa5645ba713b9605cef60e8e426952bc67edc433b47c6ed49158835d3239dfb6ce57e136cdd3880a21a533a1272725ea97f1423bebd41a3
-  data.tar.gz: 95364dfeac5dad9318c7b44897caf759c57c309a0752eb2ba23dfc59e911be90af31b8fce5ce651133699242ac0f4f7d056095a749a75fd12a7bf4d092cc19b8
+  metadata.gz: 6656db337e6b5447bc035d6d674721dae9080cca47665649fbec3201f224279d2c43bff2706527f2285020065e61eb266783321f79864d2cd71848bd2b6162e0
+  data.tar.gz: 480e3844ece342f876563345f5e5e3d458d9814bd46a42655528c36cf0bee398410f07fe6627e0519fba81da3b4304db85de1f97079ce8dfa08d621da3baffce

data/.travis.yml

@@ -1,8 +1,11 @@
+language: ruby
 before_install: sudo pip install docutils
 rvm:
   - 1.9.3
   - 2.0.0
   - 2.1.1
+  - jruby-19mode
+jdk:
+  - oraclejdk8
 notifications:
-  disabled: true
-bundler_args: --without development
+  email: false

data/Gemfile

@@ -1,10 +1,13 @@
 source "http://rubygems.org"
 gemspec
-gem "redcarpet"
+
+gem "posix-spawn", :platforms => :ruby
+gem "redcarpet", :platforms => :ruby
+gem "kramdown", :platforms => :jruby
 gem "RedCloth"
 gem "rdoc", "~>3.6"
 gem "org-ruby", "= 0.9.9"
 gem "creole", "~>0.3.6"
-gem "wikicloth", "=0.8.1"
+gem "wikicloth", "=0.8.1", :platforms => :ruby
 gem "asciidoctor", "= 0.1.4"
-gem "rake"
+gem "rake"

data/HISTORY.md

@@ -1,3 +1,10 @@
+## 1.3.2 (2015-02-17)
+
+* RST: Output code instead of tt for inline literals [#370](https://github.com/github/markup/pull/370)
+* RST: Add IDs to headers so that `.. contents` works with `.. sectnum` [#391](https://github.com/github/markup/pull/391)
+
+[Full changelog](https://github.com/github/markup/compare/v1.3.1...v1.3.2)
+
 ## 1.3.1 (2014-11-13)
 
 * Fix name error when trying to use newer versions of RedCarpet [#387](https://github.com/github/markup/pull/387)

data/README.md

@@ -19,7 +19,7 @@ you wish to run the library. You can also run `script/bootstrap` to fetch them a
 * [.rst](http://docutils.sourceforge.net/rst.html) -- `easy_install docutils`
 * [.asciidoc, .adoc, .asc](http://asciidoc.org/) -- `gem install asciidoctor` (http://asciidoctor.org)
 * [.pod](http://search.cpan.org/dist/perl/pod/perlpod.pod) -- `Pod::Simple::HTML`
-  comes with Perl >= 5.10. Lower versions should install Pod::Simple from CPAN.
+  comes with Perl >= 5.10. Lower versions should install [Pod::Simple](http://search.cpan.org/~dwheeler/Pod-Simple-3.28/lib/Pod/Simple.pod) from CPAN.
 
 Installation
 -----------

data/github-markup.gemspec

@@ -16,5 +16,9 @@ Gem::Specification.new do |s|
   s.test_files    = s.files.grep(%r{^(test|spec|features)/})
   s.require_paths = %w[lib]
 
-  s.add_dependency "posix-spawn", "~> 0.3.8"
+  s.add_development_dependency 'minitest', '~> 5.4.3'
+  s.add_development_dependency 'html-pipeline', '~> 1.0'
+  s.add_development_dependency 'sanitize', '~> 2.1.0'
+  s.add_development_dependency 'nokogiri', '~> 1.6.1'
+  s.add_development_dependency 'nokogiri-diff', '~> 0.2.0'
 end

data/lib/github-markup.rb

@@ -1,6 +1,6 @@
 module GitHub
   module Markup
-    VERSION = '1.3.1'
+    VERSION = '1.3.2'
     Version = VERSION
   end
 end

data/lib/github/commands/rest2html

@@ -66,12 +66,15 @@ class GitHubHTMLTranslator(HTMLTranslator):
     # see also: http://bit.ly/1exfq2h (warning! sourceforge link.)
     def depart_document(self, node):
         HTMLTranslator.depart_document(self, node)
-        self.html_body.pop(0)
-        self.html_body.pop()
+        self.html_body.pop(0) # pop the starting <div> off
+        self.html_body.pop() # pop the ending </div> off
 
     # technique for visiting sections, without generating additional divs
     # see also: http://bit.ly/NHtyRx
+    # the a is to support ::contents with ::sectnums: http://git.io/N1yC
     def visit_section(self, node):
+        id_attribute = node.attributes['ids'][0]
+        self.body.append('<a name="%s"></a>\n' % id_attribute)
         self.section_level += 1
 
     def depart_section(self, node):
@@ -86,6 +89,14 @@ class GitHubHTMLTranslator(HTMLTranslator):
         else:
             self.body.append(self.starttag(node, 'pre'))
 
+    # always wrap two-backtick rst inline literals in <code>, not <tt>
+    # this also avoids the generation of superfluous <span> tags
+    def visit_literal(self, node):
+        self.body.append(self.starttag(node, 'code', suffix=''))
+
+    def depart_literal(self, node):
+        self.body.append('</code>')
+
     def visit_table(self, node):
         classes = ' '.join(['docutils', self.settings.table_style]).strip()
         self.body.append(

data/lib/github/markup.rb

@@ -31,7 +31,7 @@ module GitHub
     end
 
     def command(command, regexp, &block)
-      if File.exists?(file = File.dirname(__FILE__) + "/commands/#{command}")
+      if File.exist?(file = File.dirname(__FILE__) + "/commands/#{command}")
         command = file
       end
 

data/lib/github/markup/command_implementation.rb

@@ -1,4 +1,9 @@
-require "posix-spawn"
+begin
+  require "posix-spawn"
+rescue LoadError
+  require "open3"
+end
+
 require "github/markup/implementation"
 
 module GitHub
@@ -31,15 +36,35 @@ module GitHub
           rendered
         end
       end
-
-      def execute(command, target)
-        spawn = POSIX::Spawn::Child.new(*command, :input => target)
-        if spawn.status.success?
-          spawn.out.gsub("\r", '').force_encoding(target.encoding)
-        else
-          raise CommandError.new(spawn.err.strip)
+      
+      if defined?(Posix::Spawn)
+        def execute(command, target)
+          spawn = POSIX::Spawn::Child.new(*command, :input => target)
+          if spawn.status.success?
+            sanitize(spawn.out, target.encoding)
+          else
+            raise CommandError.new(spawn.err.strip)
+          end
+        end
+      else
+        def execute(command, target)
+          output = Open3.popen3(*command) do |stdin, stdout, stderr, wait_thr|
+            stdin.puts target
+            stdin.close
+            if wait_thr.value.success?
+              stdout.readlines
+            else
+              raise CommandError.new(stderr.readlines.join('').strip)
+            end
+          end
+          sanitize(output.join(''), target.encoding)
         end
       end
+      
+      def sanitize(input, encoding)
+        input.gsub("\r", '').force_encoding(encoding)
+      end
+      
     end
   end
 end

data/test/fixtures/fail.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/env bash
+
+echo "failure message">&2 && false

data/test/markup_test.rb

@@ -3,19 +3,61 @@
 $LOAD_PATH.unshift File.dirname(__FILE__) + "/../lib"
 
 require 'github/markup'
-require 'test/unit'
+require 'minitest/autorun'
+require 'html/pipeline'
+require 'nokogiri'
+require 'nokogiri/diff'
+
+def normalize_html(text)
+  text.strip!
+  text.gsub!(/\s\s+/,' ')
+  text.gsub!(/\p{Pi}|\p{Pf}|"/u,'"')
+  text.gsub!("\u2026",'...')
+  text
+end
+
+def assert_html_equal(expected, actual, msg = nil)
+    assertion = Proc.new do
+      expected_doc = Nokogiri::HTML(expected) {|config| config.noblanks}
+      actual_doc   = Nokogiri::HTML(actual) {|config| config.noblanks}
+
+      expected_doc.search('//text()').each {|node| node.content = normalize_html node.content}
+      actual_doc.search('//text()').each {|node| node.content = normalize_html node.content}
+
+      ignore_changes = {"+" => Regexp.union(/^\s*id=".*"\s*$/), "-" => nil}
+      expected_doc.diff(actual_doc) do |change, node|
+        if change != ' ' && !node.blank? then
+          break unless node.to_html =~ ignore_changes[change]
+        end
+      end
+    end
+    assert(assertion.call, msg)
+end
+
+class MarkupTest < Minitest::Test
+  class MarkupFilter < HTML::Pipeline::Filter
+    def call
+      filename = context[:filename]
+      GitHub::Markup.render(filename, File.read(filename)).strip.force_encoding("utf-8")
+    end
+  end
+
+  Pipeline = HTML::Pipeline.new [
+    MarkupFilter,
+    HTML::Pipeline::SanitizationFilter
+  ]
 
-class MarkupTest < Test::Unit::TestCase
   Dir['test/markups/README.*'].each do |readme|
     next if readme =~ /html$/
     markup = readme.split('/').last.gsub(/^README\./, '')
 
     define_method "test_#{markup}" do
-      source = File.read(readme)
+      skip "Skipping MediaWiki test because wikicloth is currently not compatible with JRuby." if markup == "mediawiki" && RUBY_PLATFORM == "java"
 
+      source = File.read(readme)
       expected_file = "#{readme}.html"
       expected = File.read(expected_file).rstrip
-      actual = GitHub::Markup.render(readme, File.read(readme)).rstrip.force_encoding("utf-8")
+      actual = Pipeline.to_html(nil, :filename => readme)
 
       if source != expected
         assert(source != actual, "#{markup} did not render anything")
@@ -27,8 +69,8 @@ class MarkupTest < Test::Unit::TestCase
         f.read
       end
 
-      assert expected == actual, <<message
-#{File.basename expected_file}'s contents don't match command output:
+      assert_html_equal expected, actual, <<message
+#{File.basename expected_file}'s contents are not html equal to output:
 #{diff}
 message
     end
@@ -44,7 +86,7 @@ message
   end
 
   def test_raises_error_if_command_exits_non_zero
-    GitHub::Markup.command('echo "failure message">&2 && false', /fail/)
+    GitHub::Markup.command('test/fixtures/fail.sh', /fail/)
     assert GitHub::Markup.can_render?('README.fail')
     begin
       GitHub::Markup.render('README.fail', "stop swallowing errors")

data/test/markups/README.asciidoc.html

@@ -1,8 +1,8 @@
 <h1>Document Title</h1>
-<div class="sect1">
-<h2 id="first-section">First Section</h2>
-<div class="sectionbody">
-<div class="ulist">
+<div>
+<h2>First Section</h2>
+<div>
+<div>
 <ul>
 <li>
 <p>One</p>
@@ -14,26 +14,25 @@
 </div>
 </div>
 </div>
-<div class="sect1">
-<h2 id="second-section">Second Section</h2>
-<div class="sectionbody">
-<div class="admonitionblock note">
+<div>
+<h2>Second Section</h2>
+<div>
+<div>
 <table>
 <tr>
-<td class="icon">
-<div class="title">Note</div>
+<td>
+<div>Note</div>
 </td>
-<td class="content">
+<td>
 Here is some source code.
 </td>
 </tr>
 </table>
 </div>
-<div class="listingblock">
-<div class="content">
+<div>
+<div>
 <pre lang="ruby"><code>puts "Hello, World!"</code></pre>
 </div>
 </div>
 </div>
-</div>
-
+</div>

data/test/markups/README.creole.html

@@ -1,4 +1,8 @@
-<h1>H1</h1><h2>H2</h2><p>paragraph of text that will be turned into a paragraph element. It can go over several lines with line breaks, it will be turned into a contiguous paragraph element.</p><p>You can force a linebreak in your paragraph text<br/>thusly.</p><ul><li>a list element<ul><li>sub list element</li></ul></li><li>2nd list element</li></ul><pre>pre formatted text
+<h1>H1</h1><h2>H2</h2><p>paragraph of text that will be turned into a paragraph element. It can go over several lines with line breaks, it will be turned into a contiguous paragraph element.</p><p>You can force a linebreak in your paragraph text<br>thusly.</p><ul>
+<li>a list element<ul><li>sub list element</li></ul>
+</li>
+<li>2nd list element</li>
+</ul><pre>pre formatted text
 
 $ ls -la
 total 56

data/test/markups/README.litcoffee.html

@@ -6,13 +6,13 @@
 
 <p>comment comment</p>
 
-<pre><code>test &quot;basic literate CoffeeScript parsing&quot;, -&gt;
+<pre><code>test "basic literate CoffeeScript parsing", -&gt;
   ok yes
 </code></pre>
 
 <p>now with a...</p>
 
-<pre><code>test &quot;broken up indentation&quot;, -&gt;
+<pre><code>test "broken up indentation", -&gt;
 </code></pre>
 
 <p>... broken up ...</p>
@@ -27,7 +27,7 @@
 
 <p>Code must be separated from text by a blank line.</p>
 
-<pre><code>test &quot;code blocks must be preceded by a blank line&quot;, -&gt;
+<pre><code>test "code blocks must be preceded by a blank line", -&gt;
 </code></pre>
 
 <p>The next line is part of the text and will not be executed.
@@ -38,7 +38,7 @@
 
 <p>Code in <code>backticks is not parsed</code> and...</p>
 
-<pre><code>test &quot;comments in indented blocks work&quot;, -&gt;
+<pre><code>test "comments in indented blocks work", -&gt;
   do -&gt;
     do -&gt;
       # Regular comment.
@@ -62,5 +62,5 @@ like links and unordered lists, are fine:</p>
 
 <p>Tabs work too:</p>
 
-<p>test &quot;tabbed code&quot;, -&gt;
-    ok yes</p>
+<p>test "tabbed code", -&gt;
+    ok yes</p>

data/test/markups/README.markdown.html

@@ -1,4 +1,4 @@
 <ul>
 <li>One</li>
 <li>Two</li>
-</ul>
+</ul>

data/test/markups/README.mediawiki.html

@@ -1,19 +1,29 @@
-
-<p><a href="Home">&raquo; JRuby Project Wiki Home Page</a>
-<h1>Embedding JRuby</h1>
+<p><a href="Home">» JRuby Project Wiki Home Page</a>
+</p><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 id="toc" class="toc" summary="Contents"><tr><td><div id="toctitle"><h2>Table of Contents</h2></div><ul></li><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><li><a href="#Previous_Embedding_JRuby_Page">Previous Embedding JRuby Page</a></li><li><a href="#References">References</a></li></ul></td></tr></table>
-</p>
 
-<h1><a name="Red_Bridge_JRuby_Embed"></a><span class="mw-headline" id="Red_Bridge_JRuby_Embed">Red Bridge (JRuby Embed)</span></h1>
+<p></p><table summary="Contents"><tr><td>
+<div><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>
+</li>
+<li><a href="#Previous_Embedding_JRuby_Page">Previous Embedding JRuby Page</a></li>
+<li><a href="#References">References</a></li>
+</ul>
+</td></tr></table>
+
+
+<h1>
+<a name="Red_Bridge_JRuby_Embed"></a>Red Bridge (JRuby Embed)</h1>
 
 
 
 <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.
 </p>
 
-<h2><a name="Features_of_Red_Bridge"></a><span class="mw-headline" id="Features_of_Red_Bridge">Features of Red Bridge</span></h2>
+<h2>
+<a name="Features_of_Red_Bridge"></a>Features of Red Bridge</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.
@@ -23,19 +33,25 @@ Using Java from Ruby is JRuby's best-known feature---but you can also go in the
 
 
 
-<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>
+<p></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>
+
 <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>
 
-<h1><a name="Previous_Embedding_JRuby_Page"></a><span class="mw-headline" id="Previous_Embedding_JRuby_Page">Previous Embedding JRuby Page</span></h1>
+<h1>
+<a name="Previous_Embedding_JRuby_Page"></a>Previous Embedding JRuby Page</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 class="reference" id="cite_ref-1-0">[<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 href="JavaIntegration">legacy embedding</a><sup>[<a href="#cite_note-1">1</a>]</sup> page.
 </p>
 
-<h1><a name="References"></a><span class="mw-headline" id="References">References</span></h1>
+<h1>
+<a name="References"></a>References</h1>
 
 
-<p><ol><li id="cite_note-1"><b><a href="#cite_ref-1-0">^</a> </b> This link goes nowhere.</li></ol></p>
+<p></p><ol><li>
+<b><a href="#cite_ref-1-0">^</a> </b> This link goes nowhere.</li></ol>

data/test/markups/README.noformat.html

@@ -1,2 +1,2 @@
 * One
-* Two
+* Two

data/test/markups/README.org.html

@@ -1,38 +1,47 @@
-<h1 class="title">org-ruby</h1>
+<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><span class="heading-number heading-number-1">1</span> Description</h1>
+<h1>1 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 &#8220;content&#8221; from the orgfile as opposed to &#8220;metadata.&#8221;</p>
-<h1><span class="heading-number heading-number-1">2</span> History</h1>
-<h2><span class="heading-number heading-number-2">2.1</span> 2014-02-08: Version 0.9.0</h2>
+  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>
 <ul>
-  <li>Let&#8217;s make sure <code>#+INCLUDE:</code> is not supported</li>
+  <li>Let’s make sure <code>#+INCLUDE:</code> is not supported</li>
 </ul>
 <ul>
   <li>And confirm that syntax highlight is supported</li>
 </ul>
-<pre class="src" lang="ruby">
+<pre lang="ruby">
 module GitHub
   module Markup
-    VERSION = &#39;test&#39;
+    VERSION = 'test'
     Version = VERSION
   end
 end
 </pre>
-<h2><span class="heading-number heading-number-2">2.2</span> 2009-12-30: Version 0.5.1</h2>
+<h2>2.2 2009-12-30: Version 0.5.1</h2>
 <ul>
-  <li>Minor enhancement: Recognize lines starting with &#8220;:&#8221; as examples.</li>
+  <li>Minor enhancement: Recognize lines starting with “:” as examples.</li>
   <li>Minor enhancement: Recognize #+BEGIN_SRC as source blocks</li>
-  <li>Minor enhancement: Add &#8220;src&#8221; and &#8220;example&#8221; classes to &lt;pre&gt; blocks.</li>
+  <li>Minor enhancement: Add “src” and “example” classes to &lt;pre&gt; blocks.</li>
 </ul>
-<h2><span class="heading-number heading-number-2">2.3</span> 2009-12-30: Version 0.5.0</h2>
+<h2>2.3 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:
@@ -47,7 +56,7 @@ end
         the tree to export</li>
     </ul>
   </li>
-  <li>Rewrite &#8220;file:(blah).org&#8221; links to &#8220;http:(blah).html&#8221; links. This
+  <li>Rewrite “file:(blah).org” links to “http:(blah).html” 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:
@@ -56,7 +65,7 @@ end
     </ul>
   </li>
 </ul>
-<h2><span class="heading-number heading-number-2">2.4</span> 2009-12-29: Version 0.4.2</h2>
+<h2>2.4 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>
@@ -67,59 +76,59 @@ end
     </ul>
   </li>
 </ul>
-<h2><span class="heading-number heading-number-2">2.5</span> 2009-12-29: Version 0.4.1</h2>
+<h2>2.5 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><span class="heading-number heading-number-2">2.6</span> 2009-12-29: Version 0.4</h2>
+<h2>2.6 2009-12-29: Version 0.4</h2>
 <ul>
-  <li>The first thing output in HTML gets the class &#8220;title&#8221;</li>
+  <li>The first thing output in HTML gets the class “title”</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>&#8220;rake spec&#8221; wouldn&#8217;t work on Linux. Needed &#8220;require &#8216;rubygems&#8217;&#8221;.</li>
+      <li>“rake spec” wouldn’t work on Linux. Needed “require ‘rubygems’”.</li>
     </ul>
   </li>
 </ul>
-<h2><span class="heading-number heading-number-2">2.7</span> 2009-12-27: Version 0.3</h2>
+<h2>2.7 2009-12-27: Version 0.3</h2>
 <ul>
-  <li>Uses rubypants to get better typography (smart quotes, elipses, etc&#8230;).</li>
+  <li>Uses rubypants to get better typography (smart quotes, elipses, etc…).</li>
   <li>Fixed bugs:
     <ul>
       <li>Tables and lists did not get properly closed at the end of file</li>
-      <li>You couldn&#8217;t do inline formatting inside table cells</li>
+      <li>You couldn’t do inline formatting inside table cells</li>
       <li>Characters in PRE blocks were not HTML escaped.</li>
     </ul>
   </li>
 </ul>
-<h2><span class="heading-number heading-number-2">2.8</span> 2009-12-26: Version 0.2</h2>
+<h2>2.8 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>, <span style="text-decoration:underline;">underline</span>, <del>strikethrough</del>.</li>
+    <i>italic</i>, <code>code</code>, <code>verbatim</code>, underline, <del>strikethrough</del>.</li>
   <li>Lots of refactoring to make the code more maintainable.</li>
 </ul>
-<h2><span class="heading-number heading-number-2">2.9</span> 2009-12-23: Version 0.1</h2>
+<h2>2.9 2009-12-23: Version 0.1</h2>
 <ul>
   <li>Added support for block code, like this:
-    <pre class="example">
+    <pre>
   def flush!
-  @logger.debug &quot;FLUSH ==========&gt; #{@output_type}&quot;
+  @logger.debug "FLUSH ==========&gt; #{@output_type}"
   if (@output_type == :blank) then
-    @output &lt;&lt; &quot;\n&quot;
+    @output &lt;&lt; "\n"
   elsif (@buffer.length &gt; 0) then
     if @cancel_modifier then
-      @output &lt;&lt; &quot;p. &quot; if @output_type == :paragraph
+      @output &lt;&lt; "p. " 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; &quot;\n&quot;
+    @output &lt;&lt; @buffer.textile_substitution &lt;&lt; "\n"
   end
-  @buffer = &quot;&quot;
+  @buffer = ""
 end
     </pre>
   </li>
@@ -127,4 +136,4 @@ end
     greatly simplified a lot of the messiness of <code>textile</code>
     conversion.</li>
   <li>Added support for line breaks within list items.</li>
-</ul>
+</ul>

data/test/markups/README.pod.html

@@ -1,20 +1,14 @@
-<a name='___top' class='dummyTopAnchor' ></a>
+<a name="___top"></a>
 
-<h1><a class='u' href='#___top' title='click to go to top of document'
-name="Matrixy"
->Matrixy</a></h1>
+<h1><a href="#___top" title="click to go to top of document" name="Matrixy">Matrixy</a></h1>
 
-<h2><a class='u' href='#___top' title='click to go to top of document'
-name="INTRODUCTION"
->INTRODUCTION</a></h2>
+<h2><a href="#___top" title="click to go to top of document" name="INTRODUCTION">INTRODUCTION</a></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><a class='u' href='#___top' title='click to go to top of document'
-name="ABOUT"
->ABOUT</a></h2>
+<h2><a href="#___top" title="click to go to top of document" name="ABOUT">ABOUT</a></h2>
 
 <p>Primary goals are:</p>
 
@@ -22,9 +16,7 @@ name="ABOUT"
 <p>=item* Create a working compiler that understands the majority of the MATLAB/Octave programming language.</p>
 </blockquote>
 
-<h2><a class='u' href='#___top' title='click to go to top of document'
-name="IMPLEMENTATION"
->IMPLEMENTATION</a></h2>
+<h2><a href="#___top" title="click to go to top of document" name="IMPLEMENTATION">IMPLEMENTATION</a></h2>
 
 <p>This project is broken into three primary components:</p>
 
@@ -42,7 +34,7 @@ several helper functions used by the parser are located in <code>src/internals</
 These functions are,
 currently,
 written primarily in PIR.
-Function names prefixed with an underscore are &#34;private&#34; functions for use with the parser.
+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>
@@ -51,15 +43,11 @@ These are also separated into different namespaces depending on visibility and u
 or mostly M with some inline PIR code in <code>toolbox/</code>.</p>
 </blockquote>
 
-<h2><a class='u' href='#___top' title='click to go to top of document'
-name="DEPENDENCIES"
->DEPENDENCIES</a></h2>
+<h2><a href="#___top" title="click to go to top of document" name="DEPENDENCIES">DEPENDENCIES</a></h2>
 
 <p>Matrixy depends on these dependencies:</p>
 
-<h3><a class='u' href='#___top' title='click to go to top of document'
-name="Parrot"
->Parrot</a></h3>
+<h3><a href="#___top" title="click to go to top of document" name="Parrot">Parrot</a></h3>
 
 <p>To get a proper version of Parrot to build Matrixy,
 you will need to check out and build Parrot from source:</p>
@@ -67,42 +55,31 @@ you will need to check out and build Parrot from source:</p>
 <pre>    svn co http://svn.parrot.org/parrot/trunk parrot
     cd parrot
     perl Configure.pl
-    make &#38;&#38; make test &#38;&#38; make install-dev</pre>
+    make &amp;&amp; make test &amp;&amp; make install-dev</pre>
 
-<h3><a class='u' href='#___top' title='click to go to top of document'
-name="Parrot-Linear-Algebra"
->Parrot-Linear-Algebra</a></h3>
+<h3><a href="#___top" title="click to go to top of document" name="Parrot-Linear-Algebra">Parrot-Linear-Algebra</a></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><a class='u' href='#___top' title='click to go to top of document'
-name="BUILDING"
->BUILDING</a></h2>
+<h2><a href="#___top" title="click to go to top of document" name="BUILDING">BUILDING</a></h2>
 
 <p>Once all dependencies are in place, you can build Matrixy using this sequence of commands:</p>
 
 <pre>    perl Configure.pl
     nmake test</pre>
 
-<h2><a class='u' href='#___top' title='click to go to top of document'
-name="TODO"
->TODO</a></h2>
+<h2><a href="#___top" title="click to go to top of document" name="TODO">TODO</a></h2>
 
 <pre>    * Parser
     * Standard Builtins
     * Test against Octave Test Suite.</pre>
 
-<h2><a class='u' href='#___top' title='click to go to top of document'
-name="BUGS"
->BUGS</a></h2>
+<h2><a href="#___top" title="click to go to top of document" name="BUGS">BUGS</a></h2>
 
 <p>Lots!</p>
 
-<h2><a class='u' href='#___top' title='click to go to top of document'
-name="CONTACT"
->CONTACT</a></h2>
+<h2><a href="#___top" title="click to go to top of document" name="CONTACT">CONTACT</a></h2>
 
 <p>If you need to contact the Matrixy team, go to the project home page at:</p>
 
-<p>www.github.com\Whiteknight\matrixy</p>
-
+<p>www.github.com\Whiteknight\matrixy</p>

data/test/markups/README.rdoc.html

@@ -1,11 +1,12 @@
-<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 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 href="rawr.html">relative link</a>.  So is this: <a href="rawr.html">rawr.html</a></p>

data/test/markups/README.rmd.html

@@ -3,4 +3,4 @@
 <ul>
 <li>One</li>
 <li>Two</li>
-</ul>
+</ul>

data/test/markups/README.rst.html

@@ -1,61 +1,75 @@
-<h1 class="title">Header 1</h1>
-<h2 class="subtitle" id="subtitle">Subtitle</h2>
+<h1>Header 1</h1>
+<h2>Subtitle</h2>
 <p>Example text.</p>
-<div class="contents topic" id="table-of-contents">
-<p class="topic-title first">Table of Contents</p>
-<ul class="simple">
-<li><a class="reference internal" href="#header-2" id="id1">Header 2</a></li>
-<li><a class="reference internal" href="#field-list" id="id2">Field list</a></li>
+<div>
+<p>Table of Contents</p>
+<ul>
+<li><a href="#header-2">Header 2</a></li>
+<li><a href="#field-list">Field list</a></li>
 </ul>
 </div>
-<h2><a class="toc-backref" href="#id1">Header 2</a></h2>
-<ol class="arabic simple">
-<li>Blah blah <tt class="docutils literal">code</tt> blah</li>
-<li>More <tt class="docutils literal">code</tt>, hooray</li>
+<a name="header-2"></a>
+<h2><a href="#id1">Header 2</a></h2>
+<ol>
+<li>Blah blah <code>code</code> blah</li>
+<li>More <code>code</code>, hooray</li>
 <li>Somé UTF-8°</li>
 </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 class="docutils">
-<colgroup>
-<col width="19%" />
-<col width="81%" />
-</colgroup>
+<table>
+
+
+
+
 <tbody valign="top">
-<tr><td>Travis</td>
-<td><a class="reference external" href="http://travis-ci.org/tony/pullv">http://travis-ci.org/tony/pullv</a></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>
-<td><a class="reference external" href="http://pullv.rtfd.org">http://pullv.rtfd.org</a></td>
+<tr>
+<td>Docs</td>
+<td><a href="http://pullv.rtfd.org">http://pullv.rtfd.org</a></td>
 </tr>
-<tr><td>API</td>
-<td><a class="reference external" href="http://pullv.readthedocs.org/en/latest/api.html">http://pullv.readthedocs.org/en/latest/api.html</a></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>
-<td><a class="reference external" href="https://github.com/tony/pullv/issues">https://github.com/tony/pullv/issues</a></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>
-<td><a class="reference external" href="https://github.com/tony/pullv">https://github.com/tony/pullv</a></td>
+<tr>
+<td>Source</td>
+<td><a href="https://github.com/tony/pullv">https://github.com/tony/pullv</a></td>
 </tr>
 </tbody>
 </table>
-<a class="reference external image-reference" 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">
-<h2><a class="toc-backref" href="#id2">Field list</a></h2>
-<table class="docutils field-list" frame="void" rules="none">
-<col class="field-name" />
-<col class="field-body" />
+<a name="field-list"></a>
+<h2><a href="#id2">Field list</a></h2>
+<table frame="void" rules="none">
+
+
 <tbody valign="top">
-<tr class="field"><th class="field-name" colspan="2">123456789 123456789 123456789 123456789 123456789 1:</th></tr>
-<tr class="field"><td>&nbsp;</td><td class="field-body">Uh-oh! This name is too long!</td>
+<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>
-<tr class="field"><th class="field-name">123456789 123456789 123456789 123456789 1234567890:</th><td class="field-body">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 class="field"><th class="field-name">123456789 12345:</th><td class="field-body">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 class="field"><th class="field-name">123456789 1234:</th><td class="field-body">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>
-
+</table>

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

@@ -1,31 +1,37 @@
-<h1 class="title">Header 1</h1>
+<h1>Header 1</h1>
 <p>Example text.</p>
+<a name="header-2"></a>
 <h2>Header 2</h2>
-<ol class="arabic simple">
-<li>Blah blah <tt class="docutils literal">code</tt> blah</li>
-<li>More <tt class="docutils literal">code</tt>, hooray</li>
+<ol>
+<li>Blah blah <code>code</code> blah</li>
+<li>More <code>code</code>, hooray</li>
 <li>Somé UTF-8°</li>
 </ol>
-<table class="docutils">
-<colgroup>
-<col width="19%" />
-<col width="81%" />
-</colgroup>
+<table>
+
+
+
+
 <tbody valign="top">
-<tr><td>Travis</td>
-<td><a class="reference external" href="http://travis-ci.org/tony/pullv">http://travis-ci.org/tony/pullv</a></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>
-<td><a class="reference external" href="http://pullv.rtfd.org">http://pullv.rtfd.org</a></td>
+<tr>
+<td>Docs</td>
+<td><a href="http://pullv.rtfd.org">http://pullv.rtfd.org</a></td>
 </tr>
-<tr><td>API</td>
-<td><a class="reference external" href="http://pullv.readthedocs.org/en/latest/api.html">http://pullv.readthedocs.org/en/latest/api.html</a></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>
-<td><a class="reference external" href="https://github.com/tony/pullv/issues">https://github.com/tony/pullv/issues</a></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>
-<td><a class="reference external" href="https://github.com/tony/pullv">https://github.com/tony/pullv</a></td>
+<tr>
+<td>Source</td>
+<td><a href="https://github.com/tony/pullv">https://github.com/tony/pullv</a></td>
 </tr>
 </tbody>
 </table>

data/test/markups/README.toc.rst

@@ -0,0 +1,30 @@
+.. contents::
+    :backlinks: none
+
+.. sectnum::
+
+Introduction
+============
+
+What is pycparser?
+------------------
+
+**pycparser** 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.
+
+What is it good for?
+--------------------
+
+Anything that needs C code to be parsed. The following are some uses for
+**pycparser**, taken from real user reports:
+
+* C code obfuscator
+* Front-end for various specialized C compilers
+* Static code checker
+* Automatic unit-test discovery
+* Adding specialized extensions to the C language
+
+**pycparser** 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, **pycparser**'s code will be simple to understand.

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

@@ -0,0 +1,32 @@
+<div>
+<p>Contents</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>
+</ul>
+</li>
+</ul>
+</div>
+<a name="introduction"></a>
+<h2>1   Introduction</h2>
+<a name="what-is-pycparser"></a>
+<h3>1.1   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>
+<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>
+<li>C code obfuscator</li>
+<li>Front-end for various specialized C compilers</li>
+<li>Static code checker</li>
+<li>Automatic unit-test discovery</li>
+<li>Adding specialized extensions to the C language</li>
+</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>

data/test/markups/README.txt.html

@@ -1,2 +1,2 @@
 * One
-* Two
+* Two

metadata

@@ -1,29 +1,85 @@
 --- !ruby/object:Gem::Specification
 name: github-markup
 version: !ruby/object:Gem::Version
-  version: 1.3.1
+  version: 1.3.2
 platform: ruby
 authors:
 - Chris Wanstrath
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-11-13 00:00:00.000000000 Z
+date: 2015-02-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: posix-spawn
+  name: minitest
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.3.8
-  type: :runtime
+        version: 5.4.3
+  type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.3.8
+        version: 5.4.3
+- !ruby/object:Gem::Dependency
+  name: html-pipeline
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+- !ruby/object:Gem::Dependency
+  name: sanitize
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.1.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.1.0
+- !ruby/object:Gem::Dependency
+  name: nokogiri
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.1
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.1
+- !ruby/object:Gem::Dependency
+  name: nokogiri-diff
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.2.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.2.0
 description: This gem is used by GitHub to render any fancy markup such as Markdown,
   Textile, Org-Mode, etc. Fork it and add your own!
 email: chris@ozmm.org
@@ -54,6 +110,7 @@ files:
 - lib/github/markups.rb
 - script/bootstrap
 - script/cibuild
+- test/fixtures/fail.sh
 - test/markup_test.rb
 - test/markups/README.asciidoc
 - test/markups/README.asciidoc.html
@@ -81,6 +138,8 @@ files:
 - test/markups/README.rst.txt.html
 - test/markups/README.textile
 - test/markups/README.textile.html
+- test/markups/README.toc.rst
+- test/markups/README.toc.rst.html
 - test/markups/README.txt
 - test/markups/README.txt.html
 homepage: https://github.com/github/markup
@@ -108,6 +167,7 @@ signing_key:
 specification_version: 4
 summary: The code GitHub uses to render README.markup
 test_files:
+- test/fixtures/fail.sh
 - test/markup_test.rb
 - test/markups/README.asciidoc
 - test/markups/README.asciidoc.html
@@ -135,5 +195,7 @@ test_files:
 - test/markups/README.rst.txt.html
 - test/markups/README.textile
 - test/markups/README.textile.html
+- test/markups/README.toc.rst
+- test/markups/README.toc.rst.html
 - test/markups/README.txt
 - test/markups/README.txt.html