RedCloth 3.0.4 → 4.0.0

data/tests/lists.yml

@@ -1,77 +0,0 @@
---- # Bret Pettichord, Thanks.
-in: |-
-  * first line
-  * second
-    line
-  * third line
-out: |-
-  <ul>
-  	<li>first line</li>
-  		<li>second
-    line</li>
-  		<li>third line</li>
-  	</ul>
----
-in: |-
-  p. start
-
-  * one
-  and one
-  * two
-  and two
-  * three
-
-  p. end
-out: |-
-  <p>start</p>
-  	<ul>
-  	<li>one
-  and one</li>
-  		<li>two
-  and two</li>
-  		<li>three</li>
-  	</ul>
-  
-  	<p>end</p>
----
-in: |-
-  Funky:
-
-  * Testing
-  *# number
-  *##* bullet
-  *# number
-  *# number
-  yeah number
-  #* bullet
-  *** okay
-  ****# what
-
-
-out: |-
-  <p>Funky:</p>
-  	<ul>
-  	<li>Testing
-  	<ol>
-  	<li>number
-  	<ul>
-  	<li>bullet</li>
-  	</ul>
-  	</li>
-  		<li>number</li>
-  		<li>number
-  yeah number</li>
-  	<ul>
-  	<li>bullet
-  	<ul>
-  	<li>okay
-  	<ol>
-  	<li>what</li>
-  	</ul></li>
-  	</ol></li>
-  	</ul></li>
-  	</ul></li>
-  	</ol>
----
-in: "* command run: @time ruby run-tests.rb > toto@"
-out: "<ul>\n\t<li>command run: <code>time ruby run-tests.rb &gt; toto</code></li>\n\t</ul>"

data/tests/markdown.yml

@@ -1,218 +0,0 @@
-in: |
-  This is a regular paragraph.
-
-  <table>
-      <tr>
-          <td>Foo</td>
-      </tr>
-  </table>
-  
-  This is another regular paragraph.
-out: |-
-  <p>This is a regular paragraph.</p>
-
-
-  <table>
-      <tr>
-          <td>Foo</td>
-      </tr>
-  </table>
-  	<p>This is another regular paragraph.</p>
----
-in: '"Larry Bird":http://images.google.com/images?num=30&q=larry+bird'
-out: '<p>"Larry Bird":http://images.google.com/images?num=30&#38;q=larry+bird</p>'
----
-in: '&copy;'
-out: <p>&copy;</p>
----
-in: AT&T
-out: <p>AT&#38;T</p>
-
-# We don't do this.
-# ---
-# in: 4 < 5
-# out: 4 &lt; 5
----
-in: |
-  This is an H1
-  =============
-  
-  This is an H2
-  -------------
-out: |-
-  <h1>This is an H1</h1>
-
-  <h2>This is an H2</h2>
----
-in: |
-  # This is an H1
-  
-  ## This is an H2
-  
-  ###### This is an H6
-out: |-
-  <h1>This is an H1</h1>
-
-  <h2>This is an H2</h2>
-
-  <h6>This is an H6</h6>
----
-in: |
-  > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
-  > consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
-  > Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
-  > 
-  > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
-  > id sem consectetuer libero luctus adipiscing.
-out: |-
-  <blockquote>
-  	<p>This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
-  	consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
-  	Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.</p>
-  
-  	<p>Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
-  	id sem consectetuer libero luctus adipiscing.</p>
-  
-  </blockquote>
----
-in: |
-  > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
-  consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
-  Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
-  >
-  > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
-  id sem consectetuer libero luctus adipiscing.
-out: |-
-  <blockquote>
-  	<p>This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
-  	consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
-  	Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.</p>
-  
-  	<p>Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
-  	id sem consectetuer libero luctus adipiscing.</p>
-  
-  </blockquote>
----
-in: |
-  > This is the first level of quoting.
-  >
-  > > This is nested blockquote.
-  >
-  > Back to the first level.
-out: |-
-  <blockquote>
-  	<p>This is the first level of quoting.</p>
-  	<blockquote>
-  	<p>This is nested blockquote.</p>
-  
-  	</blockquote>
-  
-  
-  
-  	<p>Back to the first level.</p>
-  
-  </blockquote>
----
-in: |
-  > ## This is a header.
-  > 
-  > 1.   This is the first list item.
-  > 2.   This is the second list item.
-  > 
-  > Here's some example code:
-  > 
-  >     return shell_exec("echo $input | $markdown_script");
-out: |-
-  <blockquote>
-  	<h2>This is a header.</h2>
-  
-  
-  
-  	<p>1.   This is the first list item.
-  	2.   This is the second list item.</p>
-  
-  	<p>Here's some example code:</p>
-  	<pre><code>return shell_exec("echo $input | $markdown_script");</code></pre>
-  
-  </blockquote>
----
-in: |
-  * * *
-
-  ***
-  
-  *****
-  
-  - - -
-  
-  ---------------------------------------
-  
-  _ _ _
-out: |-
-  <hr />
-
-  <hr />
-
-  <hr />
-
-  <hr />
-
-  <hr />
-
-  <hr />
----
-in: |
-  This is [an example](http://example.com/ "Title") inline link.
-
-  [This link](http://example.net/) has no title attribute.
-out: |-
-  <p>This is <a href="http://example.com/" title="Title">an example</a> inline link.</p>
-
-  	<p><a href="http://example.net/">This link</a> has no title attribute.</p>
----
-in: See my [About](/about/) page for details.
-out: <p>See my <a href="/about/">About</a> page for details.</p>
----
-in: |
-  This is [an example][id] reference-style link.
-
-  This is [an example] [id] reference-style link.
-
-  [id]: http://example.com/  "Optional Title Here"
-out: |-
-  <p>This is <a href="http://example.com/" title="Optional Title Here">an example</a> reference-style link.</p>
-  
-  	<p>This is <a href="http://example.com/" title="Optional Title Here">an example</a> reference-style link.</p>
----
-in: |
-  [Google][]
-  [Google]: http://google.com/
-out: <p><a href="http://google.com/">Google</a></p>
----
-in: |
-  Visit [Daring Fireball][] for more information.
-  [Daring Fireball]: http://daringfireball.net/
-out: <p>Visit <a href="http://daringfireball.net/">Daring Fireball</a> for more information.</p>
----
-in: |
-  I get 10 times more traffic from [Google] [1] than from
-  [Yahoo] [2] or [MSN] [3].
-  
-    [1]: http://google.com/        "Google"
-    [2]: http://search.yahoo.com/  "Yahoo Search"
-    [3]: http://search.msn.com/    "MSN Search"
-
-out: |-
-  <p>I get 10 times more traffic from <a href="http://google.com/" title="Google">Google</a> than from
-  <a href="http://search.yahoo.com/" title="Yahoo Search">Yahoo</a> or <a href="http://search.msn.com/" title="MSN Search">MSN</a>.</p>
----
-in: |
-  I get 10 times more traffic from [Google][] than from
-  [Yahoo][] or [MSN][].
-  
-    [google]: http://google.com/        "Google"
-    [yahoo]:  http://search.yahoo.com/  "Yahoo Search"
-    [msn]:    http://search.msn.com/    "MSN Search"
-out: |-
-  <p>I get 10 times more traffic from <a href="http://google.com/" title="Google">Google</a> than from
-  <a href="http://search.yahoo.com/" title="Yahoo Search">Yahoo</a> or <a href="http://search.msn.com/" title="MSN Search">MSN</a>.</p>

data/tests/poignant.yml

@@ -1,64 +0,0 @@
---- # Tests from the (Poignant Guide)
-in: >
-  h3. False
-
-
-  !<i/blix-neg.gif(Shape of a cat.)!
-
-
-  _The cat Trady Blix.  Frozen in emptiness.  Immaculate whiskers rigid.  Placid
-  eyes of lake.  Tail of warm icicle.  Sponsored by a Very Powerful Pause Button._
-
-
-  The darkness surrounding Blix can be called *negative space*.  Hang on to that phrase.
-  Let it suggest that the emptiness has a negative connotation.  In a similar way,
-  @nil@ has a slightly sour note that it whistles.
-
-
-  Generally speaking, everything in Ruby has a positive charge to it.  This spark
-  flows through strings, numbers, regexps, all of it.  Only two keywords wear a
-  shady cloak: @nil@ and @false@ draggin us down.
-
-
-  You can test that charge with an @if@ keyword.  It looks very much like the
-  @do@ blocks we saw in the last chapter, in that both end with an @end@.
-
-
-  <pre>
-    if plastic_cup
-      print "Plastic cup is on the up 'n' up!"
-    end
-  </pre>
-
-
-  If @plastic_cup@ contains either @nil@ or @false@, you won't see anything print
-  to the screen.  They're not on the @if@ guest list.  So @if@ isn't going to run
-  any of the code it's protecting.
-
-
-  But @nil@ and @false@ need not walk away in shame.  They may be of questionable
-  character, but @unless@ runs a smaller establishment that caters to the bedraggled.
-  The @unless@ keyword has a policy of only allowing those with a negative charge in.
-  Who are: @nil@ and @false@.
-  
-
-  <pre>
-    unless plastic_cup
-      print "Plastic cup is on the down low."
-    end
-  </pre>
-
-
-  You can also use @if@ and @unless@ at the end of a single line of code, if that's
-  all that is being protected.
-
-
-  <pre>
-    print "Yeah, plastic cup is up again!" if plastic_cup
-    print "Hardly. It's down." unless plastic_cup
-  </pre>
-
-
-  Now that you've met @false@, I'm sure you can see what's on next.
-
-out: "<h3>False</h3>\n\n\t<p style=\"float:left\"><img src=\"i/blix-neg.gif\" title=\"Shape of a cat.\" alt=\"Shape of a cat.\" /></p>\n\n\t<p><em>The cat Trady Blix.  Frozen in emptiness.  Immaculate whiskers rigid.  Placid eyes of lake.  Tail of warm icicle.  Sponsored by a Very Powerful Pause Button.</em></p>\n\n\t<p>The darkness surrounding Blix can be called <strong>negative space</strong>.  Hang on to that phrase. Let it suggest that the emptiness has a negative connotation.  In a similar way, <code>nil</code> has a slightly sour note that it whistles.</p>\n\n\t<p>Generally speaking, everything in Ruby has a positive charge to it.  This spark flows through strings, numbers, regexps, all of it.  Only two keywords wear a shady cloak: <code>nil</code> and <code>false</code> draggin us down.</p>\n\n\t<p>You can test that charge with an <code>if</code> keyword.  It looks very much like the <code>do</code> blocks we saw in the last chapter, in that both end with an <code>end</code>.</p>\n\n\n<pre>\n  if plastic_cup\n    print \"Plastic cup is on the up 'n' up!\" \n  end\n</pre>\n\t<p>If <code>plastic_cup</code> contains either <code>nil</code> or <code>false</code>, you won&#8217;t see anything print to the screen.  They&#8217;re not on the <code>if</code> guest list.  So <code>if</code> isn&#8217;t going to run any of the code it&#8217;s protecting.</p>\n\n\t<p>But <code>nil</code> and <code>false</code> need not walk away in shame.  They may be of questionable character, but <code>unless</code> runs a smaller establishment that caters to the bedraggled. The <code>unless</code> keyword has a policy of only allowing those with a negative charge in. Who are: <code>nil</code> and <code>false</code>.</p>\n\n\n<pre>\n  unless plastic_cup\n    print \"Plastic cup is on the down low.\" \n  end\n</pre>\n\t<p>You can also use <code>if</code> and <code>unless</code> at the end of a single line of code, if that&#8217;s all that is being protected.</p>\n\n\n<pre>\n  print \"Yeah, plastic cup is up again!\" if plastic_cup\n  print \"Hardly. It's down.\" unless plastic_cup\n</pre>\n\t<p>Now that you&#8217;ve met <code>false</code>, I&#8217;m sure you can see what&#8217;s on next.</p>"

data/tests/table.yml

@@ -1,198 +0,0 @@
-in: |
-  {background:#ddd}. |S|Target|Complete|App|Milestone|
-  |!/i/g.gif!|11/18/04|11/18/04|070|XML spec complete|
-  |!/i/g.gif!|11/29/04|11/29/04|011|XML spec complete (KH is on schedule)|
-  |!/i/g.gif!|11/29/04|11/29/04|051|XML spec complete (KH is on schedule)|
-  |!/i/g.gif!|11/29/04|11/29/04|081|XML spec complete (KH is on schedule)|
-  |!/i/g.gif!|11/19/04|11/22/04|070|Preprocessor complete|
-  |!/i/g.gif!|11/22/04|11/22/04|070|Dialog pass 1 builds an index file|
-  |!/i/g.gif!|11/24/04|11/24/04|070|Dialog pass 2 98% complete|
-  |!/i/g.gif!|11/30/04|11/30/04|070|Feature complete. Passes end-to-end smoke test.|
-  |!/i/g.gif!|11/30/04|11/30/04|011|Preprocessor updates complete|
-  |!/i/g.gif!|11/30/04|11/30/04|051|Preprocessor updates complete|
-  |!/i/g.gif!|11/30/04|11/29/04|081|Preprocessor updates complete|
-  |!/i/w.gif!|12/02/04|.|011|Dialog pass 1 and 2 complete (98+%)|
-  |!/i/w.gif!|12/02/04|.|051|Dialog pass 1 and 2 complete (98+%)|
-  |!/i/w.gif!|12/02/04|.|081|Dialog pass 1 and 2 complete (98+%)|
-  |!/i/w.gif!|12/03/04|.|011|Feature complete|
-  |!/i/w.gif!|12/03/04|.|051|Feature complete|
-  |!/i/w.gif!|12/03/04|.|081|Feature complete|
-  |!/i/w.gif!|12/10/04|.|011|Deployed to Napa test workstation. Passes smoke test.|
-  |!/i/w.gif!|12/10/04|.|051|Deployed to Napa test workstation. Passes smoke test.|
-  |!/i/w.gif!|12/10/04|.|081|Deployed to Napa test workstation. Passes smoke test.|
-  |!/i/w.gif!|12/10/04|.|070|Deployed to Napa test workstation. Passes smoke test.|
-  |!/i/w.gif!|12/17/04|.|011|System testing complete. Begin testing with live customer data.|
-  |!/i/w.gif!|12/17/04|.|051|System testing complete. Begin testing with live customer data.|
-  |!/i/w.gif!|12/17/04|.|081|System testing complete. Begin testing with live customer data.|
-  |!/i/w.gif!|12/17/04|.|070|System testing complete. Begin testing with live customer data.|
-out: |-
-  <table>
-  		<tr style="background:#ddd;">
-  			<td>S</td>
-  			<td>Target</td>
-  			<td>Complete</td>
-  			<td>App</td>
-  			<td>Milestone</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/18/04</td>
-  			<td>11/18/04</td>
-  			<td>070</td>
-  			<td><span class="caps">XML</span> spec complete</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/29/04</td>
-  			<td>11/29/04</td>
-  			<td>011</td>
-  			<td><span class="caps">XML</span> spec complete (KH is on schedule)</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/29/04</td>
-  			<td>11/29/04</td>
-  			<td>051</td>
-  			<td><span class="caps">XML</span> spec complete (KH is on schedule)</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/29/04</td>
-  			<td>11/29/04</td>
-  			<td>081</td>
-  			<td><span class="caps">XML</span> spec complete (KH is on schedule)</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/19/04</td>
-  			<td>11/22/04</td>
-  			<td>070</td>
-  			<td>Preprocessor complete</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/22/04</td>
-  			<td>11/22/04</td>
-  			<td>070</td>
-  			<td>Dialog pass 1 builds an index file</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/24/04</td>
-  			<td>11/24/04</td>
-  			<td>070</td>
-  			<td>Dialog pass 2 98% complete</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/30/04</td>
-  			<td>11/30/04</td>
-  			<td>070</td>
-  			<td>Feature complete. Passes end-to-end smoke test.</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/30/04</td>
-  			<td>11/30/04</td>
-  			<td>011</td>
-  			<td>Preprocessor updates complete</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/30/04</td>
-  			<td>11/30/04</td>
-  			<td>051</td>
-  			<td>Preprocessor updates complete</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/g.gif" alt="" /></td>
-  			<td>11/30/04</td>
-  			<td>11/29/04</td>
-  			<td>081</td>
-  			<td>Preprocessor updates complete</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/02/04</td>
-  			<td>011</td>
-  			<td>Dialog pass 1 and 2 complete (98+%)</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/02/04</td>
-  			<td>051</td>
-  			<td>Dialog pass 1 and 2 complete (98+%)</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/02/04</td>
-  			<td>081</td>
-  			<td>Dialog pass 1 and 2 complete (98+%)</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/03/04</td>
-  			<td>011</td>
-  			<td>Feature complete</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/03/04</td>
-  			<td>051</td>
-  			<td>Feature complete</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/03/04</td>
-  			<td>081</td>
-  			<td>Feature complete</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/10/04</td>
-  			<td>011</td>
-  			<td>Deployed to Napa test workstation. Passes smoke test.</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/10/04</td>
-  			<td>051</td>
-  			<td>Deployed to Napa test workstation. Passes smoke test.</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/10/04</td>
-  			<td>081</td>
-  			<td>Deployed to Napa test workstation. Passes smoke test.</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/10/04</td>
-  			<td>070</td>
-  			<td>Deployed to Napa test workstation. Passes smoke test.</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/17/04</td>
-  			<td>011</td>
-  			<td>System testing complete. Begin testing with live customer data.</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/17/04</td>
-  			<td>051</td>
-  			<td>System testing complete. Begin testing with live customer data.</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/17/04</td>
-  			<td>081</td>
-  			<td>System testing complete. Begin testing with live customer data.</td>
-  		</tr>
-  		<tr>
-  			<td><img src="/i/w.gif" alt="" /></td>
-  			<td>12/17/04</td>
-  			<td>070</td>
-  			<td>System testing complete. Begin testing with live customer data.</td>
-  		</tr>
-  	</table>