pasta 0.0.1

data/specs/recipes/gruber/code.yml

@@ -0,0 +1,48 @@
+overview: |
+  To indicate a span of code, wrap it with backtick quotes (`). Unlike a pre-formatted code block, a code span indicates code within a normal paragraph. 
+
+  To include a literal backtick character within a code span, you can use multiple backticks as the opening and closing delimiters.  The backtick delimiters surrounding a code span may include spaces — one after the opening, one before the closing. This allows you to place literal backtick characters at the beginning or end of a code span:
+
+  With a code span, ampersands and angle brackets are encoded as HTML entities automatically, which makes it easy to include example HTML tags.
+  
+  http://daringfireball.net/projects/markdown/syntax
+tests:
+  - name: Code Ticks
+    desc: Single backticks indicate code
+    text: Use the `printf()` function.
+    html: <p>Use the <code>printf()</code> function.</p>
+
+  - name: Code Ticks
+    desc: Will escape HTML entities
+    text: |
+      Please don't use any `<blink>` tags.
+    html: |
+      <p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>
+
+  - name: Code Ticks
+    desc: Will escape HTML entities
+    text: |
+      `&#8212;` is the decimal-encoded equivalent of `&mdash;`.
+    html: |
+      <p><code>&amp;#8212;</code> is the decimal-encoded equivalent of <code>&amp;mdash;</code>.</p>
+
+  - name: Code Ticks
+    desc: Multiple ticks indicate literal tick
+    text: |
+      ``There is a literal backtick (`) here.``
+    html: |
+      <p><code>There is a literal backtick (`) here.</code></p>
+
+  - name: Code Ticks
+    desc: A single backtick in a code span
+    text: |
+      A single backtick in a code span: `` ` ``
+    html: |
+      <p>A single backtick in a code span: <code> ` </code></p>
+      
+  - name: Code Ticks
+    desc: A backtick-delimited string in a code span
+    text: |
+      A backtick-delimited string in a code span: `` `foo` ``
+    html: |
+      <p>A backtick-delimited string in a code span: <code> `foo` </code></p>

data/specs/recipes/gruber/codeblocks.yml

@@ -0,0 +1,47 @@
+overview: |
+  Code Blocks
+
+  Pre-formatted code blocks are used for writing about programming or markup source code. Rather than forming normal paragraphs, the lines of a code block are interpreted literally. Markdown wraps a code block in both <pre> and <code> tags.
+
+  To produce a code block in Markdown, simply indent every line of the block by at least 4 spaces or 1 tab.
+
+  One level of indentation — 4 spaces or 1 tab — is removed from each line of the code block.
+
+  A code block continues until it reaches a line that is not indented (or the end of the article).
+
+  Within a code block, ampersands (&) and angle brackets (< and >) are automatically converted into HTML entities. This makes it very easy to include example HTML source code using Markdown — just paste it and indent it, and Markdown will handle the hassle of encoding the ampersands and angle brackets.
+
+  Regular Markdown syntax is not processed within code blocks. E.g., asterisks are just literal asterisks within a code block. This means it’s also easy to use Markdown to write about Markdown’s own syntax.
+  
+  http://daringfireball.net/projects/markdown/syntax
+tests: 
+  - name: Single line of code
+    desc: A Single line of code with 4 leading spaces
+    text: "    This is a code block."
+    html: <pre><code>This is a code block.</code></pre>
+
+  - name: Single line of code
+    desc: A Single line of code with a leading tab
+    text: "\tThis is a code block."
+    html: <pre><code>This is a code block.</code></pre>
+
+  - name: Multi line code
+    desc: Multiple lines of code with 4 leading spaces
+    text: "    tell application Foo\n        beep\n    end tell"
+    html: "<pre><code>tell application Foo\n    beep\nend tell</code></pre>"
+
+  - name: Multi line code
+    desc: Multiple lines of code with leading tabs
+    text: "\ttell application Foo\n\t\tbeep\n\tend tell"
+    html: "<pre><code>tell application Foo\n\tbeep\nend tell</code></pre>"
+
+  - name: Escape html entities
+    desc: HTML entities within code blocks will be escaped
+    text: "    <div class='footer'>\n        &copy; 2004 Foo Corporation\n    </div>"
+    html: "<pre><code>&lt;div class=&#39;footer&#39;&gt;\n    &amp;copy; 2004 Foo Corporation\n&lt;/div&gt;</code></pre>"
+
+  - name: Multiline code
+    desc: Multiple lines of code with empty lines
+    text: "    A First Level Header\n    ====================\n    \n    A Second Level Header\n    ---------------------"
+    html: "<pre><code>A First Level Header\n====================\n\nA Second Level Header\n---------------------</code></pre>"
+      

data/specs/recipes/gruber/emphasis.yml

@@ -0,0 +1,57 @@
+overview: |
+  Markdown treats asterisks (*) and underscores (_) as indicators of emphasis. Text wrapped with one * or _ will be wrapped with an HTML <em> tag; double *’s or _’s will be wrapped with an HTML <strong> tag. E.g., this input:
+
+  You can use whichever style you prefer; the lone restriction is that the same character must be used to open and close an emphasis span.
+
+  Emphasis can be used in the middle of a word but if you surround an * or _ with spaces, it’ll be treated as a literal asterisk or underscore.
+
+  To produce a literal asterisk or underscore at a position where it would otherwise be used as an emphasis delimiter, you can backslash escape it:
+
+  \*this text is surrounded by literal asterisks\*
+
+  http://daringfireball.net/projects/markdown/syntax
+tests:
+  - name: Single Emp
+    desc: Single asterisks as emphasis
+    text: "*single asterisks*"
+    html: <p><em>single asterisks</em></p>
+
+  - name: Single Emp
+    desc: Single underscore as emphasis
+    text: "_single underscore_"
+    html: <p><em>single underscore</em></p>
+
+  - name: Single Emp
+    desc: Unmatched asterisks and underscore
+    text: "*confused emphasis_"
+    html: <p>*confused emphasis_</p>
+    
+  - name: Double Emp
+    desc: Double asteriskss as emphasis
+    text: "**double asterisks**"
+    html: <p><strong>double asterisks</strong></p>
+
+  - name: Double Emp
+    desc: Double underscores as emphasis
+    text: "__double underscore__"
+    html: <p><strong>double underscore</strong></p>
+    
+  - name: Mid-word Emp
+    desc: Asterisks mid-word
+    text: "un*frigging*believable"
+    html: <p>un<em>frigging</em>believable</p>
+
+  - name: Mid-word Emp
+    desc: Underscores mid-word
+    text: "un_frigging_believable"
+    html: <p>un<em>frigging</em>believable</p>
+    
+  - name: Escaped Emp
+    desc: Underscores surrounded by spaces
+    text: "_ unbelievable _"
+    html: <p>_ unbelievable _</p>
+    
+  - name: Escaped Emp
+    desc: Asterisks surrounded by spaces
+    text: "This is * unbelievable *"
+    html: <p>This is * unbelievable *</p>

data/specs/recipes/gruber/gruber_spec.rb

@@ -0,0 +1,22 @@
+require 'spec_helper'
+
+describe 'Gruber' do
+  before do
+    @gruber = Pasta::Recipes::Gruber.new
+  end
+  
+  it "converts text to html" do
+    @gruber.to_html('some yummy text').must_be_kind_of String
+  end
+  
+  Dir.glob(File.dirname(__FILE__) + '/*.yml').each do |file|
+    yaml = YAML.load_file(file)
+    
+    yaml['tests'].each do |test|
+      it "parses #{test['desc']} to html" do
+        @gruber.to_html(test['text']).must_equal test['html'].strip
+      end
+    end
+  end
+
+end

data/specs/recipes/gruber/headers.yml

@@ -0,0 +1,88 @@
+overview: |
+  Markdown supports two styles of headers, Setext and atx.
+
+  Setext-style headers are “underlined” using equal signs (for first-level headers) and dashes (for second-level headers). Any number of underlining =’s or -’s will work.
+
+  Atx-style headers use 1-6 hash characters at the start of the line, corresponding to header levels 1-6. Optionally, you may “close” atx-style headers. This is purely cosmetic — you can use this if you think it looks better. The closing hashes don’t even need to match the number of hashes used to open the header. (The number of opening hashes determines the header level.) 
+  
+  http://daringfireball.net/projects/markdown/syntax
+tests: 
+  - name: ATX level 1
+    desc: An ATX level 1 header
+    text: "# This is a header"
+    html: <h1>This is a header</h1>
+
+  - name: ATX level 1 trailing
+    desc: An ATX level 1 header with trailing hash
+    text: "# This is a header #"
+    html: <h1>This is a header</h1>
+
+  - name: ATX level 2
+    desc: An ATX level 2 header
+    text: "## This is a header"
+    html: <h2>This is a header</h2>
+
+  - name: ATX level 2 trailing
+    desc: An ATX level 2 header with trailing hash
+    text: "## This is a header ##"
+    html: <h2>This is a header</h2>
+
+  - name: ATX level 3
+    desc: An ATX level 3 header
+    text: "# This is a header"
+    html: <h1>This is a header</h1>
+
+  - name: ATX level 3 trailing
+    desc: An ATX level 3 header with uneven trailing hash
+    text: "### This is a header #"
+    html: <h3>This is a header</h3>
+
+  - name: ATX level 4
+    desc: An ATX level 3 header
+    text: "# This is a header"
+    html: <h1>This is a header</h1>
+
+  - name: ATX level 4
+    desc: An ATX level 4 header
+    text: "#### This is a header"
+    html: <h4>This is a header</h4>
+
+  - name: ATX level 5
+    desc: An ATX level 5 header
+    text: "##### This is a header"
+    html: <h5>This is a header</h5>
+
+  - name: ATX level 6
+    desc: An ATX level 6 header
+    text: "###### This is a header"
+    html: <h6>This is a header</h6>
+
+  - name: Oversized ATX heading
+    desc: An ATX level 6 header but with too many hashes
+    text: "######## This is a header"
+    html: "<h6>## This is a header</h6>"
+    
+  - name: Multiple headers
+    desc: One header followed by another
+    text: |
+      # This is a header
+      
+      ## And this is another
+    html: |
+      <h1>This is a header</h1>
+      <h2>And this is another</h2>
+    
+
+  - name: Setext level 1
+    desc: An setext level 1 header
+    text: |
+      Setext Header 1
+      ===============
+    html: <h1>Setext Header 1</h1>
+
+  - name: Setext level 2
+    desc: An setext level 2 header
+    text: |
+      Setext Header 2
+      ---------------
+    html: <h2>Setext Header 2</h2>

data/specs/recipes/gruber/images.yml

@@ -0,0 +1,49 @@
+overview: |
+  Admittedly, it’s fairly difficult to devise a “natural” syntax for placing images into a plain text document format.
+
+  Markdown uses an image syntax that is intended to resemble the syntax for links, allowing for two styles: inline and reference.
+
+  Inline image syntax looks like this:
+
+  ![Alt text](/path/to/img.jpg)
+
+  ![Alt text](/path/to/img.jpg "Optional title")
+
+  That is:
+
+      An exclamation mark: !;
+      followed by a set of square brackets, containing the alt attribute text for the image;
+      followed by a set of parentheses, containing the URL or path to the image, and an optional title attribute enclosed in double or single quotes.
+
+  Reference-style image syntax looks like this:
+
+  ![Alt text][id]
+
+  Where “id” is the name of a defined image reference. Image references are defined using syntax identical to link references.
+  
+  As of this writing, Markdown has no syntax for specifying the dimensions of an image; if this is important to you, you can simply use regular HTML <img> tags.
+  
+  http://daringfireball.net/projects/markdown/syntax
+tests: 
+  - name: Inline image
+    desc: An inline image
+    text: |
+      ![Alt text](/path/to/img.jpg)
+    html: |
+      <p><img src="/path/to/img.jpg" alt="Alt text" /></p>
+
+  - name: Inline image
+    desc: An inline image with optional title
+    text: |
+      ![Alt text](/path/to/img.jpg "Optional title")
+    html: |
+      <p><img src="/path/to/img.jpg" alt="Alt text" title="Optional title" /></p>
+    
+  - name: Reference image
+    desc: An reference image with optional title
+    text: |
+      ![Alt text][id]
+      
+      [id]: url/to/image  "Optional title attribute"
+    html: |
+      <p><img src="url/to/image" alt="Alt text" title="Optional title attribute" /></p>

data/specs/recipes/gruber/links.yml

@@ -0,0 +1,184 @@
+overview: |
+  Markdown supports two style of links: inline and reference.
+
+  In both styles, the link text is delimited by [square brackets].
+
+  To create an inline link, use a set of regular parentheses immediately after the link text’s closing square bracket. Inside the parentheses, put the URL where you want the link to point, along with an optional title for the link, surrounded in quotes.
+
+  If you’re referring to a local resource on the same server, you can use relative paths.
+  
+  Reference-style links use a second set of square brackets, inside which you place a label of your choosing to identify the link.  You can optionally use a space to separate the sets of brackets.  Then, anywhere in the document, you define your link label like this, on a line by itself.
+
+  That is:
+
+      Square brackets containing the link identifier (optionally indented from the left margin using up to three spaces);
+      followed by a colon;
+      followed by one or more spaces (or tabs);
+      followed by the URL for the link;
+      optionally followed by a title attribute for the link, enclosed in double or single quotes, or enclosed in parentheses.
+
+  The following three link definitions are equivalent:
+
+  --- this is not implemented ---
+  [foo]: http://example.com/  "Optional Title Here"
+  [foo]: http://example.com/  'Optional Title Here'
+  [foo]: http://example.com/  (Optional Title Here)
+  ---
+    
+  The link URL may, optionally, be surrounded by angle brackets:
+
+  You can put the title attribute on the next line and use extra spaces or tabs for padding, which tends to look better with longer URLs.
+
+  Link definitions are only used for creating links during Markdown processing, and are stripped from your document in the HTML output.
+
+  Link definition names may consist of letters, numbers, spaces, and punctuation — but they are not case sensitive.
+
+  The implicit link name shortcut allows you to omit the name of the link, in which case the link text itself is used as the name. Just use an empty set of square brackets — e.g., to link the word “Google” to the google.com web site, you could simply write [Google][] and then define the link as [Google]: http://google.com/
+
+  Because link names may contain spaces, this shortcut even works for multiple words in the link text.
+
+  Link definitions can be placed anywhere in your Markdown document. I tend to put them immediately after each paragraph in which they’re used, but if you want, you can put them all at the end of your document, sort of like footnotes.
+
+  The point of reference-style links is not that they’re easier to write. The point is that with reference-style links, your document source is vastly more readable. Compare the above examples: using reference-style links, the paragraph itself is only 81 characters long; with inline-style links, it’s 176 characters; and as raw HTML, it’s 234 characters. In the raw HTML, there’s more markup than there is text.
+
+  With Markdown’s reference-style links, a source document much more closely resembles the final output, as rendered in a browser. By allowing you to move the markup-related metadata out of the paragraph, you can add links without interrupting the narrative flow of your prose.
+  
+  http://daringfireball.net/projects/markdown/syntax
+tests: 
+  - name: Inline Links
+    desc: An inline link
+    text: | 
+      [This link](http://example.net/) has no title attribute.
+    html: |
+      <p><a href="http://example.net/">This link</a> has no title attribute.</p>
+
+  - name: Inline Links Title
+    desc: An inline link with title text
+    text: | 
+      This is [an example](http://example.com/ "Title") inline link.
+    html: |
+      <p>This is <a href="http://example.com/" title="Title">an example</a> inline link.</p>
+
+  - name: Relative links
+    desc: Inline relative link
+    text: | 
+      See my [About](/about/) page for details.
+    html: |
+      <p>See my <a href="/about/">About</a> page for details.</p>
+
+  - name: Relative links
+    desc: Multiple relative links
+    text: | 
+      See my [About](/about/) page for [details](/details).
+    html: |
+      <p>See my <a href="/about/">About</a> page for <a href="/details">details</a>.</p>
+
+  - name: Reference Links
+    desc: A reference link
+    text: | 
+      This is [an example][id] reference-style link.
+      
+      [id]: http://example.com/  "Optional Title Here"
+    html: |
+      <p>This is <a href="http://example.com/" title="Optional Title Here">an example</a> reference-style link.</p>
+
+  - name: Reference Links
+    desc: A reference link with optional space
+    text: | 
+      This is [an example] [id] reference-style link.
+      
+      [id]: http://example.com/  "Optional Title Here"
+    html: |
+      <p>This is <a href="http://example.com/" title="Optional Title Here">an example</a> reference-style link.</p>
+      
+  - name: Reference Links
+    desc: A reference link with optional angled brackets
+    text: | 
+      This is [an example][id] reference-style link.
+      
+      [id]: <http://example.de/>  "Optional Title Here"
+    html: |
+      <p>This is <a href="http://example.de/" title="Optional Title Here">an example</a> reference-style link.</p>
+      
+  - name: Reference Links
+    desc: A reference link with title text on a new line
+    text: | 
+      This is [an example][id] reference-style link.
+      
+      [id]: http://example.at/longish/path/to/resource/here
+          "Optional Title Here"
+    html: |
+      <p>This is <a href="http://example.at/longish/path/to/resource/here" title="Optional Title Here">an example</a> reference-style link.</p>
+
+  - name: Reference Links
+    desc: Reference link are case insensitive
+    text: | 
+      This is [an example][id] reference-style link.
+      
+      [iD]: http://example.com/ 
+    html: |
+      <p>This is <a href="http://example.com/">an example</a> reference-style link.</p>
+
+  - name: Reference Links
+    desc: Reference link with implicit ids
+    text: | 
+      [Google][]
+      
+      [Google]: http://google.com/
+    html: |
+      <p><a href="http://google.com/">Google</a></p>
+
+  - name: Reference Links
+    desc: Reference link with spaces in implicit ids
+    text: | 
+      Visit [Daring Fireball][] for more information.
+              
+      [Daring Fireball]: http://daringfireball.net/
+    html: |
+      <p>Visit <a href="http://daringfireball.net/">Daring Fireball</a> for more information.</p>
+
+  - name: Reference Links
+    desc: Reference link with link definitions before link
+    text: | 
+      [Daring Fireball]: http://daringfireball.net/
+      
+      Visit [Daring Fireball][] for more information.
+    html: |
+      <p>Visit <a href="http://daringfireball.net/">Daring Fireball</a> for more information.</p>
+
+  - name: Reference Links
+    desc: Reference link with multiple links and text
+    text: | 
+      This page offers a brief overview of what it's like to use Markdown.
+      The [syntax page] [s] provides complete, detailed documentation for
+      every feature, but Markdown should be very easy to pick up simply by
+      looking at a few examples of it in action. The examples on this page
+      are written in a before/after style, showing example syntax and the
+      HTML output produced by Markdown.
+      
+      It's also helpful to simply try Markdown out; the [Dingus] [d] is a
+      web application that allows you type your own Markdown-formatted text
+      and translate it to XHTML.
+      
+      **Note:** This document is itself written using Markdown; you
+      can [see the source for it by adding '.text' to the URL] [src].
+      
+      [s]: /projects/markdown/syntax "Markdown Syntax"
+      
+      [d]: /projects/markdown/dingus "Markdown Dingus"
+      
+      [src]: /projects/markdown/basics.text
+    html: |
+      <p>This page offers a brief overview of what it's like to use Markdown.
+      The <a href="/projects/markdown/syntax" title="Markdown Syntax">syntax page</a> provides complete, detailed documentation for
+      every feature, but Markdown should be very easy to pick up simply by
+      looking at a few examples of it in action. The examples on this page
+      are written in a before/after style, showing example syntax and the
+      HTML output produced by Markdown.</p>
+      
+      <p>It's also helpful to simply try Markdown out; the <a href="/projects/markdown/dingus" title="Markdown Dingus">Dingus</a> is a
+      web application that allows you type your own Markdown-formatted text
+      and translate it to XHTML.</p>
+      
+      <p><strong>Note:</strong> This document is itself written using Markdown; you
+      can <a href="/projects/markdown/basics.text">see the source for it by adding '.text' to the URL</a>.</p>