parity-RedCloth 4.2.9

data/spec/fixtures/lists.yml

@@ -0,0 +1,462 @@
+---
+name: code in bullet list
+in: "* command run: @time ruby run-tests.rb > toto@"
+html: "<ul>\n\t<li>command run: <code>time ruby run-tests.rb &gt; toto</code></li>\n</ul>"
+--- # Bret Pettichord, Thanks.
+name: hard break in list
+in: |-
+  * first line
+  * second
+    line
+  * third line
+html: |-
+  <ul>
+  	<li>first line</li>
+  	<li>second<br />
+    line</li>
+  	<li>third line</li>
+  </ul>
+---
+name: mixed nesting
+in: |-
+  * bullet
+  *# number
+  *# number
+  *#* bullet
+  *# number
+  *# number with
+  a break
+  * bullet
+  ** okay
+html: |-
+  <ul>
+  	<li>bullet
+  	<ol>
+  		<li>number</li>
+  		<li>number
+  		<ul>
+  			<li>bullet</li>
+  		</ul></li>
+  		<li>number</li>
+  		<li>number with<br />
+  a break</li>
+  	</ol></li>
+  	<li>bullet
+  	<ul>
+  		<li>okay</li>
+  	</ul></li>
+  </ul>
+---
+name: list continuation
+in: |-
+  # one
+  # two
+  # three
+
+  # one
+  # two
+  # three
+
+  #_ four
+  # five
+  # six
+html: |- 
+  <ol>
+  	<li>one</li>
+  	<li>two</li>
+  	<li>three</li>
+  </ol>
+  <ol>
+  	<li>one</li>
+  	<li>two</li>
+  	<li>three</li>
+  </ol>
+  <ol start="4">
+  	<li>four</li>
+  	<li>five</li>
+  	<li>six</li>
+  </ol>
+valid_html: false
+comment: there's not a good, valid alternative to the start attribute
+---
+name: continue after break
+in: |-
+  # one
+  # two
+  # three
+  
+  test
+
+  #_ four
+  # five
+  # six
+  
+  test
+
+  #_ seven
+  # eight
+  # nine
+html: |-
+  <ol>
+  	<li>one</li>
+  	<li>two</li>
+  	<li>three</li>
+  </ol>
+  <p>test</p>
+  <ol start="4">
+  	<li>four</li>
+  	<li>five</li>
+  	<li>six</li>
+  </ol>
+  <p>test</p>
+  <ol start="7">
+  	<li>seven</li>
+  	<li>eight</li>
+  	<li>nine</li>
+  </ol>
+valid_html: false
+comment: there's not a good, valid alternative to the start attribute
+---
+name: continue list when prior list contained nested list
+in: |-
+  # one
+  # two
+  # three
+
+  #_ four
+  # five
+  ## sub-note
+  ## another sub-note
+  # six
+
+  #_ seven
+  # eight
+  # nine
+html: |-
+  <ol>
+  	<li>one</li>
+  	<li>two</li>
+  	<li>three</li>
+  </ol>
+  <ol start="4">
+  	<li>four</li>
+  	<li>five
+  	<ol>
+  		<li>sub-note</li>
+  		<li>another sub-note</li>
+  	</ol></li>
+  	<li>six</li>
+  </ol>
+  <ol start="7">
+  	<li>seven</li>
+  	<li>eight</li>
+  	<li>nine</li>
+  </ol>
+valid_html: false
+comment: there's not a good, valid alternative to the start attribute
+---
+name: list start number
+in: |-
+  #293 two ninety three
+  # two ninety four
+  # two ninety five
+
+  #9 nine
+  # ten
+  # eleven
+html: |-
+  <ol start="293">
+  	<li>two ninety three</li>
+  	<li>two ninety four</li>
+  	<li>two ninety five</li>
+  </ol>
+  <ol start="9">
+  	<li>nine</li>
+  	<li>ten</li>
+  	<li>eleven</li>
+  </ol>
+valid_html: false
+comment: there's not a good, valid alternative to the start attribute
+---
+name: continue list after started list
+in: |-
+  #9 nine
+  # ten
+  # eleven
+
+  #_ twelve
+  # thirteen
+  # fourteen
+html: |-
+  <ol start="9">
+  	<li>nine</li>
+  	<li>ten</li>
+  	<li>eleven</li>
+  </ol>
+  <ol start="12">
+  	<li>twelve</li>
+  	<li>thirteen</li>
+  	<li>fourteen</li>
+  </ol>
+valid_html: false
+comment: there's not a good, valid alternative to the start attribute
+---
+name: end notes
+in: |-
+  h2. End Notes
+
+  # End Notes should be a numbered list
+  # Like this
+  # They must have anchors in the text
+
+  h2. See Also
+
+  * See Also notes should be bullets
+  * Like this
+
+html: |-
+  <h2>End Notes</h2>
+  <ol>
+  	<li>End Notes should be a numbered list</li>
+  	<li>Like this</li>
+  	<li>They must have anchors in the text</li>
+  </ol>
+  <h2>See Also</h2>
+  <ul>
+  	<li>See Also notes should be bullets</li>
+  	<li>Like this</li>
+  </ul>
+---
+name: ordered list immediately following paragraph
+desc: Normally a paragraph and a list that follows it should be separated by two newlines.  Textile-2.0.0 recognizes the list even when separated by only one newline, but creates invalid XHTML by placing the list inside the paragraph.  RedCloth recognizes the pattern for backward compatibility, but creates valid XHTML.
+in: |-
+  A simple example.
+  # One
+  # Two
+html: |-
+  <p>A simple example.</p>
+  <ol>
+  	<li>One</li>
+  	<li>Two</li>
+  </ol>
+---
+name: unordered list immediately following paragraph
+in: |-
+  A simple example.
+  * One
+  * Two
+html: |-
+  <p>A simple example.</p>
+  <ul>
+  	<li>One</li>
+  	<li>Two</li>
+  </ul>
+---
+name: ordered list immediately following extended block
+in: |-
+  div.. Here it comes.
+  
+  A simple example.
+  # One
+  # Two
+html: |-
+  <div>Here it comes.</div>
+  <div>A simple example.</div>
+  <ol>
+  	<li>One</li>
+  	<li>Two</li>
+  </ol>
+---
+name: unordered list immediately following extended block
+in: |-
+  div.. Here it comes.
+  
+  A simple example.
+  * One
+  * Two
+html: |-
+  <div>Here it comes.</div>
+  <div>A simple example.</div>
+  <ul>
+  	<li>One</li>
+  	<li>Two</li>
+  </ul>
+---
+name: unordered list with leading spaces
+in: " * notice the leading space\n * RedCloth 3.0.4 used to accept it\n * Now we do too"
+html: |-
+  <ul>
+  	<li>notice the leading space</li>
+  	<li>RedCloth 3.0.4 used to accept it</li>
+  	<li>Now we do too</li>
+  </ul>
+---
+name: ordered list with leading spaces
+in: " # notice the leading space\n # RedCloth 3.0.4 used to accept it\n # Now we do too"
+html: |-
+  <ol>
+  	<li>notice the leading space</li>
+  	<li>RedCloth 3.0.4 used to accept it</li>
+  	<li>Now we do too</li>
+  </ol>
+---
+name: unordered with classes
+in: |-
+  *(class-one) one
+  *(class-two) two
+  *(class-three) three
+html: |-
+  <ul>
+  	<li class="class-one">one</li>
+  	<li class="class-two">two</li>
+  	<li class="class-three">three</li>
+  </ul>
+---
+name: unordered with alignments
+in: |-
+  *< one
+  *> two
+  *<> three
+  *= four
+html: |-
+  <ul>
+  	<li style="text-align:left;">one</li>
+  	<li style="text-align:right;">two</li>
+  	<li style="text-align:justify;">three</li>
+  	<li style="text-align:center;">four</li>
+  </ul>
+---
+name: with attributes that apply to the whole list
+in: |-
+  (class#id)# one
+  # two
+  # three
+html: |-
+  <ol class="class" id="id">
+  	<li>one</li>
+  	<li>two</li>
+  	<li>three</li>
+  </ol>
+---
+name: with id on the list
+in: |-
+  (#my-id)# one
+  # two
+  # three
+html: |-
+  <ol id="my-id">
+  	<li>one</li>
+  	<li>two</li>
+  	<li>three</li>
+  </ol>
+---
+name: with class on the list
+in: |-
+  (my-class)# one
+  # two
+  # three
+html: |-
+  <ol class="my-class">
+  	<li>one</li>
+  	<li>two</li>
+  	<li>three</li>
+  </ol>
+---
+name: with id on the list item
+in: |-
+  # one
+  #(#my-item) two
+  # three
+html: |-
+  <ol>
+  	<li>one</li>
+  	<li id="my-item">two</li>
+  	<li>three</li>
+  </ol>
+---
+name: with attributes that apply to the first list item
+in: |-
+  #(class#id) one
+  # two
+  # three
+html: |-
+  <ol>
+  	<li class="class" id="id">one</li>
+  	<li>two</li>
+  	<li>three</li>
+  </ol>
+---
+name: changed from textism basics
+desc: "This was in Textism basics, but when I changed the format of list styles, I removed it"
+in: |-
+  {color:blue}# one
+  # two
+  # three
+html: |-
+  <ol style="color:blue;">
+  	<li>one</li>
+  	<li>two</li>
+  	<li>three</li>
+  </ol>
+---
+name: changed from threshold list attributes
+desc: "Was: 'Attributes applied to the first list item will apply to the list itself.' but then we changed it"
+in: |-
+  *{color:red} Item one
+  * Item two
+  * Item three
+html: |-
+  <ul>
+  	<li style="color:red;">Item one</li>
+  	<li>Item two</li>
+  	<li>Item three</li>
+  </ul>
+---
+name: with one padding-left increment
+in: "(# one"
+html: |-
+  <ol style="padding-left:1em;">
+  	<li>one</li>
+  </ol>
+---
+name: with one padding-left increment and class
+in: "((myclass)# one"
+html: |-
+  <ol style="padding-left:1em;" class="myclass">
+  	<li>one</li>
+  </ol>
+---
+name: with two padding-left increments
+in: "((# two"
+html: |-
+  <ol style="padding-left:2em;">
+  	<li>two</li>
+  </ol>
+---
+name: with one padding-right increment
+in: ")# one"
+html: |-
+  <ol style="padding-right:1em;">
+  	<li>one</li>
+  </ol>
+---
+name: with padding-left and padding-right increments
+in: "()# two"
+html: |-
+  <ol style="padding-left:1em;padding-right:1em;">
+  	<li>two</li>
+  </ol>
+---
+name: with padding-left and padding-right increments switched
+in: ")(# two"
+html: |-
+  <ol style="padding-left:1em;padding-right:1em;">
+  	<li>two</li>
+  </ol>
+---
+name: with padding-left and padding-right increments and class
+in: "()(myclass)# two"
+html: |-
+  <ol style="padding-left:1em;padding-right:1em;" class="myclass">
+  	<li>two</li>
+  </ol>

data/spec/fixtures/poignant.yml

@@ -0,0 +1,89 @@
+--- # 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.
+
+html: |-
+  <h3>False</h3>
+  <p style="float:left;"><img src="i/blix-neg.gif" title="Shape of a cat." alt="Shape of a cat." /></p>
+  <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>
+  <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>
+  <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>
+  <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>
+  <pre>
+    if plastic_cup
+      print "Plastic cup is on the up 'n' up!"
+    end
+  </pre>
+  <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>
+  <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>
+  <pre>
+    unless plastic_cup
+      print "Plastic cup is on the down low."
+    end
+  </pre>
+  <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>
+  <pre>
+    print "Yeah, plastic cup is up again!" if plastic_cup
+    print "Hardly. It's down." unless plastic_cup
+  </pre>
+  <p>Now that you&#8217;ve met <code>false</code>, I&#8217;m sure you can see what&#8217;s on next.</p>
+  

data/spec/fixtures/sanitize_html.yml

@@ -0,0 +1,42 @@
+---
+in:  Just a little harmless xss <script src=http://ha.ckers.org/xss.js>stuff</script>.
+sanitized_html: <p>Just a little harmless xss stuff.</p>
+---
+in: Here's a bad image <img src="JaVaScRiPt:alert('XSS');" />
+sanitized_html: <p>Here&#8217;s a bad image <img /></p>
+---
+in: Just some random > and < characters, but also a <br/> tag.
+sanitized_html: <p>Just some random &gt; and &lt; characters, but also a <br/> tag.</p>
+---
+name: processes text beginning with space
+in: ' This began with a space and ends with some XSS: <script type="text/javascript">alert("Hai. I`m in ya PC. Makin ya XSS viruzz! KThxBye");</script>'
+sanitized_html: 'This began with a space and ends with some <span class="caps">XSS</span>: alert(&#8220;Hai. I`m in ya PC. Makin ya <span class="caps">XSS</span> viruzz! KThxBye&#8221;);'
+---
+name: processes text in notextile tags
+in: |-
+  <notextile>
+  The bad tags should be <b>missing</b>: <script type="text/javascript">alert("Hai. I`m in ya PC. Makin ya XSS viruzz! KThxBye");</script>
+  </notextile>
+sanitized_html: |-
+  The bad tags should be <b>missing</b>: alert("Hai. I`m in ya PC. Makin ya XSS viruzz! KThxBye");
+---
+name: processes text in inline notextile tags
+in: |-
+  The bad tags should be <b>missing</b>: <notextile><script type="text/javascript">alert("Hai. I`m in ya PC. Makin ya XSS viruzz! KThxBye");</script></notextile>
+sanitized_html: |-
+  <p>The bad tags should be <b>missing</b>: alert("Hai. I`m in ya PC. Makin ya XSS viruzz! KThxBye");</p>
+---
+name: removes script tags
+in: |-
+  <script type="text/javascript">
+    alert("Hai. I`m in ya PC. Makin ya XSS viruzz! KThxBye");
+  </script>
+sanitized_html: "alert(&#8220;Hai. I`m in ya PC. Makin ya <span class=\"caps\">XSS</span> viruzz! KThxBye&#8221;);"
+---
+name: removes nested script tags
+in: |-
+  <script type="text/javascript"><script>
+    alert("Hai. I`m in ya PC. Makin ya XSS viruzz! KThxBye");
+  </script></script>
+sanitized_html: |-
+  alert(&#8220;Hai. I`m in ya PC. Makin ya <span class="caps">XSS</span> viruzz! KThxBye&#8221;);