From 14152628fff5c4c3da483746c653ad3b46916a39 Mon Sep 17 00:00:00 2001 From: Waylan Limberg Date: Fri, 5 Jun 2009 23:10:59 -0400 Subject: renamed 'markdown-test' to 'basic' as that what those tests actually are. Also resolved issue with api tests being autodiscovered. test_apis.py was executable so nose was ignoring it. --- markdown/tests/__init__.py | 2 - markdown/tests/basic/amps-and-angle-encoding.html | 9 + markdown/tests/basic/amps-and-angle-encoding.txt | 21 + markdown/tests/basic/angle-links-and-img.html | 4 + markdown/tests/basic/angle-links-and-img.txt | 4 + markdown/tests/basic/auto-links.html | 15 + markdown/tests/basic/auto-links.txt | 17 + markdown/tests/basic/backlash-escapes.html | 67 ++ markdown/tests/basic/backlash-escapes.txt | 104 +++ markdown/tests/basic/benchmark.dat | 20 + .../tests/basic/blockquotes-with-code-blocks.html | 12 + .../tests/basic/blockquotes-with-code-blocks.txt | 11 + markdown/tests/basic/codeblock-in-list.html | 14 + markdown/tests/basic/codeblock-in-list.txt | 10 + markdown/tests/basic/hard-wrapped.html | 7 + markdown/tests/basic/hard-wrapped.txt | 8 + markdown/tests/basic/horizontal-rules.html | 39 + markdown/tests/basic/horizontal-rules.txt | 67 ++ markdown/tests/basic/inline-html-advanced.html | 12 + markdown/tests/basic/inline-html-advanced.txt | 14 + markdown/tests/basic/inline-html-comments.html | 11 + markdown/tests/basic/inline-html-comments.txt | 13 + markdown/tests/basic/inline-html-simple.html | 58 ++ markdown/tests/basic/inline-html-simple.txt | 69 ++ markdown/tests/basic/links-inline.html | 5 + markdown/tests/basic/links-inline.txt | 9 + markdown/tests/basic/links-reference.html | 10 + markdown/tests/basic/links-reference.txt | 31 + markdown/tests/basic/literal-quotes.html | 2 + markdown/tests/basic/literal-quotes.txt | 7 + .../tests/basic/markdown-documentation-basics.html | 243 ++++++ .../tests/basic/markdown-documentation-basics.txt | 306 +++++++ markdown/tests/basic/markdown-syntax.html | 728 +++++++++++++++++ markdown/tests/basic/markdown-syntax.txt | 888 +++++++++++++++++++++ markdown/tests/basic/nested-blockquotes.html | 7 + markdown/tests/basic/nested-blockquotes.txt | 5 + .../tests/basic/ordered-and-unordered-list.html | 146 ++++ .../tests/basic/ordered-and-unordered-list.txt | 122 +++ markdown/tests/basic/strong-and-em-together.html | 4 + markdown/tests/basic/strong-and-em-together.txt | 7 + markdown/tests/basic/tabs.html | 23 + markdown/tests/basic/tabs.txt | 21 + markdown/tests/basic/tidyness.html | 8 + markdown/tests/basic/tidyness.txt | 5 + .../markdown-test/amps-and-angle-encoding.html | 9 - .../markdown-test/amps-and-angle-encoding.txt | 21 - .../tests/markdown-test/angle-links-and-img.html | 4 - .../tests/markdown-test/angle-links-and-img.txt | 4 - markdown/tests/markdown-test/auto-links.html | 15 - markdown/tests/markdown-test/auto-links.txt | 17 - markdown/tests/markdown-test/backlash-escapes.html | 67 -- markdown/tests/markdown-test/backlash-escapes.txt | 104 --- markdown/tests/markdown-test/benchmark.dat | 20 - .../blockquotes-with-code-blocks.html | 12 - .../markdown-test/blockquotes-with-code-blocks.txt | 11 - .../tests/markdown-test/codeblock-in-list.html | 14 - markdown/tests/markdown-test/codeblock-in-list.txt | 10 - markdown/tests/markdown-test/hard-wrapped.html | 7 - markdown/tests/markdown-test/hard-wrapped.txt | 8 - markdown/tests/markdown-test/horizontal-rules.html | 39 - markdown/tests/markdown-test/horizontal-rules.txt | 67 -- .../tests/markdown-test/inline-html-advanced.html | 12 - .../tests/markdown-test/inline-html-advanced.txt | 14 - .../tests/markdown-test/inline-html-comments.html | 11 - .../tests/markdown-test/inline-html-comments.txt | 13 - .../tests/markdown-test/inline-html-simple.html | 58 -- .../tests/markdown-test/inline-html-simple.txt | 69 -- markdown/tests/markdown-test/links-inline.html | 5 - markdown/tests/markdown-test/links-inline.txt | 9 - markdown/tests/markdown-test/links-reference.html | 10 - markdown/tests/markdown-test/links-reference.txt | 31 - markdown/tests/markdown-test/literal-quotes.html | 2 - markdown/tests/markdown-test/literal-quotes.txt | 7 - .../markdown-documentation-basics.html | 243 ------ .../markdown-documentation-basics.txt | 306 ------- markdown/tests/markdown-test/markdown-syntax.html | 728 ----------------- markdown/tests/markdown-test/markdown-syntax.txt | 888 --------------------- .../tests/markdown-test/nested-blockquotes.html | 7 - .../tests/markdown-test/nested-blockquotes.txt | 5 - .../markdown-test/ordered-and-unordered-list.html | 146 ---- .../markdown-test/ordered-and-unordered-list.txt | 122 --- .../markdown-test/strong-and-em-together.html | 4 - .../tests/markdown-test/strong-and-em-together.txt | 7 - markdown/tests/markdown-test/tabs.html | 23 - markdown/tests/markdown-test/tabs.txt | 21 - markdown/tests/markdown-test/tidyness.html | 8 - markdown/tests/markdown-test/tidyness.txt | 5 - markdown/tests/test_apis.py | 0 88 files changed, 3183 insertions(+), 3185 deletions(-) create mode 100644 markdown/tests/basic/amps-and-angle-encoding.html create mode 100644 markdown/tests/basic/amps-and-angle-encoding.txt create mode 100644 markdown/tests/basic/angle-links-and-img.html create mode 100644 markdown/tests/basic/angle-links-and-img.txt create mode 100644 markdown/tests/basic/auto-links.html create mode 100644 markdown/tests/basic/auto-links.txt create mode 100644 markdown/tests/basic/backlash-escapes.html create mode 100644 markdown/tests/basic/backlash-escapes.txt create mode 100644 markdown/tests/basic/benchmark.dat create mode 100644 markdown/tests/basic/blockquotes-with-code-blocks.html create mode 100644 markdown/tests/basic/blockquotes-with-code-blocks.txt create mode 100644 markdown/tests/basic/codeblock-in-list.html create mode 100644 markdown/tests/basic/codeblock-in-list.txt create mode 100644 markdown/tests/basic/hard-wrapped.html create mode 100644 markdown/tests/basic/hard-wrapped.txt create mode 100644 markdown/tests/basic/horizontal-rules.html create mode 100644 markdown/tests/basic/horizontal-rules.txt create mode 100644 markdown/tests/basic/inline-html-advanced.html create mode 100644 markdown/tests/basic/inline-html-advanced.txt create mode 100644 markdown/tests/basic/inline-html-comments.html create mode 100644 markdown/tests/basic/inline-html-comments.txt create mode 100644 markdown/tests/basic/inline-html-simple.html create mode 100644 markdown/tests/basic/inline-html-simple.txt create mode 100644 markdown/tests/basic/links-inline.html create mode 100644 markdown/tests/basic/links-inline.txt create mode 100644 markdown/tests/basic/links-reference.html create mode 100644 markdown/tests/basic/links-reference.txt create mode 100644 markdown/tests/basic/literal-quotes.html create mode 100644 markdown/tests/basic/literal-quotes.txt create mode 100644 markdown/tests/basic/markdown-documentation-basics.html create mode 100644 markdown/tests/basic/markdown-documentation-basics.txt create mode 100644 markdown/tests/basic/markdown-syntax.html create mode 100644 markdown/tests/basic/markdown-syntax.txt create mode 100644 markdown/tests/basic/nested-blockquotes.html create mode 100644 markdown/tests/basic/nested-blockquotes.txt create mode 100644 markdown/tests/basic/ordered-and-unordered-list.html create mode 100644 markdown/tests/basic/ordered-and-unordered-list.txt create mode 100644 markdown/tests/basic/strong-and-em-together.html create mode 100644 markdown/tests/basic/strong-and-em-together.txt create mode 100644 markdown/tests/basic/tabs.html create mode 100644 markdown/tests/basic/tabs.txt create mode 100644 markdown/tests/basic/tidyness.html create mode 100644 markdown/tests/basic/tidyness.txt delete mode 100644 markdown/tests/markdown-test/amps-and-angle-encoding.html delete mode 100644 markdown/tests/markdown-test/amps-and-angle-encoding.txt delete mode 100644 markdown/tests/markdown-test/angle-links-and-img.html delete mode 100644 markdown/tests/markdown-test/angle-links-and-img.txt delete mode 100644 markdown/tests/markdown-test/auto-links.html delete mode 100644 markdown/tests/markdown-test/auto-links.txt delete mode 100644 markdown/tests/markdown-test/backlash-escapes.html delete mode 100644 markdown/tests/markdown-test/backlash-escapes.txt delete mode 100644 markdown/tests/markdown-test/benchmark.dat delete mode 100644 markdown/tests/markdown-test/blockquotes-with-code-blocks.html delete mode 100644 markdown/tests/markdown-test/blockquotes-with-code-blocks.txt delete mode 100644 markdown/tests/markdown-test/codeblock-in-list.html delete mode 100644 markdown/tests/markdown-test/codeblock-in-list.txt delete mode 100644 markdown/tests/markdown-test/hard-wrapped.html delete mode 100644 markdown/tests/markdown-test/hard-wrapped.txt delete mode 100644 markdown/tests/markdown-test/horizontal-rules.html delete mode 100644 markdown/tests/markdown-test/horizontal-rules.txt delete mode 100644 markdown/tests/markdown-test/inline-html-advanced.html delete mode 100644 markdown/tests/markdown-test/inline-html-advanced.txt delete mode 100644 markdown/tests/markdown-test/inline-html-comments.html delete mode 100644 markdown/tests/markdown-test/inline-html-comments.txt delete mode 100644 markdown/tests/markdown-test/inline-html-simple.html delete mode 100644 markdown/tests/markdown-test/inline-html-simple.txt delete mode 100644 markdown/tests/markdown-test/links-inline.html delete mode 100644 markdown/tests/markdown-test/links-inline.txt delete mode 100644 markdown/tests/markdown-test/links-reference.html delete mode 100644 markdown/tests/markdown-test/links-reference.txt delete mode 100644 markdown/tests/markdown-test/literal-quotes.html delete mode 100644 markdown/tests/markdown-test/literal-quotes.txt delete mode 100644 markdown/tests/markdown-test/markdown-documentation-basics.html delete mode 100644 markdown/tests/markdown-test/markdown-documentation-basics.txt delete mode 100644 markdown/tests/markdown-test/markdown-syntax.html delete mode 100644 markdown/tests/markdown-test/markdown-syntax.txt delete mode 100644 markdown/tests/markdown-test/nested-blockquotes.html delete mode 100644 markdown/tests/markdown-test/nested-blockquotes.txt delete mode 100644 markdown/tests/markdown-test/ordered-and-unordered-list.html delete mode 100644 markdown/tests/markdown-test/ordered-and-unordered-list.txt delete mode 100644 markdown/tests/markdown-test/strong-and-em-together.html delete mode 100644 markdown/tests/markdown-test/strong-and-em-together.txt delete mode 100644 markdown/tests/markdown-test/tabs.html delete mode 100644 markdown/tests/markdown-test/tabs.txt delete mode 100644 markdown/tests/markdown-test/tidyness.html delete mode 100644 markdown/tests/markdown-test/tidyness.txt mode change 100755 => 100644 markdown/tests/test_apis.py diff --git a/markdown/tests/__init__.py b/markdown/tests/__init__.py index 4a191a3..29e8d45 100644 --- a/markdown/tests/__init__.py +++ b/markdown/tests/__init__.py @@ -5,8 +5,6 @@ import difflib import nose import util from plugins import HtmlOutput, Markdown -# import api tests for autodiscovery -from test_apis import * test_dir = os.path.abspath(os.path.dirname(__file__)) diff --git a/markdown/tests/basic/amps-and-angle-encoding.html b/markdown/tests/basic/amps-and-angle-encoding.html new file mode 100644 index 0000000..2c466c1 --- /dev/null +++ b/markdown/tests/basic/amps-and-angle-encoding.html @@ -0,0 +1,9 @@ +

AT&T has an ampersand in their name.

+

AT&T is another way to write it.

+

This & that.

+

4 < 5.

+

6 > 5.

+

Here's a link with an ampersand in the URL.

+

Here's a link with an amersand in the link text: AT&T.

+

Here's an inline link.

+

Here's an inline link.

\ No newline at end of file diff --git a/markdown/tests/basic/amps-and-angle-encoding.txt b/markdown/tests/basic/amps-and-angle-encoding.txt new file mode 100644 index 0000000..0e9527f --- /dev/null +++ b/markdown/tests/basic/amps-and-angle-encoding.txt @@ -0,0 +1,21 @@ +AT&T has an ampersand in their name. + +AT&T is another way to write it. + +This & that. + +4 < 5. + +6 > 5. + +Here's a [link] [1] with an ampersand in the URL. + +Here's a link with an amersand in the link text: [AT&T] [2]. + +Here's an inline [link](/script?foo=1&bar=2). + +Here's an inline [link](). + + +[1]: http://example.com/?foo=1&bar=2 +[2]: http://att.com/ "AT&T" \ No newline at end of file diff --git a/markdown/tests/basic/angle-links-and-img.html b/markdown/tests/basic/angle-links-and-img.html new file mode 100644 index 0000000..1ca3b0b --- /dev/null +++ b/markdown/tests/basic/angle-links-and-img.html @@ -0,0 +1,4 @@ +

link +image +link +image

\ No newline at end of file diff --git a/markdown/tests/basic/angle-links-and-img.txt b/markdown/tests/basic/angle-links-and-img.txt new file mode 100644 index 0000000..1dbf404 --- /dev/null +++ b/markdown/tests/basic/angle-links-and-img.txt @@ -0,0 +1,4 @@ +[link]( "title") +![image]() +[link]() +![image]() diff --git a/markdown/tests/basic/auto-links.html b/markdown/tests/basic/auto-links.html new file mode 100644 index 0000000..7481fe2 --- /dev/null +++ b/markdown/tests/basic/auto-links.html @@ -0,0 +1,15 @@ +

Link: http://example.com/.

+

Https link: https://example.com

+

Ftp link: ftp://example.com

+

With an ampersand: http://example.com/?foo=1&bar=2

+ +
+

Blockquoted: http://example.com/

+
+

Auto-links should not occur here: <http://example.com/>

+
or here: <http://example.com/>
+
\ No newline at end of file diff --git a/markdown/tests/basic/auto-links.txt b/markdown/tests/basic/auto-links.txt new file mode 100644 index 0000000..a188b40 --- /dev/null +++ b/markdown/tests/basic/auto-links.txt @@ -0,0 +1,17 @@ +Link: . + +Https link: + +Ftp link: + +With an ampersand: + +* In a list? +* +* It should. + +> Blockquoted: + +Auto-links should not occur here: `` + + or here: diff --git a/markdown/tests/basic/backlash-escapes.html b/markdown/tests/basic/backlash-escapes.html new file mode 100644 index 0000000..876775f --- /dev/null +++ b/markdown/tests/basic/backlash-escapes.html @@ -0,0 +1,67 @@ +

These should all get escaped:

+

Backslash: \

+

Backtick: `

+

Asterisk: *

+

Underscore: _

+

Left brace: {

+

Right brace: }

+

Left bracket: [

+

Right bracket: ]

+

Left paren: (

+

Right paren: )

+

Greater-than: >

+

Hash: #

+

Period: .

+

Bang: !

+

Plus: +

+

Minus: -

+

These should not, because they occur within a code block:

+
Backslash: \\
+
+Backtick: \`
+
+Asterisk: \*
+
+Underscore: \_
+
+Left brace: \{
+
+Right brace: \}
+
+Left bracket: \[
+
+Right bracket: \]
+
+Left paren: \(
+
+Right paren: \)
+
+Greater-than: \>
+
+Hash: \#
+
+Period: \.
+
+Bang: \!
+
+Plus: \+
+
+Minus: \-
+
+

Nor should these, which occur in code spans:

+

Backslash: \\

+

Backtick: \`

+

Asterisk: \*

+

Underscore: \_

+

Left brace: \{

+

Right brace: \}

+

Left bracket: \[

+

Right bracket: \]

+

Left paren: \(

+

Right paren: \)

+

Greater-than: \>

+

Hash: \#

+

Period: \.

+

Bang: \!

+

Plus: \+

+

Minus: \-

\ No newline at end of file diff --git a/markdown/tests/basic/backlash-escapes.txt b/markdown/tests/basic/backlash-escapes.txt new file mode 100644 index 0000000..16447a0 --- /dev/null +++ b/markdown/tests/basic/backlash-escapes.txt @@ -0,0 +1,104 @@ +These should all get escaped: + +Backslash: \\ + +Backtick: \` + +Asterisk: \* + +Underscore: \_ + +Left brace: \{ + +Right brace: \} + +Left bracket: \[ + +Right bracket: \] + +Left paren: \( + +Right paren: \) + +Greater-than: \> + +Hash: \# + +Period: \. + +Bang: \! + +Plus: \+ + +Minus: \- + + + +These should not, because they occur within a code block: + + Backslash: \\ + + Backtick: \` + + Asterisk: \* + + Underscore: \_ + + Left brace: \{ + + Right brace: \} + + Left bracket: \[ + + Right bracket: \] + + Left paren: \( + + Right paren: \) + + Greater-than: \> + + Hash: \# + + Period: \. + + Bang: \! + + Plus: \+ + + Minus: \- + + +Nor should these, which occur in code spans: + +Backslash: `\\` + +Backtick: `` \` `` + +Asterisk: `\*` + +Underscore: `\_` + +Left brace: `\{` + +Right brace: `\}` + +Left bracket: `\[` + +Right bracket: `\]` + +Left paren: `\(` + +Right paren: `\)` + +Greater-than: `\>` + +Hash: `\#` + +Period: `\.` + +Bang: `\!` + +Plus: `\+` + +Minus: `\-` diff --git a/markdown/tests/basic/benchmark.dat b/markdown/tests/basic/benchmark.dat new file mode 100644 index 0000000..3d549dd --- /dev/null +++ b/markdown/tests/basic/benchmark.dat @@ -0,0 +1,20 @@ +construction:0.000000:0.000000 +amps-and-angle-encoding:0.070000:131072.000000 +auto-links:0.080000:397312.000000 +backlash-escapes:0.270000:884736.000000 +blockquotes-with-dode-blocks:0.020000:0.000000 +hard-wrapped:0.020000:0.000000 +horizontal-rules:0.180000:135168.000000 +inline-html-advanced:0.070000:0.000000 +inline-html-comments:0.080000:0.000000 +inline-html-simple:0.210000:0.000000 +links-inline:0.140000:0.000000 +links-reference:0.170000:0.000000 +literal-quotes:0.090000:0.000000 +markdown-documentation-basics:0.690000:1806336.000000 +markdown-syntax:3.310000:6696960.000000 +nested-blockquotes:0.200000:0.000000 +ordered-and-unordered-list:0.530000:0.000000 +strong-and-em-together:0.200000:0.000000 +tabs:0.200000:0.000000 +tidyness:0.200000:0.000000 diff --git a/markdown/tests/basic/blockquotes-with-code-blocks.html b/markdown/tests/basic/blockquotes-with-code-blocks.html new file mode 100644 index 0000000..5fc98b1 --- /dev/null +++ b/markdown/tests/basic/blockquotes-with-code-blocks.html @@ -0,0 +1,12 @@ +
+

Example:

+
sub status {
+    print "working";
+}
+
+

Or:

+
sub status {
+    return "working";
+}
+
+
\ No newline at end of file diff --git a/markdown/tests/basic/blockquotes-with-code-blocks.txt b/markdown/tests/basic/blockquotes-with-code-blocks.txt new file mode 100644 index 0000000..c31d171 --- /dev/null +++ b/markdown/tests/basic/blockquotes-with-code-blocks.txt @@ -0,0 +1,11 @@ +> Example: +> +> sub status { +> print "working"; +> } +> +> Or: +> +> sub status { +> return "working"; +> } diff --git a/markdown/tests/basic/codeblock-in-list.html b/markdown/tests/basic/codeblock-in-list.html new file mode 100644 index 0000000..49edd56 --- /dev/null +++ b/markdown/tests/basic/codeblock-in-list.html @@ -0,0 +1,14 @@ +
    +
  • +

    A list item with a code block

    +
    Some *code*
+
    +
    • +
  • +

    Another list item

    +
    More code
+
+And more code
+
    +
    • +
\ No newline at end of file diff --git a/markdown/tests/basic/codeblock-in-list.txt b/markdown/tests/basic/codeblock-in-list.txt new file mode 100644 index 0000000..87d4e3b --- /dev/null +++ b/markdown/tests/basic/codeblock-in-list.txt @@ -0,0 +1,10 @@ +* A list item with a code block + + Some *code* + +* Another list item + + More code + + And more code + diff --git a/markdown/tests/basic/hard-wrapped.html b/markdown/tests/basic/hard-wrapped.html new file mode 100644 index 0000000..e28e900 --- /dev/null +++ b/markdown/tests/basic/hard-wrapped.html @@ -0,0 +1,7 @@ +

In Markdown 1.0.0 and earlier. Version +8. This line turns into a list item. +Because a hard-wrapped line in the +middle of a paragraph looked like a +list item.

+

Here's one with a bullet. +* criminey.

\ No newline at end of file diff --git a/markdown/tests/basic/hard-wrapped.txt b/markdown/tests/basic/hard-wrapped.txt new file mode 100644 index 0000000..f8a5b27 --- /dev/null +++ b/markdown/tests/basic/hard-wrapped.txt @@ -0,0 +1,8 @@ +In Markdown 1.0.0 and earlier. Version +8. This line turns into a list item. +Because a hard-wrapped line in the +middle of a paragraph looked like a +list item. + +Here's one with a bullet. +* criminey. diff --git a/markdown/tests/basic/horizontal-rules.html b/markdown/tests/basic/horizontal-rules.html new file mode 100644 index 0000000..478e8c5 --- /dev/null +++ b/markdown/tests/basic/horizontal-rules.html @@ -0,0 +1,39 @@ +

Dashes:

+
+
+
+
+
---
+
+
+
+
+
+
- - -
+
+

Asterisks:

+
+
+
+
+
***
+
+
+
+
+
+
* * *
+
+

Underscores:

+
+
+
+
+
___
+
+
+
+
+
+
_ _ _
+
\ No newline at end of file diff --git a/markdown/tests/basic/horizontal-rules.txt b/markdown/tests/basic/horizontal-rules.txt new file mode 100644 index 0000000..1594bda --- /dev/null +++ b/markdown/tests/basic/horizontal-rules.txt @@ -0,0 +1,67 @@ +Dashes: + +--- + + --- + + --- + + --- + + --- + +- - - + + - - - + + - - - + + - - - + + - - - + + +Asterisks: + +*** + + *** + + *** + + *** + + *** + +* * * + + * * * + + * * * + + * * * + + * * * + + +Underscores: + +___ + + ___ + + ___ + + ___ + + ___ + +_ _ _ + + _ _ _ + + _ _ _ + + _ _ _ + + _ _ _ diff --git a/markdown/tests/basic/inline-html-advanced.html b/markdown/tests/basic/inline-html-advanced.html new file mode 100644 index 0000000..af1dec1 --- /dev/null +++ b/markdown/tests/basic/inline-html-advanced.html @@ -0,0 +1,12 @@ +

Simple block on one line:

+
foo
+ +

And nested without indentation:

+
+
+
+foo +
+
+
bar
+
\ No newline at end of file diff --git a/markdown/tests/basic/inline-html-advanced.txt b/markdown/tests/basic/inline-html-advanced.txt new file mode 100644 index 0000000..9d71ddc --- /dev/null +++ b/markdown/tests/basic/inline-html-advanced.txt @@ -0,0 +1,14 @@ +Simple block on one line: + +
foo
+ +And nested without indentation: + +
+
+
+foo +
+
+
bar
+
diff --git a/markdown/tests/basic/inline-html-comments.html b/markdown/tests/basic/inline-html-comments.html new file mode 100644 index 0000000..0d4cad9 --- /dev/null +++ b/markdown/tests/basic/inline-html-comments.html @@ -0,0 +1,11 @@ +

Paragraph one.

+ + + + +

Paragraph two.

+ + +

The end.

\ No newline at end of file diff --git a/markdown/tests/basic/inline-html-comments.txt b/markdown/tests/basic/inline-html-comments.txt new file mode 100644 index 0000000..41d830d --- /dev/null +++ b/markdown/tests/basic/inline-html-comments.txt @@ -0,0 +1,13 @@ +Paragraph one. + + + + + +Paragraph two. + + + +The end. diff --git a/markdown/tests/basic/inline-html-simple.html b/markdown/tests/basic/inline-html-simple.html new file mode 100644 index 0000000..cb10451 --- /dev/null +++ b/markdown/tests/basic/inline-html-simple.html @@ -0,0 +1,58 @@ +

Here's a simple block:

+
+ foo +
+ +

This should be a code block, though:

+
<div>
+    foo
+</div>
+
+

As should this:

+
<div>foo</div>
+
+

Now, nested:

+
+
+
+ foo +
+
+
+ +

This should just be an HTML comment:

+ + +

Multiline:

+ + +

Code block:

+
<!-- Comment -->
+
+

Just plain comment, with trailing spaces on the line:

+ + +

Code:

+
<hr />
+
+

Hr's:

+
+ +
+ +
+ +
+ +
+ +
+ +
+ +
+ +
\ No newline at end of file diff --git a/markdown/tests/basic/inline-html-simple.txt b/markdown/tests/basic/inline-html-simple.txt new file mode 100644 index 0000000..14aa2dc --- /dev/null +++ b/markdown/tests/basic/inline-html-simple.txt @@ -0,0 +1,69 @@ +Here's a simple block: + +
+ foo +
+ +This should be a code block, though: + +
+ foo +
+ +As should this: + +
foo
+ +Now, nested: + +
+
+
+ foo +
+
+
+ +This should just be an HTML comment: + + + +Multiline: + + + +Code block: + + + +Just plain comment, with trailing spaces on the line: + + + +Code: + +
+ +Hr's: + +
+ +
+ +
+ +
+ +
+ +
+ +
+ +
+ +
+ diff --git a/markdown/tests/basic/links-inline.html b/markdown/tests/basic/links-inline.html new file mode 100644 index 0000000..707937a --- /dev/null +++ b/markdown/tests/basic/links-inline.html @@ -0,0 +1,5 @@ +

Just a URL.

+

URL and title.

+

URL and title.

+

URL and title.

+

Empty.

\ No newline at end of file diff --git a/markdown/tests/basic/links-inline.txt b/markdown/tests/basic/links-inline.txt new file mode 100644 index 0000000..4d0c1c2 --- /dev/null +++ b/markdown/tests/basic/links-inline.txt @@ -0,0 +1,9 @@ +Just a [URL](/url/). + +[URL and title](/url/ "title"). + +[URL and title](/url/ "title preceded by two spaces"). + +[URL and title](/url/ "title preceded by a tab"). + +[Empty](). diff --git a/markdown/tests/basic/links-reference.html b/markdown/tests/basic/links-reference.html new file mode 100644 index 0000000..165c71a --- /dev/null +++ b/markdown/tests/basic/links-reference.html @@ -0,0 +1,10 @@ +

Foo bar.

+

Foo bar.

+

Foo bar.

+

With embedded [brackets].

+

Indented once.

+

Indented twice.

+

Indented thrice.

+

Indented [four][] times.

+
[four]: /url
+
\ No newline at end of file diff --git a/markdown/tests/basic/links-reference.txt b/markdown/tests/basic/links-reference.txt new file mode 100644 index 0000000..b2fa734 --- /dev/null +++ b/markdown/tests/basic/links-reference.txt @@ -0,0 +1,31 @@ +Foo [bar] [1]. + +Foo [bar][1]. + +Foo [bar] +[1]. + +[1]: /url/ "Title" + + +With [embedded [brackets]] [b]. + + +Indented [once][]. + +Indented [twice][]. + +Indented [thrice][]. + +Indented [four][] times. + + [once]: /url + + [twice]: /url + + [thrice]: /url + + [four]: /url + + +[b]: /url/ diff --git a/markdown/tests/basic/literal-quotes.html b/markdown/tests/basic/literal-quotes.html new file mode 100644 index 0000000..0342589 --- /dev/null +++ b/markdown/tests/basic/literal-quotes.html @@ -0,0 +1,2 @@ +

Foo bar.

+

Foo bar.

\ No newline at end of file diff --git a/markdown/tests/basic/literal-quotes.txt b/markdown/tests/basic/literal-quotes.txt new file mode 100644 index 0000000..29d0e42 --- /dev/null +++ b/markdown/tests/basic/literal-quotes.txt @@ -0,0 +1,7 @@ +Foo [bar][]. + +Foo [bar](/url/ "Title with "quotes" inside"). + + + [bar]: /url/ "Title with "quotes" inside" + diff --git a/markdown/tests/basic/markdown-documentation-basics.html b/markdown/tests/basic/markdown-documentation-basics.html new file mode 100644 index 0000000..3bcaea9 --- /dev/null +++ b/markdown/tests/basic/markdown-documentation-basics.html @@ -0,0 +1,243 @@ +

Markdown: Basics

+ + +

Getting the Gist of Markdown's Formatting Syntax

+

This page offers a brief overview of what it's like to use Markdown. +The syntax page 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 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.

+

Paragraphs, Headers, Blockquotes

+

A paragraph is simply one or more consecutive lines of text, separated +by one or more blank lines. (A blank line is any line that looks like a +blank line -- a line containing nothing spaces or tabs is considered +blank.) Normal paragraphs should not be intended with spaces or tabs.

+

Markdown offers two styles of headers: Setext and atx. +Setext-style headers for <h1> and <h2> are created by +"underlining" with equal signs (=) and hyphens (-), respectively. +To create an atx-style header, you put 1-6 hash marks (#) at the +beginning of the line -- the number of hashes equals the resulting +HTML header level.

+

Blockquotes are indicated using email-style '>' angle brackets.

+

Markdown:

+
A First Level Header
+====================
+
+A Second Level Header
+---------------------
+
+Now is the time for all good men to come to
+the aid of their country. This is just a
+regular paragraph.
+
+The quick brown fox jumped over the lazy
+dog's back.
+
+### Header 3
+
+> This is a blockquote.
+> 
+> This is the second paragraph in the blockquote.
+>
+> ## This is an H2 in a blockquote
+
+

Output:

+
<h1>A First Level Header</h1>
+
+<h2>A Second Level Header</h2>
+
+<p>Now is the time for all good men to come to
+the aid of their country. This is just a
+regular paragraph.</p>
+
+<p>The quick brown fox jumped over the lazy
+dog's back.</p>
+
+<h3>Header 3</h3>
+
+<blockquote>
+    <p>This is a blockquote.</p>
+
+    <p>This is the second paragraph in the blockquote.</p>
+
+    <h2>This is an H2 in a blockquote</h2>
+</blockquote>
+
+

Phrase Emphasis

+

Markdown uses asterisks and underscores to indicate spans of emphasis.

+

Markdown:

+
Some of these words *are emphasized*.
+Some of these words _are emphasized also_.
+
+Use two asterisks for **strong emphasis**.
+Or, if you prefer, __use two underscores instead__.
+
+

Output:

+
<p>Some of these words <em>are emphasized</em>.
+Some of these words <em>are emphasized also</em>.</p>
+
+<p>Use two asterisks for <strong>strong emphasis</strong>.
+Or, if you prefer, <strong>use two underscores instead</strong>.</p>
+
+

Lists

+

Unordered (bulleted) lists use asterisks, pluses, and hyphens (*, ++, and -) as list markers. These three markers are +interchangable; this:

+
*   Candy.
+*   Gum.
+*   Booze.
+
+

this:

+
+   Candy.
++   Gum.
++   Booze.
+
+

and this:

+
-   Candy.
+-   Gum.
+-   Booze.
+
+

all produce the same output:

+
<ul>
+<li>Candy.</li>
+<li>Gum.</li>
+<li>Booze.</li>
+</ul>
+
+

Ordered (numbered) lists use regular numbers, followed by periods, as +list markers:

+
1.  Red
+2.  Green
+3.  Blue
+
+

Output:

+
<ol>
+<li>Red</li>
+<li>Green</li>
+<li>Blue</li>
+</ol>
+
+

If you put blank lines between items, you'll get <p> tags for the +list item text. You can create multi-paragraph list items by indenting +the paragraphs by 4 spaces or 1 tab:

+
*   A list item.
+
+    With multiple paragraphs.
+
+*   Another item in the list.
+
+

Output:

+
<ul>
+<li><p>A list item.</p>
+<p>With multiple paragraphs.</p></li>
+<li><p>Another item in the list.</p></li>
+</ul>
+
+

Links

+

Markdown supports two styles for creating links: inline and +reference. With both styles, you use square brackets to delimit the +text you want to turn into a link.

+

Inline-style links use parentheses immediately after the link text. +For example:

+
This is an [example link](http://example.com/).
+
+

Output:

+
<p>This is an <a href="http://example.com/">
+example link</a>.</p>
+
+

Optionally, you may include a title attribute in the parentheses:

+
This is an [example link](http://example.com/ "With a Title").
+
+

Output:

+
<p>This is an <a href="http://example.com/" title="With a Title">
+example link</a>.</p>
+
+

Reference-style links allow you to refer to your links by names, which +you define elsewhere in your document:

+
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"
+
+

Output:

+
<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>
+
+

The title attribute is optional. Link names may contain letters, +numbers and spaces, but are not case sensitive:

+
I start my morning with a cup of coffee and
+[The New York Times][NY Times].
+
+[ny times]: http://www.nytimes.com/
+
+

Output:

+
<p>I start my morning with a cup of coffee and
+<a href="http://www.nytimes.com/">The New York Times</a>.</p>
+
+

Images

+

Image syntax is very much like link syntax.

+

Inline (titles are optional):

+
![alt text](/path/to/img.jpg "Title")
+
+

Reference-style:

+
![alt text][id]
+
+[id]: /path/to/img.jpg "Title"
+
+

Both of the above examples produce the same output:

+
<img src="/path/to/img.jpg" alt="alt text" title="Title" />
+
+

Code

+

In a regular paragraph, you can create code span by wrapping text in +backtick quotes. Any ampersands (&) and angle brackets (< or +>) will automatically be translated into HTML entities. This makes +it easy to use Markdown to write about HTML example code:

+
I strongly recommend against using any `<blink>` tags.
+
+I wish SmartyPants used named entities like `&mdash;`
+instead of decimal-encoded entites like `&#8212;`.
+
+

Output:

+
<p>I strongly recommend against using any
+<code>&lt;blink&gt;</code> tags.</p>
+
+<p>I wish SmartyPants used named entities like
+<code>&amp;mdash;</code> instead of decimal-encoded
+entites like <code>&amp;#8212;</code>.</p>
+
+

To specify an entire block of pre-formatted code, indent every line of +the block by 4 spaces or 1 tab. Just like with code spans, &, <, +and > characters will be escaped automatically.

+

Markdown:

+
If you want your page to validate under XHTML 1.0 Strict,
+you've got to put paragraph tags in your blockquotes:
+
+    <blockquote>
+        <p>For example.</p>
+    </blockquote>
+
+

Output:

+
<p>If you want your page to validate under XHTML 1.0 Strict,
+you've got to put paragraph tags in your blockquotes:</p>
+
+<pre><code>&lt;blockquote&gt;
+    &lt;p&gt;For example.&lt;/p&gt;
+&lt;/blockquote&gt;
+</code></pre>
+
\ No newline at end of file diff --git a/markdown/tests/basic/markdown-documentation-basics.txt b/markdown/tests/basic/markdown-documentation-basics.txt new file mode 100644 index 0000000..486055c --- /dev/null +++ b/markdown/tests/basic/markdown-documentation-basics.txt @@ -0,0 +1,306 @@ +Markdown: Basics +================ + + + + +Getting the Gist of Markdown's Formatting Syntax +------------------------------------------------ + +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 + + +## Paragraphs, Headers, Blockquotes ## + +A paragraph is simply one or more consecutive lines of text, separated +by one or more blank lines. (A blank line is any line that looks like a +blank line -- a line containing nothing spaces or tabs is considered +blank.) Normal paragraphs should not be intended with spaces or tabs. + +Markdown offers two styles of headers: *Setext* and *atx*. +Setext-style headers for `

` and `

` are created by +"underlining" with equal signs (`=`) and hyphens (`-`), respectively. +To create an atx-style header, you put 1-6 hash marks (`#`) at the +beginning of the line -- the number of hashes equals the resulting +HTML header level. + +Blockquotes are indicated using email-style '`>`' angle brackets. + +Markdown: + + A First Level Header + ==================== + + A Second Level Header + --------------------- + + Now is the time for all good men to come to + the aid of their country. This is just a + regular paragraph. + + The quick brown fox jumped over the lazy + dog's back. + + ### Header 3 + + > This is a blockquote. + > + > This is the second paragraph in the blockquote. + > + > ## This is an H2 in a blockquote + + +Output: + +

A First Level Header

+ +

A Second Level Header

+ +

Now is the time for all good men to come to + the aid of their country. This is just a + regular paragraph.

+ +

The quick brown fox jumped over the lazy + dog's back.

+ +

Header 3

+ +
+

This is a blockquote.

+ +

This is the second paragraph in the blockquote.

+ +

This is an H2 in a blockquote

+
+ + + +### Phrase Emphasis ### + +Markdown uses asterisks and underscores to indicate spans of emphasis. + +Markdown: + + Some of these words *are emphasized*. + Some of these words _are emphasized also_. + + Use two asterisks for **strong emphasis**. + Or, if you prefer, __use two underscores instead__. + +Output: + +

Some of these words are emphasized. + Some of these words are emphasized also.

+ +

Use two asterisks for strong emphasis. + Or, if you prefer, use two underscores instead.

+ + + +## Lists ## + +Unordered (bulleted) lists use asterisks, pluses, and hyphens (`*`, +`+`, and `-`) as list markers. These three markers are +interchangable; this: + + * Candy. + * Gum. + * Booze. + +this: + + + Candy. + + Gum. + + Booze. + +and this: + + - Candy. + - Gum. + - Booze. + +all produce the same output: + +
    +
  • Candy.
    • +
  • Gum.
    • +
  • Booze.
    • +
+ +Ordered (numbered) lists use regular numbers, followed by periods, as +list markers: + + 1. Red + 2. Green + 3. Blue + +Output: + +
    +
  1. Red
    2. +
  2. Green
    3. +
  3. Blue
    4. +
+ +If you put blank lines between items, you'll get `

` tags for the +list item text. You can create multi-paragraph list items by indenting +the paragraphs by 4 spaces or 1 tab: + + * A list item. + + With multiple paragraphs. + + * Another item in the list. + +Output: + +

    +

  • A list item.

    +

    With multiple paragraphs.

    • +

  • Another item in the list.

    • +
+ + + +### Links ### + +Markdown supports two styles for creating links: *inline* and +*reference*. With both styles, you use square brackets to delimit the +text you want to turn into a link. + +Inline-style links use parentheses immediately after the link text. +For example: + + This is an [example link](http://example.com/). + +Output: + +

This is an + example link.

+ +Optionally, you may include a title attribute in the parentheses: + + This is an [example link](http://example.com/ "With a Title"). + +Output: + +

This is an + example link.

+ +Reference-style links allow you to refer to your links by names, which +you define elsewhere in your document: + + 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" + +Output: + +

I get 10 times more traffic from Google than from Yahoo or MSN.

+ +The title attribute is optional. Link names may contain letters, +numbers and spaces, but are *not* case sensitive: + + I start my morning with a cup of coffee and + [The New York Times][NY Times]. + + [ny times]: http://www.nytimes.com/ + +Output: + +

I start my morning with a cup of coffee and + The New York Times.

+ + +### Images ### + +Image syntax is very much like link syntax. + +Inline (titles are optional): + + ![alt text](/path/to/img.jpg "Title") + +Reference-style: + + ![alt text][id] + + [id]: /path/to/img.jpg "Title" + +Both of the above examples produce the same output: + + alt text + + + +### Code ### + +In a regular paragraph, you can create code span by wrapping text in +backtick quotes. Any ampersands (`&`) and angle brackets (`<` or +`>`) will automatically be translated into HTML entities. This makes +it easy to use Markdown to write about HTML example code: + + I strongly recommend against using any `` tags. + + I wish SmartyPants used named entities like `—` + instead of decimal-encoded entites like `—`. + +Output: + +

I strongly recommend against using any + <blink> tags.

+ +

I wish SmartyPants used named entities like + &mdash; instead of decimal-encoded + entites like &#8212;.

+ + +To specify an entire block of pre-formatted code, indent every line of +the block by 4 spaces or 1 tab. Just like with code spans, `&`, `<`, +and `>` characters will be escaped automatically. + +Markdown: + + If you want your page to validate under XHTML 1.0 Strict, + you've got to put paragraph tags in your blockquotes: + +
+

For example.

+
+ +Output: + +

If you want your page to validate under XHTML 1.0 Strict, + you've got to put paragraph tags in your blockquotes:

+ + 
<blockquote>
+        <p>For example.</p>
+    </blockquote>
+
diff --git a/markdown/tests/basic/markdown-syntax.html b/markdown/tests/basic/markdown-syntax.html new file mode 100644 index 0000000..038c9d1 --- /dev/null +++ b/markdown/tests/basic/markdown-syntax.html @@ -0,0 +1,728 @@ +

Markdown: Syntax

+ + + +

Note: This document is itself written using Markdown; you +can see the source for it by adding '.text' to the URL.

+
+

Overview

+ +

Philosophy

+ +

Markdown is intended to be as easy-to-read and easy-to-write as is feasible.

+

Readability, however, is emphasized above all else. A Markdown-formatted +document should be publishable as-is, as plain text, without looking +like it's been marked up with tags or formatting instructions. While +Markdown's syntax has been influenced by several existing text-to-HTML +filters -- including Setext, atx, Textile, reStructuredText, +Grutatext, and EtText -- the single biggest source of +inspiration for Markdown's syntax is the format of plain text email.

+

To this end, Markdown's syntax is comprised entirely of punctuation +characters, which punctuation characters have been carefully chosen so +as to look like what they mean. E.g., asterisks around a word actually +look like *emphasis*. Markdown lists look like, well, lists. Even +blockquotes look like quoted passages of text, assuming you've ever +used email.

+

Inline HTML

+ +

Markdown's syntax is intended for one purpose: to be used as a +format for writing for the web.

+

Markdown is not a replacement for HTML, or even close to it. Its +syntax is very small, corresponding only to a very small subset of +HTML tags. The idea is not to create a syntax that makes it easier +to insert HTML tags. In my opinion, HTML tags are already easy to +insert. The idea for Markdown is to make it easy to read, write, and +edit prose. HTML is a publishing format; Markdown is a writing +format. Thus, Markdown's formatting syntax only addresses issues that +can be conveyed in plain text.

+

For any markup that is not covered by Markdown's syntax, you simply +use HTML itself. There's no need to preface it or delimit it to +indicate that you're switching from Markdown to HTML; you just use +the tags.

+

The only restrictions are that block-level HTML elements -- e.g. <div>, +<table>, <pre>, <p>, etc. -- must be separated from surrounding +content by blank lines, and the start and end tags of the block should +not be indented with tabs or spaces. Markdown is smart enough not +to add extra (unwanted) <p> tags around HTML block-level tags.

+

For example, to add an HTML table to a Markdown article:

+
This is a regular paragraph.
+
+<table>
+    <tr>
+        <td>Foo</td>
+    </tr>
+</table>
+
+This is another regular paragraph.
+
+

Note that Markdown formatting syntax is not processed within block-level +HTML tags. E.g., you can't use Markdown-style *emphasis* inside an +HTML block.

+

Span-level HTML tags -- e.g. <span>, <cite>, or <del> -- can be +used anywhere in a Markdown paragraph, list item, or header. If you +want, you can even use HTML tags instead of Markdown formatting; e.g. if +you'd prefer to use HTML <a> or <img> tags instead of Markdown's +link or image syntax, go right ahead.

+

Unlike block-level HTML tags, Markdown syntax is processed within +span-level tags.

+

Automatic Escaping for Special Characters

+ +

In HTML, there are two characters that demand special treatment: < +and &. Left angle brackets are used to start tags; ampersands are +used to denote HTML entities. If you want to use them as literal +characters, you must escape them as entities, e.g. &lt;, and +&amp;.

+

Ampersands in particular are bedeviling for web writers. If you want to +write about 'AT&T', you need to write 'AT&amp;T'. You even need to +escape ampersands within URLs. Thus, if you want to link to:

+
http://images.google.com/images?num=30&q=larry+bird
+
+

you need to encode the URL as:

+
http://images.google.com/images?num=30&amp;q=larry+bird
+
+

in your anchor tag href attribute. Needless to say, this is easy to +forget, and is probably the single most common source of HTML validation +errors in otherwise well-marked-up web sites.

+

Markdown allows you to use these characters naturally, taking care of +all the necessary escaping for you. If you use an ampersand as part of +an HTML entity, it remains unchanged; otherwise it will be translated +into &amp;.

+

So, if you want to include a copyright symbol in your article, you can write:

+
&copy;
+
+

and Markdown will leave it alone. But if you write:

+
AT&T
+
+

Markdown will translate it to:

+
AT&amp;T
+
+

Similarly, because Markdown supports inline HTML, if you use +angle brackets as delimiters for HTML tags, Markdown will treat them as +such. But if you write:

+
4 < 5
+
+

Markdown will translate it to:

+
4 &lt; 5
+
+

However, inside Markdown code spans and blocks, angle brackets and +ampersands are always encoded automatically. This makes it easy to use +Markdown to write about HTML code. (As opposed to raw HTML, which is a +terrible format for writing about HTML syntax, because every single < +and & in your example code needs to be escaped.)

+
+

Block Elements

+ +

Paragraphs and Line Breaks

+ +

A paragraph is simply one or more consecutive lines of text, separated +by one or more blank lines. (A blank line is any line that looks like a +blank line -- a line containing nothing but spaces or tabs is considered +blank.) Normal paragraphs should not be intended with spaces or tabs.

+

The implication of the "one or more consecutive lines of text" rule is +that Markdown supports "hard-wrapped" text paragraphs. This differs +significantly from most other text-to-HTML formatters (including Movable +Type's "Convert Line Breaks" option) which translate every line break +character in a paragraph into a <br /> tag.

+

When you do want to insert a <br /> break tag using Markdown, you +end a line with two or more spaces, then type return.

+

Yes, this takes a tad more effort to create a <br />, but a simplistic +"every line break is a <br />" rule wouldn't work for Markdown. +Markdown's email-style blockquoting and multi-paragraph list items +work best -- and look better -- when you format them with hard breaks.

+ + +

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). For example:

+
This is an H1
+=============
+
+This is an H2
+-------------
+
+

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. For example:

+
# This is an H1
+
+## This is an H2
+
+###### This is an H6
+
+

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.) :

+
# This is an H1 #
+
+## This is an H2 ##
+
+### This is an H3 ######
+
+

Blockquotes

+ +

Markdown uses email-style > characters for blockquoting. If you're +familiar with quoting passages of text in an email message, then you +know how to create a blockquote in Markdown. It looks best if you hard +wrap the text and put a > before every line:

+
> 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.
+
+

Markdown allows you to be lazy and only put the > before the first +line of a hard-wrapped paragraph:

+
> 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.
+
+

Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by +adding additional levels of >:

+
> This is the first level of quoting.
+>
+> > This is nested blockquote.
+>
+> Back to the first level.
+
+

Blockquotes can contain other Markdown elements, including headers, lists, +and code blocks:

+
> ## 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");
+
+

Any decent text editor should make email-style quoting easy. For +example, with BBEdit, you can make a selection and choose Increase +Quote Level from the Text menu.

+

Lists

+ +

Markdown supports ordered (numbered) and unordered (bulleted) lists.

+

Unordered lists use asterisks, pluses, and hyphens -- interchangably +-- as list markers:

+
*   Red
+*   Green
+*   Blue
+
+

is equivalent to:

+
+   Red
++   Green
++   Blue
+
+

and:

+
-   Red
+-   Green
+-   Blue
+
+

Ordered lists use numbers followed by periods:

+
1.  Bird
+2.  McHale
+3.  Parish
+
+

It's important to note that the actual numbers you use to mark the +list have no effect on the HTML output Markdown produces. The HTML +Markdown produces from the above list is:

+
<ol>
+<li>Bird</li>
+<li>McHale</li>
+<li>Parish</li>
+</ol>
+
+

If you instead wrote the list in Markdown like this:

+
1.  Bird
+1.  McHale
+1.  Parish
+
+

or even:

+
3. Bird
+1. McHale
+8. Parish
+
+

you'd get the exact same HTML output. The point is, if you want to, +you can use ordinal numbers in your ordered Markdown lists, so that +the numbers in your source match the numbers in your published HTML. +But if you want to be lazy, you don't have to.

+

If you do use lazy list numbering, however, you should still start the +list with the number 1. At some point in the future, Markdown may support +starting ordered lists at an arbitrary number.

+

List markers typically start at the left margin, but may be indented by +up to three spaces. List markers must be followed by one or more spaces +or a tab.

+

To make lists look nice, you can wrap items with hanging indents:

+
*   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.
+
+

But if you want to be lazy, you don't have to:

+
*   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.
+
+

If list items are separated by blank lines, Markdown will wrap the +items in <p> tags in the HTML output. For example, this input:

+
*   Bird
+*   Magic
+
+

will turn into:

+
<ul>
+<li>Bird</li>
+<li>Magic</li>
+</ul>
+
+

But this:

+
*   Bird
+
+*   Magic
+
+

will turn into:

+
<ul>
+<li><p>Bird</p></li>
+<li><p>Magic</p></li>
+</ul>
+
+

List items may consist of multiple paragraphs. Each subsequent +paragraph in a list item must be intended by either 4 spaces +or one tab:

+
1.  This is a list item 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.
+
+2.  Suspendisse id sem consectetuer libero luctus adipiscing.
+
+

It looks nice if you indent every line of the subsequent +paragraphs, but here again, Markdown will allow you to be +lazy:

+
*   This is a list item with two paragraphs.
+
+    This is the second paragraph in the list item. You're
+only required to indent the first line. Lorem ipsum dolor
+sit amet, consectetuer adipiscing elit.
+
+*   Another item in the same list.
+
+

To put a blockquote within a list item, the blockquote's > +delimiters need to be indented:

+
*   A list item with a blockquote:
+
+    > This is a blockquote
+    > inside a list item.
+
+

To put a code block within a list item, the code block needs +to be indented twice -- 8 spaces or two tabs:

+
*   A list item with a code block:
+
+        <code goes here>
+
+

It's worth noting that it's possible to trigger an ordered list by +accident, by writing something like this:

+
1986. What a great season.
+
+

In other words, a number-period-space sequence at the beginning of a +line. To avoid this, you can backslash-escape the period:

+
1986\. What a great season.
+
+

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. For example, given this input:

+
This is a normal paragraph:
+
+    This is a code block.
+
+

Markdown will generate:

+
<p>This is a normal paragraph:</p>
+
+<pre><code>This is a code block.
+</code></pre>
+
+

One level of indentation -- 4 spaces or 1 tab -- is removed from each +line of the code block. For example, this:

+
Here is an example of AppleScript:
+
+    tell application "Foo"
+        beep
+    end tell
+
+

will turn into:

+
<p>Here is an example of AppleScript:</p>
+
+<pre><code>tell application "Foo"
+    beep
+end tell
+</code></pre>
+
+

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. For example, this:

+
    <div class="footer">
+        &copy; 2004 Foo Corporation
+    </div>
+
+

will turn into:

+
<pre><code>&lt;div class="footer"&gt;
+    &amp;copy; 2004 Foo Corporation
+&lt;/div&gt;
+</code></pre>
+
+

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.

+

Horizontal Rules

+ +

You can produce a horizontal rule tag (<hr />) by placing three or +more hyphens, asterisks, or underscores on a line by themselves. If you +wish, you may use spaces between the hyphens or asterisks. Each of the +following lines will produce a horizontal rule:

+
* * *
+
+***
+
+*****
+
+- - -
+
+---------------------------------------
+
+_ _ _
+
+
+

Span Elements

+ + + +

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. For example:

+
This is [an example](http://example.com/ "Title") inline link.
+
+[This link](http://example.net/) has no title attribute.
+
+

Will produce:

+
<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>
+
+

If you're referring to a local resource on the same server, you can +use relative paths:

+
See my [About](/about/) page for details.
+
+

Reference-style links use a second set of square brackets, inside +which you place a label of your choosing to identify the link:

+
This is [an example][id] reference-style link.
+
+

You can optionally use a space to separate the sets of brackets:

+
This is [an example] [id] reference-style link.
+
+

Then, anywhere in the document, you define your link label like this, +on a line by itself:

+
[id]: http://example.com/  "Optional Title Here"
+
+

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.
    • +
+

The link URL may, optionally, be surrounded by angle brackets:

+
[id]: <http://example.com/>  "Optional Title Here"
+
+

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:

+
[id]: http://example.com/longish/path/to/resource/here
+    "Optional Title Here"
+
+

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 constist of letters, numbers, spaces, and punctuation -- but they are not case sensitive. E.g. these two links:

+
[link text][a]
+[link text][A]
+
+

are equivalent.

+

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:

+
[Google]: http://google.com/
+
+

Because link names may contain spaces, this shortcut even works for +multiple words in the link text:

+
Visit [Daring Fireball][] for more information.
+
+

And then define the link:

+
[Daring Fireball]: http://daringfireball.net/
+
+

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.

+

Here's an example of reference links in action:

+
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"
+
+

Using the implicit link name shortcut, you could instead write:

+
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"
+
+

Both of the above examples will produce the following HTML output:

+
<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>
+
+

For comparison, here is the same paragraph written using +Markdown's inline link style:

+
I get 10 times more traffic from [Google](http://google.com/ "Google")
+than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
+[MSN](http://search.msn.com/ "MSN Search").
+
+

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.

+

Emphasis

+ +

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:

+
*single asterisks*
+
+_single underscores_
+
+**double asterisks**
+
+__double underscores__
+
+

will produce:

+
<em>single asterisks</em>
+
+<em>single underscores</em>
+
+<strong>double asterisks</strong>
+
+<strong>double underscores</strong>
+
+

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:

+
un*fucking*believable
+
+

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\*
+
+

Code

+ +

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. For example:

+
Use the `printf()` function.
+
+

will produce:

+
<p>Use the <code>printf()</code> function.</p>
+
+

To include a literal backtick character within a code span, you can use +multiple backticks as the opening and closing delimiters:

+
``There is a literal backtick (`) here.``
+
+

which will produce this:

+
<p><code>There is a literal backtick (`) here.</code></p>
+
+

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:

+
A single backtick in a code span: `` ` ``
+
+A backtick-delimited string in a code span: `` `foo` ``
+
+

will produce:

+
<p>A single backtick in a code span: <code>`</code></p>
+
+<p>A backtick-delimited string in a code span: <code>`foo`</code></p>
+
+

With a code span, ampersands and angle brackets are encoded as HTML +entities automatically, which makes it easy to include example HTML +tags. Markdown will turn this:

+
Please don't use any `<blink>` tags.
+
+

into:

+
<p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>
+
+

You can write this:

+
`&#8212;` is the decimal-encoded equivalent of `&mdash;`.
+
+

to produce:

+
<p><code>&amp;#8212;</code> is the decimal-encoded
+equivalent of <code>&amp;mdash;</code>.</p>
+
+

Images

+ +

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:

+
[id]: url/to/image  "Optional title attribute"
+
+

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.

+
+

Miscellaneous

+ + + +

Markdown supports a shortcut style for creating "automatic" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:

+
<http://example.com/>
+
+

Markdown will turn this into:

+
<a href="http://example.com/">http://example.com/</a>
+
+

Automatic links for email addresses work similarly, except that +Markdown will also perform a bit of randomized decimal and hex +entity-encoding to help obscure your address from address-harvesting +spambots. For example, Markdown will turn this:

+
<address@example.com>
+
+

into something like this:

+
<a href="&#x6D;&#x61;i&#x6C;&#x74;&#x6F;:&#x61;&#x64;&#x64;&#x72;&#x65;
+&#115;&#115;&#64;&#101;&#120;&#x61;&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;
+&#109;">&#x61;&#x64;&#x64;&#x72;&#x65;&#115;&#115;&#64;&#101;&#120;&#x61;
+&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;&#109;</a>
+
+

which will render in a browser as a clickable link to "address@example.com".

+

(This sort of entity-encoding trick will indeed fool many, if not +most, address-harvesting bots, but it definitely won't fool all of +them. It's better than nothing, but an address published in this way +will probably eventually start receiving spam.)

+

Backslash Escapes

+ +

Markdown allows you to use backslash escapes to generate literal +characters which would otherwise have special meaning in Markdown's +formatting syntax. For example, if you wanted to surround a word with +literal asterisks (instead of an HTML <em> tag), you can backslashes +before the asterisks, like this:

+
\*literal asterisks\*
+
+

Markdown provides backslash escapes for the following characters:

+
\   backslash
+`   backtick
+*   asterisk
+_   underscore
+{}  curly braces
+[]  square brackets
+()  parentheses
+#   hash mark
++   plus sign
+-   minus sign (hyphen)
+.   dot
+!   exclamation mark
+
\ No newline at end of file diff --git a/markdown/tests/basic/markdown-syntax.txt b/markdown/tests/basic/markdown-syntax.txt new file mode 100644 index 0000000..dabd75c --- /dev/null +++ b/markdown/tests/basic/markdown-syntax.txt @@ -0,0 +1,888 @@ +Markdown: Syntax +================ + + + + +* [Overview](#overview) + * [Philosophy](#philosophy) + * [Inline HTML](#html) + * [Automatic Escaping for Special Characters](#autoescape) +* [Block Elements](#block) + * [Paragraphs and Line Breaks](#p) + * [Headers](#header) + * [Blockquotes](#blockquote) + * [Lists](#list) + * [Code Blocks](#precode) + * [Horizontal Rules](#hr) +* [Span Elements](#span) + * [Links](#link) + * [Emphasis](#em) + * [Code](#code) + * [Images](#img) +* [Miscellaneous](#misc) + * [Backslash Escapes](#backslash) + * [Automatic Links](#autolink) + + +**Note:** This document is itself written using Markdown; you +can [see the source for it by adding '.text' to the URL][src]. + + [src]: /projects/markdown/syntax.text + +* * * + +

Overview

+ +

Philosophy

+ +Markdown is intended to be as easy-to-read and easy-to-write as is feasible. + +Readability, however, is emphasized above all else. A Markdown-formatted +document should be publishable as-is, as plain text, without looking +like it's been marked up with tags or formatting instructions. While +Markdown's syntax has been influenced by several existing text-to-HTML +filters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [4], +[Grutatext] [5], and [EtText] [6] -- the single biggest source of +inspiration for Markdown's syntax is the format of plain text email. + + [1]: http://docutils.sourceforge.net/mirror/setext.html + [2]: http://www.aaronsw.com/2002/atx/ + [3]: http://textism.com/tools/textile/ + [4]: http://docutils.sourceforge.net/rst.html + [5]: http://www.triptico.com/software/grutatxt.html + [6]: http://ettext.taint.org/doc/ + +To this end, Markdown's syntax is comprised entirely of punctuation +characters, which punctuation characters have been carefully chosen so +as to look like what they mean. E.g., asterisks around a word actually +look like \*emphasis\*. Markdown lists look like, well, lists. Even +blockquotes look like quoted passages of text, assuming you've ever +used email. + + + +

Inline HTML

+ +Markdown's syntax is intended for one purpose: to be used as a +format for *writing* for the web. + +Markdown is not a replacement for HTML, or even close to it. Its +syntax is very small, corresponding only to a very small subset of +HTML tags. The idea is *not* to create a syntax that makes it easier +to insert HTML tags. In my opinion, HTML tags are already easy to +insert. The idea for Markdown is to make it easy to read, write, and +edit prose. HTML is a *publishing* format; Markdown is a *writing* +format. Thus, Markdown's formatting syntax only addresses issues that +can be conveyed in plain text. + +For any markup that is not covered by Markdown's syntax, you simply +use HTML itself. There's no need to preface it or delimit it to +indicate that you're switching from Markdown to HTML; you just use +the tags. + +The only restrictions are that block-level HTML elements -- e.g. `
`, +``, `
`, `
`, etc. -- must be separated from surrounding
+content by blank lines, and the start and end tags of the block should
+not be indented with tabs or spaces. Markdown is smart enough not
+to add extra (unwanted) `
` tags around HTML block-level tags.
+
+For example, to add an HTML table to a Markdown article:
+
+    This is a regular paragraph.
+
+
+ + + +
Foo
+ + This is another regular paragraph. + +Note that Markdown formatting syntax is not processed within block-level +HTML tags. E.g., you can't use Markdown-style `*emphasis*` inside an +HTML block. + +Span-level HTML tags -- e.g. ``, ``, or `` -- can be +used anywhere in a Markdown paragraph, list item, or header. If you +want, you can even use HTML tags instead of Markdown formatting; e.g. if +you'd prefer to use HTML `` or `` tags instead of Markdown's +link or image syntax, go right ahead. + +Unlike block-level HTML tags, Markdown syntax *is* processed within +span-level tags. + + +

Automatic Escaping for Special Characters

+ +In HTML, there are two characters that demand special treatment: `<` +and `&`. Left angle brackets are used to start tags; ampersands are +used to denote HTML entities. If you want to use them as literal +characters, you must escape them as entities, e.g. `<`, and +`&`. + +Ampersands in particular are bedeviling for web writers. If you want to +write about 'AT&T', you need to write '`AT&T`'. You even need to +escape ampersands within URLs. Thus, if you want to link to: + + http://images.google.com/images?num=30&q=larry+bird + +you need to encode the URL as: + + http://images.google.com/images?num=30&q=larry+bird + +in your anchor tag `href` attribute. Needless to say, this is easy to +forget, and is probably the single most common source of HTML validation +errors in otherwise well-marked-up web sites. + +Markdown allows you to use these characters naturally, taking care of +all the necessary escaping for you. If you use an ampersand as part of +an HTML entity, it remains unchanged; otherwise it will be translated +into `&`. + +So, if you want to include a copyright symbol in your article, you can write: + + © + +and Markdown will leave it alone. But if you write: + + AT&T + +Markdown will translate it to: + + AT&T + +Similarly, because Markdown supports [inline HTML](#html), if you use +angle brackets as delimiters for HTML tags, Markdown will treat them as +such. But if you write: + + 4 < 5 + +Markdown will translate it to: + + 4 < 5 + +However, inside Markdown code spans and blocks, angle brackets and +ampersands are *always* encoded automatically. This makes it easy to use +Markdown to write about HTML code. (As opposed to raw HTML, which is a +terrible format for writing about HTML syntax, because every single `<` +and `&` in your example code needs to be escaped.) + + +* * * + + +

Block Elements

+ + +

Paragraphs and Line Breaks

+ +A paragraph is simply one or more consecutive lines of text, separated +by one or more blank lines. (A blank line is any line that looks like a +blank line -- a line containing nothing but spaces or tabs is considered +blank.) Normal paragraphs should not be intended with spaces or tabs. + +The implication of the "one or more consecutive lines of text" rule is +that Markdown supports "hard-wrapped" text paragraphs. This differs +significantly from most other text-to-HTML formatters (including Movable +Type's "Convert Line Breaks" option) which translate every line break +character in a paragraph into a `
` tag. + +When you *do* want to insert a `
` break tag using Markdown, you +end a line with two or more spaces, then type return. + +Yes, this takes a tad more effort to create a `
`, but a simplistic +"every line break is a `
`" rule wouldn't work for Markdown. +Markdown's email-style [blockquoting][bq] and multi-paragraph [list items][l] +work best -- and look better -- when you format them with hard breaks. + + [bq]: #blockquote + [l]: #list + + + + + +Markdown supports two styles of headers, [Setext] [1] and [atx] [2]. + +Setext-style headers are "underlined" using equal signs (for first-level +headers) and dashes (for second-level headers). For example: + + This is an H1 + ============= + + This is an H2 + ------------- + +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. For example: + + # This is an H1 + + ## This is an H2 + + ###### This is an H6 + +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.) : + + # This is an H1 # + + ## This is an H2 ## + + ### This is an H3 ###### + + +

Blockquotes

+ +Markdown uses email-style `>` characters for blockquoting. If you're +familiar with quoting passages of text in an email message, then you +know how to create a blockquote in Markdown. It looks best if you hard +wrap the text and put a `>` before every line: + + > 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. + +Markdown allows you to be lazy and only put the `>` before the first +line of a hard-wrapped paragraph: + + > 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. + +Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by +adding additional levels of `>`: + + > This is the first level of quoting. + > + > > This is nested blockquote. + > + > Back to the first level. + +Blockquotes can contain other Markdown elements, including headers, lists, +and code blocks: + + > ## 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"); + +Any decent text editor should make email-style quoting easy. For +example, with BBEdit, you can make a selection and choose Increase +Quote Level from the Text menu. + + +

Lists

+ +Markdown supports ordered (numbered) and unordered (bulleted) lists. + +Unordered lists use asterisks, pluses, and hyphens -- interchangably +-- as list markers: + + * Red + * Green + * Blue + +is equivalent to: + + + Red + + Green + + Blue + +and: + + - Red + - Green + - Blue + +Ordered lists use numbers followed by periods: + + 1. Bird + 2. McHale + 3. Parish + +It's important to note that the actual numbers you use to mark the +list have no effect on the HTML output Markdown produces. The HTML +Markdown produces from the above list is: + +
    +
  1. Bird
    2. +
  2. McHale
    3. +
  3. Parish
    4. +
+ +If you instead wrote the list in Markdown like this: + + 1. Bird + 1. McHale + 1. Parish + +or even: + + 3. Bird + 1. McHale + 8. Parish + +you'd get the exact same HTML output. The point is, if you want to, +you can use ordinal numbers in your ordered Markdown lists, so that +the numbers in your source match the numbers in your published HTML. +But if you want to be lazy, you don't have to. + +If you do use lazy list numbering, however, you should still start the +list with the number 1. At some point in the future, Markdown may support +starting ordered lists at an arbitrary number. + +List markers typically start at the left margin, but may be indented by +up to three spaces. List markers must be followed by one or more spaces +or a tab. + +To make lists look nice, you can wrap items with hanging indents: + + * 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. + +But if you want to be lazy, you don't have to: + + * 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. + +If list items are separated by blank lines, Markdown will wrap the +items in `

` tags in the HTML output. For example, this input: + + * Bird + * Magic + +will turn into: + +

    +
  • Bird
    • +
  • Magic
    • +
+ +But this: + + * Bird + + * Magic + +will turn into: + +
    +

  • Bird

    • +

  • Magic

    • +
+ +List items may consist of multiple paragraphs. Each subsequent +paragraph in a list item must be intended by either 4 spaces +or one tab: + + 1. This is a list item 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. + + 2. Suspendisse id sem consectetuer libero luctus adipiscing. + +It looks nice if you indent every line of the subsequent +paragraphs, but here again, Markdown will allow you to be +lazy: + + * This is a list item with two paragraphs. + + This is the second paragraph in the list item. You're + only required to indent the first line. Lorem ipsum dolor + sit amet, consectetuer adipiscing elit. + + * Another item in the same list. + +To put a blockquote within a list item, the blockquote's `>` +delimiters need to be indented: + + * A list item with a blockquote: + + > This is a blockquote + > inside a list item. + +To put a code block within a list item, the code block needs +to be indented *twice* -- 8 spaces or two tabs: + + * A list item with a code block: + + + + +It's worth noting that it's possible to trigger an ordered list by +accident, by writing something like this: + + 1986. What a great season. + +In other words, a *number-period-space* sequence at the beginning of a +line. To avoid this, you can backslash-escape the period: + + 1986\. What a great season. + + + +

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 `
` and `` tags.
+
+To produce a code block in Markdown, simply indent every line of the
+block by at least 4 spaces or 1 tab. For example, given this input:
+
+    This is a normal paragraph:
+
+        This is a code block.
+
+Markdown will generate:
+
+    
This is a normal paragraph:

+
+    
This is a code block.
+    

+
+One level of indentation -- 4 spaces or 1 tab -- is removed from each
+line of the code block. For example, this:
+
+    Here is an example of AppleScript:
+
+        tell application "Foo"
+            beep
+        end tell
+
+will turn into:
+
+    
Here is an example of AppleScript:

+
+    
tell application "Foo"
+        beep
+    end tell
+    

+
+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. For example, this:
+
+        

+            © 2004 Foo Corporation
+        

+
+will turn into:
+
+    
<div class="footer">
+        &copy; 2004 Foo Corporation
+    </div>
+    

+
+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.
+
+
+
+
Horizontal Rules

+
+You can produce a horizontal rule tag (`
`) by placing three or
+more hyphens, asterisks, or underscores on a line by themselves. If you
+wish, you may use spaces between the hyphens or asterisks. Each of the
+following lines will produce a horizontal rule:
+
+    * * *
+
+    ***
+
+    *****
+	
+    - - -
+
+    ---------------------------------------
+
+	_ _ _
+
+
+* * *
+
+
Span Elements

+
+
+
+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. For example:
+
+    This is [an example](http://example.com/ "Title") inline link.
+
+    [This link](http://example.net/) has no title attribute.
+
+Will produce:
+
+    
This is 
+    an example inline link.

+
+    
This link has no
+    title attribute.

+
+If you're referring to a local resource on the same server, you can
+use relative paths:
+
+    See my [About](/about/) page for details.   
+
+Reference-style links use a second set of square brackets, inside
+which you place a label of your choosing to identify the link:
+
+    This is [an example][id] reference-style link.
+
+You can optionally use a space to separate the sets of brackets:
+
+    This is [an example] [id] reference-style link.
+
+Then, anywhere in the document, you define your link label like this,
+on a line by itself:
+
+    [id]: http://example.com/  "Optional Title Here"
+
+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.
+
+The link URL may, optionally, be surrounded by angle brackets:
+
+    [id]:   "Optional Title Here"
+
+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:
+
+    [id]: http://example.com/longish/path/to/resource/here
+        "Optional Title Here"
+
+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 constist of letters, numbers, spaces, and punctuation -- but they are *not* case sensitive. E.g. these two links:
+
+	[link text][a]
+	[link text][A]
+
+are equivalent.
+
+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:
+
+	[Google]: http://google.com/
+
+Because link names may contain spaces, this shortcut even works for
+multiple words in the link text:
+
+	Visit [Daring Fireball][] for more information.
+
+And then define the link:
+	
+	[Daring Fireball]: http://daringfireball.net/
+
+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.
+
+Here's an example of reference links in action:
+
+    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"
+
+Using the implicit link name shortcut, you could instead write:
+
+    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"
+
+Both of the above examples will produce the following HTML output:
+
+    
I get 10 times more traffic from Google than from
+    Yahoo
+    or MSN.

+
+For comparison, here is the same paragraph written using
+Markdown's inline link style:
+
+    I get 10 times more traffic from [Google](http://google.com/ "Google")
+    than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
+    [MSN](http://search.msn.com/ "MSN Search").
+
+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.
+
+
+
Emphasis

+
+Markdown treats asterisks (`*`) and underscores (`_`) as indicators of
+emphasis. Text wrapped with one `*` or `_` will be wrapped with an
+HTML `` tag; double `*`'s or `_`'s will be wrapped with an HTML
+`` tag. E.g., this input:
+
+    *single asterisks*
+
+    _single underscores_
+
+    **double asterisks**
+
+    __double underscores__
+
+will produce:
+
+    single asterisks
+
+    single underscores
+
+    double asterisks
+
+    double underscores
+
+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:
+
+    un*fucking*believable
+
+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\*
+
+
+
+
Code

+
+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. For example:
+
+    Use the `printf()` function.
+
+will produce:
+
+    
Use the printf() function.

+
+To include a literal backtick character within a code span, you can use
+multiple backticks as the opening and closing delimiters:
+
+    ``There is a literal backtick (`) here.``
+
+which will produce this:
+
+    
There is a literal backtick (`) here.

+
+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:
+
+	A single backtick in a code span: `` ` ``
+	
+	A backtick-delimited string in a code span: `` `foo` ``
+
+will produce:
+
+	
A single backtick in a code span: `

+	
+	
A backtick-delimited string in a code span: `foo`

+
+With a code span, ampersands and angle brackets are encoded as HTML
+entities automatically, which makes it easy to include example HTML
+tags. Markdown will turn this:
+
+    Please don't use any `` tags.
+
+into:
+
+    
Please don't use any <blink> tags.

+
+You can write this:
+
+    `—` is the decimal-encoded equivalent of `—`.
+
+to produce:
+
+    
&#8212; is the decimal-encoded
+    equivalent of &mdash;.

+
+
+
+
Images

+
+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:
+
+    [id]: url/to/image  "Optional title attribute"
+
+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 `` tags.
+
+
+* * *
+
+
+
Miscellaneous

+
+
+
+Markdown supports a shortcut style for creating "automatic" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:
+
+    
+    
+Markdown will turn this into:
+
+    http://example.com/
+
+Automatic links for email addresses work similarly, except that
+Markdown will also perform a bit of randomized decimal and hex
+entity-encoding to help obscure your address from address-harvesting
+spambots. For example, Markdown will turn this:
+
+    
+
+into something like this:
+
+    address@exa
+    mple.com
+
+which will render in a browser as a clickable link to "address@example.com".
+
+(This sort of entity-encoding trick will indeed fool many, if not
+most, address-harvesting bots, but it definitely won't fool all of
+them. It's better than nothing, but an address published in this way
+will probably eventually start receiving spam.)
+
+
+
+
Backslash Escapes

+
+Markdown allows you to use backslash escapes to generate literal
+characters which would otherwise have special meaning in Markdown's
+formatting syntax. For example, if you wanted to surround a word with
+literal asterisks (instead of an HTML `` tag), you can backslashes
+before the asterisks, like this:
+
+    \*literal asterisks\*
+
+Markdown provides backslash escapes for the following characters:
+
+    \   backslash
+    `   backtick
+    *   asterisk
+    _   underscore
+    {}  curly braces
+    []  square brackets
+    ()  parentheses
+    #   hash mark
+	+	plus sign
+	-	minus sign (hyphen)
+    .   dot
+    !   exclamation mark
+
diff --git a/markdown/tests/basic/nested-blockquotes.html b/markdown/tests/basic/nested-blockquotes.html
new file mode 100644
index 0000000..f1b017e
--- /dev/null
+++ b/markdown/tests/basic/nested-blockquotes.html
@@ -0,0 +1,7 @@
+

+
foo

+

+
bar

+

+
foo

+

\ No newline at end of file
diff --git a/markdown/tests/basic/nested-blockquotes.txt b/markdown/tests/basic/nested-blockquotes.txt
new file mode 100644
index 0000000..ed3c624
--- /dev/null
+++ b/markdown/tests/basic/nested-blockquotes.txt
@@ -0,0 +1,5 @@
+> foo
+>
+> > bar
+>
+> foo
diff --git a/markdown/tests/basic/ordered-and-unordered-list.html b/markdown/tests/basic/ordered-and-unordered-list.html
new file mode 100644
index 0000000..090c43c
--- /dev/null
+++ b/markdown/tests/basic/ordered-and-unordered-list.html
@@ -0,0 +1,146 @@
+
Unordered

+
Asterisks tight:

+
    
+
  • asterisk 1
    • 
+
  • asterisk 2
    • 
+
  • asterisk 3
    • 
+

+
Asterisks loose:

+
    
+
  • 
+
    asterisk 1
    
+
    • 
+
  • 
+
    asterisk 2
    
+
    • 
+
  • 
+
    asterisk 3
    
+
    • 
+

+

+
Pluses tight:

+
    
+
  • Plus 1
    • 
+
  • Plus 2
    • 
+
  • Plus 3
    • 
+

+
Pluses loose:

+
    
+
  • 
+
    Plus 1
    
+
    • 
+
  • 
+
    Plus 2
    
+
    • 
+
  • 
+
    Plus 3
    
+
    • 
+

+

+
Minuses tight:

+
    
+
  • Minus 1
    • 
+
  • Minus 2
    • 
+
  • Minus 3
    • 
+

+
Minuses loose:

+
    
+
  • 
+
    Minus 1
    
+
    • 
+
  • 
+
    Minus 2
    
+
    • 
+
  • 
+
    Minus 3
    
+
    • 
+

+
Ordered

+
Tight:

+
    
+
  1. First
    2. 
+
  2. Second
    3. 
+
  3. Third
    4. 
+

+
and:

+
    
+
  1. One
    2. 
+
  2. Two
    3. 
+
  3. Three
    4. 
+

+
Loose using tabs:

+
    
+
  1. 
+
    First
    
+
    2. 
+
  2. 
+
    Second
    
+
    3. 
+
  3. 
+
    Third
    
+
    4. 
+

+
and using spaces:

+
    
+
  1. 
+
    One
    
+
    2. 
+
  2. 
+
    Two
    
+
    3. 
+
  3. 
+
    Three
    
+
    4. 
+

+
Multiple paragraphs:

+
    
+
  1. 
+
    Item 1, graf one.
    
+
    Item 2. graf two. The quick brown fox jumped over the lazy dog's
+back.
    
+
    2. 
+
  2. 
+
    Item 2.
    
+
    3. 
+
  3. 
+
    Item 3.
    
+
    4. 
+

+
Nested

+
    
+
  • Tab
      
+
    • Tab
        
+
      • Tab
        • 
+
      
+
      • 
+
    
+
    • 
+

+
Here's another:

+
    
+
  1. First
    2. 
+
  2. Second:
      
+
    • Fee
      • 
+
    • Fie
      • 
+
    • Foe
      • 
+
    
+
    3. 
+
  3. Third
    4. 
+

+
Same thing but with paragraphs:

+
    
+
  1. 
+
    First
    
+
    2. 
+
  2. 
+
    Second:
    
+
      
+
    • Fee
      • 
+
    • Fie
      • 
+
    • Foe
      • 
+
    
+
    3. 
+
  3. 
+
    Third
    
+
    4. 
+

\ No newline at end of file
diff --git a/markdown/tests/basic/ordered-and-unordered-list.txt b/markdown/tests/basic/ordered-and-unordered-list.txt
new file mode 100644
index 0000000..621db58
--- /dev/null
+++ b/markdown/tests/basic/ordered-and-unordered-list.txt
@@ -0,0 +1,122 @@
+## Unordered
+
+Asterisks tight:
+
+*	asterisk 1
+*	asterisk 2
+*	asterisk 3
+
+
+Asterisks loose:
+
+*	asterisk 1
+
+*	asterisk 2
+
+*	asterisk 3
+
+* * *
+
+Pluses tight:
+
++	Plus 1
++	Plus 2
++	Plus 3
+
+
+Pluses loose:
+
++	Plus 1
+
++	Plus 2
+
++	Plus 3
+
+* * *
+
+
+Minuses tight:
+
+-	Minus 1
+-	Minus 2
+-	Minus 3
+
+
+Minuses loose:
+
+-	Minus 1
+
+-	Minus 2
+
+-	Minus 3
+
+
+## Ordered
+
+Tight:
+
+1.	First
+2.	Second
+3.	Third
+
+and:
+
+1. One
+2. Two
+3. Three
+
+
+Loose using tabs:
+
+1.	First
+
+2.	Second
+
+3.	Third
+
+and using spaces:
+
+1. One
+
+2. Two
+
+3. Three
+
+Multiple paragraphs:
+
+1.	Item 1, graf one.
+
+	Item 2. graf two. The quick brown fox jumped over the lazy dog's
+	back.
+	
+2.	Item 2.
+
+3.	Item 3.
+
+
+
+## Nested
+
+*	Tab
+	*	Tab
+		*	Tab
+
+Here's another:
+
+1. First
+2. Second:
+	* Fee
+	* Fie
+	* Foe
+3. Third
+
+Same thing but with paragraphs:
+
+1. First
+
+2. Second:
+	* Fee
+	* Fie
+	* Foe
+
+3. Third
diff --git a/markdown/tests/basic/strong-and-em-together.html b/markdown/tests/basic/strong-and-em-together.html
new file mode 100644
index 0000000..7bf5163
--- /dev/null
+++ b/markdown/tests/basic/strong-and-em-together.html
@@ -0,0 +1,4 @@
+
This is strong and em.

+
So is this word.

+
This is strong and em.

+
So is this word.

\ No newline at end of file
diff --git a/markdown/tests/basic/strong-and-em-together.txt b/markdown/tests/basic/strong-and-em-together.txt
new file mode 100644
index 0000000..95ee690
--- /dev/null
+++ b/markdown/tests/basic/strong-and-em-together.txt
@@ -0,0 +1,7 @@
+***This is strong and em.***
+
+So is ***this*** word.
+
+___This is strong and em.___
+
+So is ___this___ word.
diff --git a/markdown/tests/basic/tabs.html b/markdown/tests/basic/tabs.html
new file mode 100644
index 0000000..3c11f14
--- /dev/null
+++ b/markdown/tests/basic/tabs.html
@@ -0,0 +1,23 @@
+
    
+
  • 
+
    this is a list item
+    indented with tabs
    
+
    • 
+
  • 
+
    this is a list item
+    indented with spaces
    
+
    • 
+

+
Code:

+
this code block is indented by one tab
+

+
And:

+
    this code block is indented by two tabs
+

+
And:

+
+   this is an example list item
+    indented with tabs
+
++   this is an example list item
+    indented with spaces
+

\ No newline at end of file
diff --git a/markdown/tests/basic/tabs.txt b/markdown/tests/basic/tabs.txt
new file mode 100644
index 0000000..589d113
--- /dev/null
+++ b/markdown/tests/basic/tabs.txt
@@ -0,0 +1,21 @@
++	this is a list item
+	indented with tabs
+
++   this is a list item
+    indented with spaces
+
+Code:
+
+	this code block is indented by one tab
+
+And:
+
+		this code block is indented by two tabs
+
+And:
+
+	+	this is an example list item
+		indented with tabs
+	
+	+   this is an example list item
+	    indented with spaces
diff --git a/markdown/tests/basic/tidyness.html b/markdown/tests/basic/tidyness.html
new file mode 100644
index 0000000..52b2eaf
--- /dev/null
+++ b/markdown/tests/basic/tidyness.html
@@ -0,0 +1,8 @@
+

+
A list within a blockquote:

+
    
+
  • asterisk 1
    • 
+
  • asterisk 2
    • 
+
  • asterisk 3
    • 
+

+

\ No newline at end of file
diff --git a/markdown/tests/basic/tidyness.txt b/markdown/tests/basic/tidyness.txt
new file mode 100644
index 0000000..5f18b8d
--- /dev/null
+++ b/markdown/tests/basic/tidyness.txt
@@ -0,0 +1,5 @@
+> A list within a blockquote:
+> 
+> *	asterisk 1
+> *	asterisk 2
+> *	asterisk 3
diff --git a/markdown/tests/markdown-test/amps-and-angle-encoding.html b/markdown/tests/markdown-test/amps-and-angle-encoding.html
deleted file mode 100644
index 2c466c1..0000000
--- a/markdown/tests/markdown-test/amps-and-angle-encoding.html
+++ /dev/null
@@ -1,9 +0,0 @@
-
AT&T has an ampersand in their name.

-
AT&T is another way to write it.

-
This & that.

-
4 < 5.

-
6 > 5.

-
Here's a link with an ampersand in the URL.

-
Here's a link with an amersand in the link text: AT&T.

-
Here's an inline link.

-
Here's an inline link.

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/amps-and-angle-encoding.txt b/markdown/tests/markdown-test/amps-and-angle-encoding.txt
deleted file mode 100644
index 0e9527f..0000000
--- a/markdown/tests/markdown-test/amps-and-angle-encoding.txt
+++ /dev/null
@@ -1,21 +0,0 @@
-AT&T has an ampersand in their name.
-
-AT&T is another way to write it.
-
-This & that.
-
-4 < 5.
-
-6 > 5.
-
-Here's a [link] [1] with an ampersand in the URL.
-
-Here's a link with an amersand in the link text: [AT&T] [2].
-
-Here's an inline [link](/script?foo=1&bar=2).
-
-Here's an inline [link]().
-
-
-[1]: http://example.com/?foo=1&bar=2
-[2]: http://att.com/  "AT&T"
\ No newline at end of file
diff --git a/markdown/tests/markdown-test/angle-links-and-img.html b/markdown/tests/markdown-test/angle-links-and-img.html
deleted file mode 100644
index 1ca3b0b..0000000
--- a/markdown/tests/markdown-test/angle-links-and-img.html
+++ /dev/null
@@ -1,4 +0,0 @@
-
link
-image
-link
-image

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/angle-links-and-img.txt b/markdown/tests/markdown-test/angle-links-and-img.txt
deleted file mode 100644
index 1dbf404..0000000
--- a/markdown/tests/markdown-test/angle-links-and-img.txt
+++ /dev/null
@@ -1,4 +0,0 @@
-[link]( "title")
-![image]()
-[link]()
-![image]()
diff --git a/markdown/tests/markdown-test/auto-links.html b/markdown/tests/markdown-test/auto-links.html
deleted file mode 100644
index 7481fe2..0000000
--- a/markdown/tests/markdown-test/auto-links.html
+++ /dev/null
@@ -1,15 +0,0 @@
-
Link: http://example.com/.

-
Https link: https://example.com

-
Ftp link: ftp://example.com

-
With an ampersand: http://example.com/?foo=1&bar=2

-
-

-
Blockquoted: http://example.com/

-

-
Auto-links should not occur here: <http://example.com/>

-
or here: <http://example.com/>
-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/auto-links.txt b/markdown/tests/markdown-test/auto-links.txt
deleted file mode 100644
index a188b40..0000000
--- a/markdown/tests/markdown-test/auto-links.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-Link: .
-
-Https link: 
-
-Ftp link: 
-
-With an ampersand: 
-
-* In a list?
-* 
-* It should.
-
-> Blockquoted: 
-
-Auto-links should not occur here: ``
-
-	or here: 
diff --git a/markdown/tests/markdown-test/backlash-escapes.html b/markdown/tests/markdown-test/backlash-escapes.html
deleted file mode 100644
index 876775f..0000000
--- a/markdown/tests/markdown-test/backlash-escapes.html
+++ /dev/null
@@ -1,67 +0,0 @@
-
These should all get escaped:

-
Backslash: \

-
Backtick: `

-
Asterisk: *

-
Underscore: _

-
Left brace: {

-
Right brace: }

-
Left bracket: [

-
Right bracket: ]

-
Left paren: (

-
Right paren: )

-
Greater-than: >

-
Hash: #

-
Period: .

-
Bang: !

-
Plus: +

-
Minus: -

-
These should not, because they occur within a code block:

-
Backslash: \\
-
-Backtick: \`
-
-Asterisk: \*
-
-Underscore: \_
-
-Left brace: \{
-
-Right brace: \}
-
-Left bracket: \[
-
-Right bracket: \]
-
-Left paren: \(
-
-Right paren: \)
-
-Greater-than: \>
-
-Hash: \#
-
-Period: \.
-
-Bang: \!
-
-Plus: \+
-
-Minus: \-
-

-
Nor should these, which occur in code spans:

-
Backslash: \\

-
Backtick: \`

-
Asterisk: \*

-
Underscore: \_

-
Left brace: \{

-
Right brace: \}

-
Left bracket: \[

-
Right bracket: \]

-
Left paren: \(

-
Right paren: \)

-
Greater-than: \>

-
Hash: \#

-
Period: \.

-
Bang: \!

-
Plus: \+

-
Minus: \-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/backlash-escapes.txt b/markdown/tests/markdown-test/backlash-escapes.txt
deleted file mode 100644
index 16447a0..0000000
--- a/markdown/tests/markdown-test/backlash-escapes.txt
+++ /dev/null
@@ -1,104 +0,0 @@
-These should all get escaped:
-
-Backslash: \\
-
-Backtick: \`
-
-Asterisk: \*
-
-Underscore: \_
-
-Left brace: \{
-
-Right brace: \}
-
-Left bracket: \[
-
-Right bracket: \]
-
-Left paren: \(
-
-Right paren: \)
-
-Greater-than: \>
-
-Hash: \#
-
-Period: \.
-
-Bang: \!
-
-Plus: \+
-
-Minus: \-
-
-
-
-These should not, because they occur within a code block:
-
-	Backslash: \\
-
-	Backtick: \`
-
-	Asterisk: \*
-
-	Underscore: \_
-
-	Left brace: \{
-
-	Right brace: \}
-
-	Left bracket: \[
-
-	Right bracket: \]
-
-	Left paren: \(
-
-	Right paren: \)
-
-	Greater-than: \>
-
-	Hash: \#
-
-	Period: \.
-
-	Bang: \!
-
-	Plus: \+
-
-	Minus: \-
-
-
-Nor should these, which occur in code spans:
-
-Backslash: `\\`
-
-Backtick: `` \` ``
-
-Asterisk: `\*`
-
-Underscore: `\_`
-
-Left brace: `\{`
-
-Right brace: `\}`
-
-Left bracket: `\[`
-
-Right bracket: `\]`
-
-Left paren: `\(`
-
-Right paren: `\)`
-
-Greater-than: `\>`
-
-Hash: `\#`
-
-Period: `\.`
-
-Bang: `\!`
-
-Plus: `\+`
-
-Minus: `\-`
diff --git a/markdown/tests/markdown-test/benchmark.dat b/markdown/tests/markdown-test/benchmark.dat
deleted file mode 100644
index 3d549dd..0000000
--- a/markdown/tests/markdown-test/benchmark.dat
+++ /dev/null
@@ -1,20 +0,0 @@
-construction:0.000000:0.000000
-amps-and-angle-encoding:0.070000:131072.000000
-auto-links:0.080000:397312.000000
-backlash-escapes:0.270000:884736.000000
-blockquotes-with-dode-blocks:0.020000:0.000000
-hard-wrapped:0.020000:0.000000
-horizontal-rules:0.180000:135168.000000
-inline-html-advanced:0.070000:0.000000
-inline-html-comments:0.080000:0.000000
-inline-html-simple:0.210000:0.000000
-links-inline:0.140000:0.000000
-links-reference:0.170000:0.000000
-literal-quotes:0.090000:0.000000
-markdown-documentation-basics:0.690000:1806336.000000
-markdown-syntax:3.310000:6696960.000000
-nested-blockquotes:0.200000:0.000000
-ordered-and-unordered-list:0.530000:0.000000
-strong-and-em-together:0.200000:0.000000
-tabs:0.200000:0.000000
-tidyness:0.200000:0.000000
diff --git a/markdown/tests/markdown-test/blockquotes-with-code-blocks.html b/markdown/tests/markdown-test/blockquotes-with-code-blocks.html
deleted file mode 100644
index 5fc98b1..0000000
--- a/markdown/tests/markdown-test/blockquotes-with-code-blocks.html
+++ /dev/null
@@ -1,12 +0,0 @@
-

-
Example:

-
sub status {
-    print "working";
-}
-

-
Or:

-
sub status {
-    return "working";
-}
-

-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/blockquotes-with-code-blocks.txt b/markdown/tests/markdown-test/blockquotes-with-code-blocks.txt
deleted file mode 100644
index c31d171..0000000
--- a/markdown/tests/markdown-test/blockquotes-with-code-blocks.txt
+++ /dev/null
@@ -1,11 +0,0 @@
-> Example:
-> 
->     sub status {
->         print "working";
->     }
-> 
-> Or:
-> 
->     sub status {
->         return "working";
->     }
diff --git a/markdown/tests/markdown-test/codeblock-in-list.html b/markdown/tests/markdown-test/codeblock-in-list.html
deleted file mode 100644
index 49edd56..0000000
--- a/markdown/tests/markdown-test/codeblock-in-list.html
+++ /dev/null
@@ -1,14 +0,0 @@
-
    
-
  • 
-
    A list item with a code block
    
-
    Some *code*
-
    
-
    • 
-
  • 
-
    Another list item
    
-
    More code
-
-And more code
-
    
-
    • 
-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/codeblock-in-list.txt b/markdown/tests/markdown-test/codeblock-in-list.txt
deleted file mode 100644
index 87d4e3b..0000000
--- a/markdown/tests/markdown-test/codeblock-in-list.txt
+++ /dev/null
@@ -1,10 +0,0 @@
-* A list item with a code block
-
-        Some *code*
-
-* Another list item
-
-        More code
-
-        And more code
-
diff --git a/markdown/tests/markdown-test/hard-wrapped.html b/markdown/tests/markdown-test/hard-wrapped.html
deleted file mode 100644
index e28e900..0000000
--- a/markdown/tests/markdown-test/hard-wrapped.html
+++ /dev/null
@@ -1,7 +0,0 @@
-
In Markdown 1.0.0 and earlier. Version
-8. This line turns into a list item.
-Because a hard-wrapped line in the
-middle of a paragraph looked like a
-list item.

-
Here's one with a bullet.
-* criminey.

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/hard-wrapped.txt b/markdown/tests/markdown-test/hard-wrapped.txt
deleted file mode 100644
index f8a5b27..0000000
--- a/markdown/tests/markdown-test/hard-wrapped.txt
+++ /dev/null
@@ -1,8 +0,0 @@
-In Markdown 1.0.0 and earlier. Version
-8. This line turns into a list item.
-Because a hard-wrapped line in the
-middle of a paragraph looked like a
-list item.
-
-Here's one with a bullet.
-* criminey.
diff --git a/markdown/tests/markdown-test/horizontal-rules.html b/markdown/tests/markdown-test/horizontal-rules.html
deleted file mode 100644
index 478e8c5..0000000
--- a/markdown/tests/markdown-test/horizontal-rules.html
+++ /dev/null
@@ -1,39 +0,0 @@
-
Dashes:

-

-

-

-

-
---
-

-

-

-

-

-
- - -
-

-
Asterisks:

-

-

-

-

-
***
-

-

-

-

-

-
* * *
-

-
Underscores:

-

-

-

-

-
___
-

-

-

-

-

-
_ _ _
-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/horizontal-rules.txt b/markdown/tests/markdown-test/horizontal-rules.txt
deleted file mode 100644
index 1594bda..0000000
--- a/markdown/tests/markdown-test/horizontal-rules.txt
+++ /dev/null
@@ -1,67 +0,0 @@
-Dashes:
-
----
-
- ---
- 
-  ---
-
-   ---
-
-	---
-
-- - -
-
- - - -
- 
-  - - -
-
-   - - -
-
-	- - -
-
-
-Asterisks:
-
-***
-
- ***
- 
-  ***
-
-   ***
-
-	***
-
-* * *
-
- * * *
- 
-  * * *
-
-   * * *
-
-	* * *
-
-
-Underscores:
-
-___
-
- ___
- 
-  ___
-
-   ___
-
-    ___
-
-_ _ _
-
- _ _ _
- 
-  _ _ _
-
-   _ _ _
-
-    _ _ _
diff --git a/markdown/tests/markdown-test/inline-html-advanced.html b/markdown/tests/markdown-test/inline-html-advanced.html
deleted file mode 100644
index af1dec1..0000000
--- a/markdown/tests/markdown-test/inline-html-advanced.html
+++ /dev/null
@@ -1,12 +0,0 @@
-
Simple block on one line:

-
foo

-
-
And nested without indentation:

-

-

-

-foo
-

-

-
bar

-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/inline-html-advanced.txt b/markdown/tests/markdown-test/inline-html-advanced.txt
deleted file mode 100644
index 9d71ddc..0000000
--- a/markdown/tests/markdown-test/inline-html-advanced.txt
+++ /dev/null
@@ -1,14 +0,0 @@
-Simple block on one line:
-
-
foo

-
-And nested without indentation:
-
-

-

-

-foo
-

-

-
bar

-

diff --git a/markdown/tests/markdown-test/inline-html-comments.html b/markdown/tests/markdown-test/inline-html-comments.html
deleted file mode 100644
index 0d4cad9..0000000
--- a/markdown/tests/markdown-test/inline-html-comments.html
+++ /dev/null
@@ -1,11 +0,0 @@
-
Paragraph one.

-
-
-
-
-
Paragraph two.

-
-
-
The end.

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/inline-html-comments.txt b/markdown/tests/markdown-test/inline-html-comments.txt
deleted file mode 100644
index 41d830d..0000000
--- a/markdown/tests/markdown-test/inline-html-comments.txt
+++ /dev/null
@@ -1,13 +0,0 @@
-Paragraph one.
-
-
-
-
-
-Paragraph two.
-
-
-
-The end.
diff --git a/markdown/tests/markdown-test/inline-html-simple.html b/markdown/tests/markdown-test/inline-html-simple.html
deleted file mode 100644
index cb10451..0000000
--- a/markdown/tests/markdown-test/inline-html-simple.html
+++ /dev/null
@@ -1,58 +0,0 @@
-
Here's a simple block:

-

-    foo
-

-
-
This should be a code block, though:

-
<div>
-    foo
-</div>
-

-
As should this:

-
<div>foo</div>
-

-
Now, nested:

-

-    

-        

-            foo
-        

-    

-

-
-
This should just be an HTML comment:

-
-
-
Multiline:

-
-
-
Code block:

-
<!-- Comment -->
-

-
Just plain comment, with trailing spaces on the line:

-
-
-
Code:

-
<hr />
-

-
Hr's:

-

-
-

-
-

-
-

-
-

-
-

-
-

-
-

-
-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/inline-html-simple.txt b/markdown/tests/markdown-test/inline-html-simple.txt
deleted file mode 100644
index 14aa2dc..0000000
--- a/markdown/tests/markdown-test/inline-html-simple.txt
+++ /dev/null
@@ -1,69 +0,0 @@
-Here's a simple block:
-
-

-	foo
-

-
-This should be a code block, though:
-
-	

-		foo
-	

-
-As should this:
-
-	
foo

-
-Now, nested:
-
-

-	

-		

-			foo
-		

-	

-

-
-This should just be an HTML comment:
-
-
-
-Multiline:
-
-
-
-Code block:
-
-	
-
-Just plain comment, with trailing spaces on the line:
-
-   
-
-Code:
-
-	

-	
-Hr's:
-
-

-
-

-
-

-
-
   
-
-
  
-
-
 
-
-

-
-

-
-

-
diff --git a/markdown/tests/markdown-test/links-inline.html b/markdown/tests/markdown-test/links-inline.html
deleted file mode 100644
index 707937a..0000000
--- a/markdown/tests/markdown-test/links-inline.html
+++ /dev/null
@@ -1,5 +0,0 @@
-
Just a URL.

-
URL and title.

-
URL and title.

-
URL and title.

-
Empty.

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/links-inline.txt b/markdown/tests/markdown-test/links-inline.txt
deleted file mode 100644
index 4d0c1c2..0000000
--- a/markdown/tests/markdown-test/links-inline.txt
+++ /dev/null
@@ -1,9 +0,0 @@
-Just a [URL](/url/).
-
-[URL and title](/url/ "title").
-
-[URL and title](/url/  "title preceded by two spaces").
-
-[URL and title](/url/	"title preceded by a tab").
-
-[Empty]().
diff --git a/markdown/tests/markdown-test/links-reference.html b/markdown/tests/markdown-test/links-reference.html
deleted file mode 100644
index 165c71a..0000000
--- a/markdown/tests/markdown-test/links-reference.html
+++ /dev/null
@@ -1,10 +0,0 @@
-
Foo bar.

-
Foo bar.

-
Foo bar.

-
With embedded [brackets].

-
Indented once.

-
Indented twice.

-
Indented thrice.

-
Indented [four][] times.

-
[four]: /url
-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/links-reference.txt b/markdown/tests/markdown-test/links-reference.txt
deleted file mode 100644
index b2fa734..0000000
--- a/markdown/tests/markdown-test/links-reference.txt
+++ /dev/null
@@ -1,31 +0,0 @@
-Foo [bar] [1].
-
-Foo [bar][1].
-
-Foo [bar]
-[1].
-
-[1]: /url/  "Title"
-
-
-With [embedded [brackets]] [b].
-
-
-Indented [once][].
-
-Indented [twice][].
-
-Indented [thrice][].
-
-Indented [four][] times.
-
- [once]: /url
-
-  [twice]: /url
-
-   [thrice]: /url
-
-    [four]: /url
-
-
-[b]: /url/
diff --git a/markdown/tests/markdown-test/literal-quotes.html b/markdown/tests/markdown-test/literal-quotes.html
deleted file mode 100644
index 0342589..0000000
--- a/markdown/tests/markdown-test/literal-quotes.html
+++ /dev/null
@@ -1,2 +0,0 @@
-
Foo bar.

-
Foo bar.

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/literal-quotes.txt b/markdown/tests/markdown-test/literal-quotes.txt
deleted file mode 100644
index 29d0e42..0000000
--- a/markdown/tests/markdown-test/literal-quotes.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-Foo [bar][].
-
-Foo [bar](/url/ "Title with "quotes" inside").
-
-
-  [bar]: /url/ "Title with "quotes" inside"
-
diff --git a/markdown/tests/markdown-test/markdown-documentation-basics.html b/markdown/tests/markdown-test/markdown-documentation-basics.html
deleted file mode 100644
index 3bcaea9..0000000
--- a/markdown/tests/markdown-test/markdown-documentation-basics.html
+++ /dev/null
@@ -1,243 +0,0 @@
-
Markdown: Basics

-
-
-
Getting the Gist of Markdown's Formatting Syntax

-
This page offers a brief overview of what it's like to use Markdown.
-The syntax page 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 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.

-
Paragraphs, Headers, Blockquotes

-
A paragraph is simply one or more consecutive lines of text, separated
-by one or more blank lines. (A blank line is any line that looks like a
-blank line -- a line containing nothing spaces or tabs is considered
-blank.) Normal paragraphs should not be intended with spaces or tabs.

-
Markdown offers two styles of headers: Setext and atx.
-Setext-style headers for <h1> and <h2> are created by
-"underlining" with equal signs (=) and hyphens (-), respectively.
-To create an atx-style header, you put 1-6 hash marks (#) at the
-beginning of the line -- the number of hashes equals the resulting
-HTML header level.

-
Blockquotes are indicated using email-style '>' angle brackets.

-
Markdown:

-
A First Level Header
-====================
-
-A Second Level Header
----------------------
-
-Now is the time for all good men to come to
-the aid of their country. This is just a
-regular paragraph.
-
-The quick brown fox jumped over the lazy
-dog's back.
-
-### Header 3
-
-> This is a blockquote.
-> 
-> This is the second paragraph in the blockquote.
->
-> ## This is an H2 in a blockquote
-

-
Output:

-
<h1>A First Level Header</h1>
-
-<h2>A Second Level Header</h2>
-
-<p>Now is the time for all good men to come to
-the aid of their country. This is just a
-regular paragraph.</p>
-
-<p>The quick brown fox jumped over the lazy
-dog's back.</p>
-
-<h3>Header 3</h3>
-
-<blockquote>
-    <p>This is a blockquote.</p>
-
-    <p>This is the second paragraph in the blockquote.</p>
-
-    <h2>This is an H2 in a blockquote</h2>
-</blockquote>
-

-
Phrase Emphasis

-
Markdown uses asterisks and underscores to indicate spans of emphasis.

-
Markdown:

-
Some of these words *are emphasized*.
-Some of these words _are emphasized also_.
-
-Use two asterisks for **strong emphasis**.
-Or, if you prefer, __use two underscores instead__.
-

-
Output:

-
<p>Some of these words <em>are emphasized</em>.
-Some of these words <em>are emphasized also</em>.</p>
-
-<p>Use two asterisks for <strong>strong emphasis</strong>.
-Or, if you prefer, <strong>use two underscores instead</strong>.</p>
-

-
Lists

-
Unordered (bulleted) lists use asterisks, pluses, and hyphens (*,
-+, and -) as list markers. These three markers are
-interchangable; this:

-
*   Candy.
-*   Gum.
-*   Booze.
-

-
this:

-
+   Candy.
-+   Gum.
-+   Booze.
-

-
and this:

-
-   Candy.
--   Gum.
--   Booze.
-

-
all produce the same output:

-
<ul>
-<li>Candy.</li>
-<li>Gum.</li>
-<li>Booze.</li>
-</ul>
-

-
Ordered (numbered) lists use regular numbers, followed by periods, as
-list markers:

-
1.  Red
-2.  Green
-3.  Blue
-

-
Output:

-
<ol>
-<li>Red</li>
-<li>Green</li>
-<li>Blue</li>
-</ol>
-

-
If you put blank lines between items, you'll get <p> tags for the
-list item text. You can create multi-paragraph list items by indenting
-the paragraphs by 4 spaces or 1 tab:

-
*   A list item.
-
-    With multiple paragraphs.
-
-*   Another item in the list.
-

-
Output:

-
<ul>
-<li><p>A list item.</p>
-<p>With multiple paragraphs.</p></li>
-<li><p>Another item in the list.</p></li>
-</ul>
-

-
Links

-
Markdown supports two styles for creating links: inline and
-reference. With both styles, you use square brackets to delimit the
-text you want to turn into a link.

-
Inline-style links use parentheses immediately after the link text.
-For example:

-
This is an [example link](http://example.com/).
-

-
Output:

-
<p>This is an <a href="http://example.com/">
-example link</a>.</p>
-

-
Optionally, you may include a title attribute in the parentheses:

-
This is an [example link](http://example.com/ "With a Title").
-

-
Output:

-
<p>This is an <a href="http://example.com/" title="With a Title">
-example link</a>.</p>
-

-
Reference-style links allow you to refer to your links by names, which
-you define elsewhere in your document:

-
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"
-

-
Output:

-
<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>
-

-
The title attribute is optional. Link names may contain letters,
-numbers and spaces, but are not case sensitive:

-
I start my morning with a cup of coffee and
-[The New York Times][NY Times].
-
-[ny times]: http://www.nytimes.com/
-

-
Output:

-
<p>I start my morning with a cup of coffee and
-<a href="http://www.nytimes.com/">The New York Times</a>.</p>
-

-
Images

-
Image syntax is very much like link syntax.

-
Inline (titles are optional):

-
![alt text](/path/to/img.jpg "Title")
-

-
Reference-style:

-
![alt text][id]
-
-[id]: /path/to/img.jpg "Title"
-

-
Both of the above examples produce the same output:

-
<img src="/path/to/img.jpg" alt="alt text" title="Title" />
-

-
Code

-
In a regular paragraph, you can create code span by wrapping text in
-backtick quotes. Any ampersands (&) and angle brackets (< or
->) will automatically be translated into HTML entities. This makes
-it easy to use Markdown to write about HTML example code:

-
I strongly recommend against using any `<blink>` tags.
-
-I wish SmartyPants used named entities like `&mdash;`
-instead of decimal-encoded entites like `&#8212;`.
-

-
Output:

-
<p>I strongly recommend against using any
-<code>&lt;blink&gt;</code> tags.</p>
-
-<p>I wish SmartyPants used named entities like
-<code>&amp;mdash;</code> instead of decimal-encoded
-entites like <code>&amp;#8212;</code>.</p>
-

-
To specify an entire block of pre-formatted code, indent every line of
-the block by 4 spaces or 1 tab. Just like with code spans, &, <,
-and > characters will be escaped automatically.

-
Markdown:

-
If you want your page to validate under XHTML 1.0 Strict,
-you've got to put paragraph tags in your blockquotes:
-
-    <blockquote>
-        <p>For example.</p>
-    </blockquote>
-

-
Output:

-
<p>If you want your page to validate under XHTML 1.0 Strict,
-you've got to put paragraph tags in your blockquotes:</p>
-
-<pre><code>&lt;blockquote&gt;
-    &lt;p&gt;For example.&lt;/p&gt;
-&lt;/blockquote&gt;
-</code></pre>
-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/markdown-documentation-basics.txt b/markdown/tests/markdown-test/markdown-documentation-basics.txt
deleted file mode 100644
index 486055c..0000000
--- a/markdown/tests/markdown-test/markdown-documentation-basics.txt
+++ /dev/null
@@ -1,306 +0,0 @@
-Markdown: Basics
-================
-
-
-
-
-Getting the Gist of Markdown's Formatting Syntax
-------------------------------------------------
-
-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
-
-
-## Paragraphs, Headers, Blockquotes ##
-
-A paragraph is simply one or more consecutive lines of text, separated
-by one or more blank lines. (A blank line is any line that looks like a
-blank line -- a line containing nothing spaces or tabs is considered
-blank.) Normal paragraphs should not be intended with spaces or tabs.
-
-Markdown offers two styles of headers: *Setext* and *atx*.
-Setext-style headers for `
` and `
` are created by
-"underlining" with equal signs (`=`) and hyphens (`-`), respectively.
-To create an atx-style header, you put 1-6 hash marks (`#`) at the
-beginning of the line -- the number of hashes equals the resulting
-HTML header level.
-
-Blockquotes are indicated using email-style '`>`' angle brackets.
-
-Markdown:
-
-    A First Level Header
-    ====================
-    
-    A Second Level Header
-    ---------------------
-
-    Now is the time for all good men to come to
-    the aid of their country. This is just a
-    regular paragraph.
-
-    The quick brown fox jumped over the lazy
-    dog's back.
-    
-    ### Header 3
-
-    > This is a blockquote.
-    > 
-    > This is the second paragraph in the blockquote.
-    >
-    > ## This is an H2 in a blockquote
-
-
-Output:
-
-    
A First Level Header

-    
-    
A Second Level Header

-    
-    
Now is the time for all good men to come to
-    the aid of their country. This is just a
-    regular paragraph.

-    
-    
The quick brown fox jumped over the lazy
-    dog's back.

-    
-    
Header 3

-    
-    

-        
This is a blockquote.

-        
-        
This is the second paragraph in the blockquote.

-        
-        
This is an H2 in a blockquote

-    

-
-
-
-### Phrase Emphasis ###
-
-Markdown uses asterisks and underscores to indicate spans of emphasis.
-
-Markdown:
-
-    Some of these words *are emphasized*.
-    Some of these words _are emphasized also_.
-    
-    Use two asterisks for **strong emphasis**.
-    Or, if you prefer, __use two underscores instead__.
-
-Output:
-
-    
Some of these words are emphasized.
-    Some of these words are emphasized also.

-    
-    
Use two asterisks for strong emphasis.
-    Or, if you prefer, use two underscores instead.

-   
-
-
-## Lists ##
-
-Unordered (bulleted) lists use asterisks, pluses, and hyphens (`*`,
-`+`, and `-`) as list markers. These three markers are
-interchangable; this:
-
-    *   Candy.
-    *   Gum.
-    *   Booze.
-
-this:
-
-    +   Candy.
-    +   Gum.
-    +   Booze.
-
-and this:
-
-    -   Candy.
-    -   Gum.
-    -   Booze.
-
-all produce the same output:
-
-    
    
-    
  • Candy.
    • 
-    
  • Gum.
    • 
-    
  • Booze.
    • 
-    

-
-Ordered (numbered) lists use regular numbers, followed by periods, as
-list markers:
-
-    1.  Red
-    2.  Green
-    3.  Blue
-
-Output:
-
-    
    
-    
  1. Red
    2. 
-    
  2. Green
    3. 
-    
  3. Blue
    4. 
-    

-
-If you put blank lines between items, you'll get `
` tags for the
-list item text. You can create multi-paragraph list items by indenting
-the paragraphs by 4 spaces or 1 tab:
-
-    *   A list item.
-    
-        With multiple paragraphs.
-
-    *   Another item in the list.
-
-Output:
-
-    
    
-    
  • A list item.
    
-    
    With multiple paragraphs.
    • 
-    
  • Another item in the list.
    • 
-    

-    
-
-
-### Links ###
-
-Markdown supports two styles for creating links: *inline* and
-*reference*. With both styles, you use square brackets to delimit the
-text you want to turn into a link.
-
-Inline-style links use parentheses immediately after the link text.
-For example:
-
-    This is an [example link](http://example.com/).
-
-Output:
-
-    
This is an 
-    example link.

-
-Optionally, you may include a title attribute in the parentheses:
-
-    This is an [example link](http://example.com/ "With a Title").
-
-Output:
-
-    
This is an 
-    example link.

-
-Reference-style links allow you to refer to your links by names, which
-you define elsewhere in your document:
-
-    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"
-
-Output:
-
-    
I get 10 times more traffic from Google than from Yahoo or MSN.

-
-The title attribute is optional. Link names may contain letters,
-numbers and spaces, but are *not* case sensitive:
-
-    I start my morning with a cup of coffee and
-    [The New York Times][NY Times].
-
-    [ny times]: http://www.nytimes.com/
-
-Output:
-
-    
I start my morning with a cup of coffee and
-    The New York Times.

-
-
-### Images ###
-
-Image syntax is very much like link syntax.
-
-Inline (titles are optional):
-
-    ![alt text](/path/to/img.jpg "Title")
-
-Reference-style:
-
-    ![alt text][id]
-
-    [id]: /path/to/img.jpg "Title"
-
-Both of the above examples produce the same output:
-
-    alt text
-
-
-
-### Code ###
-
-In a regular paragraph, you can create code span by wrapping text in
-backtick quotes. Any ampersands (`&`) and angle brackets (`<` or
-`>`) will automatically be translated into HTML entities. This makes
-it easy to use Markdown to write about HTML example code:
-
-    I strongly recommend against using any `` tags.
-
-    I wish SmartyPants used named entities like `—`
-    instead of decimal-encoded entites like `—`.
-
-Output:
-
-    
I strongly recommend against using any
-    <blink> tags.

-    
-    
I wish SmartyPants used named entities like
-    &mdash; instead of decimal-encoded
-    entites like &#8212;.

-
-
-To specify an entire block of pre-formatted code, indent every line of
-the block by 4 spaces or 1 tab. Just like with code spans, `&`, `<`,
-and `>` characters will be escaped automatically.
-
-Markdown:
-
-    If you want your page to validate under XHTML 1.0 Strict,
-    you've got to put paragraph tags in your blockquotes:
-
-        

-            
For example.

-        

-
-Output:
-
-    
If you want your page to validate under XHTML 1.0 Strict,
-    you've got to put paragraph tags in your blockquotes:

-    
-    
<blockquote>
-        <p>For example.</p>
-    </blockquote>
-    

diff --git a/markdown/tests/markdown-test/markdown-syntax.html b/markdown/tests/markdown-test/markdown-syntax.html
deleted file mode 100644
index 038c9d1..0000000
--- a/markdown/tests/markdown-test/markdown-syntax.html
+++ /dev/null
@@ -1,728 +0,0 @@
-
Markdown: Syntax

-
-
-
-
Note: This document is itself written using Markdown; you
-can see the source for it by adding '.text' to the URL.

-

-
Overview

-
-
Philosophy

-
-
Markdown is intended to be as easy-to-read and easy-to-write as is feasible.

-
Readability, however, is emphasized above all else. A Markdown-formatted
-document should be publishable as-is, as plain text, without looking
-like it's been marked up with tags or formatting instructions. While
-Markdown's syntax has been influenced by several existing text-to-HTML
-filters -- including Setext, atx, Textile, reStructuredText,
-Grutatext, and EtText -- the single biggest source of
-inspiration for Markdown's syntax is the format of plain text email.

-
To this end, Markdown's syntax is comprised entirely of punctuation
-characters, which punctuation characters have been carefully chosen so
-as to look like what they mean. E.g., asterisks around a word actually
-look like *emphasis*. Markdown lists look like, well, lists. Even
-blockquotes look like quoted passages of text, assuming you've ever
-used email.

-
Inline HTML

-
-
Markdown's syntax is intended for one purpose: to be used as a
-format for writing for the web.

-
Markdown is not a replacement for HTML, or even close to it. Its
-syntax is very small, corresponding only to a very small subset of
-HTML tags. The idea is not to create a syntax that makes it easier
-to insert HTML tags. In my opinion, HTML tags are already easy to
-insert. The idea for Markdown is to make it easy to read, write, and
-edit prose. HTML is a publishing format; Markdown is a writing
-format. Thus, Markdown's formatting syntax only addresses issues that
-can be conveyed in plain text.

-
For any markup that is not covered by Markdown's syntax, you simply
-use HTML itself. There's no need to preface it or delimit it to
-indicate that you're switching from Markdown to HTML; you just use
-the tags.

-
The only restrictions are that block-level HTML elements -- e.g. <div>,
-<table>, <pre>, <p>, etc. -- must be separated from surrounding
-content by blank lines, and the start and end tags of the block should
-not be indented with tabs or spaces. Markdown is smart enough not
-to add extra (unwanted) <p> tags around HTML block-level tags.

-
For example, to add an HTML table to a Markdown article:

-
This is a regular paragraph.
-
-<table>
-    <tr>
-        <td>Foo</td>
-    </tr>
-</table>
-
-This is another regular paragraph.
-

-
Note that Markdown formatting syntax is not processed within block-level
-HTML tags. E.g., you can't use Markdown-style *emphasis* inside an
-HTML block.

-
Span-level HTML tags -- e.g. <span>, <cite>, or <del> -- can be
-used anywhere in a Markdown paragraph, list item, or header. If you
-want, you can even use HTML tags instead of Markdown formatting; e.g. if
-you'd prefer to use HTML <a> or <img> tags instead of Markdown's
-link or image syntax, go right ahead.

-
Unlike block-level HTML tags, Markdown syntax is processed within
-span-level tags.

-
Automatic Escaping for Special Characters

-
-
In HTML, there are two characters that demand special treatment: <
-and &. Left angle brackets are used to start tags; ampersands are
-used to denote HTML entities. If you want to use them as literal
-characters, you must escape them as entities, e.g. &lt;, and
-&amp;.

-
Ampersands in particular are bedeviling for web writers. If you want to
-write about 'AT&T', you need to write 'AT&amp;T'. You even need to
-escape ampersands within URLs. Thus, if you want to link to:

-
http://images.google.com/images?num=30&q=larry+bird
-

-
you need to encode the URL as:

-
http://images.google.com/images?num=30&amp;q=larry+bird
-

-
in your anchor tag href attribute. Needless to say, this is easy to
-forget, and is probably the single most common source of HTML validation
-errors in otherwise well-marked-up web sites.

-
Markdown allows you to use these characters naturally, taking care of
-all the necessary escaping for you. If you use an ampersand as part of
-an HTML entity, it remains unchanged; otherwise it will be translated
-into &amp;.

-
So, if you want to include a copyright symbol in your article, you can write:

-
&copy;
-

-
and Markdown will leave it alone. But if you write:

-
AT&T
-

-
Markdown will translate it to:

-
AT&amp;T
-

-
Similarly, because Markdown supports inline HTML, if you use
-angle brackets as delimiters for HTML tags, Markdown will treat them as
-such. But if you write:

-
4 < 5
-

-
Markdown will translate it to:

-
4 &lt; 5
-

-
However, inside Markdown code spans and blocks, angle brackets and
-ampersands are always encoded automatically. This makes it easy to use
-Markdown to write about HTML code. (As opposed to raw HTML, which is a
-terrible format for writing about HTML syntax, because every single <
-and & in your example code needs to be escaped.)

-

-
Block Elements

-
-
Paragraphs and Line Breaks

-
-
A paragraph is simply one or more consecutive lines of text, separated
-by one or more blank lines. (A blank line is any line that looks like a
-blank line -- a line containing nothing but spaces or tabs is considered
-blank.) Normal paragraphs should not be intended with spaces or tabs.

-
The implication of the "one or more consecutive lines of text" rule is
-that Markdown supports "hard-wrapped" text paragraphs. This differs
-significantly from most other text-to-HTML formatters (including Movable
-Type's "Convert Line Breaks" option) which translate every line break
-character in a paragraph into a <br /> tag.

-
When you do want to insert a <br /> break tag using Markdown, you
-end a line with two or more spaces, then type return.

-
Yes, this takes a tad more effort to create a <br />, but a simplistic
-"every line break is a <br />" rule wouldn't work for Markdown.
-Markdown's email-style blockquoting and multi-paragraph list items
-work best -- and look better -- when you format them with hard breaks.

-
-
-
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). For example:

-
This is an H1
-=============
-
-This is an H2
--------------
-

-
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. For example:

-
# This is an H1
-
-## This is an H2
-
-###### This is an H6
-

-
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.) :

-
# This is an H1 #
-
-## This is an H2 ##
-
-### This is an H3 ######
-

-
Blockquotes

-
-
Markdown uses email-style > characters for blockquoting. If you're
-familiar with quoting passages of text in an email message, then you
-know how to create a blockquote in Markdown. It looks best if you hard
-wrap the text and put a > before every line:

-
> 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.
-

-
Markdown allows you to be lazy and only put the > before the first
-line of a hard-wrapped paragraph:

-
> 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.
-

-
Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
-adding additional levels of >:

-
> This is the first level of quoting.
->
-> > This is nested blockquote.
->
-> Back to the first level.
-

-
Blockquotes can contain other Markdown elements, including headers, lists,
-and code blocks:

-
> ## 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");
-

-
Any decent text editor should make email-style quoting easy. For
-example, with BBEdit, you can make a selection and choose Increase
-Quote Level from the Text menu.

-
Lists

-
-
Markdown supports ordered (numbered) and unordered (bulleted) lists.

-
Unordered lists use asterisks, pluses, and hyphens -- interchangably
--- as list markers:

-
*   Red
-*   Green
-*   Blue
-

-
is equivalent to:

-
+   Red
-+   Green
-+   Blue
-

-
and:

-
-   Red
--   Green
--   Blue
-

-
Ordered lists use numbers followed by periods:

-
1.  Bird
-2.  McHale
-3.  Parish
-

-
It's important to note that the actual numbers you use to mark the
-list have no effect on the HTML output Markdown produces. The HTML
-Markdown produces from the above list is:

-
<ol>
-<li>Bird</li>
-<li>McHale</li>
-<li>Parish</li>
-</ol>
-

-
If you instead wrote the list in Markdown like this:

-
1.  Bird
-1.  McHale
-1.  Parish
-

-
or even:

-
3. Bird
-1. McHale
-8. Parish
-

-
you'd get the exact same HTML output. The point is, if you want to,
-you can use ordinal numbers in your ordered Markdown lists, so that
-the numbers in your source match the numbers in your published HTML.
-But if you want to be lazy, you don't have to.

-
If you do use lazy list numbering, however, you should still start the
-list with the number 1. At some point in the future, Markdown may support
-starting ordered lists at an arbitrary number.

-
List markers typically start at the left margin, but may be indented by
-up to three spaces. List markers must be followed by one or more spaces
-or a tab.

-
To make lists look nice, you can wrap items with hanging indents:

-
*   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.
-

-
But if you want to be lazy, you don't have to:

-
*   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.
-

-
If list items are separated by blank lines, Markdown will wrap the
-items in <p> tags in the HTML output. For example, this input:

-
*   Bird
-*   Magic
-

-
will turn into:

-
<ul>
-<li>Bird</li>
-<li>Magic</li>
-</ul>
-

-
But this:

-
*   Bird
-
-*   Magic
-

-
will turn into:

-
<ul>
-<li><p>Bird</p></li>
-<li><p>Magic</p></li>
-</ul>
-

-
List items may consist of multiple paragraphs. Each subsequent
-paragraph in a list item must be intended by either 4 spaces
-or one tab:

-
1.  This is a list item 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.
-
-2.  Suspendisse id sem consectetuer libero luctus adipiscing.
-

-
It looks nice if you indent every line of the subsequent
-paragraphs, but here again, Markdown will allow you to be
-lazy:

-
*   This is a list item with two paragraphs.
-
-    This is the second paragraph in the list item. You're
-only required to indent the first line. Lorem ipsum dolor
-sit amet, consectetuer adipiscing elit.
-
-*   Another item in the same list.
-

-
To put a blockquote within a list item, the blockquote's >
-delimiters need to be indented:

-
*   A list item with a blockquote:
-
-    > This is a blockquote
-    > inside a list item.
-

-
To put a code block within a list item, the code block needs
-to be indented twice -- 8 spaces or two tabs:

-
*   A list item with a code block:
-
-        <code goes here>
-

-
It's worth noting that it's possible to trigger an ordered list by
-accident, by writing something like this:

-
1986. What a great season.
-

-
In other words, a number-period-space sequence at the beginning of a
-line. To avoid this, you can backslash-escape the period:

-
1986\. What a great season.
-

-
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. For example, given this input:

-
This is a normal paragraph:
-
-    This is a code block.
-

-
Markdown will generate:

-
<p>This is a normal paragraph:</p>
-
-<pre><code>This is a code block.
-</code></pre>
-

-
One level of indentation -- 4 spaces or 1 tab -- is removed from each
-line of the code block. For example, this:

-
Here is an example of AppleScript:
-
-    tell application "Foo"
-        beep
-    end tell
-

-
will turn into:

-
<p>Here is an example of AppleScript:</p>
-
-<pre><code>tell application "Foo"
-    beep
-end tell
-</code></pre>
-

-
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. For example, this:

-
    <div class="footer">
-        &copy; 2004 Foo Corporation
-    </div>
-

-
will turn into:

-
<pre><code>&lt;div class="footer"&gt;
-    &amp;copy; 2004 Foo Corporation
-&lt;/div&gt;
-</code></pre>
-

-
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.

-
Horizontal Rules

-
-
You can produce a horizontal rule tag (<hr />) by placing three or
-more hyphens, asterisks, or underscores on a line by themselves. If you
-wish, you may use spaces between the hyphens or asterisks. Each of the
-following lines will produce a horizontal rule:

-
* * *
-
-***
-
-*****
-
-- - -
-
----------------------------------------
-
-_ _ _
-

-

-
Span Elements

-
-
-
-
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. For example:

-
This is [an example](http://example.com/ "Title") inline link.
-
-[This link](http://example.net/) has no title attribute.
-

-
Will produce:

-
<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>
-

-
If you're referring to a local resource on the same server, you can
-use relative paths:

-
See my [About](/about/) page for details.
-

-
Reference-style links use a second set of square brackets, inside
-which you place a label of your choosing to identify the link:

-
This is [an example][id] reference-style link.
-

-
You can optionally use a space to separate the sets of brackets:

-
This is [an example] [id] reference-style link.
-

-
Then, anywhere in the document, you define your link label like this,
-on a line by itself:

-
[id]: http://example.com/  "Optional Title Here"
-

-
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.
    • 
-

-
The link URL may, optionally, be surrounded by angle brackets:

-
[id]: <http://example.com/>  "Optional Title Here"
-

-
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:

-
[id]: http://example.com/longish/path/to/resource/here
-    "Optional Title Here"
-

-
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 constist of letters, numbers, spaces, and punctuation -- but they are not case sensitive. E.g. these two links:

-
[link text][a]
-[link text][A]
-

-
are equivalent.

-
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:

-
[Google]: http://google.com/
-

-
Because link names may contain spaces, this shortcut even works for
-multiple words in the link text:

-
Visit [Daring Fireball][] for more information.
-

-
And then define the link:

-
[Daring Fireball]: http://daringfireball.net/
-

-
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.

-
Here's an example of reference links in action:

-
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"
-

-
Using the implicit link name shortcut, you could instead write:

-
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"
-

-
Both of the above examples will produce the following HTML output:

-
<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>
-

-
For comparison, here is the same paragraph written using
-Markdown's inline link style:

-
I get 10 times more traffic from [Google](http://google.com/ "Google")
-than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
-[MSN](http://search.msn.com/ "MSN Search").
-

-
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.

-
Emphasis

-
-
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:

-
*single asterisks*
-
-_single underscores_
-
-**double asterisks**
-
-__double underscores__
-

-
will produce:

-
<em>single asterisks</em>
-
-<em>single underscores</em>
-
-<strong>double asterisks</strong>
-
-<strong>double underscores</strong>
-

-
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:

-
un*fucking*believable
-

-
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\*
-

-
Code

-
-
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. For example:

-
Use the `printf()` function.
-

-
will produce:

-
<p>Use the <code>printf()</code> function.</p>
-

-
To include a literal backtick character within a code span, you can use
-multiple backticks as the opening and closing delimiters:

-
``There is a literal backtick (`) here.``
-

-
which will produce this:

-
<p><code>There is a literal backtick (`) here.</code></p>
-

-
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:

-
A single backtick in a code span: `` ` ``
-
-A backtick-delimited string in a code span: `` `foo` ``
-

-
will produce:

-
<p>A single backtick in a code span: <code>`</code></p>
-
-<p>A backtick-delimited string in a code span: <code>`foo`</code></p>
-

-
With a code span, ampersands and angle brackets are encoded as HTML
-entities automatically, which makes it easy to include example HTML
-tags. Markdown will turn this:

-
Please don't use any `<blink>` tags.
-

-
into:

-
<p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>
-

-
You can write this:

-
`&#8212;` is the decimal-encoded equivalent of `&mdash;`.
-

-
to produce:

-
<p><code>&amp;#8212;</code> is the decimal-encoded
-equivalent of <code>&amp;mdash;</code>.</p>
-

-
Images

-
-
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:

-
[id]: url/to/image  "Optional title attribute"
-

-
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.

-

-
Miscellaneous

-
-
-
-
Markdown supports a shortcut style for creating "automatic" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:

-
<http://example.com/>
-

-
Markdown will turn this into:

-
<a href="http://example.com/">http://example.com/</a>
-

-
Automatic links for email addresses work similarly, except that
-Markdown will also perform a bit of randomized decimal and hex
-entity-encoding to help obscure your address from address-harvesting
-spambots. For example, Markdown will turn this:

-
<address@example.com>
-

-
into something like this:

-
<a href="&#x6D;&#x61;i&#x6C;&#x74;&#x6F;:&#x61;&#x64;&#x64;&#x72;&#x65;
-&#115;&#115;&#64;&#101;&#120;&#x61;&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;
-&#109;">&#x61;&#x64;&#x64;&#x72;&#x65;&#115;&#115;&#64;&#101;&#120;&#x61;
-&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;&#109;</a>
-

-
which will render in a browser as a clickable link to "address@example.com".

-
(This sort of entity-encoding trick will indeed fool many, if not
-most, address-harvesting bots, but it definitely won't fool all of
-them. It's better than nothing, but an address published in this way
-will probably eventually start receiving spam.)

-
Backslash Escapes

-
-
Markdown allows you to use backslash escapes to generate literal
-characters which would otherwise have special meaning in Markdown's
-formatting syntax. For example, if you wanted to surround a word with
-literal asterisks (instead of an HTML <em> tag), you can backslashes
-before the asterisks, like this:

-
\*literal asterisks\*
-

-
Markdown provides backslash escapes for the following characters:

-
\   backslash
-`   backtick
-*   asterisk
-_   underscore
-{}  curly braces
-[]  square brackets
-()  parentheses
-#   hash mark
-+   plus sign
--   minus sign (hyphen)
-.   dot
-!   exclamation mark
-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/markdown-syntax.txt b/markdown/tests/markdown-test/markdown-syntax.txt
deleted file mode 100644
index dabd75c..0000000
--- a/markdown/tests/markdown-test/markdown-syntax.txt
+++ /dev/null
@@ -1,888 +0,0 @@
-Markdown: Syntax
-================
-
-
-
-
-*   [Overview](#overview)
-    *   [Philosophy](#philosophy)
-    *   [Inline HTML](#html)
-    *   [Automatic Escaping for Special Characters](#autoescape)
-*   [Block Elements](#block)
-    *   [Paragraphs and Line Breaks](#p)
-    *   [Headers](#header)
-    *   [Blockquotes](#blockquote)
-    *   [Lists](#list)
-    *   [Code Blocks](#precode)
-    *   [Horizontal Rules](#hr)
-*   [Span Elements](#span)
-    *   [Links](#link)
-    *   [Emphasis](#em)
-    *   [Code](#code)
-    *   [Images](#img)
-*   [Miscellaneous](#misc)
-    *   [Backslash Escapes](#backslash)
-    *   [Automatic Links](#autolink)
-
-
-**Note:** This document is itself written using Markdown; you
-can [see the source for it by adding '.text' to the URL][src].
-
-  [src]: /projects/markdown/syntax.text
-
-* * *
-
-
Overview

-
-
Philosophy

-
-Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
-
-Readability, however, is emphasized above all else. A Markdown-formatted
-document should be publishable as-is, as plain text, without looking
-like it's been marked up with tags or formatting instructions. While
-Markdown's syntax has been influenced by several existing text-to-HTML
-filters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [4],
-[Grutatext] [5], and [EtText] [6] -- the single biggest source of
-inspiration for Markdown's syntax is the format of plain text email.
-
-  [1]: http://docutils.sourceforge.net/mirror/setext.html
-  [2]: http://www.aaronsw.com/2002/atx/
-  [3]: http://textism.com/tools/textile/
-  [4]: http://docutils.sourceforge.net/rst.html
-  [5]: http://www.triptico.com/software/grutatxt.html
-  [6]: http://ettext.taint.org/doc/
-
-To this end, Markdown's syntax is comprised entirely of punctuation
-characters, which punctuation characters have been carefully chosen so
-as to look like what they mean. E.g., asterisks around a word actually
-look like \*emphasis\*. Markdown lists look like, well, lists. Even
-blockquotes look like quoted passages of text, assuming you've ever
-used email.
-
-
-
-
Inline HTML

-
-Markdown's syntax is intended for one purpose: to be used as a
-format for *writing* for the web.
-
-Markdown is not a replacement for HTML, or even close to it. Its
-syntax is very small, corresponding only to a very small subset of
-HTML tags. The idea is *not* to create a syntax that makes it easier
-to insert HTML tags. In my opinion, HTML tags are already easy to
-insert. The idea for Markdown is to make it easy to read, write, and
-edit prose. HTML is a *publishing* format; Markdown is a *writing*
-format. Thus, Markdown's formatting syntax only addresses issues that
-can be conveyed in plain text.
-
-For any markup that is not covered by Markdown's syntax, you simply
-use HTML itself. There's no need to preface it or delimit it to
-indicate that you're switching from Markdown to HTML; you just use
-the tags.
-
-The only restrictions are that block-level HTML elements -- e.g. `
`,
-``, `
`, `
`, etc. -- must be separated from surrounding
-content by blank lines, and the start and end tags of the block should
-not be indented with tabs or spaces. Markdown is smart enough not
-to add extra (unwanted) `
` tags around HTML block-level tags.
-
-For example, to add an HTML table to a Markdown article:
-
-    This is a regular paragraph.
-
-    

-        
-            
-        
-    
Foo

-
-    This is another regular paragraph.
-
-Note that Markdown formatting syntax is not processed within block-level
-HTML tags. E.g., you can't use Markdown-style `*emphasis*` inside an
-HTML block.
-
-Span-level HTML tags -- e.g. ``, ``, or `` -- can be
-used anywhere in a Markdown paragraph, list item, or header. If you
-want, you can even use HTML tags instead of Markdown formatting; e.g. if
-you'd prefer to use HTML `` or `` tags instead of Markdown's
-link or image syntax, go right ahead.
-
-Unlike block-level HTML tags, Markdown syntax *is* processed within
-span-level tags.
-
-
-
Automatic Escaping for Special Characters

-
-In HTML, there are two characters that demand special treatment: `<`
-and `&`. Left angle brackets are used to start tags; ampersands are
-used to denote HTML entities. If you want to use them as literal
-characters, you must escape them as entities, e.g. `<`, and
-`&`.
-
-Ampersands in particular are bedeviling for web writers. If you want to
-write about 'AT&T', you need to write '`AT&T`'. You even need to
-escape ampersands within URLs. Thus, if you want to link to:
-
-    http://images.google.com/images?num=30&q=larry+bird
-
-you need to encode the URL as:
-
-    http://images.google.com/images?num=30&q=larry+bird
-
-in your anchor tag `href` attribute. Needless to say, this is easy to
-forget, and is probably the single most common source of HTML validation
-errors in otherwise well-marked-up web sites.
-
-Markdown allows you to use these characters naturally, taking care of
-all the necessary escaping for you. If you use an ampersand as part of
-an HTML entity, it remains unchanged; otherwise it will be translated
-into `&`.
-
-So, if you want to include a copyright symbol in your article, you can write:
-
-    ©
-
-and Markdown will leave it alone. But if you write:
-
-    AT&T
-
-Markdown will translate it to:
-
-    AT&T
-
-Similarly, because Markdown supports [inline HTML](#html), if you use
-angle brackets as delimiters for HTML tags, Markdown will treat them as
-such. But if you write:
-
-    4 < 5
-
-Markdown will translate it to:
-
-    4 < 5
-
-However, inside Markdown code spans and blocks, angle brackets and
-ampersands are *always* encoded automatically. This makes it easy to use
-Markdown to write about HTML code. (As opposed to raw HTML, which is a
-terrible format for writing about HTML syntax, because every single `<`
-and `&` in your example code needs to be escaped.)
-
-
-* * *
-
-
-
Block Elements

-
-
-
Paragraphs and Line Breaks

-
-A paragraph is simply one or more consecutive lines of text, separated
-by one or more blank lines. (A blank line is any line that looks like a
-blank line -- a line containing nothing but spaces or tabs is considered
-blank.) Normal paragraphs should not be intended with spaces or tabs.
-
-The implication of the "one or more consecutive lines of text" rule is
-that Markdown supports "hard-wrapped" text paragraphs. This differs
-significantly from most other text-to-HTML formatters (including Movable
-Type's "Convert Line Breaks" option) which translate every line break
-character in a paragraph into a `
` tag.
-
-When you *do* want to insert a `
` break tag using Markdown, you
-end a line with two or more spaces, then type return.
-
-Yes, this takes a tad more effort to create a `
`, but a simplistic
-"every line break is a `
`" rule wouldn't work for Markdown.
-Markdown's email-style [blockquoting][bq] and multi-paragraph [list items][l]
-work best -- and look better -- when you format them with hard breaks.
-
-  [bq]: #blockquote
-  [l]:  #list
-
-
-
-
-
-Markdown supports two styles of headers, [Setext] [1] and [atx] [2].
-
-Setext-style headers are "underlined" using equal signs (for first-level
-headers) and dashes (for second-level headers). For example:
-
-    This is an H1
-    =============
-
-    This is an H2
-    -------------
-
-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. For example:
-
-    # This is an H1
-
-    ## This is an H2
-
-    ###### This is an H6
-
-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.) :
-
-    # This is an H1 #
-
-    ## This is an H2 ##
-
-    ### This is an H3 ######
-
-
-
Blockquotes

-
-Markdown uses email-style `>` characters for blockquoting. If you're
-familiar with quoting passages of text in an email message, then you
-know how to create a blockquote in Markdown. It looks best if you hard
-wrap the text and put a `>` before every line:
-
-    > 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.
-
-Markdown allows you to be lazy and only put the `>` before the first
-line of a hard-wrapped paragraph:
-
-    > 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.
-
-Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
-adding additional levels of `>`:
-
-    > This is the first level of quoting.
-    >
-    > > This is nested blockquote.
-    >
-    > Back to the first level.
-
-Blockquotes can contain other Markdown elements, including headers, lists,
-and code blocks:
-
-	> ## 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");
-
-Any decent text editor should make email-style quoting easy. For
-example, with BBEdit, you can make a selection and choose Increase
-Quote Level from the Text menu.
-
-
-
Lists

-
-Markdown supports ordered (numbered) and unordered (bulleted) lists.
-
-Unordered lists use asterisks, pluses, and hyphens -- interchangably
--- as list markers:
-
-    *   Red
-    *   Green
-    *   Blue
-
-is equivalent to:
-
-    +   Red
-    +   Green
-    +   Blue
-
-and:
-
-    -   Red
-    -   Green
-    -   Blue
-
-Ordered lists use numbers followed by periods:
-
-    1.  Bird
-    2.  McHale
-    3.  Parish
-
-It's important to note that the actual numbers you use to mark the
-list have no effect on the HTML output Markdown produces. The HTML
-Markdown produces from the above list is:
-
-    
    
-    
  1. Bird
    2. 
-    
  2. McHale
    3. 
-    
  3. Parish
    4. 
-    

-
-If you instead wrote the list in Markdown like this:
-
-    1.  Bird
-    1.  McHale
-    1.  Parish
-
-or even:
-
-    3. Bird
-    1. McHale
-    8. Parish
-
-you'd get the exact same HTML output. The point is, if you want to,
-you can use ordinal numbers in your ordered Markdown lists, so that
-the numbers in your source match the numbers in your published HTML.
-But if you want to be lazy, you don't have to.
-
-If you do use lazy list numbering, however, you should still start the
-list with the number 1. At some point in the future, Markdown may support
-starting ordered lists at an arbitrary number.
-
-List markers typically start at the left margin, but may be indented by
-up to three spaces. List markers must be followed by one or more spaces
-or a tab.
-
-To make lists look nice, you can wrap items with hanging indents:
-
-    *   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.
-
-But if you want to be lazy, you don't have to:
-
-    *   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.
-
-If list items are separated by blank lines, Markdown will wrap the
-items in `
` tags in the HTML output. For example, this input:
-
-    *   Bird
-    *   Magic
-
-will turn into:
-
-    
    
-    
  • Bird
    • 
-    
  • Magic
    • 
-    

-
-But this:
-
-    *   Bird
-
-    *   Magic
-
-will turn into:
-
-    
    
-    
  • Bird
    • 
-    
  • Magic
    • 
-    

-
-List items may consist of multiple paragraphs. Each subsequent
-paragraph in a list item must be intended by either 4 spaces
-or one tab:
-
-    1.  This is a list item 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.
-
-    2.  Suspendisse id sem consectetuer libero luctus adipiscing.
-
-It looks nice if you indent every line of the subsequent
-paragraphs, but here again, Markdown will allow you to be
-lazy:
-
-    *   This is a list item with two paragraphs.
-
-        This is the second paragraph in the list item. You're
-    only required to indent the first line. Lorem ipsum dolor
-    sit amet, consectetuer adipiscing elit.
-
-    *   Another item in the same list.
-
-To put a blockquote within a list item, the blockquote's `>`
-delimiters need to be indented:
-
-    *   A list item with a blockquote:
-
-        > This is a blockquote
-        > inside a list item.
-
-To put a code block within a list item, the code block needs
-to be indented *twice* -- 8 spaces or two tabs:
-
-    *   A list item with a code block:
-
-            
-
-
-It's worth noting that it's possible to trigger an ordered list by
-accident, by writing something like this:
-
-    1986. What a great season.
-
-In other words, a *number-period-space* sequence at the beginning of a
-line. To avoid this, you can backslash-escape the period:
-
-    1986\. What a great season.
-
-
-
-
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 `
` and `` tags.
-
-To produce a code block in Markdown, simply indent every line of the
-block by at least 4 spaces or 1 tab. For example, given this input:
-
-    This is a normal paragraph:
-
-        This is a code block.
-
-Markdown will generate:
-
-    
This is a normal paragraph:

-
-    
This is a code block.
-    

-
-One level of indentation -- 4 spaces or 1 tab -- is removed from each
-line of the code block. For example, this:
-
-    Here is an example of AppleScript:
-
-        tell application "Foo"
-            beep
-        end tell
-
-will turn into:
-
-    
Here is an example of AppleScript:

-
-    
tell application "Foo"
-        beep
-    end tell
-    

-
-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. For example, this:
-
-        

-            © 2004 Foo Corporation
-        

-
-will turn into:
-
-    
<div class="footer">
-        &copy; 2004 Foo Corporation
-    </div>
-    

-
-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.
-
-
-
-
Horizontal Rules

-
-You can produce a horizontal rule tag (`
`) by placing three or
-more hyphens, asterisks, or underscores on a line by themselves. If you
-wish, you may use spaces between the hyphens or asterisks. Each of the
-following lines will produce a horizontal rule:
-
-    * * *
-
-    ***
-
-    *****
-	
-    - - -
-
-    ---------------------------------------
-
-	_ _ _
-
-
-* * *
-
-
Span Elements

-
-
-
-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. For example:
-
-    This is [an example](http://example.com/ "Title") inline link.
-
-    [This link](http://example.net/) has no title attribute.
-
-Will produce:
-
-    
This is 
-    an example inline link.

-
-    
This link has no
-    title attribute.

-
-If you're referring to a local resource on the same server, you can
-use relative paths:
-
-    See my [About](/about/) page for details.   
-
-Reference-style links use a second set of square brackets, inside
-which you place a label of your choosing to identify the link:
-
-    This is [an example][id] reference-style link.
-
-You can optionally use a space to separate the sets of brackets:
-
-    This is [an example] [id] reference-style link.
-
-Then, anywhere in the document, you define your link label like this,
-on a line by itself:
-
-    [id]: http://example.com/  "Optional Title Here"
-
-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.
-
-The link URL may, optionally, be surrounded by angle brackets:
-
-    [id]:   "Optional Title Here"
-
-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:
-
-    [id]: http://example.com/longish/path/to/resource/here
-        "Optional Title Here"
-
-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 constist of letters, numbers, spaces, and punctuation -- but they are *not* case sensitive. E.g. these two links:
-
-	[link text][a]
-	[link text][A]
-
-are equivalent.
-
-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:
-
-	[Google]: http://google.com/
-
-Because link names may contain spaces, this shortcut even works for
-multiple words in the link text:
-
-	Visit [Daring Fireball][] for more information.
-
-And then define the link:
-	
-	[Daring Fireball]: http://daringfireball.net/
-
-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.
-
-Here's an example of reference links in action:
-
-    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"
-
-Using the implicit link name shortcut, you could instead write:
-
-    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"
-
-Both of the above examples will produce the following HTML output:
-
-    
I get 10 times more traffic from Google than from
-    Yahoo
-    or MSN.

-
-For comparison, here is the same paragraph written using
-Markdown's inline link style:
-
-    I get 10 times more traffic from [Google](http://google.com/ "Google")
-    than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
-    [MSN](http://search.msn.com/ "MSN Search").
-
-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.
-
-
-
Emphasis

-
-Markdown treats asterisks (`*`) and underscores (`_`) as indicators of
-emphasis. Text wrapped with one `*` or `_` will be wrapped with an
-HTML `` tag; double `*`'s or `_`'s will be wrapped with an HTML
-`` tag. E.g., this input:
-
-    *single asterisks*
-
-    _single underscores_
-
-    **double asterisks**
-
-    __double underscores__
-
-will produce:
-
-    single asterisks
-
-    single underscores
-
-    double asterisks
-
-    double underscores
-
-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:
-
-    un*fucking*believable
-
-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\*
-
-
-
-
Code

-
-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. For example:
-
-    Use the `printf()` function.
-
-will produce:
-
-    
Use the printf() function.

-
-To include a literal backtick character within a code span, you can use
-multiple backticks as the opening and closing delimiters:
-
-    ``There is a literal backtick (`) here.``
-
-which will produce this:
-
-    
There is a literal backtick (`) here.

-
-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:
-
-	A single backtick in a code span: `` ` ``
-	
-	A backtick-delimited string in a code span: `` `foo` ``
-
-will produce:
-
-	
A single backtick in a code span: `

-	
-	
A backtick-delimited string in a code span: `foo`

-
-With a code span, ampersands and angle brackets are encoded as HTML
-entities automatically, which makes it easy to include example HTML
-tags. Markdown will turn this:
-
-    Please don't use any `` tags.
-
-into:
-
-    
Please don't use any <blink> tags.

-
-You can write this:
-
-    `—` is the decimal-encoded equivalent of `—`.
-
-to produce:
-
-    
&#8212; is the decimal-encoded
-    equivalent of &mdash;.

-
-
-
-
Images

-
-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:
-
-    [id]: url/to/image  "Optional title attribute"
-
-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 `` tags.
-
-
-* * *
-
-
-
Miscellaneous

-
-
-
-Markdown supports a shortcut style for creating "automatic" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:
-
-    
-    
-Markdown will turn this into:
-
-    http://example.com/
-
-Automatic links for email addresses work similarly, except that
-Markdown will also perform a bit of randomized decimal and hex
-entity-encoding to help obscure your address from address-harvesting
-spambots. For example, Markdown will turn this:
-
-    
-
-into something like this:
-
-    address@exa
-    mple.com
-
-which will render in a browser as a clickable link to "address@example.com".
-
-(This sort of entity-encoding trick will indeed fool many, if not
-most, address-harvesting bots, but it definitely won't fool all of
-them. It's better than nothing, but an address published in this way
-will probably eventually start receiving spam.)
-
-
-
-
Backslash Escapes

-
-Markdown allows you to use backslash escapes to generate literal
-characters which would otherwise have special meaning in Markdown's
-formatting syntax. For example, if you wanted to surround a word with
-literal asterisks (instead of an HTML `` tag), you can backslashes
-before the asterisks, like this:
-
-    \*literal asterisks\*
-
-Markdown provides backslash escapes for the following characters:
-
-    \   backslash
-    `   backtick
-    *   asterisk
-    _   underscore
-    {}  curly braces
-    []  square brackets
-    ()  parentheses
-    #   hash mark
-	+	plus sign
-	-	minus sign (hyphen)
-    .   dot
-    !   exclamation mark
-
diff --git a/markdown/tests/markdown-test/nested-blockquotes.html b/markdown/tests/markdown-test/nested-blockquotes.html
deleted file mode 100644
index f1b017e..0000000
--- a/markdown/tests/markdown-test/nested-blockquotes.html
+++ /dev/null
@@ -1,7 +0,0 @@
-

-
foo

-

-
bar

-

-
foo

-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/nested-blockquotes.txt b/markdown/tests/markdown-test/nested-blockquotes.txt
deleted file mode 100644
index ed3c624..0000000
--- a/markdown/tests/markdown-test/nested-blockquotes.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-> foo
->
-> > bar
->
-> foo
diff --git a/markdown/tests/markdown-test/ordered-and-unordered-list.html b/markdown/tests/markdown-test/ordered-and-unordered-list.html
deleted file mode 100644
index 090c43c..0000000
--- a/markdown/tests/markdown-test/ordered-and-unordered-list.html
+++ /dev/null
@@ -1,146 +0,0 @@
-
Unordered

-
Asterisks tight:

-
    
-
  • asterisk 1
    • 
-
  • asterisk 2
    • 
-
  • asterisk 3
    • 
-

-
Asterisks loose:

-
    
-
  • 
-
    asterisk 1
    
-
    • 
-
  • 
-
    asterisk 2
    
-
    • 
-
  • 
-
    asterisk 3
    
-
    • 
-

-

-
Pluses tight:

-
    
-
  • Plus 1
    • 
-
  • Plus 2
    • 
-
  • Plus 3
    • 
-

-
Pluses loose:

-
    
-
  • 
-
    Plus 1
    
-
    • 
-
  • 
-
    Plus 2
    
-
    • 
-
  • 
-
    Plus 3
    
-
    • 
-

-

-
Minuses tight:

-
    
-
  • Minus 1
    • 
-
  • Minus 2
    • 
-
  • Minus 3
    • 
-

-
Minuses loose:

-
    
-
  • 
-
    Minus 1
    
-
    • 
-
  • 
-
    Minus 2
    
-
    • 
-
  • 
-
    Minus 3
    
-
    • 
-

-
Ordered

-
Tight:

-
    
-
  1. First
    2. 
-
  2. Second
    3. 
-
  3. Third
    4. 
-

-
and:

-
    
-
  1. One
    2. 
-
  2. Two
    3. 
-
  3. Three
    4. 
-

-
Loose using tabs:

-
    
-
  1. 
-
    First
    
-
    2. 
-
  2. 
-
    Second
    
-
    3. 
-
  3. 
-
    Third
    
-
    4. 
-

-
and using spaces:

-
    
-
  1. 
-
    One
    
-
    2. 
-
  2. 
-
    Two
    
-
    3. 
-
  3. 
-
    Three
    
-
    4. 
-

-
Multiple paragraphs:

-
    
-
  1. 
-
    Item 1, graf one.
    
-
    Item 2. graf two. The quick brown fox jumped over the lazy dog's
-back.
    
-
    2. 
-
  2. 
-
    Item 2.
    
-
    3. 
-
  3. 
-
    Item 3.
    
-
    4. 
-

-
Nested

-
    
-
  • Tab
      
-
    • Tab
        
-
      • Tab
        • 
-
      
-
      • 
-
    
-
    • 
-

-
Here's another:

-
    
-
  1. First
    2. 
-
  2. Second:
      
-
    • Fee
      • 
-
    • Fie
      • 
-
    • Foe
      • 
-
    
-
    3. 
-
  3. Third
    4. 
-

-
Same thing but with paragraphs:

-
    
-
  1. 
-
    First
    
-
    2. 
-
  2. 
-
    Second:
    
-
      
-
    • Fee
      • 
-
    • Fie
      • 
-
    • Foe
      • 
-
    
-
    3. 
-
  3. 
-
    Third
    
-
    4. 
-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/ordered-and-unordered-list.txt b/markdown/tests/markdown-test/ordered-and-unordered-list.txt
deleted file mode 100644
index 621db58..0000000
--- a/markdown/tests/markdown-test/ordered-and-unordered-list.txt
+++ /dev/null
@@ -1,122 +0,0 @@
-## Unordered
-
-Asterisks tight:
-
-*	asterisk 1
-*	asterisk 2
-*	asterisk 3
-
-
-Asterisks loose:
-
-*	asterisk 1
-
-*	asterisk 2
-
-*	asterisk 3
-
-* * *
-
-Pluses tight:
-
-+	Plus 1
-+	Plus 2
-+	Plus 3
-
-
-Pluses loose:
-
-+	Plus 1
-
-+	Plus 2
-
-+	Plus 3
-
-* * *
-
-
-Minuses tight:
-
--	Minus 1
--	Minus 2
--	Minus 3
-
-
-Minuses loose:
-
--	Minus 1
-
--	Minus 2
-
--	Minus 3
-
-
-## Ordered
-
-Tight:
-
-1.	First
-2.	Second
-3.	Third
-
-and:
-
-1. One
-2. Two
-3. Three
-
-
-Loose using tabs:
-
-1.	First
-
-2.	Second
-
-3.	Third
-
-and using spaces:
-
-1. One
-
-2. Two
-
-3. Three
-
-Multiple paragraphs:
-
-1.	Item 1, graf one.
-
-	Item 2. graf two. The quick brown fox jumped over the lazy dog's
-	back.
-	
-2.	Item 2.
-
-3.	Item 3.
-
-
-
-## Nested
-
-*	Tab
-	*	Tab
-		*	Tab
-
-Here's another:
-
-1. First
-2. Second:
-	* Fee
-	* Fie
-	* Foe
-3. Third
-
-Same thing but with paragraphs:
-
-1. First
-
-2. Second:
-	* Fee
-	* Fie
-	* Foe
-
-3. Third
diff --git a/markdown/tests/markdown-test/strong-and-em-together.html b/markdown/tests/markdown-test/strong-and-em-together.html
deleted file mode 100644
index 7bf5163..0000000
--- a/markdown/tests/markdown-test/strong-and-em-together.html
+++ /dev/null
@@ -1,4 +0,0 @@
-
This is strong and em.

-
So is this word.

-
This is strong and em.

-
So is this word.

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/strong-and-em-together.txt b/markdown/tests/markdown-test/strong-and-em-together.txt
deleted file mode 100644
index 95ee690..0000000
--- a/markdown/tests/markdown-test/strong-and-em-together.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-***This is strong and em.***
-
-So is ***this*** word.
-
-___This is strong and em.___
-
-So is ___this___ word.
diff --git a/markdown/tests/markdown-test/tabs.html b/markdown/tests/markdown-test/tabs.html
deleted file mode 100644
index 3c11f14..0000000
--- a/markdown/tests/markdown-test/tabs.html
+++ /dev/null
@@ -1,23 +0,0 @@
-
    
-
  • 
-
    this is a list item
-    indented with tabs
    
-
    • 
-
  • 
-
    this is a list item
-    indented with spaces
    
-
    • 
-

-
Code:

-
this code block is indented by one tab
-

-
And:

-
    this code block is indented by two tabs
-

-
And:

-
+   this is an example list item
-    indented with tabs
-
-+   this is an example list item
-    indented with spaces
-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/tabs.txt b/markdown/tests/markdown-test/tabs.txt
deleted file mode 100644
index 589d113..0000000
--- a/markdown/tests/markdown-test/tabs.txt
+++ /dev/null
@@ -1,21 +0,0 @@
-+	this is a list item
-	indented with tabs
-
-+   this is a list item
-    indented with spaces
-
-Code:
-
-	this code block is indented by one tab
-
-And:
-
-		this code block is indented by two tabs
-
-And:
-
-	+	this is an example list item
-		indented with tabs
-	
-	+   this is an example list item
-	    indented with spaces
diff --git a/markdown/tests/markdown-test/tidyness.html b/markdown/tests/markdown-test/tidyness.html
deleted file mode 100644
index 52b2eaf..0000000
--- a/markdown/tests/markdown-test/tidyness.html
+++ /dev/null
@@ -1,8 +0,0 @@
-

-
A list within a blockquote:

-
    
-
  • asterisk 1
    • 
-
  • asterisk 2
    • 
-
  • asterisk 3
    • 
-

-

\ No newline at end of file
diff --git a/markdown/tests/markdown-test/tidyness.txt b/markdown/tests/markdown-test/tidyness.txt
deleted file mode 100644
index 5f18b8d..0000000
--- a/markdown/tests/markdown-test/tidyness.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-> A list within a blockquote:
-> 
-> *	asterisk 1
-> *	asterisk 2
-> *	asterisk 3
diff --git a/markdown/tests/test_apis.py b/markdown/tests/test_apis.py
old mode 100755
new mode 100644
-- 
cgit v1.2.3