From 1085168bbf0fcffdb60f8847749ac4c249c5e8aa Mon Sep 17 00:00:00 2001 From: Jacques Distler Date: Tue, 8 Jan 2008 00:01:35 -0600 Subject: [PATCH] Update to latest HTML5lib, Add Maruku testdir Sync with the latest html5lib. Having the Maruku unit tests on-hand may be useful for debugging; so let's include them. --- vendor/plugins/HTML5lib/Manifest.txt | 25 +- .../plugins/HTML5lib/lib/core_ext/kernel.rb | 13 - .../plugins/HTML5lib/lib/core_ext/string.rb | 17 - vendor/plugins/HTML5lib/lib/html5/cli.rb | 25 +- .../plugins/HTML5lib/lib/html5/html5parser.rb | 4 +- .../lib/html5/html5parser/in_body_phase.rb | 22 +- .../plugins/HTML5lib/lib/html5/inputstream.rb | 46 +- .../lib/html5/serializer/htmlserializer.rb | 2 +- vendor/plugins/HTML5lib/lib/html5/version.rb | 4 +- vendor/plugins/HTML5lib/test/preamble.rb | 5 +- vendor/plugins/HTML5lib/test/test_parser.rb | 5 +- vendor/plugins/HTML5lib/test19.rb | 40 + vendor/plugins/maruku/AUTHORS | 11 + vendor/plugins/maruku/LICENSE | 340 ++++ vendor/plugins/maruku/Rakefile | 73 + vendor/plugins/maruku/bin/Markdown.pl | 1451 +++++++++++++++++ vendor/plugins/maruku/bin/maruku | 168 ++ vendor/plugins/maruku/bin/marutest | 339 ++++ vendor/plugins/maruku/bin/marutex | 31 + .../lib/maruku/input/parse_span_better.rb | 2 +- vendor/plugins/maruku/tests/Makefile | 5 + .../tests/MarkdownTest_1.0/MarkdownTest.pl | 157 ++ .../Tests/Amps and angle encoding.html | 38 + .../Tests/Amps and angle encoding.html.dist | 17 + .../Tests/Amps and angle encoding.text | 23 + .../MarkdownTest_1.0/Tests/Auto links.html | 36 + .../Tests/Auto links.html.dist | 18 + .../MarkdownTest_1.0/Tests/Auto links.text | 13 + .../Tests/Backslash escapes.html | 122 ++ .../Tests/Backslash escapes.html.dist | 102 ++ .../Tests/Backslash escapes.text | 104 ++ .../Tests/Blockquotes with code blocks.html | 33 + .../Blockquotes with code blocks.html.dist | 15 + .../Tests/Blockquotes with code blocks.text | 11 + ...apped paragraphs with list-like lines.html | 22 + ... paragraphs with list-like lines.html.dist | 8 + ...apped paragraphs with list-like lines.text | 8 + .../Tests/Horizontal rules.html | 91 ++ .../Tests/Horizontal rules.html.dist | 71 + .../Tests/Horizontal rules.text | 67 + .../Tests/Inline HTML (Advanced).html | 39 + .../Tests/Inline HTML (Advanced).html.dist | 14 + .../Tests/Inline HTML (Advanced).text | 14 + .../Tests/Inline HTML (Simple).html | 88 + .../Tests/Inline HTML (Simple).html.dist | 72 + .../Tests/Inline HTML (Simple).text | 69 + .../Tests/Inline HTML comments.html | 26 + .../Tests/Inline HTML comments.html.dist | 13 + .../Tests/Inline HTML comments.text | 13 + .../Tests/Links, inline style.html | 28 + .../Tests/Links, inline style.html.dist | 9 + .../Tests/Links, inline style.text | 9 + .../Tests/Links, reference style.html | 38 + .../Tests/Links, reference style.html.dist | 18 + .../Tests/Links, reference style.text | 31 + .../Tests/Literal quotes in titles.html | 22 + .../Tests/Literal quotes in titles.html.dist | 3 + .../Tests/Literal quotes in titles.text | 7 + .../Markdown Documentation - Basics.html | 322 ++++ .../Markdown Documentation - Basics.html.dist | 314 ++++ .../Markdown Documentation - Basics.text | 306 ++++ .../Markdown Documentation - Syntax.html | 840 ++++++++++ .../Markdown Documentation - Syntax.html.dist | 942 +++++++++++ .../Markdown Documentation - Syntax.text | 888 ++++++++++ .../Tests/Nested blockquotes.html | 28 + .../Tests/Nested blockquotes.html.dist | 9 + .../Tests/Nested blockquotes.text | 5 + .../Tests/Ordered and unordered lists.html | 228 +++ .../Ordered and unordered lists.html.dist | 137 ++ .../Tests/Ordered and unordered lists.text | 122 ++ .../Tests/Strong and em together.html | 26 + .../Tests/Strong and em together.html.dist | 7 + .../Tests/Strong and em together.text | 7 + .../tests/MarkdownTest_1.0/Tests/Tabs.html | 46 + .../MarkdownTest_1.0/Tests/Tabs.html.dist | 25 + .../tests/MarkdownTest_1.0/Tests/Tabs.text | 21 + .../MarkdownTest_1.0/Tests/Tidyness.html | 30 + .../MarkdownTest_1.0/Tests/Tidyness.html.dist | 8 + .../MarkdownTest_1.0/Tests/Tidyness.text | 5 + .../maruku/tests/bugs/code_in_links.md | 16 + .../maruku/tests/bugs/complex_escaping.md | 4 + vendor/plugins/maruku/tests/convert_all.sh | 6 + vendor/plugins/maruku/tests/math/math.css | 40 + vendor/plugins/maruku/tests/math/preamble.tex | 2 + vendor/plugins/maruku/tests/math/run.sh | 7 + vendor/plugins/maruku/tests/math/syntax.md | 46 + vendor/plugins/maruku/tests/math/syntax.xhtml | 37 + vendor/plugins/maruku/tests/math/use_itex.rb | 34 + .../maruku/tests/math_usage/document.md | 13 + .../plugins/maruku/tests/math_usage/math.css | 26 + .../plugins/maruku/tests/math_usage/script.sh | 13 + .../tests/others/Backslash escapes.text | 106 ++ .../maruku/tests/others/abbreviations.html | 16 + .../maruku/tests/others/abbreviations.md | 11 + vendor/plugins/maruku/tests/others/blank.html | 16 + vendor/plugins/maruku/tests/others/blank.md | 4 + vendor/plugins/maruku/tests/others/code.html | 18 + vendor/plugins/maruku/tests/others/code.md | 5 + vendor/plugins/maruku/tests/others/code2.html | 26 + vendor/plugins/maruku/tests/others/code2.md | 8 + vendor/plugins/maruku/tests/others/code3.html | 29 + vendor/plugins/maruku/tests/others/code3.md | 16 + vendor/plugins/maruku/tests/others/email.html | 14 + vendor/plugins/maruku/tests/others/email.md | 4 + .../plugins/maruku/tests/others/entities.html | 59 + .../plugins/maruku/tests/others/entities.md | 19 + .../plugins/maruku/tests/others/escaping.html | 26 + .../plugins/maruku/tests/others/escaping.md | 16 + .../plugins/maruku/tests/others/extra_dl.html | 157 ++ .../plugins/maruku/tests/others/extra_dl.md | 101 ++ .../maruku/tests/others/extra_header_id.html | 22 + .../maruku/tests/others/extra_header_id.md | 13 + .../maruku/tests/others/extra_table1.html | 114 ++ .../maruku/tests/others/extra_table1.md | 40 + .../maruku/tests/others/footnotes.html | 38 + .../plugins/maruku/tests/others/footnotes.md | 17 + .../plugins/maruku/tests/others/headers.html | 18 + vendor/plugins/maruku/tests/others/headers.md | 10 + vendor/plugins/maruku/tests/others/hrule.html | 22 + vendor/plugins/maruku/tests/others/hrule.md | 10 + .../plugins/maruku/tests/others/images.html | 22 + vendor/plugins/maruku/tests/others/images.md | 20 + .../maruku/tests/others/inline_html.html | 54 + .../maruku/tests/others/inline_html.md | 42 + vendor/plugins/maruku/tests/others/links.html | 34 + vendor/plugins/maruku/tests/others/links.md | 38 + vendor/plugins/maruku/tests/others/list1.html | 22 + vendor/plugins/maruku/tests/others/list1.md | 4 + vendor/plugins/maruku/tests/others/list2.html | 20 + vendor/plugins/maruku/tests/others/list2.md | 5 + vendor/plugins/maruku/tests/others/list3.html | 28 + vendor/plugins/maruku/tests/others/list3.md | 8 + vendor/plugins/maruku/tests/others/lists.html | 52 + vendor/plugins/maruku/tests/others/lists.md | 32 + .../tests/others/lists_after_paragraph.html | 54 + .../others/lists_after_paragraph.markdown-pl | 23 + .../tests/others/lists_after_paragraph.md | 44 + .../plugins/maruku/tests/others/lists_ol.html | 60 + .../plugins/maruku/tests/others/lists_ol.md | 39 + .../plugins/maruku/tests/others/misc_sw.html | 92 ++ vendor/plugins/maruku/tests/others/misc_sw.md | 105 ++ vendor/plugins/maruku/tests/others/one.html | 14 + vendor/plugins/maruku/tests/others/one.md | 1 + .../maruku/tests/others/paragraphs.html | 21 + .../plugins/maruku/tests/others/paragraphs.md | 13 + vendor/plugins/maruku/tests/others/sss06.html | 227 +++ vendor/plugins/maruku/tests/others/sss06.md | 352 ++++ vendor/plugins/maruku/tests/others/style.css | 27 + vendor/plugins/maruku/tests/others/test.html | 24 + vendor/plugins/maruku/tests/others/test.md | 4 + vendor/plugins/maruku/tests/s5/s5profiling.md | 48 + .../maruku/tests/s5/ui/default/blank.gif | Bin 0 -> 49 bytes .../maruku/tests/s5/ui/default/bodybg.gif | Bin 0 -> 10119 bytes .../maruku/tests/s5/ui/default/framing.css | 23 + .../maruku/tests/s5/ui/default/iepngfix.htc | 42 + .../maruku/tests/s5/ui/default/opera.css | 7 + .../maruku/tests/s5/ui/default/outline.css | 15 + .../maruku/tests/s5/ui/default/pretty.css | 86 + .../maruku/tests/s5/ui/default/print.css | 1 + .../maruku/tests/s5/ui/default/s5-core.css | 9 + .../maruku/tests/s5/ui/default/slides.css | 3 + .../maruku/tests/s5/ui/default/slides.js | 552 +++++++ .../maruku/tests/s5/ui/i18n/00_head.txt | 8 + .../maruku/tests/s5/ui/i18n/bg-shade.png | Bin 0 -> 594 bytes .../maruku/tests/s5/ui/i18n/bg-slide.jpg | Bin 0 -> 31239 bytes .../maruku/tests/s5/ui/i18n/framing.css | 23 + .../maruku/tests/s5/ui/i18n/pretty.css | 44 + .../maruku/tests/s5/ui/i18n/s5-core.css | 9 + .../maruku/tests/s5/ui/i18n/slides.css | 3 + .../maruku/tests/unittest/abbreviations.html | 11 + .../maruku/tests/unittest/abbreviations.md | 72 + vendor/plugins/maruku/tests/unittest/alt.html | 9 + vendor/plugins/maruku/tests/unittest/alt.md | 30 + .../tests/unittest/attributes/att2.html | 7 + .../maruku/tests/unittest/attributes/att2.md | 34 + .../tests/unittest/attributes/att3.html | 11 + .../maruku/tests/unittest/attributes/att3.md | 45 + .../tests/unittest/attributes/attributes.html | 17 + .../tests/unittest/attributes/attributes.md | 82 + .../tests/unittest/attributes/circular.html | 9 + .../tests/unittest/attributes/circular.md | 43 + .../tests/unittest/attributes/default.html | 9 + .../tests/unittest/attributes/default.md | 38 + .../plugins/maruku/tests/unittest/blank.html | 11 + vendor/plugins/maruku/tests/unittest/blank.md | 39 + .../maruku/tests/unittest/blanks_in_code.html | 24 + .../maruku/tests/unittest/blanks_in_code.md | 106 ++ .../maruku/tests/unittest/bug_def.html | 9 + .../plugins/maruku/tests/unittest/bug_def.md | 29 + .../maruku/tests/unittest/bug_table.html | 10 + .../maruku/tests/unittest/bug_table.md | 67 + .../plugins/maruku/tests/unittest/code.html | 14 + vendor/plugins/maruku/tests/unittest/code.md | 53 + .../plugins/maruku/tests/unittest/code2.html | 13 + vendor/plugins/maruku/tests/unittest/code2.md | 46 + .../plugins/maruku/tests/unittest/code3.html | 23 + vendor/plugins/maruku/tests/unittest/code3.md | 102 ++ .../maruku/tests/unittest/data_loss.html | 11 + .../maruku/tests/unittest/data_loss.md | 42 + .../plugins/maruku/tests/unittest/easy.html | 9 + vendor/plugins/maruku/tests/unittest/easy.md | 28 + .../plugins/maruku/tests/unittest/email.html | 9 + vendor/plugins/maruku/tests/unittest/email.md | 33 + .../tests/unittest/encoding/iso-8859-1.html | 9 + .../tests/unittest/encoding/iso-8859-1.md | 38 + .../maruku/tests/unittest/encoding/utf-8.html | 9 + .../maruku/tests/unittest/encoding/utf-8.md | 33 + .../maruku/tests/unittest/entities.html | 22 + .../plugins/maruku/tests/unittest/entities.md | 124 ++ .../maruku/tests/unittest/escaping.html | 17 + .../plugins/maruku/tests/unittest/escaping.md | 89 + .../maruku/tests/unittest/extra_dl.html | 18 + .../plugins/maruku/tests/unittest/extra_dl.md | 72 + .../tests/unittest/extra_header_id.html | 17 + .../maruku/tests/unittest/extra_header_id.md | 86 + .../maruku/tests/unittest/extra_table1.html | 10 + .../maruku/tests/unittest/extra_table1.md | 55 + .../maruku/tests/unittest/footnotes.html | 31 + .../maruku/tests/unittest/footnotes.md | 126 ++ .../maruku/tests/unittest/headers.html | 13 + .../plugins/maruku/tests/unittest/headers.md | 54 + .../maruku/tests/unittest/hex_entities.html | 9 + .../maruku/tests/unittest/hex_entities.md | 50 + .../plugins/maruku/tests/unittest/hrule.html | 7 + vendor/plugins/maruku/tests/unittest/hrule.md | 60 + .../plugins/maruku/tests/unittest/html2.html | 9 + vendor/plugins/maruku/tests/unittest/html2.md | 38 + .../plugins/maruku/tests/unittest/html3.html | 9 + vendor/plugins/maruku/tests/unittest/html3.md | 47 + .../plugins/maruku/tests/unittest/html4.html | 7 + vendor/plugins/maruku/tests/unittest/html4.md | 42 + .../plugins/maruku/tests/unittest/html5.html | 7 + vendor/plugins/maruku/tests/unittest/html5.md | 38 + vendor/plugins/maruku/tests/unittest/ie.html | 17 + vendor/plugins/maruku/tests/unittest/ie.md | 82 + .../plugins/maruku/tests/unittest/images.html | 17 + .../plugins/maruku/tests/unittest/images.md | 114 ++ .../maruku/tests/unittest/images2.html | 11 + .../plugins/maruku/tests/unittest/images2.md | 46 + .../maruku/tests/unittest/inline_html.html | 31 + .../maruku/tests/unittest/inline_html.md | 260 +++ .../maruku/tests/unittest/inline_html2.html | 7 + .../maruku/tests/unittest/inline_html2.md | 36 + .../plugins/maruku/tests/unittest/links.html | 27 + vendor/plugins/maruku/tests/unittest/links.md | 197 +++ .../plugins/maruku/tests/unittest/list1.html | 17 + vendor/plugins/maruku/tests/unittest/list1.md | 66 + .../plugins/maruku/tests/unittest/list2.html | 19 + vendor/plugins/maruku/tests/unittest/list2.md | 76 + .../plugins/maruku/tests/unittest/list3.html | 23 + vendor/plugins/maruku/tests/unittest/list3.md | 88 + .../plugins/maruku/tests/unittest/list4.html | 27 + vendor/plugins/maruku/tests/unittest/list4.md | 116 ++ .../plugins/maruku/tests/unittest/lists.html | 47 + vendor/plugins/maruku/tests/unittest/lists.md | 241 +++ .../maruku/tests/unittest/lists11.html | 9 + .../plugins/maruku/tests/unittest/lists11.md | 31 + .../plugins/maruku/tests/unittest/lists6.html | 7 + .../plugins/maruku/tests/unittest/lists6.md | 54 + .../plugins/maruku/tests/unittest/lists7.html | 13 + .../plugins/maruku/tests/unittest/lists7.md | 79 + .../maruku/tests/unittest/lists7b.html | 23 + .../plugins/maruku/tests/unittest/lists7b.md | 136 ++ .../plugins/maruku/tests/unittest/lists8.html | 11 + .../plugins/maruku/tests/unittest/lists8.md | 83 + .../plugins/maruku/tests/unittest/lists9.html | 25 + .../plugins/maruku/tests/unittest/lists9.md | 85 + .../tests/unittest/lists_after_paragraph.html | 45 + .../tests/unittest/lists_after_paragraph.md | 268 +++ .../maruku/tests/unittest/lists_ol.html | 69 + .../plugins/maruku/tests/unittest/lists_ol.md | 324 ++++ .../plugins/maruku/tests/unittest/loss.html | 7 + vendor/plugins/maruku/tests/unittest/loss.md | 29 + .../maruku/tests/unittest/math/equations.html | 15 + .../maruku/tests/unittest/math/equations.md | 69 + .../maruku/tests/unittest/math/inline.html | 17 + .../maruku/tests/unittest/math/inline.md | 101 ++ .../maruku/tests/unittest/math/math2.html | 12 + .../maruku/tests/unittest/math/math2.md | 74 + .../maruku/tests/unittest/math/notmath.html | 11 + .../maruku/tests/unittest/math/notmath.md | 40 + .../maruku/tests/unittest/math/table.html | 7 + .../maruku/tests/unittest/math/table.md | 58 + .../maruku/tests/unittest/math/table2.html | 9 + .../maruku/tests/unittest/math/table2.md | 60 + .../maruku/tests/unittest/misc_sw.html | 87 + .../plugins/maruku/tests/unittest/misc_sw.md | 615 +++++++ .../maruku/tests/unittest/notyet/escape.html | 11 + .../maruku/tests/unittest/notyet/escape.md | 36 + .../unittest/notyet/header_after_par.html | 19 + .../tests/unittest/notyet/header_after_par.md | 81 + .../maruku/tests/unittest/notyet/ticks.html | 9 + .../maruku/tests/unittest/notyet/ticks.md | 31 + .../tests/unittest/notyet/triggering.html | 37 + .../tests/unittest/notyet/triggering.md | 206 +++ .../plugins/maruku/tests/unittest/olist.html | 17 + vendor/plugins/maruku/tests/unittest/olist.md | 64 + vendor/plugins/maruku/tests/unittest/one.html | 9 + vendor/plugins/maruku/tests/unittest/one.md | 28 + .../maruku/tests/unittest/paragraph.html | 9 + .../maruku/tests/unittest/paragraph.md | 29 + .../paragraph_rules/dont_merge_ref.html | 13 + .../paragraph_rules/dont_merge_ref.md | 57 + .../paragraph_rules/tab_is_blank.html | 11 + .../unittest/paragraph_rules/tab_is_blank.md | 39 + .../maruku/tests/unittest/paragraphs.html | 13 + .../maruku/tests/unittest/paragraphs.md | 66 + .../tests/unittest/recover/recover_links.html | 9 + .../tests/unittest/recover/recover_links.md | 28 + .../unittest/references/long_example.html | 11 + .../tests/unittest/references/long_example.md | 88 + .../references/spaces_and_numbers.html | 7 + .../unittest/references/spaces_and_numbers.md | 28 + .../maruku/tests/unittest/smartypants.html | 25 + .../maruku/tests/unittest/smartypants.md | 171 ++ .../maruku/tests/unittest/syntax_hl.html | 19 + .../maruku/tests/unittest/syntax_hl.md | 80 + .../tests/unittest/table_attributes.html | 8 + .../maruku/tests/unittest/table_attributes.md | 52 + .../plugins/maruku/tests/unittest/test.html | 9 + vendor/plugins/maruku/tests/unittest/test.md | 32 + .../maruku/tests/unittest/wrapping.html | 15 + .../plugins/maruku/tests/unittest/wrapping.md | 88 + vendor/plugins/maruku/tests/unittest/xml.html | 7 + vendor/plugins/maruku/tests/unittest/xml.md | 54 + .../plugins/maruku/tests/unittest/xml2.html | 7 + vendor/plugins/maruku/tests/unittest/xml2.md | 34 + .../plugins/maruku/tests/unittest/xml3.html | 7 + vendor/plugins/maruku/tests/unittest/xml3.md | 44 + .../tests/unittest/xml_instruction.html | 11 + .../maruku/tests/unittest/xml_instruction.md | 72 + .../plugins/maruku/tests/utf8-files/TeX.html | 229 +++ .../plugins/maruku/tests/utf8-files/TeX.tex | 219 +++ .../plugins/maruku/tests/utf8-files/TeX.txt | 210 +++ .../plugins/maruku/tests/utf8-files/simple.md | 1 + .../maruku/tests/utf8-files/simple.tex | 18 + .../plugins/maruku/tests/utf8-files/ucs.sty | 749 +++++++++ 337 files changed, 21290 insertions(+), 72 deletions(-) delete mode 100644 vendor/plugins/HTML5lib/lib/core_ext/kernel.rb delete mode 100644 vendor/plugins/HTML5lib/lib/core_ext/string.rb create mode 100644 vendor/plugins/HTML5lib/test19.rb create mode 100644 vendor/plugins/maruku/AUTHORS create mode 100644 vendor/plugins/maruku/LICENSE create mode 100644 vendor/plugins/maruku/Rakefile create mode 100755 vendor/plugins/maruku/bin/Markdown.pl create mode 100644 vendor/plugins/maruku/bin/maruku create mode 100644 vendor/plugins/maruku/bin/marutest create mode 100644 vendor/plugins/maruku/bin/marutex create mode 100644 vendor/plugins/maruku/tests/Makefile create mode 100755 vendor/plugins/maruku/tests/MarkdownTest_1.0/MarkdownTest.pl create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.text create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.html create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.html.dist create mode 100644 vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.text create mode 100644 vendor/plugins/maruku/tests/bugs/code_in_links.md create mode 100644 vendor/plugins/maruku/tests/bugs/complex_escaping.md create mode 100755 vendor/plugins/maruku/tests/convert_all.sh create mode 100644 vendor/plugins/maruku/tests/math/math.css create mode 100644 vendor/plugins/maruku/tests/math/preamble.tex create mode 100755 vendor/plugins/maruku/tests/math/run.sh create mode 100644 vendor/plugins/maruku/tests/math/syntax.md create mode 100644 vendor/plugins/maruku/tests/math/syntax.xhtml create mode 100644 vendor/plugins/maruku/tests/math/use_itex.rb create mode 100644 vendor/plugins/maruku/tests/math_usage/document.md create mode 100644 vendor/plugins/maruku/tests/math_usage/math.css create mode 100755 vendor/plugins/maruku/tests/math_usage/script.sh create mode 100644 vendor/plugins/maruku/tests/others/Backslash escapes.text create mode 100644 vendor/plugins/maruku/tests/others/abbreviations.html create mode 100644 vendor/plugins/maruku/tests/others/abbreviations.md create mode 100644 vendor/plugins/maruku/tests/others/blank.html create mode 100644 vendor/plugins/maruku/tests/others/blank.md create mode 100644 vendor/plugins/maruku/tests/others/code.html create mode 100644 vendor/plugins/maruku/tests/others/code.md create mode 100644 vendor/plugins/maruku/tests/others/code2.html create mode 100644 vendor/plugins/maruku/tests/others/code2.md create mode 100644 vendor/plugins/maruku/tests/others/code3.html create mode 100644 vendor/plugins/maruku/tests/others/code3.md create mode 100644 vendor/plugins/maruku/tests/others/email.html create mode 100644 vendor/plugins/maruku/tests/others/email.md create mode 100644 vendor/plugins/maruku/tests/others/entities.html create mode 100644 vendor/plugins/maruku/tests/others/entities.md create mode 100644 vendor/plugins/maruku/tests/others/escaping.html create mode 100644 vendor/plugins/maruku/tests/others/escaping.md create mode 100644 vendor/plugins/maruku/tests/others/extra_dl.html create mode 100644 vendor/plugins/maruku/tests/others/extra_dl.md create mode 100644 vendor/plugins/maruku/tests/others/extra_header_id.html create mode 100644 vendor/plugins/maruku/tests/others/extra_header_id.md create mode 100644 vendor/plugins/maruku/tests/others/extra_table1.html create mode 100644 vendor/plugins/maruku/tests/others/extra_table1.md create mode 100644 vendor/plugins/maruku/tests/others/footnotes.html create mode 100644 vendor/plugins/maruku/tests/others/footnotes.md create mode 100644 vendor/plugins/maruku/tests/others/headers.html create mode 100644 vendor/plugins/maruku/tests/others/headers.md create mode 100644 vendor/plugins/maruku/tests/others/hrule.html create mode 100644 vendor/plugins/maruku/tests/others/hrule.md create mode 100644 vendor/plugins/maruku/tests/others/images.html create mode 100644 vendor/plugins/maruku/tests/others/images.md create mode 100644 vendor/plugins/maruku/tests/others/inline_html.html create mode 100644 vendor/plugins/maruku/tests/others/inline_html.md create mode 100644 vendor/plugins/maruku/tests/others/links.html create mode 100644 vendor/plugins/maruku/tests/others/links.md create mode 100644 vendor/plugins/maruku/tests/others/list1.html create mode 100644 vendor/plugins/maruku/tests/others/list1.md create mode 100644 vendor/plugins/maruku/tests/others/list2.html create mode 100644 vendor/plugins/maruku/tests/others/list2.md create mode 100644 vendor/plugins/maruku/tests/others/list3.html create mode 100644 vendor/plugins/maruku/tests/others/list3.md create mode 100644 vendor/plugins/maruku/tests/others/lists.html create mode 100644 vendor/plugins/maruku/tests/others/lists.md create mode 100644 vendor/plugins/maruku/tests/others/lists_after_paragraph.html create mode 100644 vendor/plugins/maruku/tests/others/lists_after_paragraph.markdown-pl create mode 100644 vendor/plugins/maruku/tests/others/lists_after_paragraph.md create mode 100644 vendor/plugins/maruku/tests/others/lists_ol.html create mode 100644 vendor/plugins/maruku/tests/others/lists_ol.md create mode 100644 vendor/plugins/maruku/tests/others/misc_sw.html create mode 100644 vendor/plugins/maruku/tests/others/misc_sw.md create mode 100644 vendor/plugins/maruku/tests/others/one.html create mode 100644 vendor/plugins/maruku/tests/others/one.md create mode 100644 vendor/plugins/maruku/tests/others/paragraphs.html create mode 100644 vendor/plugins/maruku/tests/others/paragraphs.md create mode 100644 vendor/plugins/maruku/tests/others/sss06.html create mode 100644 vendor/plugins/maruku/tests/others/sss06.md create mode 100644 vendor/plugins/maruku/tests/others/style.css create mode 100644 vendor/plugins/maruku/tests/others/test.html create mode 100644 vendor/plugins/maruku/tests/others/test.md create mode 100644 vendor/plugins/maruku/tests/s5/s5profiling.md create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/blank.gif create mode 100755 vendor/plugins/maruku/tests/s5/ui/default/bodybg.gif create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/framing.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/iepngfix.htc create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/opera.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/outline.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/pretty.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/print.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/s5-core.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/slides.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/default/slides.js create mode 100644 vendor/plugins/maruku/tests/s5/ui/i18n/00_head.txt create mode 100755 vendor/plugins/maruku/tests/s5/ui/i18n/bg-shade.png create mode 100755 vendor/plugins/maruku/tests/s5/ui/i18n/bg-slide.jpg create mode 100644 vendor/plugins/maruku/tests/s5/ui/i18n/framing.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/i18n/pretty.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/i18n/s5-core.css create mode 100644 vendor/plugins/maruku/tests/s5/ui/i18n/slides.css create mode 100644 vendor/plugins/maruku/tests/unittest/abbreviations.html create mode 100644 vendor/plugins/maruku/tests/unittest/abbreviations.md create mode 100644 vendor/plugins/maruku/tests/unittest/alt.html create mode 100644 vendor/plugins/maruku/tests/unittest/alt.md create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/att2.html create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/att2.md create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/att3.html create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/att3.md create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/attributes.html create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/attributes.md create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/circular.html create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/circular.md create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/default.html create mode 100644 vendor/plugins/maruku/tests/unittest/attributes/default.md create mode 100644 vendor/plugins/maruku/tests/unittest/blank.html create mode 100644 vendor/plugins/maruku/tests/unittest/blank.md create mode 100644 vendor/plugins/maruku/tests/unittest/blanks_in_code.html create mode 100644 vendor/plugins/maruku/tests/unittest/blanks_in_code.md create mode 100644 vendor/plugins/maruku/tests/unittest/bug_def.html create mode 100644 vendor/plugins/maruku/tests/unittest/bug_def.md create mode 100644 vendor/plugins/maruku/tests/unittest/bug_table.html create mode 100644 vendor/plugins/maruku/tests/unittest/bug_table.md create mode 100644 vendor/plugins/maruku/tests/unittest/code.html create mode 100644 vendor/plugins/maruku/tests/unittest/code.md create mode 100644 vendor/plugins/maruku/tests/unittest/code2.html create mode 100644 vendor/plugins/maruku/tests/unittest/code2.md create mode 100644 vendor/plugins/maruku/tests/unittest/code3.html create mode 100644 vendor/plugins/maruku/tests/unittest/code3.md create mode 100644 vendor/plugins/maruku/tests/unittest/data_loss.html create mode 100644 vendor/plugins/maruku/tests/unittest/data_loss.md create mode 100644 vendor/plugins/maruku/tests/unittest/easy.html create mode 100644 vendor/plugins/maruku/tests/unittest/easy.md create mode 100644 vendor/plugins/maruku/tests/unittest/email.html create mode 100644 vendor/plugins/maruku/tests/unittest/email.md create mode 100644 vendor/plugins/maruku/tests/unittest/encoding/iso-8859-1.html create mode 100644 vendor/plugins/maruku/tests/unittest/encoding/iso-8859-1.md create mode 100644 vendor/plugins/maruku/tests/unittest/encoding/utf-8.html create mode 100644 vendor/plugins/maruku/tests/unittest/encoding/utf-8.md create mode 100644 vendor/plugins/maruku/tests/unittest/entities.html create mode 100644 vendor/plugins/maruku/tests/unittest/entities.md create mode 100644 vendor/plugins/maruku/tests/unittest/escaping.html create mode 100644 vendor/plugins/maruku/tests/unittest/escaping.md create mode 100644 vendor/plugins/maruku/tests/unittest/extra_dl.html create mode 100644 vendor/plugins/maruku/tests/unittest/extra_dl.md create mode 100644 vendor/plugins/maruku/tests/unittest/extra_header_id.html create mode 100644 vendor/plugins/maruku/tests/unittest/extra_header_id.md create mode 100644 vendor/plugins/maruku/tests/unittest/extra_table1.html create mode 100644 vendor/plugins/maruku/tests/unittest/extra_table1.md create mode 100644 vendor/plugins/maruku/tests/unittest/footnotes.html create mode 100644 vendor/plugins/maruku/tests/unittest/footnotes.md create mode 100644 vendor/plugins/maruku/tests/unittest/headers.html create mode 100644 vendor/plugins/maruku/tests/unittest/headers.md create mode 100644 vendor/plugins/maruku/tests/unittest/hex_entities.html create mode 100644 vendor/plugins/maruku/tests/unittest/hex_entities.md create mode 100644 vendor/plugins/maruku/tests/unittest/hrule.html create mode 100644 vendor/plugins/maruku/tests/unittest/hrule.md create mode 100644 vendor/plugins/maruku/tests/unittest/html2.html create mode 100644 vendor/plugins/maruku/tests/unittest/html2.md create mode 100644 vendor/plugins/maruku/tests/unittest/html3.html create mode 100644 vendor/plugins/maruku/tests/unittest/html3.md create mode 100644 vendor/plugins/maruku/tests/unittest/html4.html create mode 100644 vendor/plugins/maruku/tests/unittest/html4.md create mode 100644 vendor/plugins/maruku/tests/unittest/html5.html create mode 100644 vendor/plugins/maruku/tests/unittest/html5.md create mode 100644 vendor/plugins/maruku/tests/unittest/ie.html create mode 100644 vendor/plugins/maruku/tests/unittest/ie.md create mode 100644 vendor/plugins/maruku/tests/unittest/images.html create mode 100644 vendor/plugins/maruku/tests/unittest/images.md create mode 100644 vendor/plugins/maruku/tests/unittest/images2.html create mode 100644 vendor/plugins/maruku/tests/unittest/images2.md create mode 100644 vendor/plugins/maruku/tests/unittest/inline_html.html create mode 100644 vendor/plugins/maruku/tests/unittest/inline_html.md create mode 100644 vendor/plugins/maruku/tests/unittest/inline_html2.html create mode 100644 vendor/plugins/maruku/tests/unittest/inline_html2.md create mode 100644 vendor/plugins/maruku/tests/unittest/links.html create mode 100644 vendor/plugins/maruku/tests/unittest/links.md create mode 100644 vendor/plugins/maruku/tests/unittest/list1.html create mode 100644 vendor/plugins/maruku/tests/unittest/list1.md create mode 100644 vendor/plugins/maruku/tests/unittest/list2.html create mode 100644 vendor/plugins/maruku/tests/unittest/list2.md create mode 100644 vendor/plugins/maruku/tests/unittest/list3.html create mode 100644 vendor/plugins/maruku/tests/unittest/list3.md create mode 100644 vendor/plugins/maruku/tests/unittest/list4.html create mode 100644 vendor/plugins/maruku/tests/unittest/list4.md create mode 100644 vendor/plugins/maruku/tests/unittest/lists.html create mode 100644 vendor/plugins/maruku/tests/unittest/lists.md create mode 100644 vendor/plugins/maruku/tests/unittest/lists11.html create mode 100644 vendor/plugins/maruku/tests/unittest/lists11.md create mode 100644 vendor/plugins/maruku/tests/unittest/lists6.html create mode 100644 vendor/plugins/maruku/tests/unittest/lists6.md create mode 100644 vendor/plugins/maruku/tests/unittest/lists7.html create mode 100644 vendor/plugins/maruku/tests/unittest/lists7.md create mode 100644 vendor/plugins/maruku/tests/unittest/lists7b.html create mode 100644 vendor/plugins/maruku/tests/unittest/lists7b.md create mode 100644 vendor/plugins/maruku/tests/unittest/lists8.html create mode 100644 vendor/plugins/maruku/tests/unittest/lists8.md create mode 100644 vendor/plugins/maruku/tests/unittest/lists9.html create mode 100644 vendor/plugins/maruku/tests/unittest/lists9.md create mode 100644 vendor/plugins/maruku/tests/unittest/lists_after_paragraph.html create mode 100644 vendor/plugins/maruku/tests/unittest/lists_after_paragraph.md create mode 100644 vendor/plugins/maruku/tests/unittest/lists_ol.html create mode 100644 vendor/plugins/maruku/tests/unittest/lists_ol.md create mode 100644 vendor/plugins/maruku/tests/unittest/loss.html create mode 100644 vendor/plugins/maruku/tests/unittest/loss.md create mode 100644 vendor/plugins/maruku/tests/unittest/math/equations.html create mode 100644 vendor/plugins/maruku/tests/unittest/math/equations.md create mode 100644 vendor/plugins/maruku/tests/unittest/math/inline.html create mode 100644 vendor/plugins/maruku/tests/unittest/math/inline.md create mode 100644 vendor/plugins/maruku/tests/unittest/math/math2.html create mode 100644 vendor/plugins/maruku/tests/unittest/math/math2.md create mode 100644 vendor/plugins/maruku/tests/unittest/math/notmath.html create mode 100644 vendor/plugins/maruku/tests/unittest/math/notmath.md create mode 100644 vendor/plugins/maruku/tests/unittest/math/table.html create mode 100644 vendor/plugins/maruku/tests/unittest/math/table.md create mode 100644 vendor/plugins/maruku/tests/unittest/math/table2.html create mode 100644 vendor/plugins/maruku/tests/unittest/math/table2.md create mode 100644 vendor/plugins/maruku/tests/unittest/misc_sw.html create mode 100644 vendor/plugins/maruku/tests/unittest/misc_sw.md create mode 100644 vendor/plugins/maruku/tests/unittest/notyet/escape.html create mode 100644 vendor/plugins/maruku/tests/unittest/notyet/escape.md create mode 100644 vendor/plugins/maruku/tests/unittest/notyet/header_after_par.html create mode 100644 vendor/plugins/maruku/tests/unittest/notyet/header_after_par.md create mode 100644 vendor/plugins/maruku/tests/unittest/notyet/ticks.html create mode 100644 vendor/plugins/maruku/tests/unittest/notyet/ticks.md create mode 100644 vendor/plugins/maruku/tests/unittest/notyet/triggering.html create mode 100644 vendor/plugins/maruku/tests/unittest/notyet/triggering.md create mode 100644 vendor/plugins/maruku/tests/unittest/olist.html create mode 100644 vendor/plugins/maruku/tests/unittest/olist.md create mode 100644 vendor/plugins/maruku/tests/unittest/one.html create mode 100644 vendor/plugins/maruku/tests/unittest/one.md create mode 100644 vendor/plugins/maruku/tests/unittest/paragraph.html create mode 100644 vendor/plugins/maruku/tests/unittest/paragraph.md create mode 100644 vendor/plugins/maruku/tests/unittest/paragraph_rules/dont_merge_ref.html create mode 100644 vendor/plugins/maruku/tests/unittest/paragraph_rules/dont_merge_ref.md create mode 100644 vendor/plugins/maruku/tests/unittest/paragraph_rules/tab_is_blank.html create mode 100644 vendor/plugins/maruku/tests/unittest/paragraph_rules/tab_is_blank.md create mode 100644 vendor/plugins/maruku/tests/unittest/paragraphs.html create mode 100644 vendor/plugins/maruku/tests/unittest/paragraphs.md create mode 100644 vendor/plugins/maruku/tests/unittest/recover/recover_links.html create mode 100644 vendor/plugins/maruku/tests/unittest/recover/recover_links.md create mode 100644 vendor/plugins/maruku/tests/unittest/references/long_example.html create mode 100644 vendor/plugins/maruku/tests/unittest/references/long_example.md create mode 100644 vendor/plugins/maruku/tests/unittest/references/spaces_and_numbers.html create mode 100644 vendor/plugins/maruku/tests/unittest/references/spaces_and_numbers.md create mode 100644 vendor/plugins/maruku/tests/unittest/smartypants.html create mode 100644 vendor/plugins/maruku/tests/unittest/smartypants.md create mode 100644 vendor/plugins/maruku/tests/unittest/syntax_hl.html create mode 100644 vendor/plugins/maruku/tests/unittest/syntax_hl.md create mode 100644 vendor/plugins/maruku/tests/unittest/table_attributes.html create mode 100644 vendor/plugins/maruku/tests/unittest/table_attributes.md create mode 100644 vendor/plugins/maruku/tests/unittest/test.html create mode 100644 vendor/plugins/maruku/tests/unittest/test.md create mode 100644 vendor/plugins/maruku/tests/unittest/wrapping.html create mode 100644 vendor/plugins/maruku/tests/unittest/wrapping.md create mode 100644 vendor/plugins/maruku/tests/unittest/xml.html create mode 100644 vendor/plugins/maruku/tests/unittest/xml.md create mode 100644 vendor/plugins/maruku/tests/unittest/xml2.html create mode 100644 vendor/plugins/maruku/tests/unittest/xml2.md create mode 100644 vendor/plugins/maruku/tests/unittest/xml3.html create mode 100644 vendor/plugins/maruku/tests/unittest/xml3.md create mode 100644 vendor/plugins/maruku/tests/unittest/xml_instruction.html create mode 100644 vendor/plugins/maruku/tests/unittest/xml_instruction.md create mode 100644 vendor/plugins/maruku/tests/utf8-files/TeX.html create mode 100644 vendor/plugins/maruku/tests/utf8-files/TeX.tex create mode 100644 vendor/plugins/maruku/tests/utf8-files/TeX.txt create mode 100644 vendor/plugins/maruku/tests/utf8-files/simple.md create mode 100644 vendor/plugins/maruku/tests/utf8-files/simple.tex create mode 100644 vendor/plugins/maruku/tests/utf8-files/ucs.sty diff --git a/vendor/plugins/HTML5lib/Manifest.txt b/vendor/plugins/HTML5lib/Manifest.txt index 082b2b0b..0f5a2ea6 100644 --- a/vendor/plugins/HTML5lib/Manifest.txt +++ b/vendor/plugins/HTML5lib/Manifest.txt @@ -3,7 +3,6 @@ Manifest.txt README Rakefile.rb bin/html5 -lib/core_ext/string.rb lib/html5.rb lib/html5/constants.rb lib/html5/filters/base.rb @@ -103,15 +102,15 @@ testdata/validator/ol-start-attribute.test testdata/validator/starttags.test testdata/validator/style-scoped-attribute.test testdata/validator/tabindexattribute.test -tests/preamble.rb -tests/test_encoding.rb -tests/test_lxp.rb -tests/test_parser.rb -tests/test_sanitizer.rb -tests/test_serializer.rb -tests/test_sniffer.rb -tests/test_stream.rb -tests/test_tokenizer.rb -tests/test_treewalkers.rb -tests/test_validator.rb -tests/tokenizer_test_parser.rb +test/preamble.rb +test/test_encoding.rb +test/test_lxp.rb +test/test_parser.rb +test/test_sanitizer.rb +test/test_serializer.rb +test/test_sniffer.rb +test/test_stream.rb +test/test_tokenizer.rb +test/test_treewalkers.rb +test/test_validator.rb +test/tokenizer_test_parser.rb diff --git a/vendor/plugins/HTML5lib/lib/core_ext/kernel.rb b/vendor/plugins/HTML5lib/lib/core_ext/kernel.rb deleted file mode 100644 index 3bb75ad8..00000000 --- a/vendor/plugins/HTML5lib/lib/core_ext/kernel.rb +++ /dev/null @@ -1,13 +0,0 @@ -module Kernel - def silence - if $VERBOSE - $VERBOSE = false - yield - $VERBOSE = true - else - yield - end - end -end - - \ No newline at end of file diff --git a/vendor/plugins/HTML5lib/lib/core_ext/string.rb b/vendor/plugins/HTML5lib/lib/core_ext/string.rb deleted file mode 100644 index dec1fa4f..00000000 --- a/vendor/plugins/HTML5lib/lib/core_ext/string.rb +++ /dev/null @@ -1,17 +0,0 @@ -class String - alias old_format % - define_method("%") do |data| - unless data.kind_of?(Hash) - $VERBOSE = false - r = old_format(data) - $VERBOSE = true - r - else - ret = self.clone - data.each do |k,v| - ret.gsub!(/\%\(#{k}\)/, v) - end - ret - end - end -end \ No newline at end of file diff --git a/vendor/plugins/HTML5lib/lib/html5/cli.rb b/vendor/plugins/HTML5lib/lib/html5/cli.rb index ef49d4c6..28d4e98a 100644 --- a/vendor/plugins/HTML5lib/lib/html5/cli.rb +++ b/vendor/plugins/HTML5lib/lib/html5/cli.rb @@ -1,6 +1,5 @@ $:.unshift File.dirname(__FILE__), 'lib' require 'html5' -require 'core_ext/string' require 'ostruct' require 'optparse' @@ -190,7 +189,7 @@ module HTML5::CLI t1 = Time.new print_output(p, document, opts) t2 = Time.new - puts "\n\nRun took: %fs (plus %fs to print the output)"%[t1-t0, t2-t1] + puts "\n\nRun took: #{t1-t0}s (plus #{t2-t1}s to print the output)" else document = p.send(opts.parsemethod, *args) print_output(p, document, opts) @@ -218,14 +217,32 @@ module HTML5::CLI if opts.error errList=[] for pos, errorcode, datavars in parser.errors - errList << "Line #{pos[0]} Col #{pos[1]} " + (HTML5::E[errorcode] || "Unknown error \"#{errorcode}\"") % datavars + formatstring = HTML5::E[errorcode] || 'Unknown error "%(errorcode)"' + message = PythonicTemplate.new(formatstring).to_s(datavars) + errList << "Line #{pos[0]} Col #{pos[1]} " + message end $stdout.write("\nParse errors:\n" + errList.join("\n")+"\n") end end + class PythonicTemplate + # convert Python format string into a Ruby string, ready to eval + def initialize format + @format = format + @format.gsub!('"', '\\"') + @format.gsub!(/%\((\w+)\)/, '#{@_\1}') + @format = '"' + @format + '"' + end + + # evaluate string + def to_s(vars=nil) + vars.each {|var,value| eval "@_#{var}=#{value.dump}"} if vars + eval @format + end + end + def self.run options = parse_opts ARGV parse options, ARGV end -end \ No newline at end of file +end diff --git a/vendor/plugins/HTML5lib/lib/html5/html5parser.rb b/vendor/plugins/HTML5lib/lib/html5/html5parser.rb index e6c2a8a2..edcb8de8 100644 --- a/vendor/plugins/HTML5lib/lib/html5/html5parser.rb +++ b/vendor/plugins/HTML5lib/lib/html5/html5parser.rb @@ -46,8 +46,8 @@ module HTML5 @tree = TreeBuilders::REXML::TreeBuilder options.each {|name, value| instance_variable_set("@#{name}", value) } - @lowercase_attr_name = nil unless instance_variables.include?("@lowercase_attr_name") - @lowercase_element_name = nil unless instance_variables.include?("@lowercase_element_name") + @lowercase_attr_name = nil unless instance_variable_defined?("@lowercase_attr_name") + @lowercase_element_name = nil unless instance_variable_defined?("@lowercase_element_name") @tree = @tree.new diff --git a/vendor/plugins/HTML5lib/lib/html5/html5parser/in_body_phase.rb b/vendor/plugins/HTML5lib/lib/html5/html5parser/in_body_phase.rb index f592c57b..4ec74060 100644 --- a/vendor/plugins/HTML5lib/lib/html5/html5parser/in_body_phase.rb +++ b/vendor/plugins/HTML5lib/lib/html5/html5parser/in_body_phase.rb @@ -1,5 +1,4 @@ require 'html5/html5parser/phase' -require 'core_ext/kernel' module HTML5 class InBodyPhase < Phase @@ -51,10 +50,8 @@ module HTML5 super(parser, tree) # for special handling of whitespace in 
-      silence do
-        class << self
-          alias processSpaceCharactersNonPre processSpaceCharacters
-        end
+      class << self
+        alias processSpaceCharactersNonPre processSpaceCharacters
       end
     end
 
@@ -62,9 +59,8 @@ module HTML5
       # #Sometimes (start of 
 blocks) we want to drop leading newlines
 
       class << self
-        silence do
-          alias processSpaceCharacters processSpaceCharactersNonPre
-        end
+        remove_method :processSpaceCharacters rescue nil
+        alias processSpaceCharacters processSpaceCharactersNonPre
       end
       
       if (data.length > 0 and data[0] == ?\n && 
@@ -119,9 +115,8 @@ module HTML5
       @tree.insert_element(name, attributes)
       if name == 'pre'
         class << self
-          silence do
-            alias processSpaceCharacters processSpaceCharactersDropNewline
-          end
+          remove_method :processSpaceCharacters rescue nil
+          alias processSpaceCharacters processSpaceCharactersDropNewline
         end
       end
     end
@@ -293,7 +288,10 @@ module HTML5
       # XXX Form element pointer checking here as well...
       @tree.insert_element(name, attributes)
       @parser.tokenizer.content_model_flag = :RCDATA
-      class << self; alias processSpaceCharacters processSpaceCharactersDropNewline; end
+      class << self
+        remove_method :processSpaceCharacters rescue nil
+        alias processSpaceCharacters processSpaceCharactersDropNewline
+      end
     end
 
     # iframe, noembed noframes, noscript(if scripting enabled)
diff --git a/vendor/plugins/HTML5lib/lib/html5/inputstream.rb b/vendor/plugins/HTML5lib/lib/html5/inputstream.rb
index a07aa815..d63477cd 100755
--- a/vendor/plugins/HTML5lib/lib/html5/inputstream.rb
+++ b/vendor/plugins/HTML5lib/lib/html5/inputstream.rb
@@ -33,6 +33,11 @@ module HTML5
 
       options.each {|name, value| instance_variable_set("@#{name}", value) }
 
+      # partial Ruby 1.9 support
+      if @encoding and source.respond_to? :force_encoding
+        source.force_encoding(@encoding) rescue nil
+      end
+
       # Raw Stream
       @raw_stream = open_stream(source)
 
@@ -265,6 +270,38 @@ module HTML5
         @tell += 1
 
         case c
+
+        when String
+          # partial Ruby 1.9 support
+          case c
+          when "\0"
+            @errors.push("null-character")
+            c = "\uFFFD" # null characters are invalid
+          when "\r"
+            @tell += 1 if @buffer[@tell] == "\n"
+            c = "\n"
+          when "\x80" .. "\x9F"
+            c = ''.force_encoding('UTF-8') << ENTITIES_WINDOWS1252[c.ord-0x80]
+          end
+
+          if c == "\x0D"
+            # normalize newlines
+            @tell += 1 if @buffer[@tell] == 0x0A
+            c = 0x0A
+          end
+
+          # update position in stream
+          if c == "\x0a"
+            @line_lengths << @col
+            @line += 1
+            @col = 0
+          else
+            @col += 1
+          end
+
+          # binary utf-8
+          c.ord > 126 ? [c.ord].pack('U') : c
+
         when 0x01..0x7F
           if c == 0x0D
             # normalize newlines
@@ -293,7 +330,7 @@ module HTML5
           end
 
         when 0xC0..0xFF
-          if instance_variables.include?("@win1252") && @win1252
+          if instance_variable_defined?("@win1252") && @win1252
             "\xC3" + (c - 64).chr # convert to utf-8
           # from http://www.w3.org/International/questions/qa-forms-utf-8.en.php
           elsif @buffer[@tell - 1..@tell + 3] =~ /^
@@ -340,7 +377,12 @@ module HTML5
     end
 
     def unget(characters)
-      @queue.unshift(*characters.to_a) unless characters == :EOF
+      return if characters == :EOF
+      if characters.respond_to? :to_a
+        @queue.unshift(*characters.to_a)
+      else
+        characters.reverse.each_char {|c| @queue.unshift(c)}
+      end
     end
   end
 
diff --git a/vendor/plugins/HTML5lib/lib/html5/serializer/htmlserializer.rb b/vendor/plugins/HTML5lib/lib/html5/serializer/htmlserializer.rb
index ae799f83..ca5841e7 100644
--- a/vendor/plugins/HTML5lib/lib/html5/serializer/htmlserializer.rb
+++ b/vendor/plugins/HTML5lib/lib/html5/serializer/htmlserializer.rb
@@ -31,7 +31,7 @@ module HTML5
       @inject_meta_charset = true
 
       options.each do |name, value|
-        next unless instance_variables.include?("@#{name}")
+        next unless instance_variable_defined?("@#{name}")
         @use_best_quote_char = false if name.to_s == 'quote_char'
         instance_variable_set("@#{name}", value)
       end
diff --git a/vendor/plugins/HTML5lib/lib/html5/version.rb b/vendor/plugins/HTML5lib/lib/html5/version.rb
index 655548e5..4673962c 100644
--- a/vendor/plugins/HTML5lib/lib/html5/version.rb
+++ b/vendor/plugins/HTML5lib/lib/html5/version.rb
@@ -1,3 +1,3 @@
 module HTML5
-  VERSION = '0.10.0'
-end
\ No newline at end of file
+  VERSION = '0.10.1'
+end
diff --git a/vendor/plugins/HTML5lib/test/preamble.rb b/vendor/plugins/HTML5lib/test/preamble.rb
index ce4b1297..b13651ab 100644
--- a/vendor/plugins/HTML5lib/test/preamble.rb
+++ b/vendor/plugins/HTML5lib/test/preamble.rb
@@ -5,14 +5,13 @@ HTML5_BASE = File.dirname(File.dirname(File.dirname(File.expand_path(__FILE__)))
 if File.exists?(File.join(HTML5_BASE, 'ruby', 'testdata'))
   TESTDATA_DIR = File.join(HTML5_BASE, 'ruby', 'testdata')
 else
-  TESTDATA_DIR = File.join(HTML5_BASE, 'testdata')
+  HTML5_BASE_RUBY = File.dirname(File.dirname(File.expand_path(__FILE__)))
+  TESTDATA_DIR = File.join(HTML5_BASE_RUBY, 'testdata')
 end
 
 $:.unshift File.join(File.dirname(File.dirname(__FILE__)), 'lib')
 $:.unshift File.dirname(__FILE__)
 
-require 'core_ext/string'
-
 def html5_test_files(subdirectory)
   Dir[File.join(TESTDATA_DIR, subdirectory, '*.*')]
 end
diff --git a/vendor/plugins/HTML5lib/test/test_parser.rb b/vendor/plugins/HTML5lib/test/test_parser.rb
index 15764c52..5f33b28d 100644
--- a/vendor/plugins/HTML5lib/test/test_parser.rb
+++ b/vendor/plugins/HTML5lib/test/test_parser.rb
@@ -2,7 +2,7 @@ require File.join(File.dirname(__FILE__), 'preamble')
 
 require 'html5/treebuilders'
 require 'html5/html5parser'
-
+require 'html5/cli'
 
 $tree_types_to_test = ['simpletree', 'rexml']
 
@@ -45,7 +45,8 @@ class Html5ParserTestCase < Test::Unit::TestCase
           ].join("\n")
 
           actual_errors = parser.errors.map do |(line, col), message, datavars|
-            'Line: %i Col: %i %s' % [line, col, E[message] % datavars]
+            message = CLI::PythonicTemplate.new(E[message]).to_s(datavars)
+            "Line: #{line} Col: #{col} #{message}"
           end
 
           assert_equal errors, actual_errors, [
diff --git a/vendor/plugins/HTML5lib/test19.rb b/vendor/plugins/HTML5lib/test19.rb
new file mode 100644
index 00000000..69ebe77c
--- /dev/null
+++ b/vendor/plugins/HTML5lib/test19.rb
@@ -0,0 +1,40 @@
+# 
+# This temporary test driver tracks progress on getting HTML5lib working
+# on Ruby 1.9.  Prereqs of Hoe, Hpricot, and UniversalDetector will be
+# required to complete this.
+#
+# Once all the tests pass, this file should be deleted
+#
+
+require 'test/test_cli'
+
+# requires UniversalDetector
+# require 'test/test_encoding'
+
+require 'test/test_input_stream'
+
+# incompatible encoding regexp match
+# require 'test/test_lxp'
+
+require 'test/test_parser'
+
+# warning: method redefined; discarding old test
+# warning: instance variable @expanded_name not initialized
+# require 'test/test_sanitizer'
+
+# warning: instance variable @delegate_sd_obj not initialized
+# require 'test/test_serializer'
+
+# undebugged
+# require 'test/test_sniffer'
+
+require 'test/test_stream'
+
+# warning: shadowing outer local variable - tokens
+# require 'test/test_tokenizer'
+
+# requires hpricot
+# require 'test/test_treewalkers'
+
+# warning: instance variable @delegate_sd_obj not initialized
+# require 'test/test_validator'
diff --git a/vendor/plugins/maruku/AUTHORS b/vendor/plugins/maruku/AUTHORS
new file mode 100644
index 00000000..a9fc233b
--- /dev/null
+++ b/vendor/plugins/maruku/AUTHORS
@@ -0,0 +1,11 @@
+Authors:
+
+* [Andrea Censi](http://www.dis.uniroma1.it/~acensi)
+
+Bug reporting, feature requests and praise:
+
+* [Jacques Distler](http://golem.ph.utexas.edu/~distler)
+* Snowman 
+* Sander Bouwhuis
+* Aggelos Orfanakos
+
diff --git a/vendor/plugins/maruku/LICENSE b/vendor/plugins/maruku/LICENSE
new file mode 100644
index 00000000..04137b9b
--- /dev/null
+++ b/vendor/plugins/maruku/LICENSE
@@ -0,0 +1,340 @@
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    
+    Copyright (C)   
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  , 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/vendor/plugins/maruku/Rakefile b/vendor/plugins/maruku/Rakefile
new file mode 100644
index 00000000..9389f6c2
--- /dev/null
+++ b/vendor/plugins/maruku/Rakefile
@@ -0,0 +1,73 @@
+require 'rubygems'
+Gem::manage_gems
+require 'rake/gempackagetask'
+
+#require 'maruku_gem'
+
+task :default => [:package]
+
+#Rake::GemPackageTask.new($spec) do |pkg|
+#  pkg.need_zip = true
+#  pkg.need_tar = true
+#end
+
+#PKG_NAME = 'maruku'
+#PKG_FILE_NAME = "#{PKG_NAME}-#{MaRuKu::Version}"
+#RUBY_FORGE_PROJECT = PKG_NAME
+#RUBY_FORGE_USER = 'andrea'
+
+#RELEASE_NAME  = MaRuKu::Version
+#RUBY_FORGE_GROUPID = '2795'
+#RUBY_FORGE_PACKAGEID = '3292'
+
+desc "Publish the release files to RubyForge."
+task :release => [:gem, :package] do
+	system("rubyforge login --username #{RUBY_FORGE_USER}")
+
+	gem = "pkg/#{PKG_FILE_NAME}.gem"
+	# -n notes/#{Maruku::Version}.txt
+	cmd = "rubyforge  add_release %s %s \"%s\" %s" %
+		[RUBY_FORGE_GROUPID, RUBY_FORGE_PACKAGEID, RELEASE_NAME, gem]
+	
+	puts cmd
+	system(cmd)
+	
+	files = ["gem", "tgz", "zip"].map { |ext| "pkg/#{PKG_FILE_NAME}.#{ext}" }
+	files.each do |file|
+#		system("rubyforge add_file %s %s %s %s" %
+#		[RUBY_FORGE_GROUPID, RUBY_FORGE_PACKAGEID, RELEASE_NAME, file])
+  end
+end
+
+task :test => [:markdown_span_tests, :markdown_block_tests]
+
+task :markdown_block_tests do
+	tests = Dir['tests/unittest/**/*.md'].join(' ')
+	puts "Executing tests #{tests}"
+#	ok = marutest(tests)
+	ok = system "ruby -I../syntax/lib -Ilib bin/marutest #{tests}"
+	raise "Failed block unittest" if not ok
+end
+
+task :markdown_span_tests do
+	ok = system( "ruby -Ilib  -I.. lib/maruku/tests/new_parser.rb v b")
+	raise "Failed span unittest" if not ok
+end
+
+require 'rake/rdoctask'
+
+Rake::RDocTask.new do |rdoc|
+	files = [#'README', 'LICENSE', 'COPYING', 
+		'lib/**/*.rb', 
+		'rdoc/*.rdoc'#, 'test/*.rb'
+	]
+	rdoc.rdoc_files.add(files)
+	rdoc.main = "rdoc/main.rdoc" # page to start on
+	rdoc.title = "Maruku Documentation"
+	rdoc.template = "jamis.rb"
+	rdoc.rdoc_dir = 'doc' # rdoc output folder
+	rdoc.options << '--line-numbers' << '--inline-source'
+end
+
+
+
diff --git a/vendor/plugins/maruku/bin/Markdown.pl b/vendor/plugins/maruku/bin/Markdown.pl
new file mode 100755
index 00000000..42e00550
--- /dev/null
+++ b/vendor/plugins/maruku/bin/Markdown.pl
@@ -0,0 +1,1451 @@
+#!/usr/bin/perl
+
+#
+# Markdown -- A text-to-HTML conversion tool for web writers
+#
+# Copyright (c) 2004 John Gruber
+# 
+#
+
+
+package Markdown;
+require 5.006_000;
+use strict;
+use warnings;
+
+use Digest::MD5 qw(md5_hex);
+use vars qw($VERSION);
+$VERSION = '1.0.1';
+# Tue 14 Dec 2004
+
+## Disabled; causes problems under Perl 5.6.1:
+# use utf8;
+# binmode( STDOUT, ":utf8" );  # c.f.: http://acis.openlib.org/dev/perl-unicode-struggle.html
+
+
+#
+# Global default settings:
+#
+my $g_empty_element_suffix = " />";     # Change to ">" for HTML output
+my $g_tab_width = 4;
+
+
+#
+# Globals:
+#
+
+# Regex to match balanced [brackets]. See Friedl's
+# "Mastering Regular Expressions", 2nd Ed., pp. 328-331.
+my $g_nested_brackets;
+$g_nested_brackets = qr{
+	(?> 								# Atomic matching
+	   [^\[\]]+							# Anything other than brackets
+	 | 
+	   \[
+		 (??{ $g_nested_brackets })		# Recursive set of nested brackets
+	   \]
+	)*
+}x;
+
+
+# Table of hash values for escaped characters:
+my %g_escape_table;
+foreach my $char (split //, '\\`*_{}[]()>#+-.!') {
+	$g_escape_table{$char} = md5_hex($char);
+}
+
+
+# Global hashes, used by various utility routines
+my %g_urls;
+my %g_titles;
+my %g_html_blocks;
+
+# Used to track when we're inside an ordered or unordered list
+# (see _ProcessListItems() for details):
+my $g_list_level = 0;
+
+
+#### Blosxom plug-in interface ##########################################
+
+# Set $g_blosxom_use_meta to 1 to use Blosxom's meta plug-in to determine
+# which posts Markdown should process, using a "meta-markup: markdown"
+# header. If it's set to 0 (the default), Markdown will process all
+# entries.
+my $g_blosxom_use_meta = 0;
+
+sub start { 1; }
+sub story {
+	my($pkg, $path, $filename, $story_ref, $title_ref, $body_ref) = @_;
+
+	if ( (! $g_blosxom_use_meta) or
+	     (defined($meta::markup) and ($meta::markup =~ /^\s*markdown\s*$/i))
+	     ){
+			$$body_ref  = Markdown($$body_ref);
+     }
+     1;
+}
+
+
+#### Movable Type plug-in interface #####################################
+eval {require MT};  # Test to see if we're running in MT.
+unless ($@) {
+    require MT;
+    import  MT;
+    require MT::Template::Context;
+    import  MT::Template::Context;
+
+	eval {require MT::Plugin};  # Test to see if we're running >= MT 3.0.
+	unless ($@) {
+		require MT::Plugin;
+		import  MT::Plugin;
+		my $plugin = new MT::Plugin({
+			name => "Markdown",
+			description => "A plain-text-to-HTML formatting plugin. (Version: $VERSION)",
+			doc_link => 'http://daringfireball.net/projects/markdown/'
+		});
+		MT->add_plugin( $plugin );
+	}
+
+	MT::Template::Context->add_container_tag(MarkdownOptions => sub {
+		my $ctx	 = shift;
+		my $args = shift;
+		my $builder = $ctx->stash('builder');
+		my $tokens = $ctx->stash('tokens');
+
+		if (defined ($args->{'output'}) ) {
+			$ctx->stash('markdown_output', lc $args->{'output'});
+		}
+
+		defined (my $str = $builder->build($ctx, $tokens) )
+			or return $ctx->error($builder->errstr);
+		$str;		# return value
+	});
+
+	MT->add_text_filter('markdown' => {
+		label     => 'Markdown',
+		docs      => 'http://daringfireball.net/projects/markdown/',
+		on_format => sub {
+			my $text = shift;
+			my $ctx  = shift;
+			my $raw  = 0;
+		    if (defined $ctx) {
+		    	my $output = $ctx->stash('markdown_output'); 
+				if (defined $output  &&  $output =~ m/^html/i) {
+					$g_empty_element_suffix = ">";
+					$ctx->stash('markdown_output', '');
+				}
+				elsif (defined $output  &&  $output eq 'raw') {
+					$raw = 1;
+					$ctx->stash('markdown_output', '');
+				}
+				else {
+					$raw = 0;
+					$g_empty_element_suffix = " />";
+				}
+			}
+			$text = $raw ? $text : Markdown($text);
+			$text;
+		},
+	});
+
+	# If SmartyPants is loaded, add a combo Markdown/SmartyPants text filter:
+	my $smartypants;
+
+	{
+		no warnings "once";
+		$smartypants = $MT::Template::Context::Global_filters{'smarty_pants'};
+	}
+        $smartypants = 0;
+
+	if ($smartypants) {
+		MT->add_text_filter('markdown_with_smartypants' => {
+			label     => 'Markdown With SmartyPants',
+			docs      => 'http://daringfireball.net/projects/markdown/',
+			on_format => sub {
+				my $text = shift;
+				my $ctx  = shift;
+				if (defined $ctx) {
+					my $output = $ctx->stash('markdown_output'); 
+					if (defined $output  &&  $output eq 'html') {
+						$g_empty_element_suffix = ">";
+					}
+					else {
+						$g_empty_element_suffix = " />";
+					}
+				}
+				$text = Markdown($text);
+				$text = $smartypants->($text, '1');
+			},
+		});
+	}
+}
+else {
+#### BBEdit/command-line text filter interface ##########################
+# Needs to be hidden from MT (and Blosxom when running in static mode).
+
+    # We're only using $blosxom::version once; tell Perl not to warn us:
+	no warnings 'once';
+    unless ( defined($blosxom::version) ) {
+		use warnings;
+
+		#### Check for command-line switches: #################
+		my %cli_opts;
+		use Getopt::Long;
+		Getopt::Long::Configure('pass_through');
+		GetOptions(\%cli_opts,
+			'version',
+			'shortversion',
+			'html4tags',
+		);
+		if ($cli_opts{'version'}) {		# Version info
+			print "\nThis is Markdown, version $VERSION.\n";
+			print "Copyright 2004 John Gruber\n";
+			print "http://daringfireball.net/projects/markdown/\n\n";
+			exit 0;
+		}
+		if ($cli_opts{'shortversion'}) {		# Just the version number string.
+			print $VERSION;
+			exit 0;
+		}
+		if ($cli_opts{'html4tags'}) {			# Use HTML tag style instead of XHTML
+			$g_empty_element_suffix = ">";
+		}
+
+
+		#### Process incoming text: ###########################
+		my $text;
+		{
+			local $/;               # Slurp the whole file
+			$text = <>;
+		}
+        print Markdown($text);
+    }
+}
+
+
+
+sub Markdown {
+#
+# Main function. The order in which other subs are called here is
+# essential. Link and image substitutions need to happen before
+# _EscapeSpecialChars(), so that any *'s or _'s in the 
+# and  tags get encoded.
+#
+	my $text = shift;
+
+	# Clear the global hashes. If we don't clear these, you get conflicts
+	# from other articles when generating a page which contains more than
+	# one article (e.g. an index page that shows the N most recent
+	# articles):
+	%g_urls = ();
+	%g_titles = ();
+	%g_html_blocks = ();
+
+
+	# Standardize line endings:
+	$text =~ s{\r\n}{\n}g; 	# DOS to Unix
+	$text =~ s{\r}{\n}g; 	# Mac to Unix
+
+	# Make sure $text ends with a couple of newlines:
+	$text .= "\n\n";
+
+	# Convert all tabs to spaces.
+	$text = _Detab($text);
+
+	# Strip any lines consisting only of spaces and tabs.
+	# This makes subsequent regexen easier to write, because we can
+	# match consecutive blank lines with /\n+/ instead of something
+	# contorted like /[ \t]*\n+/ .
+	$text =~ s/^[ \t]+$//mg;
+
+	# Turn block-level HTML blocks into hash entries
+	$text = _HashHTMLBlocks($text);
+
+	# Strip link definitions, store in hashes.
+	$text = _StripLinkDefinitions($text);
+
+	$text = _RunBlockGamut($text);
+
+	$text = _UnescapeSpecialChars($text);
+
+	return $text . "\n";
+}
+
+
+sub _StripLinkDefinitions {
+#
+# Strips link definitions from text, stores the URLs and titles in
+# hash references.
+#
+	my $text = shift;
+	my $less_than_tab = $g_tab_width - 1;
+
+	# Link defs are in the form: ^[id]: url "optional title"
+	while ($text =~ s{
+						^[ ]{0,$less_than_tab}\[(.+)\]:	# id = $1
+						  [ \t]*
+						  \n?				# maybe *one* newline
+						  [ \t]*
+						?			# url = $2
+						  [ \t]*
+						  \n?				# maybe one newline
+						  [ \t]*
+						(?:
+							(?<=\s)			# lookbehind for whitespace
+							["(]
+							(.+?)			# title = $3
+							[")]
+							[ \t]*
+						)?	# title is optional
+						(?:\n+|\Z)
+					}
+					{}mx) {
+		$g_urls{lc $1} = _EncodeAmpsAndAngles( $2 );	# Link IDs are case-insensitive
+		if ($3) {
+			$g_titles{lc $1} = $3;
+			$g_titles{lc $1} =~ s/"/"/g;
+		}
+	}
+
+	return $text;
+}
+
+
+sub _HashHTMLBlocks {
+	my $text = shift;
+	my $less_than_tab = $g_tab_width - 1;
+
+	# Hashify HTML blocks:
+	# We only want to do this for block-level HTML tags, such as headers,
+	# lists, and tables. That's because we still want to wrap 
s around
+	# "paragraphs" that are wrapped in non-block-level tags, such as anchors,
+	# phrase emphasis, and spans. The list of tags we're looking for is
+	# hard-coded:
+	my $block_tags_a = qr/p|div|h[1-6]|blockquote|pre|table|dl|ol|ul|script|noscript|form|fieldset|iframe|math|ins|del/;
+	my $block_tags_b = qr/p|div|h[1-6]|blockquote|pre|table|dl|ol|ul|script|noscript|form|fieldset|iframe|math/;
+
+	# First, look for nested blocks, e.g.:
+	# 	

+	# 		

+	# 		tags for inner block must be indented.
+	# 		

+	# 	

+	#
+	# The outermost tags must start at the left margin for this to match, and
+	# the inner nested divs must be indented.
+	# We need to do this before the next, more liberal match, because the next
+	# match will start at the first `
` and stop at the first `
`.
+	$text =~ s{
+				(						# save in $1
+					^					# start of line  (with /m)
+					<($block_tags_a)	# start tag = $2
+					\b					# word break
+					(.*\n)*?			# any number of lines, minimally matching
+									# the matching end tag
+					[ \t]*				# trailing spaces/tabs
+					(?=\n+|\Z)	# followed by a newline or end of document
+				)
+			}{
+				my $key = md5_hex($1);
+				$g_html_blocks{$key} = $1;
+				"\n\n" . $key . "\n\n";
+			}egmx;
+
+
+	#
+	# Now match more liberally, simply from `\n` to `\n`
+	#
+	$text =~ s{
+				(						# save in $1
+					^					# start of line  (with /m)
+					<($block_tags_b)	# start tag = $2
+					\b					# word break
+					(.*\n)*?			# any number of lines, minimally matching
+					.*				# the matching end tag
+					[ \t]*				# trailing spaces/tabs
+					(?=\n+|\Z)	# followed by a newline or end of document
+				)
+			}{
+				my $key = md5_hex($1);
+				$g_html_blocks{$key} = $1;
+				"\n\n" . $key . "\n\n";
+			}egmx;
+	# Special case just for 
. It was easier to make a special case than
+	# to make the other regex more complicated.	
+	$text =~ s{
+				(?:
+					(?<=\n\n)		# Starting after a blank line
+					|				# or
+					\A\n?			# the beginning of the doc
+				)
+				(						# save in $1
+					[ ]{0,$less_than_tab}
+					<(hr)				# start tag = $2
+					\b					# word break
+					([^<>])*?			# 
+					/?>					# the matching end tag
+					[ \t]*
+					(?=\n{2,}|\Z)		# followed by a blank line or end of document
+				)
+			}{
+				my $key = md5_hex($1);
+				$g_html_blocks{$key} = $1;
+				"\n\n" . $key . "\n\n";
+			}egx;
+
+	# Special case for standalone HTML comments:
+	$text =~ s{
+				(?:
+					(?<=\n\n)		# Starting after a blank line
+					|				# or
+					\A\n?			# the beginning of the doc
+				)
+				(						# save in $1
+					[ ]{0,$less_than_tab}
+					(?s:
+						
+					)
+					[ \t]*
+					(?=\n{2,}|\Z)		# followed by a blank line or end of document
+				)
+			}{
+				my $key = md5_hex($1);
+				$g_html_blocks{$key} = $1;
+				"\n\n" . $key . "\n\n";
+			}egx;
+
+
+	return $text;
+}
+
+
+sub _RunBlockGamut {
+#
+# These are all the transformations that form block-level
+# tags like paragraphs, headers, and list items.
+#
+	my $text = shift;
+
+	$text = _DoHeaders($text);
+
+	# Do Horizontal Rules:
+	$text =~ s{^[ ]{0,2}([ ]?\*[ ]?){3,}[ \t]*$}{\n tags around block-level tags.
+	$text = _HashHTMLBlocks($text);
+
+	$text = _FormParagraphs($text);
+
+	return $text;
+}
+
+
+sub _RunSpanGamut {
+#
+# These are all the transformations that occur *within* block-level
+# tags like paragraphs, headers, and list items.
+#
+	my $text = shift;
+
+	$text = _DoCodeSpans($text);
+
+	$text = _EscapeSpecialChars($text);
+
+	# Process anchor and image tags. Images must come first,
+	# because ![foo][f] looks like an anchor.
+	$text = _DoImages($text);
+	$text = _DoAnchors($text);
+
+	# Make links out of things like ``
+	# Must come after _DoAnchors(), because you can use < and >
+	# delimiters in inline links like [this]().
+	$text = _DoAutoLinks($text);
+
+	$text = _EncodeAmpsAndAngles($text);
+
+	$text = _DoItalicsAndBold($text);
+
+	# Do hard breaks:
+	$text =~ s/ {2,}\n/  or  tags.
+# 	my $tags_to_skip = qr!<(/?)(?:pre|code|kbd|script|math)[\s>]!;
+
+	foreach my $cur_token (@$tokens) {
+		if ($cur_token->[0] eq "tag") {
+			# Within tags, encode * and _ so they don't conflict
+			# with their use in Markdown for italics and strong.
+			# We're replacing each such character with its
+			# corresponding MD5 checksum value; this is likely
+			# overkill, but it should prevent us from colliding
+			# with the escape values by accident.
+			$cur_token->[1] =~  s! \* !$g_escape_table{'*'}!gx;
+			$cur_token->[1] =~  s! _  !$g_escape_table{'_'}!gx;
+			$text .= $cur_token->[1];
+		} else {
+			my $t = $cur_token->[1];
+			$t = _EncodeBackslashEscapes($t);
+			$text .= $t;
+		}
+	}
+	return $text;
+}
+
+
+sub _DoAnchors {
+#
+# Turn Markdown link shortcuts into XHTML  tags.
+#
+	my $text = shift;
+
+	#
+	# First, handle reference-style links: [link text] [id]
+	#
+	$text =~ s{
+		(					# wrap whole match in $1
+		  \[
+		    ($g_nested_brackets)	# link text = $2
+		  \]
+
+		  [ ]?				# one optional space
+		  (?:\n[ ]*)?		# one optional newline followed by spaces
+
+		  \[
+		    (.*?)		# id = $3
+		  \]
+		)
+	}{
+		my $result;
+		my $whole_match = $1;
+		my $link_text   = $2;
+		my $link_id     = lc $3;
+
+		if ($link_id eq "") {
+			$link_id = lc $link_text;     # for shortcut links like [this][].
+		}
+
+		if (defined $g_urls{$link_id}) {
+			my $url = $g_urls{$link_id};
+			$url =~ s! \* !$g_escape_table{'*'}!gx;		# We've got to encode these to avoid
+			$url =~ s!  _ !$g_escape_table{'_'}!gx;		# conflicting with italics/bold.
+			$result = "?	# href = $3
+		  	[ \t]*
+			(			# $4
+			  (['"])	# quote char = $5
+			  (.*?)		# Title = $6
+			  \5		# matching quote
+			)?			# title is optional
+		  \)
+		)
+	}{
+		my $result;
+		my $whole_match = $1;
+		my $link_text   = $2;
+		my $url	  		= $3;
+		my $title		= $6;
+
+		$url =~ s! \* !$g_escape_table{'*'}!gx;		# We've got to encode these to avoid
+		$url =~ s!  _ !$g_escape_table{'_'}!gx;		# conflicting with italics/bold.
+		$result = " tags.
+#
+	my $text = shift;
+
+	#
+	# First, handle reference-style labeled images: ![alt text][id]
+	#
+	$text =~ s{
+		(				# wrap whole match in $1
+		  !\[
+		    (.*?)		# alt text = $2
+		  \]
+
+		  [ ]?				# one optional space
+		  (?:\n[ ]*)?		# one optional newline followed by spaces
+
+		  \[
+		    (.*?)		# id = $3
+		  \]
+
+		)
+	}{
+		my $result;
+		my $whole_match = $1;
+		my $alt_text    = $2;
+		my $link_id     = lc $3;
+
+		if ($link_id eq "") {
+			$link_id = lc $alt_text;     # for shortcut links like ![this][].
+		}
+
+		$alt_text =~ s/"/"/g;
+		if (defined $g_urls{$link_id}) {
+			my $url = $g_urls{$link_id};
+			$url =~ s! \* !$g_escape_table{'*'}!gx;		# We've got to encode these to avoid
+			$url =~ s!  _ !$g_escape_table{'_'}!gx;		# conflicting with italics/bold.
+			$result = "\"$alt_text\"";?	# src url = $3
+		  	[ \t]*
+			(			# $4
+			  (['"])	# quote char = $5
+			  (.*?)		# title = $6
+			  \5		# matching quote
+			  [ \t]*
+			)?			# title is optional
+		  \)
+		)
+	}{
+		my $result;
+		my $whole_match = $1;
+		my $alt_text    = $2;
+		my $url	  		= $3;
+		my $title		= '';
+		if (defined($6)) {
+			$title		= $6;
+		}
+
+		$alt_text =~ s/"/"/g;
+		$title    =~ s/"/"/g;
+		$url =~ s! \* !$g_escape_table{'*'}!gx;		# We've got to encode these to avoid
+		$url =~ s!  _ !$g_escape_table{'_'}!gx;		# conflicting with italics/bold.
+		$result = "\"$alt_text\"";"  .  _RunSpanGamut($1)  .  "\n\n";
+	}egmx;
+
+	$text =~ s{ ^(.+)[ \t]*\n-+[ \t]*\n+ }{
+		"
"  .  _RunSpanGamut($1)  .  "
\n\n";
+	}egmx;
+
+
+	# atx-style headers:
+	#	# Header 1
+	#	## Header 2
+	#	## Header 2 with closing hashes ##
+	#	...
+	#	###### Header 6
+	#
+	$text =~ s{
+			^(\#{1,6})	# $1 = string of #'s
+			[ \t]*
+			(.+?)		# $2 = Header text
+			[ \t]*
+			\#*			# optional closing #'s (not counted)
+			\n+
+		}{
+			my $h_level = length($1);
+			""  .  _RunSpanGamut($2)  .  "\n\n";
+		}egmx;
+
+	return $text;
+}
+
+
+sub _DoLists {
+#
+# Form HTML ordered (numbered) and unordered (bulleted) lists.
+#
+	my $text = shift;
+	my $less_than_tab = $g_tab_width - 1;
+
+	# Re-usable patterns to match list item bullets and number markers:
+	my $marker_ul  = qr/[*+-]/;
+	my $marker_ol  = qr/\d+[.]/;
+	my $marker_any = qr/(?:$marker_ul|$marker_ol)/;
+
+	# Re-usable pattern to match any entirel ul or ol list:
+	my $whole_list = qr{
+		(								# $1 = whole list
+		  (								# $2
+			[ ]{0,$less_than_tab}
+			(${marker_any})				# $3 = first list item marker
+			[ \t]+
+		  )
+		  (?s:.+?)
+		  (								# $4
+			  \z
+			|
+			  \n{2,}
+			  (?=\S)
+			  (?!						# Negative lookahead for another list item marker
+				[ \t]*
+				${marker_any}[ \t]+
+			  )
+		  )
+		)
+	}mx;
+
+	# We use a different prefix before nested lists than top-level lists.
+	# See extended comment in _ProcessListItems().
+	#
+	# Note: There's a bit of duplication here. My original implementation
+	# created a scalar regex pattern as the conditional result of the test on
+	# $g_list_level, and then only ran the $text =~ s{...}{...}egmx
+	# substitution once, using the scalar as the pattern. This worked,
+	# everywhere except when running under MT on my hosting account at Pair
+	# Networks. There, this caused all rebuilds to be killed by the reaper (or
+	# perhaps they crashed, but that seems incredibly unlikely given that the
+	# same script on the same server ran fine *except* under MT. I've spent
+	# more time trying to figure out why this is happening than I'd like to
+	# admit. My only guess, backed up by the fact that this workaround works,
+	# is that Perl optimizes the substition when it can figure out that the
+	# pattern will never change, and when this optimization isn't on, we run
+	# afoul of the reaper. Thus, the slightly redundant code to that uses two
+	# static s/// patterns rather than one conditional pattern.
+
+	if ($g_list_level) {
+		$text =~ s{
+				^
+				$whole_list
+			}{
+				my $list = $1;
+				my $list_type = ($3 =~ m/$marker_ul/) ? "ul" : "ol";
+				# Turn double returns into triple returns, so that we can make a
+				# paragraph for the last item in a list, if necessary:
+				$list =~ s/\n{2,}/\n\n\n/g;
+				my $result = _ProcessListItems($list, $marker_any);
+				$result = "<$list_type>\n" . $result . "\n";
+				$result;
+			}egmx;
+	}
+	else {
+		$text =~ s{
+				(?:(?<=\n\n)|\A\n?)
+				$whole_list
+			}{
+				my $list = $1;
+				my $list_type = ($3 =~ m/$marker_ul/) ? "ul" : "ol";
+				# Turn double returns into triple returns, so that we can make a
+				# paragraph for the last item in a list, if necessary:
+				$list =~ s/\n{2,}/\n\n\n/g;
+				my $result = _ProcessListItems($list, $marker_any);
+				$result = "<$list_type>\n" . $result . "\n";
+				$result;
+			}egmx;
+	}
+
+
+	return $text;
+}
+
+
+sub _ProcessListItems {
+#
+#	Process the contents of a single ordered or unordered list, splitting it
+#	into individual list items.
+#
+
+	my $list_str = shift;
+	my $marker_any = shift;
+
+
+	# The $g_list_level global keeps track of when we're inside a list.
+	# Each time we enter a list, we increment it; when we leave a list,
+	# we decrement. If it's zero, we're not in a list anymore.
+	#
+	# We do this because when we're not inside a list, we want to treat
+	# something like this:
+	#
+	#		I recommend upgrading to version
+	#		8. Oops, now this line is treated
+	#		as a sub-list.
+	#
+	# As a single paragraph, despite the fact that the second line starts
+	# with a digit-period-space sequence.
+	#
+	# Whereas when we're inside a list (or sub-list), that line will be
+	# treated as the start of a sub-list. What a kludge, huh? This is
+	# an aspect of Markdown's syntax that's hard to parse perfectly
+	# without resorting to mind-reading. Perhaps the solution is to
+	# change the syntax rules such that sub-lists must start with a
+	# starting cardinal number; e.g. "1." or "a.".
+
+	$g_list_level++;
+
+	# trim trailing blank lines:
+	$list_str =~ s/\n{2,}\z/\n/;
+
+
+	$list_str =~ s{
+		(\n)?							# leading line = $1
+		(^[ \t]*)						# leading whitespace = $2
+		($marker_any) [ \t]+			# list marker = $3
+		((?s:.+?)						# list item text   = $4
+		(\n{1,2}))
+		(?= \n* (\z | \2 ($marker_any) [ \t]+))
+	}{
+		my $item = $4;
+		my $leading_line = $1;
+		my $leading_space = $2;
+
+		if ($leading_line or ($item =~ m/\n{2,}/)) {
+			$item = _RunBlockGamut(_Outdent($item));
+		}
+		else {
+			# Recursion for sub-lists:
+			$item = _DoLists(_Outdent($item));
+			chomp $item;
+			$item = _RunSpanGamut($item);
+		}
+
+		"
  • " . $item . "
    • \n";
+	}egmx;
+
+	$g_list_level--;
+	return $list_str;
+}
+
+
+
+sub _DoCodeBlocks {
+#
+#	Process Markdown `
    ` blocks.
+#	
+
+	my $text = shift;
+
+	$text =~ s{
+			(?:\n\n|\A)
+			(	            # $1 = the code block -- one or more lines, starting with a space/tab
+			  (?:
+			    (?:[ ]{$g_tab_width} | \t)  # Lines must start with a tab or a tab-width of spaces
+			    .*\n+
+			  )+
+			)
+			((?=^[ ]{0,$g_tab_width}\S)|\Z)	# Lookahead for non-space at line-start, or end of doc
+		}{
+			my $codeblock = $1;
+			my $result; # return value
+
+			$codeblock = _EncodeCode(_Outdent($codeblock));
+			$codeblock = _Detab($codeblock);
+			$codeblock =~ s/\A\n+//; # trim leading newlines
+			$codeblock =~ s/\s+\z//; # trim trailing whitespace
+
+			$result = "\n\n
    " . $codeblock . "\n
    \n\n";
+
+			$result;
+		}egmx;
+
+	return $text;
+}
+
+
+sub _DoCodeSpans {
+#
+# 	*	Backtick quotes are used for  spans.
+# 
+# 	*	You can use multiple backticks as the delimiters if you want to
+# 		include literal backticks in the code span. So, this input:
+#     
+#         Just type ``foo `bar` baz`` at the prompt.
+#     
+#     	Will translate to:
+#     
+#         
    Just type foo `bar` baz at the prompt.
    
+#     
+#		There's no arbitrary limit to the number of backticks you
+#		can use as delimters. If you need three consecutive backticks
+#		in your code, use four for delimiters, etc.
+#
+#	*	You can use spaces to get literal backticks at the edges:
+#     
+#         ... type `` `bar` `` ...
+#     
+#     	Turns to:
+#     
+#         ... type `bar` ...
+#
+
+	my $text = shift;
+
+	$text =~ s@
+			(`+)		# $1 = Opening run of `
+			(.+?)		# $2 = The code block
+			(?$c    ";
+		@egsx;
+
+	return $text;
+}
+
+
+sub _EncodeCode {
+#
+# Encode/escape certain characters inside Markdown code runs.
+# The point is that in code, these characters are literals,
+# and lose their special Markdown meanings.
+#
+    local $_ = shift;
+
+	# Encode all ampersands; HTML entities are not
+	# entities within a Markdown code span.
+	s/&/&/g;
+
+	# Encode $'s, but only if we're running under Blosxom.
+	# (Blosxom interpolates Perl variables in article bodies.)
+	{
+		no warnings 'once';
+    	if (defined($blosxom::version)) {
+    		s/\$/$/g;	
+    	}
+    }
+
+
+	# Do the angle bracket song and dance:
+	s! <  !<!gx;
+	s! >  !>!gx;
+
+	# Now, escape characters that are magic in Markdown:
+	s! \* !$g_escape_table{'*'}!gx;
+	s! _  !$g_escape_table{'_'}!gx;
+	s! {  !$g_escape_table{'{'}!gx;
+	s! }  !$g_escape_table{'}'}!gx;
+	s! \[ !$g_escape_table{'['}!gx;
+	s! \] !$g_escape_table{']'}!gx;
+	s! \\ !$g_escape_table{'\\'}!gx;
+
+	return $_;
+}
+
+
+sub _DoItalicsAndBold {
+	my $text = shift;
+
+	#  must go first:
+	$text =~ s{ (\*\*|__) (?=\S) (.+?[*_]*) (?<=\S) \1 }
+		{$2}gsx;
+
+	$text =~ s{ (\*|_) (?=\S) (.+?) (?<=\S) \1 }
+		{$2}gsx;
+
+	return $text;
+}
+
+
+sub _DoBlockQuotes {
+	my $text = shift;
+
+	$text =~ s{
+		  (								# Wrap whole match in $1
+			(
+			  ^[ \t]*>[ \t]?			# '>' at the start of a line
+			    .+\n					# rest of the first line
+			  (.+\n)*					# subsequent consecutive lines
+			  \n*						# blanks
+			)+
+		  )
+		}{
+			my $bq = $1;
+			$bq =~ s/^[ \t]*>[ \t]?//gm;	# trim one level of quoting
+			$bq =~ s/^[ \t]+$//mg;			# trim whitespace-only lines
+			$bq = _RunBlockGamut($bq);		# recurse
+
+			$bq =~ s/^/  /g;
+			# These leading spaces screw with 
     content, so we need to fix that:
+			$bq =~ s{
+					(\s*
    .+?
    )
+				}{
+					my $pre = $1;
+					$pre =~ s/^  //mg;
+					$pre;
+				}egsx;
+
+			"
    \n$bq\n
    \n\n";
+		}egmx;
+
+
+	return $text;
+}
+
+
+sub _FormParagraphs {
+#
+#	Params:
+#		$text - string to process with html 
     tags
+#
+	my $text = shift;
+
+	# Strip leading and trailing lines:
+	$text =~ s/\A\n+//;
+	$text =~ s/\n+\z//;
+
+	my @grafs = split(/\n{2,}/, $text);
+
+	#
+	# Wrap 
     tags.
+	#
+	foreach (@grafs) {
+		unless (defined( $g_html_blocks{$_} )) {
+			$_ = _RunSpanGamut($_);
+			s/^([ \t]*)/
    /;
+			$_ .= "
    ";
+		}
+	}
+
+	#
+	# Unhashify HTML blocks
+	#
+	foreach (@grafs) {
+		if (defined( $g_html_blocks{$_} )) {
+			$_ = $g_html_blocks{$_};
+		}
+	}
+
+	return join "\n\n", @grafs;
+}
+
+
+sub _EncodeAmpsAndAngles {
+# Smart processing for ampersands and angle brackets that need to be encoded.
+
+	my $text = shift;
+
+	# Ampersand-encoding based entirely on Nat Irons's Amputator MT plugin:
+	#   http://bumppo.net/projects/amputator/
+ 	$text =~ s/&(?!#?[xX]?(?:[0-9a-fA-F]+|\w+);)/&/g;
+
+	# Encode naked <'s
+ 	$text =~ s{<(?![a-z/?\$!])}{<}gi;
+
+	return $text;
+}
+
+
+sub _EncodeBackslashEscapes {
+#
+#   Parameter:  String.
+#   Returns:    The string, with after processing the following backslash
+#               escape sequences.
+#
+    local $_ = shift;
+
+    s! \\\\  !$g_escape_table{'\\'}!gx;		# Must process escaped backslashes first.
+    s! \\`   !$g_escape_table{'`'}!gx;
+    s! \\\*  !$g_escape_table{'*'}!gx;
+    s! \\_   !$g_escape_table{'_'}!gx;
+    s! \\\{  !$g_escape_table{'{'}!gx;
+    s! \\\}  !$g_escape_table{'}'}!gx;
+    s! \\\[  !$g_escape_table{'['}!gx;
+    s! \\\]  !$g_escape_table{']'}!gx;
+    s! \\\(  !$g_escape_table{'('}!gx;
+    s! \\\)  !$g_escape_table{')'}!gx;
+    s! \\>   !$g_escape_table{'>'}!gx;
+    s! \\\#  !$g_escape_table{'#'}!gx;
+    s! \\\+  !$g_escape_table{'+'}!gx;
+    s! \\\-  !$g_escape_table{'-'}!gx;
+    s! \\\.  !$g_escape_table{'.'}!gx;
+    s{ \\!  }{$g_escape_table{'!'}}gx;
+
+    return $_;
+}
+
+
+sub _DoAutoLinks {
+	my $text = shift;
+
+	$text =~ s{<((https?|ftp):[^'">\s]+)>}{    $1}gi;
+
+	# Email addresses: 
+	$text =~ s{
+		<
+        (?:mailto:)?
+		(
+			[-.\w]+
+			\@
+			[-a-z0-9]+(\.[-a-z0-9]+)*\.[a-z]+
+		)
+		>
+	}{
+		_EncodeEmailAddress( _UnescapeSpecialChars($1) );
+	}egix;
+
+	return $text;
+}
+
+
+sub _EncodeEmailAddress {
+#
+#	Input: an email address, e.g. "foo@example.com"
+#
+#	Output: the email address as a mailto link, with each character
+#		of the address encoded as either a decimal or hex entity, in
+#		the hopes of foiling most address harvesting spam bots. E.g.:
+#
+#	  foo
+#       @example.com
+#
+#	Based on a filter by Matthew Wickline, posted to the BBEdit-Talk
+#	mailing list: 
+#
+
+	my $addr = shift;
+
+	srand;
+	my @encode = (
+		sub { '&#' .                 ord(shift)   . ';' },
+		sub { '&#x' . sprintf( "%X", ord(shift) ) . ';' },
+		sub {                            shift          },
+	);
+
+	$addr = "mailto:" . $addr;
+
+	$addr =~ s{(.)}{
+		my $char = $1;
+		if ( $char eq '@' ) {
+			# this *must* be encoded. I insist.
+			$char = $encode[int rand 1]->($char);
+		} elsif ( $char ne ':' ) {
+			# leave ':' alone (to spot mailto: later)
+			my $r = rand;
+			# roughly 10% raw, 45% hex, 45% dec
+			$char = (
+				$r > .9   ?  $encode[2]->($char)  :
+				$r < .45  ?  $encode[1]->($char)  :
+							 $encode[0]->($char)
+			);
+		}
+		$char;
+	}gex;
+
+	$addr = qq{$addr};
+	$addr =~ s{">.+?:}{">}; # strip the mailto: from the visible part
+
+	return $addr;
+}
+
+
+sub _UnescapeSpecialChars {
+#
+# Swap back in all the special characters we've hidden.
+#
+	my $text = shift;
+
+	while( my($char, $hash) = each(%g_escape_table) ) {
+		$text =~ s/$hash/$char/g;
+	}
+    return $text;
+}
+
+
+sub _TokenizeHTML {
+#
+#   Parameter:  String containing HTML markup.
+#   Returns:    Reference to an array of the tokens comprising the input
+#               string. Each token is either a tag (possibly with nested,
+#               tags contained therein, such as , or a
+#               run of text between tags. Each element of the array is a
+#               two-element array; the first is either 'tag' or 'text';
+#               the second is the actual value.
+#
+#
+#   Derived from the _tokenize() subroutine from Brad Choate's MTRegex plugin.
+#       
+#
+
+    my $str = shift;
+    my $pos = 0;
+    my $len = length $str;
+    my @tokens;
+
+    my $depth = 6;
+    my $nested_tags = join('|', ('(?:<[a-z/!$](?:[^<>]') x $depth) . (')*>)' x  $depth);
+    my $match = qr/(?s:  ) |  # comment
+                   (?s: <\? .*? \?> ) |              # processing instruction
+                   $nested_tags/ix;                   # nested tags
+
+    while ($str =~ m/($match)/g) {
+        my $whole_tag = $1;
+        my $sec_start = pos $str;
+        my $tag_start = $sec_start - length $whole_tag;
+        if ($pos < $tag_start) {
+            push @tokens, ['text', substr($str, $pos, $tag_start - $pos)];
+        }
+        push @tokens, ['tag', $whole_tag];
+        $pos = pos $str;
+    }
+    push @tokens, ['text', substr($str, $pos, $len - $pos)] if $pos < $len;
+    \@tokens;
+}
+
+
+sub _Outdent {
+#
+# Remove one level of line-leading tabs or spaces
+#
+	my $text = shift;
+
+	$text =~ s/^(\t|[ ]{1,$g_tab_width})//gm;
+	return $text;
+}
+
+
+sub _Detab {
+#
+# Cribbed from a post by Bart Lateur:
+# 
+#
+	my $text = shift;
+
+	$text =~ s{(.*?)\t}{$1.(' ' x ($g_tab_width - length($1) % $g_tab_width))}ge;
+	return $text;
+}
+
+
+1;
+
+__END__
+
+
+=pod
+
+=head1 NAME
+
+B
+
+
+=head1 SYNOPSIS
+
+B [ B<--html4tags> ] [ B<--version> ] [ B<-shortversion> ]
+    [ I ... ]
+
+
+=head1 DESCRIPTION
+
+Markdown is a text-to-HTML filter; it translates an easy-to-read /
+easy-to-write structured text format into HTML. Markdown's text format
+is most similar to that of plain text email, and supports features such
+as headers, *emphasis*, code blocks, blockquotes, and links.
+
+Markdown's syntax is designed not as a generic markup language, but
+specifically to serve as a front-end to (X)HTML. You can  use span-level
+HTML tags anywhere in a Markdown document, and you can use block level
+HTML tags (like 
     and  as well).
+
+For more information about Markdown's syntax, see:
+
+    http://daringfireball.net/projects/markdown/
+
+
+=head1 OPTIONS
+
+Use "--" to end switch parsing. For example, to open a file named "-z", use:
+
+	Markdown.pl -- -z
+
+=over 4
+
+
+=item B<--html4tags>
+
+Use HTML 4 style for empty element tags, e.g.:
+
+    
    
+
+instead of Markdown's default XHTML style tags, e.g.:
+
+    
    
+
+
+=item B<-v>, B<--version>
+
+Display Markdown's version number and copyright information.
+
+
+=item B<-s>, B<--shortversion>
+
+Display the short-form version number.
+
+
+=back
+
+
+
+=head1 BUGS
+
+To file bug reports or feature requests (other than topics listed in the
+Caveats section above) please send email to:
+
+    support@daringfireball.net
+
+Please include with your report: (1) the example input; (2) the output
+you expected; (3) the output Markdown actually produced.
+
+
+=head1 VERSION HISTORY
+
+See the readme file for detailed release notes for this version.
+
+1.0.1 - 14 Dec 2004
+
+1.0 - 28 Aug 2004
+
+
+=head1 AUTHOR
+
+    John Gruber
+    http://daringfireball.net
+
+    PHP port and other contributions by Michel Fortin
+    http://michelf.com
+
+
+=head1 COPYRIGHT AND LICENSE
+
+Copyright (c) 2003-2004 John Gruber   
+   
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are
+met:
+
+* Redistributions of source code must retain the above copyright notice,
+  this list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright
+  notice, this list of conditions and the following disclaimer in the
+  documentation and/or other materials provided with the distribution.
+
+* Neither the name "Markdown" nor the names of its contributors may
+  be used to endorse or promote products derived from this software
+  without specific prior written permission.
+
+This software is provided by the copyright holders and contributors "as
+is" and any express or implied warranties, including, but not limited
+to, the implied warranties of merchantability and fitness for a
+particular purpose are disclaimed. In no event shall the copyright owner
+or contributors be liable for any direct, indirect, incidental, special,
+exemplary, or consequential damages (including, but not limited to,
+procurement of substitute goods or services; loss of use, data, or
+profits; or business interruption) however caused and on any theory of
+liability, whether in contract, strict liability, or tort (including
+negligence or otherwise) arising in any way out of the use of this
+software, even if advised of the possibility of such damage.
+
+=cut
diff --git a/vendor/plugins/maruku/bin/maruku b/vendor/plugins/maruku/bin/maruku
new file mode 100644
index 00000000..60d33d8a
--- /dev/null
+++ b/vendor/plugins/maruku/bin/maruku
@@ -0,0 +1,168 @@
+#!/usr/bin/env ruby
+
+require 'maruku'
+require 'optparse'
+
+export = :html
+break_on_error = false
+using_math = false
+using_mathml = false
+output_file = nil
+
+opt = OptionParser.new do |opts|
+	opts.banner = "Usage: maruku [options] [file1.md [file2.md ..."
+
+	opts.on("-v", "--[no-]verbose", "Run verbosely") do |v|
+		MaRuKu::Globals[:verbose] = v end
+	opts.on("-u", "--[no-]unsafe", "Use unsafe features") do |v|
+		MaRuKu::Globals[:unsafe_features] = v end
+
+	opts.on("-b", "Break on error") do |v|
+		break_on_error = true end
+
+
+	opts.on("-i", "--math-images ENGINE", "Uses ENGINE to render TeX to PNG.") do |s|
+		using_math = true
+		MaRuKu::Globals[:html_math_output_png] = true
+		MaRuKu::Globals[:html_math_output_mathml] = false
+		MaRuKu::Globals[:html_png_engine] = s
+		$stderr.puts "Using png engine #{s}."
+	end
+
+	opts.on("-m", "--math-engine ENGINE", "Uses ENGINE to render MathML") do |s|
+		MaRuKu::Globals[:html_math_output_png] = false
+		MaRuKu::Globals[:html_math_output_mathml] = true
+		using_math = true
+		using_mathml = true
+		MaRuKu::Globals[:html_math_engine] = s
+	end
+
+	opts.on("-o", "--output FILE", "Output filename") do |s|
+		output_file = s
+	end
+
+	opts.on_tail("--pdf",  "Write PDF","First writes LaTeX, then calls pdflatex." ) do export = :pdf  end
+	opts.on_tail("--s5", "Write S5 slideshow") do export = :s5 end
+	opts.on_tail("--html", "Write HTML") do export = :html end
+	opts.on_tail("--html-frag", "Write the contents of the BODY.") do export = :html_frag end
+	opts.on_tail("--tex",  "Write LaTeX" ) do export = :tex  end
+	opts.on_tail("--inspect",  "Shows the parsing result" ) do export = :inspect  end
+
+	opts.on_tail("--version", "Show version") do
+		puts OptionParser::Version.join('.')
+		exit
+	end
+
+	opts.on_tail("-h", "--help", "Show this message") do
+		puts opts
+		exit
+	end
+
+end
+
+begin 
+opt.parse!
+rescue OptionParser::InvalidOption=>e
+	$stderr.puts e
+	$stderr.puts opt
+	exit
+end
+
+if using_math
+	$stderr.puts "Using Math extensions."
+	require 'maruku/ext/math'
+end
+
+#p ARGV
+#p MaRuKu::Globals
+
+inputs =
+# If we are given filenames, convert each file 
+if not ARGV.empty?
+	ARGV.map do |f|
+		# read file content
+		$stderr.puts "Reading from #{f}."
+		[f, File.open(f,'r').read]
+	end
+else
+	export = :html_frag if export == :html
+	export = :tex_frag if export == :tex
+	
+	$stderr.puts "Reading from standard input."
+	[[nil, $stdin.read]]
+end
+
+inputs.each do |f, input|
+	
+		# create Maruku
+		params = {}
+		params[:on_error] = break_on_error ? :raise : :warning
+
+		t = Time.now
+		doc = Maruku.new(input, params)
+		$stderr.puts "Parsing in %.2f seconds." % (Time.now-t)
+
+		out=""; suffix = "?"
+		t = Time.now
+		case export
+		when :html 
+			suffix = using_mathml ? '.xhtml' : '.html'
+			out = doc.to_html_document( {:indent => -1})
+		when :html_frag 
+			suffix='.html_frag'
+			out = doc.to_html( {:indent => -1})
+		when :pdf, :tex
+			suffix='.tex'
+			out = doc.to_latex_document
+		when :tex_frag
+			suffix='.tex_frag'
+			out = doc.to_latex
+		when :inspect
+			suffix='.txt'
+			out = doc.inspect
+		when :markdown
+			suffix='.pretty_md'
+			out = doc.to_markdown
+		when :s5
+			suffix='_s5slides.xhtml'
+			out = doc.to_s5({:content_only => false})
+		end
+		$stderr.puts "Rendering in %.2f seconds." % (Time.now-t)
+			
+		# write to file or stdout
+		if f
+			
+			if not output_file 
+				dir = File.dirname(f)
+				job = File.join(dir, File.basename(f, File.extname(f)))
+				output_file = job  + suffix
+			else
+				job = File.basename(output_file, File.extname(output_file))
+			end
+			
+			if output_file == "-"
+				$stderr.puts "Writing to standard output"
+				$stdout.puts out
+			else
+			
+				if not (export == :pdf)
+					$stderr.puts "Writing to #{output_file}"
+					File.open(output_file,'w') do |f| f.puts out end
+				else
+					$stderr.puts "Writing to #{job}.tex"
+					File.open("#{job}.tex",'w') do |f| f.puts out end
+					cmd = "pdflatex '#{job}.tex' -interaction=nonstopmode "+
+					      "'-output-directory=#{dir}' "
+					$stderr.puts "maruku: executing $ #{cmd}"
+					# run twice for cross references
+					system cmd 
+					system cmd
+				end
+			
+			end
+		else # write to stdout
+			$stderr.puts "Writing to standard output"
+			$stdout.puts out
+		end
+	end
+	
diff --git a/vendor/plugins/maruku/bin/marutest b/vendor/plugins/maruku/bin/marutest
new file mode 100644
index 00000000..68e5de69
--- /dev/null
+++ b/vendor/plugins/maruku/bin/marutest
@@ -0,0 +1,339 @@
+#!/usr/bin/env ruby
+
+require 'maruku'
+#require 'maruku/textile2'
+require 'maruku/input_textile2/t2_parser'
+
+$marutest_language = :markdown
+
+#MARKER = "\n***EOF***\n"
+SPLIT = %r{\n\*\*\*[^\*]+\*\*\*\n}m
+
+def marker(x)
+	"\n*** Output of #{x} ***\n"
+end
+
+def write_lines(i, j, lines, prefix, i_star)
+	i = [i, 0].max
+	j = [j, lines.size-1].min
+	for a in i..j
+		l = lines[a].gsub(/\t/,'  ')
+		puts( ("%s %3d" % [prefix, a]) + 
+			(a==i_star ? " -->" : "    ")+lines[a])
+	end
+end
+
+# a = expected   b = found 
+def equals(a, b)
+	a = a.split("\n")
+	b = b.split("\n")
+	
+	for i in 0..([a.size-1,b.size-1].max)
+		la = a[i]
+		lb = b[i]
+		if la != lb
+			puts "\n"
+			
+			
+			write_lines(i-3, i+3, a, "expected", i )
+			write_lines(i-3, i+3, b, "   found", i )
+			return false
+		end
+	end
+	return true
+end
+
+TOTEST = [:inspect,:to_html,:to_latex,:to_md,:to_s]
+
+def run_test(filename, its_ok, verbose=true)
+	# read file content
+	input =  (f=File.open(filename,'r')).read; f.close
+	
+	output_html = File.join(File.dirname(filename), 
+		File.basename(filename, File.extname(filename)) + ".html")	
+	
+	# split the input in sections
+	
+	stuff = input.split(SPLIT)
+	if stuff.size == 1
+		stuff[2] = stuff[0]
+		stuff[0] = "Write a comment here"
+		stuff[1] = "{} # params "
+	end
+
+	comment   = stuff.shift
+	params_s = stuff.shift
+	
+	params = eval(params_s||'{}')
+	if params == nil
+		raise "Null params? #{params_s.inspect}"
+	end
+	
+	markdown  = stuff.shift
+
+#	puts "comment: #{markdown.inspect}"	
+#	puts "markdown: #{markdown.inspect}"
+	
+	failed = []
+	relaxed = []
+	crashed = []
+	actual = {}
+	
+	doc = 
+		if $marutest_language == :markdown
+			Maruku.new(markdown, params)
+		else
+			MaRuKu.textile2(markdown, params)
+		end
+
+	for s in TOTEST
+		begin
+			if s==:to_html
+				actual[s] = doc.to_html
+			else
+				actual[s] = doc.send s
+				raise "Methods #{s} gave nil" if not actual[s]
+			end
+		rescue Exception => e
+			crashed << s
+			actual[s] = e.inspect+ "\n"+ e.backtrace.join("\n")
+			puts actual[s]
+		end
+	end
+
+	File.open(output_html, 'w') do |f|
+		f.write doc.to_html_document
+	end
+
+		begin
+			m = Maruku.new
+			d = m.instance_eval(actual[:inspect])
+		rescue Exception => e
+			s = e.inspect + e.backtrace.join("\n")
+			raise "Inspect is not correct:\n ========\n#{actual[:inspect]}"+
+			"============\n #{s}"
+		end
+
+	expected = {}
+	if (stuff.size < TOTEST.size)
+		$stdout.write " (first time!) "
+		TOTEST.each do |x| expected[x] = actual[x] end
+	else
+		TOTEST.each_index do |i|
+			symbol = TOTEST[i]
+			expected[symbol] = stuff[i]
+#			puts "symbol: #{symbol.inspect} = #{stuff[i].inspect}"
+		end
+	end
+
+	m = Maruku.new
+	
+	
+	if not its_ok.include? :inspect
+		begin
+			d = m.instance_eval(expected[:inspect])
+	#		puts "Eval: #{d.inspect}"
+			expected[:inspect] = d.inspect
+		rescue Exception => e
+			s = e.inspect + e.backtrace.join("\n")
+			raise "Cannot eval user-provided string:\n #{expected[:inspect].to_s}"+
+			"\n #{s}"
+		end
+	end
+
+#	 m.instance_eval(actual[:inspect]) != m.instance_eval(expected[:inspect])	
+
+#	actual[:inspect] = m.instance_eval(actual[:inspect]) 
+#	expected[:inspect] =  m.instance_eval(expected[:inspect])
+
+
+	TOTEST.each do |x|
+		expected[x].strip!
+		actual[x].strip!
+		if not equals(expected[x], actual[x])
+			if its_ok.include? x
+				expected[x] = actual[x]
+				$stdout.write " relax:#{x} "
+				relaxed << x
+			else
+				actual[x] = "-----| WARNING | -----\n" + actual[x].to_s
+				failed << x
+			end
+		end
+	end
+	
+	f = File.open(filename, 'w')
+	
+	f.write comment
+	f.write "\n*** Parameters: ***\n"
+	f.write params_s
+	f.write "\n*** Markdown input: ***\n"
+	f.write markdown
+
+	TOTEST.each do |x|
+		f.write marker(x) 
+		f.write expected[x]
+	end
+	f.write "\n*** EOF ***\n"
+	
+	if not failed.empty? or not crashed.empty? 
+		
+		f.puts "\n\n\n\nFailed tests:   #{failed.inspect} \n" 
+	
+		TOTEST.each do |x|
+			f.write marker(x) 
+			f.write actual[x]
+		end
+
+	else
+		f.puts "\n\n\n\tOK!\n\n\n"
+	end
+
+	
+	md_pl = markdown_pl(markdown)
+		
+	f.write "\n*** Output of Markdown.pl ***\n" 
+	f.write md_pl
+	
+	f.write "\n*** Output of Markdown.pl (parsed) ***\n"
+	begin 
+		doc = REXML::Document.new("
    #{md_pl}
    ",{
+			:compress_whitespace=>['div','p'],
+			:ignore_whitespace_nodes=>['div','p'],
+			:respect_whitespace=>['pre','code']
+		})
+		div = doc.root
+		xml =""
+		div.write_children(xml,indent=1,transitive=true,ie_hack=false)
+		f.write xml
+	rescue Exception=>e
+		f.puts "Error: #{e.inspect}"
+	end
+	f.close
+	
+	
+	return failed, relaxed, crashed
+end
+
+def markdown_pl(markdown)
+	tmp1 = "/tmp/marutest1"
+	tmp2 = "/tmp/marutest2"
+	File.open(tmp1,'w') do |f| f.puts markdown end
+	system "bin/Markdown.pl < #{tmp1} > #{tmp2}"
+	f = File.open(tmp2,'r')
+	s = f.read
+	f.close
+	s
+end
+
+def passed?(args, arg)
+	if args.include? arg
+		args.delete arg
+		true
+	else
+		false
+	end
+end
+
+def marutest(args)
+	dont_worry = []
+	TOTEST.each do |x|
+		arg = "ok:#{x}"
+	#	puts arg
+		if passed?(args, arg)
+			dont_worry << x
+		end
+	end
+	
+	if passed?(args, 'ok')
+		dont_worry = TOTEST.clone
+	end
+	
+	if dont_worry.size > 0
+		puts "Relaxed on #{dont_worry.inspect}"
+	end
+	
+
+	failed = {}
+	relaxed = {}
+	
+	args.each do |f|
+		$stdout.write  f + ' '*(50-f.size) + " "
+		$stdout.flush
+		tf, tr, tcrashed = run_test(f, dont_worry)
+		
+		tf = tf + tcrashed
+
+		
+		if tr.size > 0
+			$stdout.write " relax #{tr.inspect} "
+		end
+		
+		if tf.size>0
+			$stdout.write " failed on #{tf.inspect} "
+		else
+			$stdout.write " OK "
+		end
+
+		if tcrashed.size > 0
+			$stdout.write "    CRASHED on #{tcrashed.inspect}"
+		end
+
+			$stdout.write "\n"		
+			
+		failed[f]  = tf
+		relaxed[f]  = tr	
+	end
+	
+	num_failed = 0
+	failed_cat = {}
+
+	puts "\n\n\n**** FINAL REPORT ****\n\n"
+
+	
+	if failed.size > 0
+		failed.each do |file, fl|
+			num_failed += fl.size
+			if fl.size > 0
+				puts "\t#{file}\tfailed on #{fl.inspect}"
+			end
+			fl.each do |x|
+				failed_cat[x] = failed_cat[x] || 0
+				failed_cat[x] = failed_cat[x]  + 1
+			end
+		end
+	end
+
+	if dont_worry.size > 0
+		puts "Relaxed on #{dont_worry.inspect}"
+	end
+
+	if relaxed.size > 0
+		relaxed.each do |file, r|
+			if r.size > 0
+				puts "\t#{file}\t\trelaxed on #{r.inspect}"
+			end
+		end
+	end
+	
+	if failed_cat.size > 0
+		puts "\nCategories:\n"
+	
+		failed_cat.each do |x, num|
+			puts "\t#{x.inspect} \tfailed #{num}/#{args.size}"
+		end
+	end
+	
+	return num_failed == 0
+end
+
+if File.basename(__FILE__) == 'marutest'
+	if ARGV.empty?
+		puts "marutest is a tool for running Maruku's unittest."
+		exit 1
+	end
+	ok = marutest(ARGV.clone)
+	
+	exit ok ? 0 : -1 
+end
+
diff --git a/vendor/plugins/maruku/bin/marutex b/vendor/plugins/maruku/bin/marutex
new file mode 100644
index 00000000..b3ed099d
--- /dev/null
+++ b/vendor/plugins/maruku/bin/marutex
@@ -0,0 +1,31 @@
+#!/usr/bin/env ruby
+
+require 'maruku'
+
+if File.basename($0) =~ /^marutex/
+	# Convert each file 
+	ARGV.each do |f|
+		puts "Opening #{f}"
+	
+		# read file content
+		input =  File.open(f,'r').read
+		
+		# create Maruku
+		doc = Maruku.new(input)
+		# convert to a complete html document
+		latex = doc.to_latex_document
+	
+		# write to file
+		dir = File.dirname(f)
+		job = File.join(dir, File.basename(f, File.extname(f)))
+		filename = job + ".tex"
+
+		File.open(filename,'w') do |f| f.puts latex end
+
+		# run twice for cross references
+		system "pdflatex '#{job}'  '-output-directory=#{dir}' "
+		system "pdflatex '#{job}' '-output-directory=#{dir}' "
+		
+#		system "open #{job}.pdf"
+	end
+end
\ No newline at end of file
diff --git a/vendor/plugins/maruku/lib/maruku/input/parse_span_better.rb b/vendor/plugins/maruku/lib/maruku/input/parse_span_better.rb
index 966be898..ee1f38f8 100644
--- a/vendor/plugins/maruku/lib/maruku/input/parse_span_better.rb
+++ b/vendor/plugins/maruku/lib/maruku/input/parse_span_better.rb
@@ -271,7 +271,7 @@ module MaRuKu; module In; module Markdown; module SpanLevelParser
 			extension_meta(src, con, break_on_chars)
 		else
 			stuff = read_simple(src, escaped=[?}], break_on_chars, [])
-			if stuff =~ /^(\w+\s|[^\w])/
+			if stuff =~ /^(\w+\s|[^\w])/u
 				extension_id = $1.strip
 				if false
 				else
diff --git a/vendor/plugins/maruku/tests/Makefile b/vendor/plugins/maruku/tests/Makefile
new file mode 100644
index 00000000..df0f5526
--- /dev/null
+++ b/vendor/plugins/maruku/tests/Makefile
@@ -0,0 +1,5 @@
+test:
+	ruby -I../lib ../bin/marutest unittest/*.md
+
+all:
+	./convert_all.sh
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/MarkdownTest.pl b/vendor/plugins/maruku/tests/MarkdownTest_1.0/MarkdownTest.pl
new file mode 100755
index 00000000..5cc5cc68
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/MarkdownTest.pl
@@ -0,0 +1,157 @@
+#!/usr/bin/perl
+
+#
+# MarkdownTester -- Run tests for Markdown implementations
+#
+# Copyright (c) 2004 John Gruber
+# 
+#
+
+use strict;
+use warnings;
+use Getopt::Long;
+use Benchmark;
+
+our $VERSION = '1.0';
+# Mon 13 Dec 2004
+
+my $time_start = new Benchmark;
+my $test_dir = "Tests";
+my $script  = "./Markdown.pl";
+my $use_tidy = 0;
+my ($flag_version);
+
+GetOptions (
+			"script=s"   => \$script,
+			"testdir=s"  => \$test_dir,
+			"tidy"       => \$use_tidy,
+			"version"    => \$flag_version,
+			);
+
+if($flag_version) {
+	my $progname = $0;
+	$progname =~ s{.*/}{};
+	die "$progname version $VERSION\n";
+}
+
+unless (-d $test_dir) { die "'$test_dir' is not a directory.\n"; }
+unless (-f $script)   { die "$script does not exist.\n"; }
+unless (-x $script)   { die "$script is not executable.\n"; }
+
+my $tests_passed = 0;
+my $tests_failed = 0;
+
+foreach my $testfile (glob "$test_dir/*.text") {
+	my $testname = $testfile;
+	$testname =~ s{.*/(.+)\.text$}{$1}i; 
+	print "$testname ... ";
+
+	# Look for a corresponding .html file for each .text file:
+	my $resultfile = $testfile;
+	$resultfile =~ s{\.text$}{\.html}i;
+	unless (-f $resultfile) {die "'$resultfile' does not exist.\n";}
+	
+	# open(TEST, $testfile)     || die("Can't open testfile: $!");
+	open(RESULT, $resultfile) || die("Can't open resultfile: $!");
+	undef $/;
+	# my $t_input = ;
+	my $t_result = ;
+
+	my $t_output = `$script '$testfile'`;
+
+	# Normalize the output and expected result strings:
+	$t_result =~ s/\s+\z//; # trim trailing whitespace
+	$t_output =~ s/\s+\z//; # trim trailing whitespace
+	if ($use_tidy) {
+		#  Escape the strings, pass them through to CLI tidy tool for tag-level equivalency
+		$t_result =~ s{'}{'\\''}g; # escape ' chars for shell
+		$t_output =~ s{'}{'\\''}g;
+		$t_result = `echo '$t_result' | tidy --show-body-only 1 --quiet 1 --show-warnings 0`;
+		$t_output = `echo '$t_output' | tidy --show-body-only 1 --quiet 1 --show-warnings 0`;
+	}
+
+	if ($t_output eq $t_result) {
+		print "OK\n";
+		$tests_passed++;
+	}
+	else {
+		print "FAILED\n\n";
+		$tests_failed++;
+	}
+}
+
+print "\n\n";
+print "$tests_passed passed; $tests_failed failed.\n";
+
+my $time_end = new Benchmark;
+my $time_diff = timediff($time_end, $time_start);
+print "Benchmark: ", timestr($time_diff), "\n";
+
+
+__END__
+
+=pod
+
+=head1 NAME
+
+B
+
+
+=head1 SYNOPSIS
+
+B [ B<--options> ]  [ I ... ]
+
+
+=head1 DESCRIPTION
+
+
+=head1 OPTIONS
+
+Use "--" to end switch parsing. For example, to open a file named "-z", use:
+
+	MarkdownTest.pl -- -z
+
+=over 4
+
+=item B<--script>
+
+Specify the path to the Markdown script to test. Defaults to
+"./Markdown.pl". Example:
+
+	./MarkdownTest.pl --script ./PHP-Markdown/php-markdown
+
+=item B<--testdir>
+
+Specify the path to a directory containing test data. Defaults to "Tests".
+
+=item B<--tidy>
+
+Flag to turn on using the command line 'tidy' tool to normalize HTML
+output before comparing script output to the expected test result.
+Assumes that the 'tidy' command is available in your PATH. Defaults to
+off.
+
+=back
+
+
+
+=head1 BUGS
+
+
+
+=head1 VERSION HISTORY
+
+1.0	Mon 13 Dec 2004
+
+
+
+=head1 COPYRIGHT AND LICENSE
+
+Copyright (c) 2004 John Gruber  
+   
+All rights reserved.
+
+This is free software; you may redistribute it and/or modify it under
+the same terms as Perl itself.
+
+=cut
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.html
new file mode 100644
index 00000000..7b38ff3c
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.html	
@@ -0,0 +1,38 @@
+
+
+
+
+
+
+
+
    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 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.
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.html.dist
new file mode 100644
index 00000000..9606860b
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.html.dist	
@@ -0,0 +1,17 @@
+
    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.
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.text
new file mode 100644
index 00000000..5e22bd35
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Amps and angle encoding.text	
@@ -0,0 +1,23 @@
+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] [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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.html
new file mode 100644
index 00000000..bcd5ffcb
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.html	
@@ -0,0 +1,36 @@
+
+
+
+
+
+
+
+
    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/>
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.html.dist
new file mode 100644
index 00000000..f8df9852
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.html.dist	
@@ -0,0 +1,18 @@
+
    Link: http://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/>
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.text
new file mode 100644
index 00000000..abbc4886
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Auto links.text	
@@ -0,0 +1,13 @@
+Link: .
+
+With an ampersand: 
+
+* In a list?
+* 
+* It should.
+
+> Blockquoted: 
+
+Auto-links should not occur here: ``
+
+	or here: 
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.html
new file mode 100644
index 00000000..4e3ae796
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.html	
@@ -0,0 +1,122 @@
+
+
+
+
+
+
+
+
    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: \-
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.html.dist
new file mode 100644
index 00000000..77823c3c
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.html.dist	
@@ -0,0 +1,102 @@
+
    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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.text
new file mode 100644
index 00000000..16447a01
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Backslash escapes.text	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.html
new file mode 100644
index 00000000..ef953e7e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.html	
@@ -0,0 +1,33 @@
+
+
+
+
+
+
+
+
    
+
    Example:
    
+
+
    sub status {
+    print "working";
+}
+
    
+
+
    Or:
    
+
+
    sub status {
+    return "working";
+}
    
+
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.html.dist
new file mode 100644
index 00000000..990202a1
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.html.dist	
@@ -0,0 +1,15 @@
+
    
+  
    Example:
    
+
+
    sub status {
+    print "working";
+}
+
    
+  
+  
    Or:
    
+
+
    sub status {
+    return "working";
+}
+
    
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.text
new file mode 100644
index 00000000..c31d1710
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Blockquotes with code blocks.text	
@@ -0,0 +1,11 @@
+> Example:
+> 
+>     sub status {
+>         print "working";
+>     }
+> 
+> Or:
+> 
+>     sub status {
+>         return "working";
+>     }
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.html
new file mode 100644
index 00000000..5f0a806e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.html	
@@ -0,0 +1,22 @@
+
+
+
+
+
+
+
+
    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.
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.html.dist
new file mode 100644
index 00000000..e21ac79a
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.html.dist	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.text
new file mode 100644
index 00000000..f8a5b27b
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Hard-wrapped paragraphs with list-like lines.text	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.html
new file mode 100644
index 00000000..e34cb275
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.html	
@@ -0,0 +1,91 @@
+
+
+
+
+
+
+
+
    Dashes:
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    ---
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    - - -
+
+
    
+
+
    Asterisks:
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    ***
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    * * *
+
+
    
+
+
    Underscores:
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    ___
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    _ _ _
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.html.dist
new file mode 100644
index 00000000..2dc2ab65
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.html.dist	
@@ -0,0 +1,71 @@
+
    Dashes:
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    ---
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    - - -
+
    
+
+
    Asterisks:
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    ***
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    * * *
+
    
+
+
    Underscores:
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    ___
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    _ _ _
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.text
new file mode 100644
index 00000000..1594bda2
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Horizontal rules.text	
@@ -0,0 +1,67 @@
+Dashes:
+
+---
+
+ ---
+ 
+  ---
+
+   ---
+
+	---
+
+- - -
+
+ - - -
+ 
+  - - -
+
+   - - -
+
+	- - -
+
+
+Asterisks:
+
+***
+
+ ***
+ 
+  ***
+
+   ***
+
+	***
+
+* * *
+
+ * * *
+ 
+  * * *
+
+   * * *
+
+	* * *
+
+
+Underscores:
+
+___
+
+ ___
+ 
+  ___
+
+   ___
+
+    ___
+
+_ _ _
+
+ _ _ _
+ 
+  _ _ _
+
+   _ _ _
+
+    _ _ _
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).html
new file mode 100644
index 00000000..cec63b6d
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).html	
@@ -0,0 +1,39 @@
+
+
+
+
+
+
+
+
    Simple block on one line:
    
+
+
    foo
    
+
+
    And nested without indentation:
    
+
+
    
+
+
    
+
+
    
+foo
+
    
+
+
    
+
+
+
    bar
    
+
+
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).html.dist
new file mode 100644
index 00000000..1972d875
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).html.dist	
@@ -0,0 +1,14 @@
+
    Simple block on one line:
    
+
+
    foo
    
+
+
    And nested without indentation:
    
+
+
    
+
    
+
    
+foo
+
    
+
    
+
    bar
    
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).text
new file mode 100644
index 00000000..9d71ddcc
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Advanced).text	
@@ -0,0 +1,14 @@
+Simple block on one line:
+
+
    foo
    
+
+And nested without indentation:
+
+
    
+
    
+
    
+foo
+
    
+
    
+
    bar
    
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).html
new file mode 100644
index 00000000..f073fa51
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).html	
@@ -0,0 +1,88 @@
+
+
+
+
+
+
+
+
    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:
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).html.dist
new file mode 100644
index 00000000..6bf78f8f
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).html.dist	
@@ -0,0 +1,72 @@
+
    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:
    
+
+
    
+
+
    
+
+
    
+
+
       
+
+
      
+
+
     
+
+
    
+
+
    
+
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).text
new file mode 100644
index 00000000..14aa2dc2
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML (Simple).text	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.html
new file mode 100644
index 00000000..ca8e9518
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.html	
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
    Paragraph one.
    
+
+
    Paragraph two.
    
+
+
    The end.
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.html.dist
new file mode 100644
index 00000000..3f167a16
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.html.dist	
@@ -0,0 +1,13 @@
+
    Paragraph one.
    
+
+
+
+
+
+
    Paragraph two.
    
+
+
+
+
    The end.
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.text
new file mode 100644
index 00000000..41d830d0
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Inline HTML comments.text	
@@ -0,0 +1,13 @@
+Paragraph one.
+
+
+
+
+
+Paragraph two.
+
+
+
+The end.
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.html
new file mode 100644
index 00000000..7d5420c2
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.html	
@@ -0,0 +1,28 @@
+
+
+
+
+
+
+
+
    Just a URL.
    
+
+
    URL and title.
    
+
+
    URL and title.
    
+
+
    URL and title.
    
+
+
    Empty.
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.html.dist
new file mode 100644
index 00000000..bdfabb57
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.html.dist	
@@ -0,0 +1,9 @@
+
    Just a URL.
    
+
+
    URL and title.
    
+
+
    URL and title.
    
+
+
    URL and title.
    
+
+
    Empty.
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.text
new file mode 100644
index 00000000..4d0c1c26
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, inline style.text	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.html
new file mode 100644
index 00000000..3731aee7
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.html	
@@ -0,0 +1,38 @@
+
+
+
+
+
+
+
+
    Foo bar.
    
+
+
    Foo bar.
    
+
+
    Foo bar 1.
    
+
+
    With embedded brackets.
    
+
+
    Indented once.
    
+
+
    Indented twice.
    
+
+
    Indented thrice.
    
+
+
    Indented four times.
    
+
+
    [four]: /url
+
+
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.html.dist
new file mode 100644
index 00000000..cf4d8332
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.html.dist	
@@ -0,0 +1,18 @@
+
    Foo bar.
    
+
+
    Foo bar.
    
+
+
    Foo bar.
    
+
+
    With embedded [brackets].
    
+
+
    Indented once.
    
+
+
    Indented twice.
    
+
+
    Indented thrice.
    
+
+
    Indented [four][] times.
    
+
+
    [four]: /url
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.text
new file mode 100644
index 00000000..b2fa7345
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Links, reference style.text	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.html
new file mode 100644
index 00000000..92bc5f0d
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.html	
@@ -0,0 +1,22 @@
+
+
+
+
+
+
+
+
    Foo bar.
    
+
+
    Foo bar.
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.html.dist
new file mode 100644
index 00000000..611c1ac6
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.html.dist	
@@ -0,0 +1,3 @@
+
    Foo bar.
    
+
+
    Foo bar.
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.text
new file mode 100644
index 00000000..29d0e423
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Literal quotes in titles.text	
@@ -0,0 +1,7 @@
+Foo [bar][].
+
+Foo [bar](/url/ "Title with "quotes" inside").
+
+
+  [bar]: /url/ "Title with "quotes" inside"
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.html
new file mode 100644
index 00000000..1cfe98e5
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.html	
@@ -0,0 +1,322 @@
+
+
+
+
+Markdown: Basics
+
+
+
    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>
+
+
+
    
+
+
+
+
    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>
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.html.dist
new file mode 100644
index 00000000..d5bdbb29
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.html.dist	
@@ -0,0 +1,314 @@
+
    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>
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.text
new file mode 100644
index 00000000..486055ca
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Basics.text	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.html
new file mode 100644
index 00000000..889706af
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.html	
@@ -0,0 +1,840 @@
+
+
+
+
+Markdown: Syntax
+
+
+
    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
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.html.dist
new file mode 100644
index 00000000..5c01306c
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.html.dist	
@@ -0,0 +1,942 @@
+
    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
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.text
new file mode 100644
index 00000000..dabd75c0
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Markdown Documentation - Syntax.text	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.html
new file mode 100644
index 00000000..e9f27abb
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.html	
@@ -0,0 +1,28 @@
+
+
+
+
+
+
+
+
    
+
    foo
    
+
+
    
+
    bar
    
+
    
+
+
    foo
    
+
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.html.dist
new file mode 100644
index 00000000..d8ec7f8e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.html.dist	
@@ -0,0 +1,9 @@
+
    
+  
    foo
    
+  
+  
    
+    
    bar
    
+  
    
+  
+  
    foo
    
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.text
new file mode 100644
index 00000000..ed3c624f
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Nested blockquotes.text	
@@ -0,0 +1,5 @@
+> foo
+>
+> > bar
+>
+> foo
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.html
new file mode 100644
index 00000000..4308acd5
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.html	
@@ -0,0 +1,228 @@
+
+
+
+
+
+
+
+
    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. 
+
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.html.dist
new file mode 100644
index 00000000..ce85c3aa
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.html.dist	
@@ -0,0 +1,137 @@
+
    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. 
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.text
new file mode 100644
index 00000000..621db581
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Ordered and unordered lists.text	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.html
new file mode 100644
index 00000000..fb77c762
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.html	
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
    This is strong and em.
    
+
+
    So is this word.
    
+
+
    This is strong and em.
    
+
+
    So is this word.
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.html.dist
new file mode 100644
index 00000000..71ec78c7
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.html.dist	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.text
new file mode 100644
index 00000000..95ee690d
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Strong and em together.text	
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.html
new file mode 100644
index 00000000..1fac814e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.html
@@ -0,0 +1,46 @@
+
+
+
+
+
+
+
+
      
+
    • 
+
      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
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.html.dist
new file mode 100644
index 00000000..3301ba80
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.html.dist
@@ -0,0 +1,25 @@
+
      
+
    • 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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.text
new file mode 100644
index 00000000..589d1136
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tabs.text
@@ -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/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.html b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.html
new file mode 100644
index 00000000..82b36396
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.html
@@ -0,0 +1,30 @@
+
+
+
+
+
+
+
+
    
+
    A list within a blockquote:
    
+
+
      
+
    • asterisk 1
      • 
+
+
    • asterisk 2
      • 
+
+
    • asterisk 3
      • 
+
    
+
    
+
+
    
+
    
+
+
      
+
    
+
+
    
+
    
+Created by Maruku at 23:15 on Friday, January 05th, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.html.dist b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.html.dist
new file mode 100644
index 00000000..f2a8ce70
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.html.dist
@@ -0,0 +1,8 @@
+
    
+
    A list within a blockquote:
    
+
      
+
    • asterisk 1
      • 
+
    • asterisk 2
      • 
+
    • asterisk 3
      • 
+
    
+
    
diff --git a/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.text b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.text
new file mode 100644
index 00000000..5f18b8da
--- /dev/null
+++ b/vendor/plugins/maruku/tests/MarkdownTest_1.0/Tests/Tidyness.text
@@ -0,0 +1,5 @@
+> A list within a blockquote:
+> 
+> *	asterisk 1
+> *	asterisk 2
+> *	asterisk 3
diff --git a/vendor/plugins/maruku/tests/bugs/code_in_links.md b/vendor/plugins/maruku/tests/bugs/code_in_links.md
new file mode 100644
index 00000000..0b510b61
--- /dev/null
+++ b/vendor/plugins/maruku/tests/bugs/code_in_links.md
@@ -0,0 +1,16 @@
+**This bug is now solved**
+
+Previously, a bug would not let you use `code` inside links text.
+
+So this:
+	Use the [`syntax`][syntax]
+produces:
+> Use the [`syntax`][syntax]
+
+And this:
+	Use the `[syntax][syntax]`
+produces:
+> Use the `[syntax][syntax]`
+
+[syntax]: http://gogole.com
+
diff --git a/vendor/plugins/maruku/tests/bugs/complex_escaping.md b/vendor/plugins/maruku/tests/bugs/complex_escaping.md
new file mode 100644
index 00000000..89135374
--- /dev/null
+++ b/vendor/plugins/maruku/tests/bugs/complex_escaping.md
@@ -0,0 +1,4 @@
+
+
+What do you see here? `\\` it should be two backslashes.
+
diff --git a/vendor/plugins/maruku/tests/convert_all.sh b/vendor/plugins/maruku/tests/convert_all.sh
new file mode 100755
index 00000000..ea645173
--- /dev/null
+++ b/vendor/plugins/maruku/tests/convert_all.sh
@@ -0,0 +1,6 @@
+#!/bin/bash
+
+ruby -I../lib ../bin/maruku MarkdownTest_1.0/Tests/*.text
+
+ruby -I../lib ../bin/maruku others/*.md
+#ruby -I../lib ../bin/marutex others/*.md
diff --git a/vendor/plugins/maruku/tests/math/math.css b/vendor/plugins/maruku/tests/math/math.css
new file mode 100644
index 00000000..7d9f3183
--- /dev/null
+++ b/vendor/plugins/maruku/tests/math/math.css
@@ -0,0 +1,40 @@
+
+body {
+	max-width: 36em;
+}
+
+div.maruku-equation {
+	display: block;
+	padding-top: 0.5em;
+	padding-bottom: 0.5em;
+}
+
+div.maruku-equation span.maruku-eq-number {
+	float: right;
+	padding-right: 2em;
+}
+
+div.maruku-equation div.maruku-eq-tex {
+	font-size: 70%;
+	float: left;
+	margin-top: -3em;
+	padding: .5em;
+	border: dashed 1px pink;
+}
+
+div.maruku-equation  div.maruku-eq-tex:hover {
+	float: none;
+	display: block;
+	padding: 3em;
+	/*background-color: lightgray;*/
+}
+
+div.maruku-equation  div.maruku-eq-tex code {
+	display: none;
+	background-color: #ffe;
+	padding: 1em;
+}
+
+div.maruku-equation  div.maruku-eq-tex:hover  code {
+	display: block !important;
+}
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/math/preamble.tex b/vendor/plugins/maruku/tests/math/preamble.tex
new file mode 100644
index 00000000..4bf1cf38
--- /dev/null
+++ b/vendor/plugins/maruku/tests/math/preamble.tex
@@ -0,0 +1,2 @@
+%\def\text{\textrm}
+\usepackage{amssymb,amsmath}
diff --git a/vendor/plugins/maruku/tests/math/run.sh b/vendor/plugins/maruku/tests/math/run.sh
new file mode 100755
index 00000000..5289fa4f
--- /dev/null
+++ b/vendor/plugins/maruku/tests/math/run.sh
@@ -0,0 +1,7 @@
+
+# 
+ruby -I../../lib use_itex.rb < private.txt
+
+# creates the pdf
+
+ruby -I../../lib ../../bin/maruku --pdf private.txt
diff --git a/vendor/plugins/maruku/tests/math/syntax.md b/vendor/plugins/maruku/tests/math/syntax.md
new file mode 100644
index 00000000..d98d124b
--- /dev/null
+++ b/vendor/plugins/maruku/tests/math/syntax.md
@@ -0,0 +1,46 @@
+LaTeX preamble: preamble.tex
+CSS: math.css
+
+Here are some formulas:
+
+*	$\alpha$
+*	$x^{n}+y^{n} \neq z^{n}$
+
+Some inline maths: $\sum_{n=1}^\infty \frac{(-1)^n}{n} = \ln 2$. 
+
+Some display  maths:
+
+\[ \sum_{n=1}^\infty \frac{1}{n} \]
+\[ \sum_{n=1}^\infty \frac{1}{n} \text{ is divergent, but } \lim_{n \to \infty} \sum_{i=1}^n \frac{1}{i} - \ln n \text{ exists.} \]     (a)
+
+Some random AMSTeX symbols - thanks to Robin Snader for adding these:
+
+$$ \beth \Subset \bigtriangleup \smallsmile \bumpeq \ggg \pitchfork $$ 
+
+Note that $\hat g$ , $J$, and $\gamma_1\gamma_2$ all restrict to
+
+$x_1 \overline{x_2} \oplus x_2 \overline{x_1}$ and that this module
+is linear in $x_1$ and $x_2$.
+
+See label \eqref{a}.
+
+$$ \href{#hello}{\alpha+\beta} $$
+
+## Cross references ##
+
+The following are 4 equations, labeled A,B,C,D:
+
+$$ \alpha $$ (A)
+
+\[ 
+	\beta
+\] (B) 
+
+$$ \gamma \label{C} $$
+
+\[ 
+	\delta \label{D}
+\]
+
+You can now refer to (eq:A), (eq:B), \eqref{C}, \eqref{D}.
+
diff --git a/vendor/plugins/maruku/tests/math/syntax.xhtml b/vendor/plugins/maruku/tests/math/syntax.xhtml
new file mode 100644
index 00000000..faf8ef52
--- /dev/null
+++ b/vendor/plugins/maruku/tests/math/syntax.xhtml
@@ -0,0 +1,37 @@
+
+
+
+
+
+
    Here are some formulas:
    
+
+
      
+
    • α
      • 
+
+
    • x n+y n≠z n
      • 
+
    
+
+
    Some inline maths: ∑ n=1  ∞(−1 ) nn=ln2 .
    
+
+
    Some display maths:
    
+
    ∑ n=1  ∞1 n
     \sum_{n=1}^\infty \frac{1}{n} 
    (1)∑ n=1  ∞1 n is divergent, but lim n→∞∑ i=1  n1 i−lnn exists.
     \sum_{n=1}^\infty \frac{1}{n} \text{ is divergent, but } \lim_{n \to \infty} \sum_{i=1}^n \frac{1}{i} - \ln n \text{ exists.} 
    
+
    Some random AMSTeX symbols - thanks to Robin Snader for adding these:
    
+
    ℶ⋐△smallsmile≏⋙⋔
     \beth \Subset \bigtriangleup \smallsmile \bumpeq \ggg \pitchfork 
    
+
    Note that ĝ , J, and γ 1 γ 2  all restrict to
    
+
+
    x 1 x 2 ‾⊕x 2 x 1 ‾ and that this module is linear in x 1  and x 2 .
    
+
+
    See label (1).
    
+
    α+β
     \href{#hello}{\alpha+\beta} 
    
+
    Cross references
    
+
+
    The following are 4 equations, labeled A,B,C,D:
    
+
    (2)α
     \alpha 
    (3)β
     	\beta
+
+
    (4)γ
     \gamma  
    (5)δ
     	\delta 
+
+
    
+
    You can now refer to (2), (3), (4), (5).
    
+
    Created by Maruku at 21:13 on Sunday, January 14th, 2007.
    
diff --git a/vendor/plugins/maruku/tests/math/use_itex.rb b/vendor/plugins/maruku/tests/math/use_itex.rb
new file mode 100644
index 00000000..5a3ec196
--- /dev/null
+++ b/vendor/plugins/maruku/tests/math/use_itex.rb
@@ -0,0 +1,34 @@
+
+# run this as:
+# ruby -I../../lib use_itex.rb < private.txt
+
+require 'maruku'
+
+module MaRuKu; module Out; module HTML
+	
+	def to_html_inline_math_itex
+		# You can: either return a REXML::Element
+		#    return Element.new 'div'    
+		# or return an empty array on error
+		#    return []  
+		# or have a string parsed by REXML:
+		tex = self.math
+		tex.gsub!('&','&')
+		mathml = "#{tex}"
+		return Document.new(mathml).root
+	end
+	
+	def to_html_equation_itex
+		return to_html_inline_math_itex
+	end
+
+end end end
+
+MaRuKu::Globals[:html_math_engine] = 'itex'
+
+doc = Maruku.new($stdin.read, {:on_error => :raise})
+
+File.open('output.xhtml','w') do |f|
+	f.puts doc.to_html_document
+end
+
diff --git a/vendor/plugins/maruku/tests/math_usage/document.md b/vendor/plugins/maruku/tests/math_usage/document.md
new file mode 100644
index 00000000..5ade2241
--- /dev/null
+++ b/vendor/plugins/maruku/tests/math_usage/document.md
@@ -0,0 +1,13 @@
+css: math.css
+
+This is an example document. Inline: $a$, $b$, $q$ and stop.
+
+$$        \int_a^b f(x) dx       $$     (1)
+
+See for example (eq:1).
+
+Equation inline: $  \int_a^b f(x) dx $ and that's it.
+
+
+Spacing: Maruku outputs sizes and alignment for images in `ex`. An `ex` is one `x`:
+x, $\textrm{x}$, $x$ should have the same height. 
diff --git a/vendor/plugins/maruku/tests/math_usage/math.css b/vendor/plugins/maruku/tests/math_usage/math.css
new file mode 100644
index 00000000..3d5eb7c9
--- /dev/null
+++ b/vendor/plugins/maruku/tests/math_usage/math.css
@@ -0,0 +1,26 @@
+
+body {
+	max-width: 35em;
+}
+
+span.maruku-inline .maruku-mathml  {
+	//display: none;
+}
+
+div.maruku-equation .maruku-mathml  {
+	//display: none;
+}
+
+span.maruku-inline .maruku-png  {
+}
+
+div.maruku-equation .maruku-png  {
+}
+
+div.maruku-equation {
+	text-align: center;
+}
+
+div.maruku-equation span.maruku-eq-number  {
+	display: block; float: right; padding-right: 2em;
+}
diff --git a/vendor/plugins/maruku/tests/math_usage/script.sh b/vendor/plugins/maruku/tests/math_usage/script.sh
new file mode 100755
index 00000000..b027b6aa
--- /dev/null
+++ b/vendor/plugins/maruku/tests/math_usage/script.sh
@@ -0,0 +1,13 @@
+
+maruku="ruby -I../../lib ../../bin/maruku"
+
+#input="private.txt"
+input="document.md"
+
+$maruku -m itex2mml -o itex2mml.xhtml $input
+$maruku -m ritex    -o ritex.xhtml  $input
+$maruku -m none     -o none.html  $input
+$maruku -m blahtex  -o blahtex.xhtml  $input
+$maruku -m none    --math-images blahtex  -o blahtexi.html  $input
+$maruku -m blahtex --math-images blahtex  -o blahtexmi.xhtml  $input
+ 
diff --git a/vendor/plugins/maruku/tests/others/Backslash escapes.text b/vendor/plugins/maruku/tests/others/Backslash escapes.text
new file mode 100644
index 00000000..d4bf4289
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/Backslash escapes.text	
@@ -0,0 +1,106 @@
+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: \-
+
+So, these are TeX's special chars: 
+> \\ { } $ & # ^ _ % ~ 
+
+
+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/vendor/plugins/maruku/tests/others/abbreviations.html b/vendor/plugins/maruku/tests/others/abbreviations.html
new file mode 100644
index 00000000..11ad0711
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/abbreviations.html
@@ -0,0 +1,16 @@
+
+
+
+
+
+
+
+
    The HTML specification is maintained by the W3C.
    
+
+
    Operation Tigra Genesis is going well.
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/abbreviations.md b/vendor/plugins/maruku/tests/others/abbreviations.md
new file mode 100644
index 00000000..06253d1e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/abbreviations.md
@@ -0,0 +1,11 @@
+
+The HTML specification is maintained by the W3C.
+
+*[HTML]: Hyper Text Markup Language
+*[W3C]:  World Wide Web Consortium
+
+
+
+Operation Tigra Genesis is going well.
+
+*[Tigra Genesis]:
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/blank.html b/vendor/plugins/maruku/tests/others/blank.html
new file mode 100644
index 00000000..749c8ac0
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/blank.html
@@ -0,0 +1,16 @@
+
+
+
+
+
+
+
+
    Linea 1
    
+
+
    Linea 2
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/blank.md b/vendor/plugins/maruku/tests/others/blank.md
new file mode 100644
index 00000000..78d83a21
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/blank.md
@@ -0,0 +1,4 @@
+
+Linea 1
+
+Linea 2
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/code.html b/vendor/plugins/maruku/tests/others/code.html
new file mode 100644
index 00000000..ed7d1888
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/code.html
@@ -0,0 +1,18 @@
+
+
+
+
+
+
+
+
    Here is an example of AppleScript:
    
+
+
    tell application "Foo"
+    beep
+end tell
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/code.md b/vendor/plugins/maruku/tests/others/code.md
new file mode 100644
index 00000000..ce027b7b
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/code.md
@@ -0,0 +1,5 @@
+Here is an example of AppleScript:
+
+    tell application "Foo"
+        beep
+    end tell
diff --git a/vendor/plugins/maruku/tests/others/code2.html b/vendor/plugins/maruku/tests/others/code2.html
new file mode 100644
index 00000000..ead4ef40
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/code2.html
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
    
+
    This is a header.
    
+
+
      
+
    1. This is the first list item.
      2. 
+
+
    2. This is the second list item.
      3. 
+
    
+
+
    Here's some example code:
    
+
+
    return shell_exec("echo $input | $markdown_script");
    
+
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/code2.md b/vendor/plugins/maruku/tests/others/code2.md
new file mode 100644
index 00000000..eea196e9
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/code2.md
@@ -0,0 +1,8 @@
+> ## 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");
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/code3.html b/vendor/plugins/maruku/tests/others/code3.html
new file mode 100644
index 00000000..17c337e2
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/code3.html
@@ -0,0 +1,29 @@
+
+
+
+
+
+
+
+
    This is code (4 spaces):
    
+
+
    Code
    
+
+
    This is not code
    
+
+
    Code
+
    
+
+
    This is code (1 tab):
    
+
+
    Code
    
+
+
    This is not code
    
+
+
    Code
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/code3.md b/vendor/plugins/maruku/tests/others/code3.md
new file mode 100644
index 00000000..fd3b027f
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/code3.md
@@ -0,0 +1,16 @@
+
+This is code (4 spaces):
+
+    Code
+This is not code
+    
+    Code
+
+This is code (1 tab):
+
+	Code
+This is not code
+
+	Code
+
+
diff --git a/vendor/plugins/maruku/tests/others/email.html b/vendor/plugins/maruku/tests/others/email.html
new file mode 100644
index 00000000..0b6b2357
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/email.html
@@ -0,0 +1,14 @@
+
+
+
+
+
+
+
+
    This is an email address: andrea@invalid.it
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/email.md b/vendor/plugins/maruku/tests/others/email.md
new file mode 100644
index 00000000..ed31f085
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/email.md
@@ -0,0 +1,4 @@
+
+
+This is an email address: 
+	
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/entities.html b/vendor/plugins/maruku/tests/others/entities.html
new file mode 100644
index 00000000..afab3d30
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/entities.html
@@ -0,0 +1,59 @@
+
+
+
+
+
+
+
+
    Maruku translates HTML entities to the equivalent in LaTeX:
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    EntityResult
    &copy;©
    &pound;£
    a&nbsp;ba b
    &lambda;λ
    &mdash;—
    
+
+
    Entity-substitution does not happen in code blocks or inline code.
    
+
+
    The following should not be translated:
    
+
+
    &copy;
+
    
+
+
    It should read just like this: &copy;.
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/entities.md b/vendor/plugins/maruku/tests/others/entities.md
new file mode 100644
index 00000000..56cb3e47
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/entities.md
@@ -0,0 +1,19 @@
+Maruku translates HTML entities to the equivalent in LaTeX:
+
+Entity      | Result
+------------|----------
+`©`    |  ©
+`£`   |  £
+`a b`  |  a b
+`λ`  |  λ
+`—`   |  —
+
+
+Entity-substitution does not happen in code blocks or inline code.
+
+The following should not be translated:
+
+	©
+
+It should read just like this: `©`.
+
diff --git a/vendor/plugins/maruku/tests/others/escaping.html b/vendor/plugins/maruku/tests/others/escaping.html
new file mode 100644
index 00000000..3c39b1bc
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/escaping.html
@@ -0,0 +1,26 @@
+
+
+
+
+
+
+
+
     Hello: ! ! ` { } [ ] ( ) # . ! * *
    
+
+
    Ora, emphasis, bold, * <- due asterischi-> * , un underscore-> _ , emphasis, incrediblee!
    
+
+
    This is Code with an escape:  -> ` <- (after)
    
+
+
    This is Code with a special: -> ` <-(after)
    
+
+
    Start  of paragraph
    
+
+
    End of paragraph 
    
+
+
    Exactly one space:     and also here:  
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/escaping.md b/vendor/plugins/maruku/tests/others/escaping.md
new file mode 100644
index 00000000..b1b56f82
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/escaping.md
@@ -0,0 +1,16 @@
+ Hello: ! \! \` \{ \} \[ \] \( \) \# \. \! * \*
+
+
+Ora, *emphasis*, **bold**, * <- due asterischi-> * , un underscore-> _ , _emphasis_,
+ incre*dible*e!
+
+
+This is ``Code with an escape:  -> ` <- `` (after)
+
+This is ```Code with a special: -> ` <- ```(after)
+
+`Start ` of paragraph
+
+End of `paragraph `
+
+Exactly one space: `   ` and also here: ``   ``
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/extra_dl.html b/vendor/plugins/maruku/tests/others/extra_dl.html
new file mode 100644
index 00000000..4801519e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/extra_dl.html
@@ -0,0 +1,157 @@
+
+
+
+
+
+
+
+
+
+
    
+
    Apple
    
+
+
    Pomaceous fruit of plants of the genus Malus in the family Rosaceae.
    
+
+
    Orange
    
+
+
    The fruit of an evergreen tree of the genus Citrus.
    
+
    
+
+
    
+
+
    
+
    Apple
    
+
+
    Pomaceous fruit of plants of the genus Malus in the family Rosaceae
    
+
+
    Orange
    
+
+
    The fruit of an evergreen tree of the genus Citrus.
    
+
    
+
+
    
+
+
    
+
    Apple
    
+
+
    Pomaceous fruit of plants of the genus Malus in the family Rosaceae.
    
+
+
    An american computer company.
    
+
+
    Orange
    
+
+
    The fruit of an evergreen tree of the genus Citrus.
    
+
    
+
+
    
+
+
    
+
    Term 1
    
+
+
    Term 2
    
+
+
    Definition a
    
+
+
    Term 3
    
+
+
    Definition b
    
+
    
+
+
    
+
+
    
+
    Term 1
    
+
+
    Term 2
    
+
+
    Term 2a
    
+
+
    Term 2b
    
+
+
    Definition a
    
+
+
    Term 3
    
+
+
    Definition b
    
+
    
+
+
    
+
+
    
+
    Apple
    
+
+
    
+
    Pomaceous fruit of plants of the genus Malus in the family Rosaceae.
    
+
    
+
+
    Orange
    
+
+
    
+
    The fruit of an evergreen tree of the genus Citrus.
    
+
    
+
    
+
+
    
+
+
    
+
    Term 1
    
+
+
    
+
    This is a definition 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.
    
+
    
+
+
    
+
    Second definition for term 1, also wrapped in a paragraph because of the blank line preceding it.
    
+
    
+
+
    Term 2
    
+
+
    
+
    This definition has a code block, a blockquote and a list.
    
+
+
    code block.
+
    
+
+
    
+
    block quote on two lines.
    
+
    
+
+
      
+
    1. first list item
      2. 
+
+
    2. second list item
      3. 
+
    
+
    
+
    
+
+
    
+
+
    
+
    Term 1
    
+
+
    Term 2
    
+
+
    Term 2a
    
+
+
    Term 2b
    
+
+
    Definition a
    
+
    
+
+
    This is a paragraph
    
+
+
    
+
    This is a term
    
+
+
    
+
    definition
    
+
    
+
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/extra_dl.md b/vendor/plugins/maruku/tests/others/extra_dl.md
new file mode 100644
index 00000000..f2747b01
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/extra_dl.md
@@ -0,0 +1,101 @@
+CSS: style.css
+
+
+Apple
+:   Pomaceous fruit of plants of the genus Malus in 
+    the family Rosaceae.
+
+Orange
+:   The fruit of an evergreen tree of the genus Citrus.
+
+***
+
+Apple
+:   Pomaceous fruit of plants of the genus Malus in 
+the family Rosaceae.
+
+Orange
+:   The fruit of an evergreen tree of the genus Citrus.
+
+
+***
+
+Apple
+:   Pomaceous fruit of plants of the genus Malus in 
+    the family Rosaceae.
+:   An american computer company.
+
+Orange
+:   The fruit of an evergreen tree of the genus Citrus.
+
+***
+
+Term 1
+Term 2
+:   Definition a
+
+Term 3
+:   Definition b
+
+***
+
+
+Term 1
+Term 2
+Term 2a
+Term 2b
+:   Definition a
+
+Term 3
+:   Definition b
+
+***
+
+Apple
+
+:   Pomaceous fruit of plants of the genus Malus in 
+    the family Rosaceae.
+
+Orange
+
+:    The fruit of an evergreen tree of the genus Citrus.
+
+***
+
+Term 1
+
+:   This is a definition 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.
+
+:   Second definition for term 1, also wrapped in a paragraph
+    because of the blank line preceding it.
+
+Term 2
+
+:   This definition has a code block, a blockquote and a list.
+
+        code block.
+
+    > block quote
+    > on two lines.
+
+    1.  first list item
+    2.  second list item
+
+***
+
+Term 1
+Term 2
+Term 2a
+Term 2b
+:   Definition a
+
+This is a paragraph
+
+This is a term
+
+: definition
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/extra_header_id.html b/vendor/plugins/maruku/tests/others/extra_header_id.html
new file mode 100644
index 00000000..86d8c215
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/extra_header_id.html
@@ -0,0 +1,22 @@
+
+
+
+
+Header 1
+
+
+
    Header 1
    
+
+
    Header 2
    
+
+
    Header 3
    
+
+
    Then you can create links to different parts of the same document like this:
    
+
+
    Link back to header 1, Link back to header 2, Link back to header 3
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/extra_header_id.md b/vendor/plugins/maruku/tests/others/extra_header_id.md
new file mode 100644
index 00000000..05c1afd9
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/extra_header_id.md
@@ -0,0 +1,13 @@
+Header 1            {#header1}
+========
+
+Header 2            {#header2}
+--------
+
+### Header 3 ###      {#header3}
+
+Then you can create links to different parts of the same document like this:
+
+[Link back to header 1](#header1),
+[Link back to header 2](#header2),
+[Link back to header 3](#header3)
diff --git a/vendor/plugins/maruku/tests/others/extra_table1.html b/vendor/plugins/maruku/tests/others/extra_table1.html
new file mode 100644
index 00000000..7c383119
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/extra_table1.html
@@ -0,0 +1,114 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    First HeaderSecond Header
    Content CellContent Cell
    Content CellContent Cell
    
+
+
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    ItemValue
    Computer$1600
    Phone$12
    Pipe$1
    
+
+
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    Function nameDescription
    help()Display the help window.
    destroy()Destroy your computer!
    
+
+
    
+
+
+
+
+
+
+
+
+
+
    Very long long head
    left
    
+
+
    
+
+
+
+
+
+
+
+
+
+
    Very long long head
    right
    
+
+
    
+
+
+
+
+
+
+
+
+
+
    Very long long head
    center
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/extra_table1.md b/vendor/plugins/maruku/tests/others/extra_table1.md
new file mode 100644
index 00000000..c094f778
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/extra_table1.md
@@ -0,0 +1,40 @@
+CSS: style.css
+
+First Header  | Second Header
+------------- | -------------
+Content Cell  | Content Cell
+Content Cell  | Content Cell
+
+***
+
+| Item      | Value |
+| --------- | -----:|
+| Computer  | $1600 |
+| Phone     |   $12 |
+| Pipe      |    $1 |
+
+***
+
+| Function name | Description                    |
+| ------------- | ------------------------------ |
+| `help()`      | Display the help window.       |
+| `destroy()`   | **Destroy your computer!**     |
+
+
+***
+
+| Very long long head  | 
+| :------------        | 
+| left                 | 
+
+***
+
+| Very long long head  | 
+| -------------------: | 
+| right                |
+
+***
+
+| Very long long head  | 
+| :------------------: | 
+| center               |
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/footnotes.html b/vendor/plugins/maruku/tests/others/footnotes.html
new file mode 100644
index 00000000..6ec9bdff
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/footnotes.html
@@ -0,0 +1,38 @@
+
+
+
+
+
+
+
+
    That's some text with a footnote 1 and another 2 and another 3.
    
+
+
    This is not a footnote.
    
+
+
    
+
    
+
+
      
+
    1. 
+
      And that's the footnote. This is second sentence (same paragraph)↩
      
+
      2. 
+
+
    2. 
+
      This is the very long one.
      
+
+
      That's the second paragraph.↩
      
+
      3. 
+
+
    3. 
+
      And that's the footnote.
      
+
+
      That's the second paragraph of the footnote.↩
      
+
      4. 
+
    
+
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/footnotes.md b/vendor/plugins/maruku/tests/others/footnotes.md
new file mode 100644
index 00000000..5f8c9e7d
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/footnotes.md
@@ -0,0 +1,17 @@
+That's some text with a footnote [^b] and another [^c] and another [^a].
+
+[^a]: And that's the footnote.
+
+    That's the second paragraph of the footnote.
+
+
+[^b]: And that's the footnote.
+This is second sentence (same paragraph).
+
+[^c]:
+    This is the very long one.
+
+    That's the second paragraph.
+
+
+This is not a footnote.
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/headers.html b/vendor/plugins/maruku/tests/others/headers.html
new file mode 100644
index 00000000..ff49f33b
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/headers.html
@@ -0,0 +1,18 @@
+
+
+
+
+A title with emphasis
+
+
+
    A title with emphasis
    
+
+
    A title with emphasis
    
+
+
    A title with emphasis
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/headers.md b/vendor/plugins/maruku/tests/others/headers.md
new file mode 100644
index 00000000..5eef6825
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/headers.md
@@ -0,0 +1,10 @@
+A title with *emphasis*
+=======================
+
+A title with *emphasis*
+-----------------------
+
+
+#### A title with *emphasis* ####
+
+
diff --git a/vendor/plugins/maruku/tests/others/hrule.html b/vendor/plugins/maruku/tests/others/hrule.html
new file mode 100644
index 00000000..9ebda12c
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/hrule.html
@@ -0,0 +1,22 @@
+
+
+
+
+
+
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/hrule.md b/vendor/plugins/maruku/tests/others/hrule.md
new file mode 100644
index 00000000..8705b9e4
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/hrule.md
@@ -0,0 +1,10 @@
+* * *
+
+***
+
+*****
+
+- - -
+
+---------------------------------------
+
diff --git a/vendor/plugins/maruku/tests/others/images.html b/vendor/plugins/maruku/tests/others/images.html
new file mode 100644
index 00000000..038a9059
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/images.html
@@ -0,0 +1,22 @@
+
+
+
+
+
+
+
+
    This page does not utilizes 
    
+
+
    Please mouseover to see the title: 
    
+
+
    Please mouseover to see the title: 
    
+
+
    I'll say it one more time: this page does not use 
    
+
+
    This is double size: 
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/images.md b/vendor/plugins/maruku/tests/others/images.md
new file mode 100644
index 00000000..cbfd31bb
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/images.md
@@ -0,0 +1,20 @@
+
+This page does not utilizes ![Cascading Style Sheets](http://jigsaw.w3.org/css-validator/images/vcss)
+
+
+Please mouseover to see the title: ![Cascading Style Sheets](http://jigsaw.w3.org/css-validator/images/vcss "Title ok!")
+
+Please mouseover to see the title: ![Cascading Style Sheets](http://jigsaw.w3.org/css-validator/images/vcss 'Title ok!')
+
+
+I'll say it one more time: this page does not use ![Cascading Style Sheets] [css]
+
+This is double size: ![Cascading Style Sheets] [css2]
+
+
+
+[css]: http://jigsaw.w3.org/css-validator/images/vcss "Optional title attribute"
+
+[css2]: http://jigsaw.w3.org/css-validator/images/vcss "Optional title attribute" class=external
+   style="border:0;width:188px;height:131px"
+
diff --git a/vendor/plugins/maruku/tests/others/inline_html.html b/vendor/plugins/maruku/tests/others/inline_html.html
new file mode 100644
index 00000000..4676b031
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/inline_html.html
@@ -0,0 +1,54 @@
+
+
+
+
+
+
+
+
+
+
    Input: Emphasis Result: Emphasis
    
+
+
    Input:  Result on span: 
    
+
+
    Result alone: 
    
+
+
    Without closing:
    
+
+
    
+
    This is true markdown text (paragraph)
    
+
+
    This is true markdown text (no paragraph)
    
+
    
+
+
+
+
+
+
+
+
+
+
+
+
+
    This is true markdown text. (no par)
+
    This is true markdown text. (par)
    
+
    
+
+
    The following is invalid HTML, and will generate an error:
    
+
+
    HTML parse error: 
+<table>
+<td markdown="1">This is *true* markdown text. (no par)</td>
+<td markdown="block">This is *true* markdown text. (par)</td>
+</tr>
    
+
+
    HTML parse error: 
+</table>
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/inline_html.md b/vendor/plugins/maruku/tests/others/inline_html.md
new file mode 100644
index 00000000..a5a68a18
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/inline_html.md
@@ -0,0 +1,42 @@
+CSS: style.css
+
+Input:
+     Emphasis
+Result: Emphasis
+
+Input:
+	
+Result on span: 
+
+Result alone: 
+
+
+
+Without closing:
+
+
+
+
    
+	This is *true* markdown text (paragraph)
+
+	
    
+		This is *true* markdown text (no paragraph)
+	
    
+
    
+
+
+
+
+
+
+
    This is *true* markdown text. (no par)This is *true* markdown text. (par)
    
+
+
+The following is invalid HTML, and will generate an error:
+
+
+
+
+
+
    This is *true* markdown text. (no par)This is *true* markdown text. (par)
    
+
diff --git a/vendor/plugins/maruku/tests/others/links.html b/vendor/plugins/maruku/tests/others/links.html
new file mode 100644
index 00000000..21b9262e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/links.html
@@ -0,0 +1,34 @@
+
+
+
+
+
+
+
+
    Search on Google
    
+
+
    Search on Google
    
+
+
    Search on Google
    
+
+
    Search on Google
    
+
+
    Search on Google images
    
+
+
    Search on Google images
    
+
+
    Inline: Google images
    
+
+
    Inline with title: Google images
    
+
+
    Inline with title: Google images
    
+
+
    Search on http://www.gogole.com or http://Here.com or ask bill@google.com or you might ask bill@google.com.
    
+
+
    If all else fails, ask Google
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/links.md b/vendor/plugins/maruku/tests/others/links.md
new file mode 100644
index 00000000..9c6eac33
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/links.md
@@ -0,0 +1,38 @@
+
+Search on [Google][]
+
+Search on [Google] []
+
+Search on [Google] [google]
+
+Search on [Google] [Google]
+
+Search on [Google images][]
+
+Search on [Google images][ 	GoOgle_search ]
+
+Inline: [Google images](http://google.com)
+
+Inline with title: [Google images](http://google.com "Title")
+
+Inline with title: [Google images]( http://google.com  "Title" )
+
+
+Search on  or  or ask 
+or you might ask bill@google.com.
+
+If all else fails, ask [Google](http://www.google.com)
+	
+[google]: http://www.google.com
+
+[google2]: http://www.google.com 'Single quotes'
+
+[google3]: http://www.google.com "Double quotes"
+
+[google4]: http://www.google.com (Parenthesis)
+
+[Google Search]: 
+ http://www.google.com "Google search"
+
+[Google Images]: 
+ http://images.google.com  (Google images)
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/list1.html b/vendor/plugins/maruku/tests/others/list1.html
new file mode 100644
index 00000000..67ff8e3e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/list1.html
@@ -0,0 +1,22 @@
+
+
+
+
+
+
+
+
      
+
    • 
+
      A list item with a blockquote:
      
+
+
      
+
      This is a blockquote inside a list item.
      
+
      
+
      • 
+
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/list1.md b/vendor/plugins/maruku/tests/others/list1.md
new file mode 100644
index 00000000..68c79a91
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/list1.md
@@ -0,0 +1,4 @@
+*   A list item with a blockquote:
+
+    > This is a blockquote
+    > inside a list item.
diff --git a/vendor/plugins/maruku/tests/others/list2.html b/vendor/plugins/maruku/tests/others/list2.html
new file mode 100644
index 00000000..e4a69095
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/list2.html
@@ -0,0 +1,20 @@
+
+
+
+
+
+
+
+
      
+
    • 
+
      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 dolo sit amet, consectetuer adipiscing elit
      
+
      • 
+
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/list2.md b/vendor/plugins/maruku/tests/others/list2.md
new file mode 100644
index 00000000..db67519d
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/list2.md
@@ -0,0 +1,5 @@
+*   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.
diff --git a/vendor/plugins/maruku/tests/others/list3.html b/vendor/plugins/maruku/tests/others/list3.html
new file mode 100644
index 00000000..b9398cd1
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/list3.html
@@ -0,0 +1,28 @@
+
+
+
+
+
+
+
+
      
+
    • 
+
      A list item with a blockquote:
      
+
+
      
+
      This is a blockquote inside a list item.
      
+
      
+
      • 
+
+
    • 
+
      A list item with a code block:
      
+
+
      <code goes here>
      
+
      • 
+
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/list3.md b/vendor/plugins/maruku/tests/others/list3.md
new file mode 100644
index 00000000..8cec2562
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/list3.md
@@ -0,0 +1,8 @@
+*   A list item with a blockquote:
+
+    > This is a blockquote
+    > inside a list item.
+
+*   A list item with a code block:
+
+        
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/lists.html b/vendor/plugins/maruku/tests/others/lists.html
new file mode 100644
index 00000000..10f8e3c0
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/lists.html
@@ -0,0 +1,52 @@
+
+
+
+
+
+
+
+
      
+
    • 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.
      • 
+
+
    • Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse id sem consectetuer libero luctus adipiscing
      • 
+
+
    • Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse id sem consectetuer libero luctus adipiscing
      • 
+
+
    • Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse id sem consectetuer libero luctus adipiscing.
      • 
+
    
+
+
    Ancora
    
+
+
      
+
    • 
+
      This is a list item with two paragraphs. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
      
+
+
      ATTENZIONE!
      
+
      • 
+
+
    • 
+
      Suspendisse id sem consectetuer libero luctus adipiscing.
      
+
      • 
+
    
+
+
    Ancora
    
+
+
      
+
    • 
+
      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 dolo sit amet, consectetuer adipiscing elit
      
+
      • 
+
+
    • 
+
      Another item in the same list.
      
+
      • 
+
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/lists.md b/vendor/plugins/maruku/tests/others/lists.md
new file mode 100644
index 00000000..9cfdde28
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/lists.md
@@ -0,0 +1,32 @@
+*   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.
+*   Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+Suspendisse id sem consectetuer libero luctus adipiscing.
+ *  Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+Suspendisse id sem consectetuer libero luctus adipiscing.
+ *  Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+ Suspendisse id sem consectetuer libero luctus adipiscing.
+
+Ancora
+
+*   This is a list item with two paragraphs. Lorem ipsum dolor
+    sit amet, consectetuer adipiscing elit. Aliquam hendrerit
+    mi posuere lectus.
+
+    ATTENZIONE!
+
+*  Suspendisse id sem consectetuer libero luctus adipiscing.
+
+
+Ancora
+
+*   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.
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/lists_after_paragraph.html b/vendor/plugins/maruku/tests/others/lists_after_paragraph.html
new file mode 100644
index 00000000..f3d24912
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/lists_after_paragraph.html
@@ -0,0 +1,54 @@
+
+
+
+
+
+
+
+
    Paragraph, list with no space: * ciao
    
+
+
    Paragraph, list with 1 space: * ciao
    
+
+
    Paragraph, list with 3 space: * ciao
    
+
+
    Paragraph, list with 4 spaces: * ciao
    
+
+
    Paragraph, list with 1 tab: * ciao
    
+
+
    Paragraph (1 space after), list with no space: * ciao
    
+
+
    Paragraph (2 spaces after), list with no space:
    
+* ciao
    
+
+
    Paragraph (3 spaces after), list with no space: 
    
+* ciao
    
+
+
    Paragraph with block quote:
    
+
+
    
+
    Quoted
    
+
    
+
+
    Paragraph with header:
    
+
+
+
+
    Paragraph with header on two lines:
    
+
+
+
+
    Paragraph with html after
    
+
+
    
+
+
    Paragraph with html after, indented: Emphasis
    
+
+
    Paragraph with html after, indented: Emphasis tralla Emph
    
+
+
    Paragraph with html after, indented: Emphasis *tralla* Emph
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/lists_after_paragraph.markdown-pl b/vendor/plugins/maruku/tests/others/lists_after_paragraph.markdown-pl
new file mode 100644
index 00000000..d44ac8e7
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/lists_after_paragraph.markdown-pl
@@ -0,0 +1,23 @@
+
    Paragraph, list with no space:
+* ciao
    
+
+
    Paragraph, list with 1 space:
+ * ciao
    
+
+
    Paragraph, list with 3 space:
+   * ciao
    
+
+
    Paragraph, list with 4 spaces:
+    * ciao
    
+
+
    Paragraph, list with 1 tab:
+    * ciao
    
+
+
    Paragraph (1 space after), list with no space: 
+* ciao
    
+
+
    Paragraph (2 spaces after), list with no space: 
    
+* ciao
    
+
+
    Paragraph (3 spaces after), list with no space: 
    
+* ciao
    
diff --git a/vendor/plugins/maruku/tests/others/lists_after_paragraph.md b/vendor/plugins/maruku/tests/others/lists_after_paragraph.md
new file mode 100644
index 00000000..441d39c2
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/lists_after_paragraph.md
@@ -0,0 +1,44 @@
+Paragraph, list with no space:
+* ciao
+
+Paragraph, list with 1 space:
+ * ciao
+
+Paragraph, list with 3 space:
+   * ciao
+
+Paragraph, list with 4 spaces:
+    * ciao
+
+Paragraph, list with 1 tab:
+	* ciao
+
+Paragraph (1 space after), list with no space: 
+* ciao
+
+Paragraph (2 spaces after), list with no space:  
+* ciao
+
+Paragraph (3 spaces after), list with no space:   
+* ciao
+
+Paragraph with block quote:
+> Quoted
+
+Paragraph with header:
+### header ###
+
+Paragraph with header on two lines:
+header
+------
+
+
+Paragraph with html after
+
    
+
+Paragraph with html after, indented:
+     Emphasis
+
+Paragraph with html after, indented: Emphasis *tralla* Emph
+
+Paragraph with html after, indented: Emphasis *tralla* Emph
diff --git a/vendor/plugins/maruku/tests/others/lists_ol.html b/vendor/plugins/maruku/tests/others/lists_ol.html
new file mode 100644
index 00000000..ea4e4c60
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/lists_ol.html
@@ -0,0 +1,60 @@
+
+
+
+
+
+
+
+
      
+
    1. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
      2. 
+
+
    2. Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse id sem consectetuer libero luctus adipiscing.
      3. 
+
+
    3. Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse id sem consectetuer libero luctus adipiscing
      4. 
+
+
    4. Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse id sem consectetuer libero luctus adipiscing
      5. 
+
+
    5. Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse id sem consectetuer libero luctus adipiscing.
      6. 
+
    
+
+
    Ancora
    
+
+
      
+
    1. 
+
      This is a list item with two paragraphs. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
      
+
+
      ATTENZIONE!
      
+
+
        
+
      • Uno
        • 
+
+
      • Due 1. tre 1. tre 1. tre
        • 
+
+
      • Due
        • 
+
      
+
      2. 
+
+
    2. 
+
      Suspendisse id sem consectetuer libero luctus adipiscing.
      
+
      3. 
+
    
+
+
    Ancora
    
+
+
      
+
    • 
+
      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 dolo sit amet, consectetuer adipiscing elit
      
+
      • 
+
+
    • 
+
      Another item in the same list.
      
+
      • 
+
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/lists_ol.md b/vendor/plugins/maruku/tests/others/lists_ol.md
new file mode 100644
index 00000000..3e5d699e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/lists_ol.md
@@ -0,0 +1,39 @@
+1.   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
+    Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
+    viverra nec, fringilla in, laoreet vitae, risus.
+ 2.   Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+    Suspendisse id sem consectetuer libero luctus adipiscing.
+3.   Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+Suspendisse id sem consectetuer libero luctus adipiscing.
+ 3.  Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+Suspendisse id sem consectetuer libero luctus adipiscing.
+ 4.  Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
+ Suspendisse id sem consectetuer libero luctus adipiscing.
+
+Ancora
+
+1.  This is a list item with two paragraphs. Lorem ipsum dolor
+    sit amet, consectetuer adipiscing elit. Aliquam hendrerit
+    mi posuere lectus.
+
+    ATTENZIONE!
+
+    - Uno
+    - Due
+      1. tre
+      1. tre
+      1. tre
+    - Due
+
+2.  Suspendisse id sem consectetuer libero luctus adipiscing.
+
+
+Ancora
+
+*   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.
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/misc_sw.html b/vendor/plugins/maruku/tests/others/misc_sw.html
new file mode 100644
index 00000000..493c4251
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/misc_sw.html
@@ -0,0 +1,92 @@
+
+
+
+
+Software not painful to use
+
+
+
    General
    
+
+
      
+
    • Operating System : Mac OS X: heaven, after the purgatory of Linux and the hell of Windows.
      • 
+
+
    • Browser: Firefox. On a Mac, Camino.
      • 
+
+
    • Email: GMail, "search, don't sort" really works.
      • 
+
+
    • Text Editor: TextMate, you have to buy it, but it's worth every penny. There are rumours that it's been converting (recovering) Emacs users (addicts). Unfortunately, it's Mac only. An alternative is jedit (GPL, Java).
      • 
+
    
+
+
    Development
    
+
+
      
+
    • 
+
      Build system: cmake, throw the autotools away.
      
+
      • 
+
+
    • 
+
      Source code control system: ditch CVS for subversion.
      
+
      • 
+
+
    • 
+
      Project management: Trac tracks everything.
      
+
      • 
+
+
    • 
+
      Scripting language: Ruby is Japanese pragmatism (and has a poignant guide). Python, you say? Python is too academic and snob:
      
+
+
      $ python       
+Python 2.4.1 (\#1, Jun  4 2005, 00:54:33) 
+Type "help", "copyright", "credits" or "license" for more information.
+>>> exit
+'Use Ctrl-D (i.e. EOF) to exit.'
+>>> quit
+'Use Ctrl-D (i.e. EOF) to exit.'
      
+
      • 
+
+
    • 
+
      Java IDE: JBuilder is great software and has a free version (IMHO better than Eclipse). Java is not a pain anymore since it gained generics and got opensourced.
      
+
      • 
+
+
    • 
+
      Mark-up language: HTML is so 2001, why don't you take at look at Markdown? Look at the source of this page.
      
+
      • 
+
+
    • 
+
      C+ libraries:  QT for GUIs. * GSL for math. * Magick++ for manipulating images. * Cairo for creating PDFs. * Boost for just about everything else.
      
+
      • 
+
    
+
+
    Research
    
+
+
      
+
    • Writing papers: LaTeX
      • 
+
+
    • Writing papers & enjoying the process: LyX
      • 
+
+
    • Handsome figures in your papers: xfig or, better, jfig.
      • 
+
+
    • The occasional presentation with many graphical content: OpenOffice Impress (using the OOOlatex plugin); the alternative is PowerPoint with the TexPoint plugin.
      • 
+
+
    • Managing BibTeX: jabref: multi-platform, for all your bibtex needs.
      • 
+
+
    • IEEExplore and BibTeX: convert citations using BibConverter.
      • 
+
    
+
+
    Cool websites
    
+
+
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/misc_sw.md b/vendor/plugins/maruku/tests/others/misc_sw.md
new file mode 100644
index 00000000..2ba51cc1
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/misc_sw.md
@@ -0,0 +1,105 @@
+Subject: Software not painful to use
+Subject_short: painless software
+Topic: /misc/coolsw
+Archive: no
+Date: Nov 20 2006
+Order: -9.5
+inMenu: true
+
+
+### General ###
+
+* *Operating System* : [Mac OS X][switch]: heaven, after the purgatory of Linux 
+  and the hell of Windows.
+* *Browser*: [Firefox][firefox]. On a Mac, [Camino][camino].
+* *Email*: [GMail][gmail], "search, don't sort" really works.
+* *Text Editor*: [TextMate][textmate], you have to buy it, but it's worth every
+  penny. There are rumours that it's been converting (recovering) Emacs
+  users (addicts). Unfortunately, it's Mac only. An alternative is
+  [jedit][jedit] (GPL, Java).
+
+### Development ###
+
+* *Build system*: [cmake][cmake], throw the [autotools][autotools] away.
+* *Source code control system*: ditch CVS for [subversion][subversion].
+* *Project management*: [Trac][trac] tracks everything.
+* *Scripting language*: [Ruby][ruby] is Japanese pragmatism (and has a [poignant][poignant] guide). 
+   Python, you say? Python is too academic and snob:
+
+      $ python       
+      Python 2.4.1 (\#1, Jun  4 2005, 00:54:33) 
+      Type "help", "copyright", "credits" or "license" for more information.
+      >>> exit
+      'Use Ctrl-D (i.e. EOF) to exit.'
+      >>> quit
+      'Use Ctrl-D (i.e. EOF) to exit.'
+
+* *Java IDE*: [JBuilder][jbuilder] is great software and has a free version (IMHO better than Eclipse). Java
+ is not a pain anymore since it gained [generics][java-generics] and got opensourced.
+* *Mark-up language*: HTML is so 2001, why don't you take at look at [Markdown][markdown]? [Look at the source of this page](data/misc_markdown.png).
+* *C++ libraries*: 
+    * [QT][qt] for GUIs.
+    * [GSL][gsl] for math.
+    * [Magick++][magick] for manipulating images.
+    * [Cairo][cairo] for creating PDFs.
+    * [Boost][boost] for just about everything else.
+
+
+### Research ###
+
+* *Writing papers*: [LaTeX][latex]
+* *Writing papers & enjoying the process*: [LyX][lyx]
+* *Handsome figures in your papers*: [xfig][xfig] or, better, [jfig][jfig].
+* *The occasional presentation with many graphical content*: 
+  [OpenOffice Impress][impress] (using the [OOOlatex plugin][ooolatex]); 
+  the alternative is PowerPoint with the [TexPoint][texpoint] plugin.
+* *Managing BibTeX*: [jabref][jabref]: multi-platform, for all your bibtex needs.
+* *IEEExplore and BibTeX*: convert citations using [BibConverter][bibconverter].
+
+### Cool websites ###
+
+* *Best site in the wwworld*: [Wikipedia][wikipedia]
+* [Mutopia][mutopia] for sheet music; [the Gutenberg Project][gutenberg] for books; [LiberLiber][liberliber] for books in italian.
+* *Blogs*: [Bloglines][bloglines]
+* *Sharing photos*: [flickr][flickr] exposes an API you can use.
+
+
+[firefox]:   http://getfirefox.com/
+[gmail]:     http://gmail.com/
+[bloglines]: http://bloglines.com/
+[wikipedia]: http://en.wikipedia.org/
+[ruby]:      http://www.ruby-lang.org/
+[poignant]:  http://poignantguide.net/ruby/
+[webgen]:    http://webgen.rubyforge.org/
+[markdown]:  http://daringfireball.net/projects/markdown/
+[latex]:     http://en.wikipedia.org/wiki/LaTeX
+[lyx]:       http://www.lyx.org
+[impress]:   http://www.openoffice.org/product/impress.html
+[ooolatex]:  http://ooolatex.sourceforge.net/
+[texpoint]:  http://texpoint.necula.org/
+[jabref]:    http://jabref.sourceforge.net/
+[camino]:    http://www.caminobrowser.org/
+[switch]:    http://www.apple.com/getamac/
+[textmate]:  http://www.apple.com/getamac/
+[cmake]:     http://www.cmake.org/
+[xfig]:      http://www.xfig.org/
+[jfig]:         http://tams-www.informatik.uni-hamburg.de/applets/jfig/
+[subversion]:   http://subversion.tigris.org
+[jbuilder]:     http://www.borland.com/us/products/jbuilder/index.html
+[flickr]:       http://www.flickr.com/
+[myflickr]:     http://www.flickr.com/photos/censi
+[bibconverter]: http://www.bibconverter.net/ieeexplore/
+[autotools]:    http://sources.redhat.com/autobook/
+[jedit]:        http://www.jedit.org/
+[qt]:           http://www.trolltech.no/
+[gsl]:          http://www.gnu.org/software/gsl/
+[magick]:       http://www.imagemagick.org/Magick++/
+[cairo]:        http://cairographics.org/
+[boost]:        http://www.boost.org/
+[markdown]:     http://en.wikipedia.org/wiki/Markdown
+[trac]:         http://trac.edgewall.org/
+[mutopia]:      http://www.mutopiaproject.org/
+[liberliber]:   http://www.liberliber.it/
+[gutenberg]:    http://www.gutenberg.org/
+[java-generics]: http://java.sun.com/j2se/1.5.0/docs/guide/language/generics.html
+
diff --git a/vendor/plugins/maruku/tests/others/one.html b/vendor/plugins/maruku/tests/others/one.html
new file mode 100644
index 00000000..dd72f1c8
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/one.html
@@ -0,0 +1,14 @@
+
+
+
+
+
+
+
+
    One line
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/one.md b/vendor/plugins/maruku/tests/others/one.md
new file mode 100644
index 00000000..7452380b
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/one.md
@@ -0,0 +1 @@
+One line
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/paragraphs.html b/vendor/plugins/maruku/tests/others/paragraphs.html
new file mode 100644
index 00000000..97ca3038
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/paragraphs.html
@@ -0,0 +1,21 @@
+
+
+
+
+
+
+
+
    Paragraph 1
    
+
+
    Paragraph 2
    
+
+
    Paragraph 3 Paragraph 4 Paragraph Br->
    
+Paragraph 5
    
+
+
    Escaping: & { } ! 
    
+
+
    
+
    
+Created by Maruku at 00:19 on Wednesday, January 03rd, 2007.
    
+
diff --git a/vendor/plugins/maruku/tests/others/paragraphs.md b/vendor/plugins/maruku/tests/others/paragraphs.md
new file mode 100644
index 00000000..2fc20f52
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/paragraphs.md
@@ -0,0 +1,13 @@
+Paragraph 1
+
+Paragraph 2
+
+
+Paragraph 3
+Paragraph 4
+Paragraph Br->  
+Paragraph 5
+
+
+
+Escaping: & { } [ ] ! 
diff --git a/vendor/plugins/maruku/tests/others/sss06.html b/vendor/plugins/maruku/tests/others/sss06.html
new file mode 100644
index 00000000..e227a0a7
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/sss06.html
@@ -0,0 +1,227 @@
+
+
+  A report about Oxford and the 2006 SLAM Summer SchoolA report about Oxford and the 2006 SLAM Summer School
    Let me quote the words of a renowned Oxford scholar:
    "Life is too important to be taken seriously."
    If you do not wholeheartedly agree with this statement, please stop reading this.
    I stayed three weeks in Oxford: one week for the SLAM school and, before that, two weeks for an English course. You might ask: why? A very good question indeed - "Why I am not on a sunny beach?" - I kept asking myself as I walked down the misty alleys of the old town, wearing a scarf on August, 16th, and realizing that - maybe - I would not need the three pairs of shorts and the swimsuit I had brought.
    Summary:
    1. The Queen's English
    2. The Harry Potter experience
    3. Parsnip, Marmite and the tea conspiracy
    4. The Summer School
    5. Minor open issues in SLAM 
    Appendix: How to offend seven nationalities at once
    I. The Queen's English
    It turns out that a course of English at an advanced level is mostly about vocabulary and idioms: by the end of the first week I knew seven different ways to address a "promiscuous" woman, and I can tell which ones are applicable to American and which to British English. It remains to be seen how this will benefit my academic writing.
    It was a lot of fun to learn the differences (or, as the teacher put it, "to purify my English after years of prolonged unhealthy exposure to American media"), which are not only linguistic, but above all in attitude and social norms. For example, in the US the first question that people ask you is "What do you do?" (meaning: "How much do you earn?"), while in England such a question would be felt as unnecessary direct and impolite. As a rule, it is compulsory to exchange comments about the weather, and there is a lot of specialized vocabulary for this; the following table might prove handy to understand your acquaintance:
    • "It's a lovely day!" = "It doesn't rain"
    • "It's a nice day!" = "It doesn't rain heavily"
    • "What a wonderful day!"="This morning, at 10:13, I caught a glimpse of the sun"
    (the correct answer to any of these is "isn't it?")
    II. The Harry Potter experience
     flickr: http://www.flickr.com/photos/censi/232006603/
    During my three-week stay I tried my best to immerse myself in the English atmosphere.
    I went to a place called Oxford Story 3, where we paid £7 to go through a painfully slow indoor ride, sat on a mobile school-desk in the dark for 25 minutes. It is the claustrophobic equivalent of the American Epcot center in Disney World.
    At Epcot, I learned that the final goal of all the scientific progress in the last three millennia was to let Walt Disney broadcast Snow White using Siemens equipment (Siemens sponsored the ride). In Oxford, I learned that the glorious University is the repository of all human knowledge, and that the English understatement is a legend. At the end of the ride, I was amazed that in Italy I had managed to learn to read and write.
     flickr: http://www.flickr.com/photos/censi/232023681/
    Still, one thing the ride did not explain is how the well-educated, smart elite students of Oxford can possibly find rowing fun -- (probably it IS fun, compared to cricket).
     flickr: http://www.flickr.com/photos/censi/232529032/
    I went to a candle-light baroque concert in the Exeter college chapel. The ensemble was 75% Asian, all Oxford researchers, and we were given a twenty minute speech about the effort they put in the historical research of this obscure composer, that they had a microfilm of the original manuscript delivered from a German library, that the viola would be played in the original style, blah blah blah. Only in Oxford!
     flickr: http://www.flickr.com/photos/censi/232031895/
    I read "The Hobbit" (Tolkien was a fellow of Exeter college) - I discovered that the only two peoples in the known and invented universes to have the concept of a "second breakfast" are Hobbits and Italians.
    I watched a performance of MacBeth at an open-air theatre. I couldn't understand but one sentence, which is worth mentioning: "Alcohol provokes the desire, but it takes away the performance"
    Regarding alcohol, England is one of the places where you can't drink if you are under 21 (in Italy, at 18 you have decided to quit). Young people have their ID checked at the entrance of pubs and in liquor stores: that's only a minor annoyance, as they just need to wait outside the store for the first Spanish guy passing by that will buy the wine for them (and be compensated with just the change - did you keep the penny, Felix?).
    Anyway the guys at the door use the ID checking mostly as a form of flattery: "You are 32? I thought you were 20!" is probably the best pick-up line that the English can come up with.
    The other characteristic thing is that in English pubs there is no table service: you have to walk to the bar and ask by yourself. The first time can be confusing: and you can spend quite some time waiting at the table whining about the "poor service".
    III. Parsnip, Marmite & the tea conspiracy
    During the first week I was a guest of a lovely 79-year-old lady. Working at the University, she made a point of speaking very posh English. And she made a point of cooking traditional English food. The typical English dish is some meat with two vegetables aside. For the vegetables, pick any two in {parsnip, carrot, potato}.
    Don't look in your dictionary for a translation of "parsnip" as probably there isn't one. The lady would tell me that in the next-to-last century, this famous professor spent years raising the finest crossbreed of Parsnip as to finally obtain what is best described as a big white carrot with no taste whatsoever 4.
    Nevertheless, the many regional variants give spectacular variety to the English cuisine: the two vegetables can be boiled, fried, baked, microwaved, or roasted. There exist also exotic twists, in which the vegetables are put on top of the meat, or underneath, or even inside. In important occasions, the recipes stay the same but gain a French name.
     flickr: http://www.flickr.com/photos/censi/232526897/
    I tried a thing called Marmite, which the teacher sold to me as "the British answer to Nutella". It has the aspect and consistency of engine grease, and, as far as I know, also the taste is similar (I've never tasted the grease, but next time, presented with choice, I'd give it a go).
    The austerity of English food can be explained by the pitiless weather; but how can you explain Marmite, if not with alimentary masochism?
    But... there's one thing that is much better in England: tea. Wherever I tried it (at the old lady's, at tearooms, at coffee breaks) it was sooo delicious. In Italy we don't get the real thing. Why is that? Is this some sort of conspiracy orchestrated by the Italian coffee producers? And is it the tea cartello which does not allow good coffee to be imported in England?
    IV. The Summer School
    If you go for a career in research, in general you don't get much money, or fame, and you don't get to rescue the princess either. The two benefits that you do get are: playing with very expensive toys and the occasional trip in which you meet all sort of people.
    And when you talk with them, it's sort of strange to realize that your interlocutor is one of the 5 people - worldwide - that actually care about your research theme, and yet the things you have in common end there, as he has different culture, race, religion, and while you two happen to agree that Lie brackets are an indispensable tool to characterize the propagation of errors on the Euclidean group, you have very different answers to the important questions about life, the universe and everything. (In these cases I have anecdotal proof that it is much better to stick to research talk, and to avoid at all costs the kind of jokes that you can find in the Appendix).
    Instead, at this particular school, I would say that the European character was clearly perceived, and I enjoyed it -- but whether England is in Europe is a delicate matter.
    Here are some impressions of the people.
    • Juan Domingo Tardos (aka Mingo) is the funniest of the bunch, the man you want to go partying with.
      He taught us two deep truths about SLAM and life: 1. The size of your banana matters. 2. Never under-estimate the size of your lemons.
      I thought: wow, I want to write a paper with "banana" in the title - finally some inspiration from the school! I already had big projects for Fig. 1,2 and a full-page Fig. 3, but after a little googling I found: "Functional Programming with Bananas, Lenses, Envelopes and Barbed Wire"5 "Dealing with large bananas" 6. I gave up: I cannot beat this last one. And the existence of 6 proves once again that SLAM is a solved problem.
    • Paul Newman, the organizer, told us, more than once, that the future of SLAM is in long term operation if we want the systems to be reliable. (Personally, I disagree: I think that it is possible to build anything at the desired level of reliability, given reasonable funding, time, and an appropriate number of German engineers)
    • One of the lessons learned in the school is that almost everything has already been done by someone else. More specifically, most of the things have already been done by Durrant-Whyte some twenty years ago, when men were men, CS was electrical engineering, master students knew calculus, and Kalman filters ran free in the wild lands of Australia.
    • Frank Dellaert is a jolly chap as well, and he does interesting things with graphs. As he introduced three different formalisms in the first three slides, I regretted not to have put more CS in my curriculum, then shut my eyes. Interestingly, at summer schools and conferences, if you close your eyes people assume that you are very smart and that you are thinking about some new impressive algorithm -- I was just dreaming of a sunny beach.
    • Henrik Christensen has implemented SLAM on the cleaning robot for $45 in sensors and electronics. It puts things in perspective, especially if you consider that I paid £16 for a one-hour coach trip from Heathrow to Oxford.
    • Andy Davison is a wonderful person, he tutored the practicals with infinite patience. Never did I meet such a knowledgeable, affable, and humble person. (Probably he is the kind of person that some day will show up at work with automatic guns)
    • Wolfram Burgard - he wins my "best robot" award for the photo of our beloved Albert 7.
    • Dieter Fox wins "most nostalgic slide from the 90s": and every time we feel the same emotion as the first time.
    • Kurt Konolige reminded me why I bought a Mac.
    • Simon Lacroix - Once we sat at the same table during lunch. While he talked with Dellaert, he would send me alarmed glances, the kind of glances that you would reserve to a relative returning from death. I wanted to ask him why, but then I decided I'd better not to (was I so wasted from the night before?).
    • Simon Julier -- he seems very smart, but he lost me between slide #3 and #4. I started to be seasick from all those covariance matrices - so I muttered to my neighbours: "I wonder whether it still holds in higher-dimensional spaces...", then I closed my eyes and was back again on the sunny beach.
    • But all in all, the most interesting presentation was the magical show that Davide Scaramuzza (who at daytime pretends to work at ETHZ) gave to a selected audience after the banquet (8). It was another confirmation that all the time spent in front of a monitor is, in fact, wasted, and all of us should have studied card tricks instead: you have NO IDEA of how a girl's face brightens up and her eyes expand when she watches a magician.
    V. Other minor issues in SLAM
    We all know that the most important open problem in SLAM is that there are not enough women doing research in the area and coming at summer schools. As for the other minor issues, this is the result of asking "What is the future of SLAM?" to a random sampling of the participants. (the list does not include answers given after 10:00 PM)
    • For 30% of the respondents, SLAM is a solved problem, and we just need some German engineers to work out the details of the implementations.
    • Long term operation: make filters that reconsider their decisions at a a later time (so not delaying decisions, but explicitly reconsider).
    • Make it robust for real applications: or, your method should work in more than one experiment and possibly also outside of your lab.
    • Put more knowledge in SLAM about the environment. Teach your filter what is a tree, a road, a mirror so that it can make smarter decisions.
    • Active SLAM and SLAM-guided exploration (once we figure out good acronyms).
    • Some boring work is to be done for taking into account linearization errors in the already existing results about consistency, sparsity, etc.
    • "Where can I get some real coffee?" (2 people)
    • Methods and representations for real sensor fusion (laser, camera, etc).
    • Do robust stuff with a single camera. Omnidirectional cameras are cool. Mix different techniques at different time-scales: visual odometry between frames, then stable features, then databases of places to close the loop (or don't close the loop at all).
    Appendix. How to offend seven nationalities at once
    In Oxford I learned the ultimate rude stereotypical joke -- I think it's worth sharing.
    Heaven & Hell
    In Heaven: the policemen are British, mechanics are German, chefs are French, wives are Japanese, neighbours are Dutch, lovers are Italian, and the Swiss organize it all.
    In Hell: the policemen are German, mechanics are French, chefs are British, neighbours are Japanese, wives are Dutch, lovers are Swiss, and the Italians organize it all.
    For related work, see for example 9, 10.
    And here's the research version:
    The BEST international research project
    • The French do the overall math analysis,
    • a Chinese refines a ten-line proof of the main Theorem,
    • the Germans design the implementation,
    • Japanese undergrads do the actual work,
    • the British write the paper,
    • an American gives the presentation,
    • the Spanish organize the social events,
    • and the Italians organize the banquet.
    The WORST international research project
    • The Germans do the overall math analysis,
    • an American PhD student spends 10 CPU year on his department's 48-node cluster and proves with a Monte Carlo simulation in Matlab tha Theorem 1 indeed holds for some values of the parameters
    • the French design the implementation,
    • one Spanish undergrad does the actual work,
    • the Italians write the papers,
    • a Chinese gives the presentation,
    • the Japanese organize the social events,
    • and the British organize the banquet.
    :-)
     Flickr: http://www.flickr.com/photos/censi/232003838
    References
    [1] http://www.spellingsociety.org/news/media/poems.php
    [2] 
     http://www.flickr.com/photos/censi/236722418/
    [3] 

    //www.oxfords
    y.co.uk](http://www.oxfordstory.co.uk)
    [4] 
    ttp://www.botani
    .com/botanical/mg

    arsni12.html](
    p://www.botanical.com/botanical/mgmh/p/parsni12.html )
    [5] 

    ijer, M. Fokkinga, R
    aterson. "F
    tional Programmin
    ith Bananas, Lenses, Envelopes and Barbed Wire"
    991)
     http://c
    seer.ist.psu.edu/
    jer91functional.
    l
    [6] 
    Lammel, J. Visser, J. Kort. "Dealing

    large bananas" (2000) http://citeseer.ist.psu.edu/lammel00dealing.html
    [7] http://www.informatik.uni-freiburg.de/
    rgard/
    [8] 
    tp://asl.epfl.ch/~scaramuz/cabaret/cabaret.wmv](http://asl.epfl.ch/~scaramuz/cabaret/cabaret.wmv)
    [9] http://www.anth.uconn.edu/faculty/boster/cultvar/euweb/
    [10] http://www.infonegocio.com/xeron/bruno/italy.html 
    Created by Maruku at 02:13 on Monday, January 01st, 2007.
    
diff --git a/vendor/plugins/maruku/tests/others/sss06.md b/vendor/plugins/maruku/tests/others/sss06.md
new file mode 100644
index 00000000..fbe8b4fa
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/sss06.md
@@ -0,0 +1,352 @@
+Category: sss06
+Date: Sep 10 2006
+From: "Andrea Censi" 
+Subject: A report about Oxford and the 2006 SLAM Summer School
+Encoding: BlueCloth FlickrHTML
+format: bluecloth>
+inMenu: true
+
+Let me quote the words of a renowned Oxford scholar:
+
+> "Life is too important to be taken seriously."
+
+If you do not wholeheartedly agree with this statement,
+please stop reading this.
+
+----------------------
+
+I stayed three weeks in Oxford: one week for the SLAM school and,
+before that, two weeks for an English course. You might ask: why?
+A very good question indeed - "Why I am not on a sunny beach?" -
+I kept asking myself as I walked down the misty alleys of the old town,
+wearing a scarf on August, 16th, and realizing that - maybe - I would not
+need the three pairs of shorts and the swimsuit I had brought.
+
+
+Summary:
+
+1. The Queen's English
+2. The Harry Potter experience
+3. Parsnip, Marmite and the tea conspiracy
+4. The Summer School
+5. Minor open issues in SLAM  
+
+> Appendix: How to offend seven nationalities at once
+
+`I`. The Queen's English
+----------------------
+ 
+It turns out that a course of English at an advanced level is mostly
+about vocabulary and idioms: by the end of the first week I knew seven
+different ways to address a "promiscuous" woman, and I can tell which ones
+are applicable to American and which to British English. It remains to be
+seen how this will benefit my academic writing.
+
+It was a lot of fun to learn the differences (or, as the teacher put it,
+"to purify my English after years of prolonged unhealthy exposure to American
+media"), which are not only linguistic, but above all in attitude and
+social norms.
+For example, in the US the first question that people ask you is
+"What do you do?" (meaning: "How much do you earn?"), while in England such
+a question would be felt as unnecessary direct and impolite. 
+As a rule,
+it is compulsory to exchange comments about the weather, and there is a lot
+of specialized vocabulary for this; the following table might prove handy
+to understand your acquaintance:
+
+- "It's a lovely day!" = "It doesn't rain"
+- "It's a nice day!" = "It doesn't rain heavily"
+- "What a wonderful day!"="This morning, at 10:13, I caught a glimpse of the sun"
+
+(the correct answer to any of these is "isn't it?")
+
+`II`. The Harry Potter experience
+-------------------------
+
+  flickr: http://www.flickr.com/photos/censi/232006603/
+
+During my three-week stay I tried my best to immerse myself in the English
+atmosphere.
+
+I went to a place called Oxford Story [3], where we paid £7 to go through a
+painfully slow indoor ride, sat on a mobile school-desk in the dark for 25
+minutes. It is the claustrophobic equivalent of the American Epcot center in
+Disney World.
+
+At Epcot, I learned that the final goal of all the scientific progress in the
+last three millennia was to let Walt Disney broadcast Snow White using
+Siemens equipment (Siemens sponsored the ride).
+In Oxford, I learned that the glorious University is the repository of all
+human knowledge, and that the English understatement is a legend. At the end of
+the ride, I was amazed that in Italy I had managed to learn to read and write.
+
+  flickr: http://www.flickr.com/photos/censi/232023681/
+
+Still, one thing the ride did not explain is how the well-educated,
+smart elite students of Oxford can possibly find rowing fun --
+(probably it IS fun, compared to cricket).
+
+  flickr: http://www.flickr.com/photos/censi/232529032/
+
+I went to a candle-light baroque concert in the Exeter college chapel.
+The ensemble was 75% Asian, all Oxford researchers, and we were given
+a twenty minute speech about the effort they put in the historical
+research of this obscure composer, that they had a microfilm of the original
+manuscript delivered from a German library, that the viola would be played
+in the original style, blah blah blah. Only in Oxford!
+
+  flickr: http://www.flickr.com/photos/censi/232031895/
+
+I read "The Hobbit" (Tolkien was a fellow of Exeter college) - I discovered
+that the only two peoples in the known and invented universes to have
+the concept of a "second breakfast" are Hobbits and Italians.
+
+
+I watched a performance of MacBeth at an open-air theatre.
+I couldn't understand but one sentence, which is worth mentioning:
+"Alcohol provokes the desire, but it takes away the performance"
+
+Regarding alcohol, England is one of the places where you can't drink if you
+are under 21 (in Italy, at 18 you have decided to quit).
+Young people have their ID checked at the entrance of pubs and in liquor
+stores: that's only a minor annoyance, as they just need to wait outside
+the store for the first Spanish guy passing by that will buy the wine for them
+(and be compensated with just the change - did you keep the penny, Felix?).
+
+Anyway the guys at the door use the ID checking mostly as a form of flattery:
+"You are 32? I thought you were 20!" is probably the best pick-up line that
+the English can come up with.
+
+The other characteristic thing is that in English pubs there is no table
+service: you have to walk to the bar and ask by yourself. The first time can
+be confusing: and you can spend quite some time waiting at the table whining
+about the "poor service".
+
+`III`. Parsnip, Marmite & the tea conspiracy 
+---------------------------------------------
+
+During the first week I was a guest of a lovely 79-year-old lady.
+Working at the University, she made a point of speaking very posh English.
+And she made a point of cooking traditional English food.
+The typical English dish is some meat with two vegetables aside.
+For the vegetables, pick any two in {parsnip, carrot, potato}.
+
+Don't look in your dictionary for a translation of "parsnip" as probably
+there isn't one. The lady would tell me that in the next-to-last century,
+this famous professor spent years raising the finest crossbreed of Parsnip as
+to finally obtain what is best described as a big white carrot
+with no taste whatsoever [4].
+
+Nevertheless, the many regional variants give spectacular variety to the
+English cuisine: the two vegetables can be boiled, fried, baked, microwaved,
+or roasted. There exist also exotic twists, in which the vegetables are put
+on top of the meat, or underneath, or even inside.
+In important occasions, the recipes stay the same but gain a French name.
+
+
+   flickr: http://www.flickr.com/photos/censi/232526897/
+
+
+I tried a thing called Marmite, which the teacher sold to me as "the British
+answer to Nutella". It has the aspect and consistency of engine grease, and,
+as far as I know, also the taste is similar (I've never tasted the grease,
+but next time, presented with choice, I'd give it a go).
+
+The austerity of English food can be explained by the pitiless weather; but
+how can you explain Marmite, if not with alimentary masochism?
+
+But... there's one thing that is much better in England: tea. Wherever I tried
+it (at the old lady's, at tearooms, at coffee breaks) it was sooo delicious.
+In Italy we don't get the real thing. Why is that? Is this some sort of
+conspiracy orchestrated by the Italian coffee producers? And is it the
+tea cartello which does not allow good coffee to be imported in England?
+
+`IV`. The Summer School
+---------------------
+
+If you go for a career in research, in general you don't get much money,
+or fame, and you don't get to rescue the princess either.
+The two benefits that you do get are: playing with very expensive toys
+and the occasional trip in which you meet all sort of people.
+
+And when you talk with them, it's sort of strange to realize that your
+interlocutor is one of the 5 people - worldwide - that actually care about your
+research theme, and yet the things you have in common end there, as he has
+different culture, race, religion, and while you two happen to agree that Lie
+brackets are an indispensable tool to characterize the propagation of errors
+on the Euclidean group, you have very different answers to the important
+questions about life, the universe and everything. (In these cases I have
+anecdotal proof that it is much better to stick to research talk, and to
+avoid at all costs the kind of jokes that you can find in the Appendix).
+
+Instead, at this particular school, I would say that the European character was
+clearly perceived, and I enjoyed it -- but whether England is in Europe is a
+delicate matter.
+
+
+Here are some impressions of the people.
+
+ * Juan Domingo Tardos (aka Mingo) is the funniest of the bunch, the man you
+   want to go partying with.
+   
+   He taught us two deep truths about SLAM and life:
+   1. The size of your banana matters.
+   2. Never under-estimate the size of your lemons.
+   
+   I thought: wow, I want to write a paper with "banana" in the title - finally
+   some inspiration from the school! I already had big projects for Fig. 1,2
+   and a full-page Fig. 3, but after a little googling I found:
+   "Functional Programming with Bananas, Lenses, Envelopes and Barbed Wire"[5]
+   "Dealing with large bananas" [6].
+   I gave up: I cannot beat this last one. And the existence of [6] proves
+   once again that SLAM is a solved problem.
+
+ * Paul Newman, the organizer, told us, more than once, that the future of SLAM
+   is in long term operation if we want the systems to be reliable.
+   (Personally, I disagree: I think that it is possible to build anything at
+   the desired level of reliability, given reasonable funding, time, and
+   an appropriate number of German engineers)
+
+ * One of the lessons learned in the school is that almost everything has
+   already been done by someone else.
+   More specifically, most of the things have already been done by
+   Durrant-Whyte some twenty years ago, when men were men, CS was electrical
+   engineering, master students knew calculus, and Kalman filters ran
+   free in the wild lands of Australia.
+
+ * Frank Dellaert is a jolly chap as well, and he does interesting things with
+   graphs. As he introduced three different formalisms in the first
+   three slides, I regretted not to have put more CS in my curriculum, then
+   shut my eyes. Interestingly, at summer schools and conferences, if you close
+   your eyes people assume that you are very smart and that you are thinking
+   about some new impressive algorithm -- I was just dreaming of a sunny beach.
+
+ * Henrik Christensen has implemented SLAM on the cleaning robot for $45
+   in sensors and electronics. It puts things in perspective, especially
+   if you consider that I paid  £16 for a one-hour coach trip from Heathrow
+   to Oxford.
+
+ * Andy Davison is a wonderful person, he tutored the practicals with
+   infinite patience. Never did I meet such a knowledgeable, affable,
+   and humble person. (Probably he is the kind of person that some day will
+   show up at work with automatic guns)
+
+ * Wolfram Burgard - he wins my "best robot" award for the photo of our
+   beloved Albert [7].
+
+ * Dieter Fox wins "most nostalgic slide from the 90s": and every time we feel
+   the same emotion as the first time.
+
+ * Kurt Konolige reminded me why I bought a Mac.
+
+ * Simon Lacroix - Once we sat at the same table during lunch. While he
+   talked with Dellaert, he would send me alarmed glances, the kind of glances
+   that you would reserve to a relative returning from death. I wanted
+   to ask him why, but then I decided I'd better not to (was I so wasted
+   from the night before?).
+
+ * Simon Julier -- he seems very smart, but he lost me between slide #3 and #4.
+   I started to be seasick from all those covariance matrices -
+   so I muttered to my neighbours: "I wonder whether it still holds in
+   higher-dimensional spaces...", then I closed my eyes and was back again on
+   the sunny beach.
+
+ * But all in all, the most interesting presentation was the magical show
+   that Davide Scaramuzza (who at daytime pretends to work at ETHZ) gave to a
+   selected audience after the banquet ([8]).
+   It was another confirmation that all the time spent in front of a monitor is,
+   in fact, wasted, and all of us should have studied card tricks instead:
+   you have NO IDEA of how a girl's face brightens up and her eyes expand when
+   she watches a magician.
+
+`V`. Other minor issues in SLAM 
+--------------------------------
+
+We all know that the most important open problem in SLAM is that there are
+not enough women doing research in the area and coming at summer schools.
+As for the other minor issues, this is the result of asking
+"What is the future of SLAM?" to a random sampling of the participants.
+(the list does not include answers given after 10:00 PM)
+
+ - For 30% of the respondents, SLAM is a solved problem, and we just need some
+   German engineers to work out the details of the implementations.
+ - Long term operation: make filters that reconsider their decisions at a
+   a later time (so not delaying decisions, but explicitly reconsider).
+ - Make it robust for real applications: or, your method should work in more
+   than one experiment and possibly also outside of your lab.
+ - Put more knowledge in SLAM about the environment. Teach your
+   filter what is a tree, a road, a mirror so that it can make smarter
+   decisions.
+ - Active SLAM and SLAM-guided exploration (once we figure out good acronyms).
+ - Some boring work is to be done for taking into account linearization errors
+   in the already existing results about consistency, sparsity, etc.
+ - "Where can I get some real coffee?" (2 people)
+ - Methods and representations for real sensor fusion (laser, camera, etc).
+ - Do robust stuff with a single camera. Omnidirectional cameras are cool.
+   Mix different techniques at different time-scales: visual odometry between
+   frames, then stable features, then databases of places to close the loop
+   (or don't close the loop at all).
+
+Appendix. How to offend seven nationalities at once
+--------------------------------------------------
+
+In Oxford I learned the ultimate rude stereotypical joke -- I think it's
+worth sharing.
+
+> **Heaven & Hell**
+>
+> *In Heaven*: the policemen are British, mechanics are German, chefs are French,
+> wives are Japanese, neighbours are Dutch, lovers are Italian,
+> and the Swiss organize it all.
+>
+> *In Hell*: the policemen are German, mechanics are French, chefs are British,
+> neighbours are Japanese, wives are Dutch, lovers are Swiss,
+> and the Italians organize it all.
+
+For related work, see for example [9], [10].
+
+
+And here's the research version:
+
+> **The BEST international research project**
+> 
+> - The French do the overall math analysis,
+> - a Chinese refines a ten-line proof of the main Theorem,
+> - the Germans design the implementation,
+> - Japanese undergrads do the actual work,
+> - the British write the paper,
+> - an American gives the presentation,
+> - the Spanish organize the social events,
+> - and the Italians organize the banquet.
+> 
+> **The WORST international research project**
+> 
+> - The Germans do the overall math analysis,
+> - an American PhD student spends 10 CPU year on his department's 48-node
+> cluster and proves with a Monte Carlo simulation in Matlab that
+> Theorem 1 indeed holds for some values of the parameters,
+> - the French design the implementation,
+> - one Spanish undergrad does the actual work,
+> - the Italians write the papers,
+> - a Chinese gives the presentation,
+> - the Japanese organize the social events,
+> - and the British organize the banquet.
+
+`:-)`
+
+  Flickr: 
+
+References
+----------
+
+\[1\]   [http://www.spellingsociety.org/news/media/poems.php](http://www.spellingsociety.org/news/media/poems.php)  
+\[2\] dde [http://www.flickr.com/photos/censi/236722418/](http://www.flickr.com/photos/censi/236722418/)  
+\[3\]  [http://www.oxfordstory.co.uk](http://www.oxfordstory.co.uk)  
+\[4\]   [http://www.botanical.com/botanical/mgmh/p/parsni12.html](http://www.botanical.com/botanical/mgmh/p/parsni12.html  )  
+\[5\]  E. Meijer, M. Fokkinga, R. Paterson. "Functional Programming with Bananas, Lenses, Envelopes and Barbed Wire" (1991)  
+ [http://citeseer.ist.psu.edu/meijer91functional.html](http://citeseer.ist.psu.edu/meijer91functional.html)  
+\[6\]  R. Lammel, J. Visser, J. Kort. "Dealing with large bananas" (2000)   
+\[7\]  [http://www.informatik.uni-freiburg.de/~burgard/](http://citeseer.ist.psu.edu/lammel00dealing.html)  
+\[8\]  [http://asl.epfl.ch/~scaramuz/cabaret/cabaret.wmv](http://asl.epfl.ch/~scaramuz/cabaret/cabaret.wmv)  
+\[9\]  [http://www.anth.uconn.edu/faculty/boster/cultvar/euweb/](http://www.anth.uconn.edu/faculty/boster/cultvar/euweb/)  
+\[10\]  [http://www.infonegocio.com/xeron/bruno/italy.html](http://www.infonegocio.com/xeron/bruno/italy.html)  
diff --git a/vendor/plugins/maruku/tests/others/style.css b/vendor/plugins/maruku/tests/others/style.css
new file mode 100644
index 00000000..8ed5c03b
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/style.css
@@ -0,0 +1,27 @@
+
+BODY {
+	font-size: .7em;
+	max-width: 40em;
+}
+
+PRE {
+	margin-left: 3em;
+	background-color: #eef;
+	padding: 3px;
+}
+
+DL,DT,DD { padding: 5px; margin: 10px;}
+DL { border: solid 3px black;}
+DT { border: solid 3px blue;}
+DD { border: solid 3px red;}
+
+P { border: solid 3px #888;}
+
+
+TR { border: solid 2px #888; padding: 3px;}
+TD,TH { border: solid 1px #888; padding: 3px; margin: 3px; }
+
+TABLE { border: solid 4px black; padding: 3px;}
+TBODY, THEAD { border: solid 3px #888; padding: 3px;}
+
+IMG { min-width: 40px; min-height: 40px; border: solid 2px yellow;}
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/others/test.html b/vendor/plugins/maruku/tests/others/test.html
new file mode 100644
index 00000000..cc205fcf
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/test.html
@@ -0,0 +1,24 @@
+
+
+  
           $ python       
+
+
    Created by Maruku at 02:05 on Monday, January 01st, 2007.
    
diff --git a/vendor/plugins/maruku/tests/others/test.md b/vendor/plugins/maruku/tests/others/test.md
new file mode 100644
index 00000000..96ecb936
--- /dev/null
+++ b/vendor/plugins/maruku/tests/others/test.md
@@ -0,0 +1,4 @@
+
+           $ python       
+
+
diff --git a/vendor/plugins/maruku/tests/s5/s5profiling.md b/vendor/plugins/maruku/tests/s5/s5profiling.md
new file mode 100644
index 00000000..fbf6caf4
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/s5profiling.md
@@ -0,0 +1,48 @@
+subtitle: news
+author: Andrea Censi
+company: Università La Sapienza
+css: math.css
+
+RDK news
+========
+
+Profiling
+---------------------------------------------------------
+
+1. `ragent2` writes profiling information on a pipe.
+2. `rdk-profiler` reads the pipe and creates graphs in HTML+Javascript.
+3. The user reads the data on a browser. 
+
+Things logged
+-----------------------------------------------------------
+
+	17288397 1730000 0 16384 END pantiltClient 
+	17288439 1730000 0 16384 START pantiltClient 
+	17288564 1730000 0 16384 LOCK pantiltClient:tilt 
+	17288622 1730000 0 16384 UNLOCK pantiltClient:tilt
+
+* `START/END`: how much does it take to ...?
+
+Footnotes 1/2
+---------------------------------------------------
+
+You can use footnotes [^1]
+
+[^1]: And they work.
+
+Footnotes 2/2
+---------------------------------------------------
+
+Each footnote on its page [^2]
+
+[^2]: alone.
+
+And now: math!
+---------------------------------------------------
+
+Consider, for example the group $\int_{a}^{b} x^{a} db$ of 
+
+\[         \alpha_{\beta}^{\gamma} \]
+
+Unfortunately S5 and MathML are mutually exclusive. 
+See  for explanations.
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/s5/ui/default/blank.gif b/vendor/plugins/maruku/tests/s5/ui/default/blank.gif
new file mode 100644
index 0000000000000000000000000000000000000000..75b945d2553848b8b6f41fe5e24599c0687b8472
GIT binary patch
literal 49
zcmZ?wbhEHbWMp7unE0RJ|Ns9C3=9Vj8~~DvKUo+V7?>DzfNY>Fh|Ltj$Y2csQN9XW

literal 0
HcmV?d00001

diff --git a/vendor/plugins/maruku/tests/s5/ui/default/bodybg.gif b/vendor/plugins/maruku/tests/s5/ui/default/bodybg.gif
new file mode 100755
index 0000000000000000000000000000000000000000..5f448a16fe6dc7a03a4279fb19f9ba3af38eb634
GIT binary patch
literal 10119
zcmZX3S5T7;xAl`i3Q6cCp@jeeLNy3T$0YP70qM=qy9N+cUc}Hl(gj2a9YJ~#6*W`=
z6=@&2)5qwt!QhQ8vJ0vHJS@?%%&Z
zK0ZD@J-xWNxU#acy}kYU^XKp1zyJTiX8&*Q|EagXf1h4iS=`=U`TTi&aq<3tmbbTo
z|5MUGIYIvgRsP%ldlP`LSEaGfVni3dkn$=h_24H*;kJyvh4_<-NG4^`kD!7uJ9lS6
zU8Iz=r;!E9GcgTlZu_G$PmchLTn~EmvUZMM`F8(R#=?LBqUG+$EI|jw8(@eK5`{;)
z`df2R(<2S|bi(v}kU}Q9P8wY1C_Zj|7hzG4tHJgjT%xIEHYi~WEu`r29-*YhI|k7*
zyxdB$yfO?1kAp#&^Ho)AK-YcKGd*K5?OoH2Sd=X%E$+Bxw1&9
z(%P=T$`mA)oBd#|;heV-Os1VoLH_=0H*qy~4w~-96SyJmEjd|~Cr%$ceAF}Pb<+JY
z&UlJ`yYIwW@RsPUloS;m*G`i5B4yC&&}>+BNa_E||2vggX@uLZ?Y5#Vj~oSe9QG9c6I<78&I!r~%gz
ziZ5!^;)2vJ%_rluN`P5bar_)9-T;gnj*-LCuELL}G!{CaYPpCZy(;5h60~xXONQ`0
zal}iE+ZMd_)}NVUTs6Ql{0s4W(%xCn`#)v4>Cgj=;DmJ3!aqAs(X-clZT5qBd6%@4
z=_172Ygb^JtVY+=X`HOVB};^J)+y*1=b4b9%m&;vNa+k=nSdihxidoFRb0j5q$}rC
zPH^11Q!Fnn+YlM@TBAD@jVUk$T9qUWh5hBT8C5gyCDvp7^K*JDWa{)fI=^tR(R+Q`
zro~!3zxQqde>6Y@hFE8~QC=^GH~0Pc=?dqfuBNc&XwwgE17hM?ppb?zr^ZEWKaQ@poO#_^%*oyAHq$@~Dx8R?-!+fH_yQeXoW!V&)UH_kj
znQ36SkN|n=;QX5%Czpz-5l_wZf@2APOJ4L$DL?B><%d{$s
zjxvT_*P8t_?j)@AQFWU&dG~xydaM&N7uq3k&d^WUMYeE=>6wl}>ROUOW4@^tq}%h7
zr{R`wf{s!~eP{Uoj^9ZCYY5p``IMWsp_CZ?k&i3#@Y+I7?BGfc*vKY%AZA~u
z9Np15F%#l|`{?Sss7(AWEcl0s2|g<;dtD$d`p|}tn<|yQJ<(Ed4OLLqr2)2l(roa~
zM$b&!iO?IjD_b!W
z?ktdJ9gu5VBb!57MP1inP13t?D*MmO^pOR-S)=
zKI{-Pk{Dhpj#l>{^g6&iP-%o?^##Yo6ky1BPbXos0GQafp#QTs%-JM7{($K9?h
zU|>O@oJ3H=_mX=#Z=*<|+}>e8<#)55yO%?*1t~mEb`j0(y)$!G-+X3Tuz8gSO(5~4
z$&|gkdkqZU_kh?Hr9H&c)H{_N0nXJM5BZvkXXVD~_c*ez@tfxPx|?ida9$T;zg1Q_pUL-2e6L{&_aFY)+A1-a#~lleKjMc@?A
z`V#9Ld(BG0ases_2*h%wwSGKn6kj8|;{6k|taD!D7@eZyQ9;`mg}53z7Qa=+fej-H
zQp{!*+bZM6`L4g@D`Bks
zRNxs{#W+nCN2AsOJRRYFmC`oM;+f#XTPFx*hIa_3$K#BZh&Dwinw=Qoe0Xj
z;UQA=!K5=bzW}Ir!zQF9-uqBfj^ca06xZT-{smER19&s3SYg-olmK$ta}KFvHC#+M
z(S0v)K{(E)Oo+W_EDNWS5Gi%_)xp|Pb>&mnqjUsfR@&SJI02Z34Czh+QaS%*!I13h#?-u{`cNWL`9q;`6rrqg
zS=M1O{~k8uYdHQG`p0uBD!^^>01$qx3+>a-f~YM)FAEUOX3B>Jn>~KMtJP}|J+{u}
z8jio^3Qtv_({x&r(+cf}rq-kBaD2Gf2LgIX%9DcI^oW5;IbVo7pp*w1++U~eOh&ao
zoND!dsP&%b$@l&Fi*-XQ9+{zgd58V?!=5qKG-~Y4$8)*h^&h@?%z^K$5@D0i5+O6f-
zqi4W_EO3jQ;oVqfldgC
zE+z^ijn}7LrR!=k;h`yj>ZXLi_td8&;2-&?FI+UI2E%yruY{CkJztg6V?x+pBf0XV
z37Bq)(C7MM-I#VirE9CMc{*n&%rmv5;SHzl?(`4}jiCyi0__d}o|OY*z#h;+@q8%5
ziDMRJki1eZ!g=~$4W<-Fuj@2OozW*6Yo`DtAu22--}UY&*ETFCgD$#}EWJmQJWGel
z&Vcvpc^fl87AdisDbQO?*}tW!%rUOk{QTBcQvdhZjnR|+`>2?G9y(yWH_`VF
zI5(UEzxbD)IVAcrFy=E-fpjov30lqPQ~2}j2#e?T4F6L;(J-niZ;Z|+l-Ign;yn$l
zA%eiwm9asQLDT?uzLSQ-@tA!WzcVtItNnpSA<_%TOsu6TSfU#RLCwOO@q)u2M$i!-=X*a@D7(tEZX8
z)&9Ky(A2*3391*CB#~W^3W}?Wo~{~v_1~h?zwga*LS~}zziKDUFHZF+&D&`7*Adiwf
zyU;6l7zyPA=A|Wb1yClP{3`u5dz&(jL2ykIb-xpoy)Nu|m_Jk*L^!);ZcNC;S
zFEdUI_I@92Fl159Y`7v1_I}U9zOV!+GPoWduQI6-@}A^wx`>3+oivCVCUdbb!FnO~
zu~>7&+d!lXF|9p!e
z3VjYn&N^GPl%u;tG+oBcff<*TgS@HGlW8t3-hIilp>6IiZLv5ouDmTqI-zS(rZp4&
zoFQhq-TswRXoaTvhA!N{2Dmkzh3`jxjgz+T?3%u-SmRI_bm#)3*Qv~;ya;L6fW~mS
ziIJ)NE76$n)6QQ_A~)5w9a#KFAm|OV4$@3)P)=Acy
zn3cVAD%Hgf2nmnje>~JPAKj%-R3iiZNxz{{2Rgi~QrKSD-3H$4L$Kl1EB2AeQZ?aW
z(OM}p*`7&#jYY{-A2=LEFffz;hA_VFVE*)boLdfn!YUB$QuvGNeE|TexY%*589s2K
z-rXi;e!o0gbe~He_f&r+6&lr
zB@SRRv1~489y9a-hN6q40*dy)a>LbMOM_p5hg%L7&HOIok4`LWQiaO0M7n?;dkBJ#
z>!BOm?hV+qW`SxleP|$u0p!npr0)A-o{mha
zEIiZMMW&Kdi^ZQckV#Z{+B+#TmK=uo=)8??)vB!gYx$#m-Z@uZ=>CwmCE8-ojLkT(
zoe5HUT7cD@#U-kn-1iapbLX*CKbb?9BGOpM@MS&8UMjgJoMBJBt8MUuSO72o}sV^6KB=NYf?|l
z;{+py28)EEoOaF&)i|`4aW+X+8n6YayL!{aBmUe;J*#2SIglVSqMCPnu;(5I&ewiQ
zy>um+Go6XZqk-;eQN6w)je8`S5eDch7vp0uEQY~q
zo){&pTUpgWbg6K3b_y5T;qbI^=eC1cv{^BYOS5%OR+A?)a*$k9$cFUABcH-R)TB)(
z7%xLtPDB;~UVOFC=2f6%2ZOdSN7g}$4=IC$q7t^TUYvUEsecz-I=O}n;G^OAD_cAt
zg+PNd;F$cjT?`2O)u$uIt+Y>~$e4>bCnFK6_zPNmT>w!Y17VXIW79OM#ItC5
z>jVpB5m{jR-K6Kx93Kq_>KVdb-mI%F(RsY)DwpFNtm!AwRW)eKk-q;r6ldmga5k{Z
zE7akYEJNh8FI3}|O9zeCQz#O;SutD*F{ioR`*&Hd5z4-_e3E-;V7Dzs_H|4&T_N6Q
zsid!JU7{meiIzPgehHGKT3B^y>aA9dstEZ>vvA{!8W@Ji>$S{%?+|^@$r1L2Lyh8o
zJa&!JqiOn;*u{LfHI$0M#xriOMe(JYIKNRs1Je^Uv~7#%{>9es2`f8%`G&_c%g|P<
zil;YyWPZuU-NF98yfMKrD(N)Qq&Ax@((;DEARMY@N0=K2;@`KaKkn{*7vZ<@=&(Pq
zcZ9pg%tv8l{F9XiXY*6@yiH6u6-E>a9gg|;cK`lk(d-6;N2O?LQ^u=B$lUnOBzc=o
zRb4mN_?CDQo)0`-+jgc1XBPsAr#P;3_6{;t*mDHXc}*VR+NGBT-D`Iu`YtW=>{rEI
z;871_MYVDA=PwW13MafroYUj@v!fKlboUG@#Aiwp5f5PewwDXycnikbIxnBdlM)n6
z$qBlcw6U9ehm^0r*SbzN_f;zmQS*>YP3EIt8F5v6#r@k%J@ZguWnw6{U-1@3Y3#Vb
z%3l-Xq7Acd-k$`Nd~g@<|Xb6t&h
z0l8IY!z-tZVssj<@Uez0V;IUDcaCh>^)u$=i~kH1zq~4&c}kj7?ClqevrscSYIYX+
z@m&tl1~lUVNgIbwB?~C`=8^M3eqVarctr^**8buaiuT-IpTDkRq2zOTIg9D6
z!9LGzol7906&(CH;QM*2CVjZLUmVi@kvX9%+;KGF43}-RMGbC>{1?FA$df+C-0$@B@Xq(Yt}
zXtBEhvhx^H=el^S$;%ZUea(@f^lq5i0nm37ya~xII%&+E#4TN1b~;ilH)Ym?VClid
zjk#BGgZI<=C!suAx{Oh91TL5@#sNlXf;JsML2mLTCATuWZ`o{im-ihS)Dh%Gu0_1i
z2yhU!NQ2S_^X3%$Lht+byu$94)6O@*O?GKUb=*9UMk0eBCL&BseUj>_gDGQNm{Jlc
z{zfyNxKj=lI*$pg6w6)GpFH~dmUQd(A{N{YSe5{TJ`Z6@nbG0lb&28u_v
ztEwuXol7N@8P_MSoLAPgC_nm1D&PL>sqAU~ijuSEpwi`YWB<8wrNTjOp{2X(=8ZO8
zO@sQZcO^v9)*DV<4(|D-UgptnlR|Jk7;oj6^mQ&x1~HJvBUO>_5&#m7-bQ)qaMW-^
zVuf<(`URj=ZgB%8wgtz!|06A9(cT+JBgx<~`13~Qf+h%JlVNlvDXNqdconiaU4ALG
zF;NeK&ia{Y;-iEQQtn+#79*N-oi*V5wi-JWS|WdydJ)nR`>|LJWtFQR#{-_%picvI
zMA3GxSX|m)H{zOewa_A9U?FZHZ*@iX9Jah*Z4=dBdaQ#GlNmmnWx?woUczI`1-V*;
zCm+qdu)v(&gjdwIDO~ME7B82zxFR5M%?o}!e~WesAoPMoh-Agl4da&rEsX&5YTZ;l
zj>E#i=XT{2g{_AE^$d#X+SZjUKa&m5!`ar*=$6ij58pm!_sl!bax@;viaNB>xoubw
zR|-&h;~INa8;Nsu6tz~pz~JDk97)!!JX$}4`9WB;bmfvHiz63y$u#e)8O_YBx_EmC
zCYu=vN^LdCcwsYLzmzSdUmrYYN%SX)C^^)Zf>0j(mxi*eV~suK9$8*Y1l_`aU$LB?
zF!$$8j_mgk;7y5qErimXKXYuiBww~D%omhgq$Sar!QpV~4uaFc`G=oNu*@9=v|Bq)
z$_nBjz2j_VrB1k>?R_AU96ZhdP!S8kW(_BxcP*;pyl<|R*qjHMBnPdma=MC$4K=sq
zbgqtiz;Njo<`M9hevg>Xp;NF95ghILz>JY{M0Q;gh=a4ohz?S%
zR!4uzbj+AahTtXam+q*I{(d{SorNn3i6tG#-*2_j=kW~Jp#rR1m|N{*@1{6Gj5E?U
zXQdu|g@TM7bTo2?P&`pxPyZRzfq*r`k3K&Fo%!)-(lDnp9l|~3nFP7)N}3n3WRsx_
z+Hb?vISOUA4xTw%ac~T9RvUc14XhN}VQ)Gg^gTI=veoJp{a};)%;WV%>yY4+8hy(m
zXPYJw0ohCzcLZ81hkvzVum5#^X{QFz^I(<*`S|Avm+?R5W_+*8n)bm#aQ{9w$M)EA
zvbh>X`P5f*zPI7ccaSF+Uj&twF}}Z@twhD4)a)X!Yu;UYunA}Jmi`($rZiV8By@AG
z&FgHu{Kdef-5_Z|f3m07!uahsyRY|Qb?If}^Y`xhM0jzt#L&SJP&2{yL&hJC2_jd;
zMhEjgD%O9_9RK!8)3LX$CVmr5I+(I^mjGO{3JRzH-HQd{4j&Q2jB4&_u0!GgitHhU
z17gAyGNpH3FIpZBw{b9pcA%W|n`L;0G_jI0epp
zo8nEJr@fx^*C<~YwgSdwszcr>6PgPhFqxHJFa1SuJ>m#LN9D{^J<6G7Vcj-@x}f~R
z1XXxL#r1gjqlKoV;dixB%^GHf(RIbXuGv09%E(p;0TDJJTv}F=UX$%^g8spU6Vt-!
zMpw)$nFXaf88ua{FO|H2D>%q2+VT6j)6mYpOgwFQG;h(<6&zBUl}uzTQj3z8&bFB3
z{;WyVc(vHSih-Rq`w*bm8Pa$b$Fqy05j|txR~&}45t}!fqPvy!@?ukcGBhx0bX~nYM%mTa|Kyh05B?n2cMi8UagcW3`n{f;8p`M;Ii!~ekihqmJXC6?bNr6;
zdE1hYPbEGiyZ($03x_Wqt*Cn*zpogqCfEMHijS?01#bC4cP8F^TTP;JYZLG5dtSV0
zeQe_svA()o*la5nDB?HsY1Ry$h=W~yTmIsrUaBajNZ&ELu?G0D+WL9t`on%Q=t0sv
zIU!g3_}1lsC@}4
z?w&e2CGG`|&97Kcyxid^i34$I0{m)J24_M{G8s)cGvpB)lU*0Q_f4gHVUX18WYC(&
z=YI;blxWT?){HB>Hx-e2O=w5HhIZyR_|@OXw|5IZ2X;@toIAQbtef~e`NKb#+PnuI
zN~^uDj9h!O6rj_n^2zZ(DY%2g=YdD26$aBRMu$1(PMh`FsCAuCN0oB}kHdcMigku<
zs&xE(q-(62{j_o$C5edmGB&_O-e;H6kqvb%jHCJ&-R{nlFGl};9NBzre!%3yuj#J5
z{h(maZQ1W}3)#lLN(MLfBJ&o#JMv@uimvJqnRlLx@_ZN8+eJFP{jv1pt=@U?UA@RIG@|&YDuB_iK7ain<)On)ZpC8>`DXwlPOuvUye#$iUo6-i+UGjKn=uTc
z(2P5?1vQx*ua+U*sX9-V39d|7-f)7c$$L>8P)IWdu**NaVeL2*25sZ~2z-21qzsqV
zoTR<9%I%x@pT7%xs0#6mMx~QO;*EJl))a+c3h*_)t+xVc!>BEY4xvT}TXT3&EG!@`
z;+`m&GNchf`)XQ)4oviz82PO=DqP{ia~$`Fyv9+nCYt1hsDHZ|vnCO^hRq)~?pza?
zTMQh;@@~~&jX+5@Zv_i$B>LC3h7bxlYd?f#xU90ND&V-j37q^IzK|)lTg=&gL-6mY
zRB82ZU2H48$}WHX>nyt}CQ;%EUWR&W{h*|{7h^8tG%RT1OL$Vd_cA+jz!HtBRbBBx
zluFBet4@9MhQD#05ap|AB={s`-H24BVkE2lU`$|ll}m3zq}}vbAl6cmmliC8Jd*Zc
z_-%opVhJ^B-e!7fbwBznMQKn25$~gjYQa?*J@1V#ee1$-KXrk1_3ks6Q^>e6)?0YG
zq3^PhL~Tg}pj}gPiHKi-;M)Ua1!bg7zin*as70qZ2g31afp=df>kNiXdDe3XRpzFP
zo@_~PF`0J>P8*b1|218IF+I;ExoYkHceWzfAEJ^nJWLr%iglsn_@<1t65PR8@}uFp
zV6mSecyn8h{mdvX(O|(pNoVu)aE<{@&c(Umt=D>>NrPm&rHi|Sr=#^I_o{`vpXIMw
zuy?s`)m&|}+$dzD44!I#Sm*g3OZkRRS=)4N@d_?+bXBwTrbvA5o9ZFT-y!4CIwP&5
zMxVHbH_usWfAO>y*{^QAuERC9aq=69YYuwSo=|iDsEVQ=cmTM)=lJ
z$@9k7tAWWwSyFskPmkndY~Nz5WY76FjujL~o(c$;-yV8dE3(pXfNDDJxn?X%!y4~1KVT7=Czt-Pdz
zd-2WESTSVfn>IJMWP%tm%~hE>BCeH>s^O?OQL6BZ>{a1q_lvP}P#=CDomv)BdTLVK
z{`D2#^3)TEh^jM8fos1fcI)ScYqHWr35}60kUviHM$YU0EwD46K*8fTfAhW1nF&!o
z&whNOAJPhjRBy>(wsLfw*CR{(9+*t!9ABu+f=al(uU5~nGD|T4Lz>qytqUYUqvqBm
zuTvjw%1#I>``^4_vY0c<3jA}EP_<=!34CZEm^LG??dIE`m#IkQ>@5{su5amiUac#`
zH*go;Q`*|vwp*ea?q(TN_}MY%@6K
z{9bI!r}f8L@KD0Y$*FCuo{BwSWqV*TD?`SpBiO1py#@A`Y`gaAUL4`#87tG{-nojslH
zKlkCIa7jyrfUjqp^T(e*6{8GKAMW926^HwlkZGr^Kf|R=Ey5?ge8w@$eG~5k9rvQV
zo0bDN7Y&P+-Bo|hEY4y>9>z)!iHzl9TZ?Pw>vr%f-&Eb#!+69V70Ta$oUQf%2-EzV
zOJ|L#cLmPouG2I_mF{m@zjAo&q38Qi^5eTnd5@KK>58jkNd>g_PkoDL
zx74>5Z^*B|TGQL|zq9q`nRMHjdf?8o=f7W7yS`07-F*D`{mLO?L-oYt=HvWJ%QCwZ
zPw$FWp1V^N{2Y8vVSoM2tU-(wYYlo@3qI?v~>LRb>lmMu$RD=O`m&uhh6W`
z|Cv{5)7eXf^De&q^6+G;&tCf~d$?w{0X^x>yn^T$nG9yHNM1;)b(}gT@-1+F?agDc
zc3Ah;T+-%GvGrA5DXPseGyz~Y(*HQ++1(0nO>sXwMNIvxI(^9%WtV8kv+w;h@yR${
zuR^XpH*rx!of=pd=o#>xryc!@8F+L}hB4IRyU*=g^?arIneABt^8@N>-QC6-JGZ2-U1NIYX>ZEDSV3Ebbc52_&>Eg;OSiwWj0ei{na~R~I
z$f&zRhP(fy9UjfXTW58ubqDC=b3C2Gw~9;LD-g{Yl53q{dtt0R8^~
Duh@-b

literal 0
HcmV?d00001

diff --git a/vendor/plugins/maruku/tests/s5/ui/default/framing.css b/vendor/plugins/maruku/tests/s5/ui/default/framing.css
new file mode 100644
index 00000000..14d8509e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/ui/default/framing.css
@@ -0,0 +1,23 @@
+/* The following styles size, place, and layer the slide components.
+   Edit these if you want to change the overall slide layout.
+   The commented lines can be uncommented (and modified, if necessary) 
+    to help you with the rearrangement process. */
+
+/* target = 1024x768 */
+
+div#header, div#footer, .slide {width: 100%; top: 0; left: 0;}
+div#header {top: 0; height: 3em; z-index: 1;}
+div#footer {top: auto; bottom: 0; height: 2.5em; z-index: 5;}
+.slide {top: 0; width: 92%; padding: 3.5em 4% 4%; z-index: 2;  list-style: none;}
+div#controls {left: 50%; bottom: 0; width: 50%; z-index: 100;}
+div#controls form {position: absolute; bottom: 0; right: 0; width: 100%;
+  margin: 0;}
+#currentSlide {position: absolute; width: 10%; left: 45%; bottom: 1em; z-index: 10;}
+html>body #currentSlide {position: fixed;}
+
+/*
+div#header {background: #FCC;}
+div#footer {background: #CCF;}
+div#controls {background: #BBD;}
+div#currentSlide {background: #FFC;}
+*/
diff --git a/vendor/plugins/maruku/tests/s5/ui/default/iepngfix.htc b/vendor/plugins/maruku/tests/s5/ui/default/iepngfix.htc
new file mode 100644
index 00000000..bba2db75
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/ui/default/iepngfix.htc
@@ -0,0 +1,42 @@
+
+
+
+
+
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/s5/ui/default/opera.css b/vendor/plugins/maruku/tests/s5/ui/default/opera.css
new file mode 100644
index 00000000..9e9d2a3c
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/ui/default/opera.css
@@ -0,0 +1,7 @@
+/* DO NOT CHANGE THESE unless you really want to break Opera Show */
+.slide {
+	visibility: visible !important;
+	position: static !important;
+	page-break-before: always;
+}
+#slide0 {page-break-before: avoid;}
diff --git a/vendor/plugins/maruku/tests/s5/ui/default/outline.css b/vendor/plugins/maruku/tests/s5/ui/default/outline.css
new file mode 100644
index 00000000..62db519e
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/ui/default/outline.css
@@ -0,0 +1,15 @@
+/* don't change this unless you want the layout stuff to show up in the outline view! */
+
+.layout div, #footer *, #controlForm * {display: none;}
+#footer, #controls, #controlForm, #navLinks, #toggle {
+  display: block; visibility: visible; margin: 0; padding: 0;}
+#toggle {float: right; padding: 0.5em;}
+html>body #toggle {position: fixed; top: 0; right: 0;}
+
+/* making the outline look pretty-ish */
+
+#slide0 h1, #slide0 h2, #slide0 h3, #slide0 h4 {border: none; margin: 0;}
+#slide0 h1 {padding-top: 1.5em;}
+.slide h1 {margin: 1.5em 0 0; padding-top: 0.25em;
+  border-top: 1px solid #888; border-bottom: 1px solid #AAA;}
+#toggle {border: 1px solid; border-width: 0 0 1px 1px; background: #FFF;}
diff --git a/vendor/plugins/maruku/tests/s5/ui/default/pretty.css b/vendor/plugins/maruku/tests/s5/ui/default/pretty.css
new file mode 100644
index 00000000..3d3aceff
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/ui/default/pretty.css
@@ -0,0 +1,86 @@
+/* Following are the presentation styles -- edit away! */
+
+body {background: #FFF url(bodybg.gif) -16px 0 no-repeat; color: #000; font-size: 2em;}
+:link, :visited {text-decoration: none; color: #00C;}
+#controls :active {color: #88A !important;}
+#controls :focus {outline: 1px dotted #227;}
+h1, h2, h3, h4 {font-size: 100%; margin: 0; padding: 0; font-weight: inherit;}
+ul, pre {margin: 0; line-height: 1em;}
+html, body {margin: 0; padding: 0;}
+
+blockquote, q {font-style: italic;}
+blockquote {padding: 0 2em 0.5em; margin: 0 1.5em 0.5em; text-align: center; font-size: 1em;}
+blockquote p {margin: 0;}
+blockquote i {font-style: normal;}
+blockquote b {display: block; margin-top: 0.5em; font-weight: normal; font-size: smaller; font-style: normal;}
+blockquote b i {font-style: italic;}
+
+kbd {font-weight: bold; font-size: 1em;}
+sup {font-size: smaller; line-height: 1px;}
+
+.slide code {padding: 2px 0.25em; font-weight: bold; color: #533;}
+.slide code.bad, code del {color: red;}
+.slide code.old {color: silver;}
+.slide pre {padding: 0; margin: 0.25em 0 0.5em 0.5em; color: #533; font-size: 90%;}
+.slide pre code {display: block;}
+.slide ul {margin-left: 5%; margin-right: 7%; list-style: disc;}
+.slide li {margin-top: 0.75em; margin-right: 0;}
+.slide ul ul {line-height: 1;}
+.slide ul ul li {margin: .2em; font-size: 85%; list-style: square;}
+.slide img.leader {display: block; margin: 0 auto;}
+
+div#header, div#footer {background: #005; color: #AAB;
+  font-family: Verdana, Helvetica, sans-serif;}
+div#header {background: #005 url(bodybg.gif) -16px 0 no-repeat;
+  line-height: 1px;}
+div#footer {font-size: 0.5em; font-weight: bold; padding: 1em 0;}
+#footer h1, #footer h2 {display: block; padding: 0 1em;}
+#footer h2 {font-style: italic;}
+
+div.long {font-size: 0.75em;}
+.slide h1 {position: absolute; top: 0.7em; left: 87px; z-index: 1;
+  margin: 0; padding: 0.3em 0 0 50px; white-space: nowrap;
+  font: bold 150%/1em Helvetica, sans-serif; text-transform: capitalize;
+  color: #DDE; background: #005;}
+.slide h3 {font-size: 130%;}
+h1 abbr {font-variant: small-caps;}
+
+div#controls {position: absolute; left: 50%; bottom: 0;
+  width: 50%;
+  text-align: right; font: bold 0.9em Verdana, Helvetica, sans-serif;}
+html>body div#controls {position: fixed; padding: 0 0 1em 0;
+  top: auto;}
+div#controls form {position: absolute; bottom: 0; right: 0; width: 100%;
+  margin: 0; padding: 0;}
+#controls #navLinks a {padding: 0; margin: 0 0.5em; 
+  background: #005; border: none; color: #779; 
+  cursor: pointer;}
+#controls #navList {height: 1em;}
+#controls #navList #jumplist {position: absolute; bottom: 0; right: 0; background: #DDD; color: #227;}
+
+#currentSlide {text-align: center; font-size: 0.5em; color: #449;}
+
+#slide0 {padding-top: 3.5em; font-size: 90%;}
+#slide0 h1 {position: static; margin: 1em 0 0; padding: 0;
+   font: bold 2em Helvetica, sans-serif; white-space: normal;
+   color: #000; background: transparent;}
+#slide0 h2 {font: bold italic 1em Helvetica, sans-serif; margin: 0.25em;}
+#slide0 h3 {margin-top: 1.5em; font-size: 1.5em;}
+#slide0 h4 {margin-top: 0; font-size: 1em;}
+
+ul.urls {list-style: none; display: inline; margin: 0;}
+.urls li {display: inline; margin: 0;}
+.note {display: none;}
+.external {border-bottom: 1px dotted gray;}
+html>body .external {border-bottom: none;}
+.external:after {content: " \274F"; font-size: smaller; color: #77B;}
+
+.incremental, .incremental *, .incremental *:after {color: #DDE; visibility: visible;}
+img.incremental {visibility: hidden;}
+.slide .current {color: #B02;}
+
+
+/* diagnostics
+
+li:after {content: " [" attr(class) "]"; color: #F88;}
+ */
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/s5/ui/default/print.css b/vendor/plugins/maruku/tests/s5/ui/default/print.css
new file mode 100644
index 00000000..e7a71d14
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/ui/default/print.css
@@ -0,0 +1 @@
+/* The following rule is necessary to have all slides appear in print! DO NOT REMOVE IT! */
.slide, ul {page-break-inside: avoid; visibility: visible !important;}
h1 {page-break-after: avoid;}

body {font-size: 12pt; background: white;}
* {color: black;}

#slide0 h1 {font-size: 200%; border: none; margin: 0.5em 0 0.25em;}
#slide0 h3 {margin: 0; padding: 0;}
#slide0 h4 {margin: 0 0 0.5em; padding: 0;}
#slide0 {margin-bottom: 3em;}

h1 {border-top: 2pt solid gray; border-bottom: 1px dotted silver;}
.extra {background: transparent !important;}
div.extra, pre.extra, .example {font-size: 10pt; color: #333;}
ul.extra a {font-weight: bold;}
p.example {display: none;}

#header {display: none;}
#footer h1 {margin: 0; border-bottom: 1px solid; color: gray; font-style: italic;}
#footer h2, #controls {display: none;}

/* The following rule keeps the layout stuff out of print.  Remove at your own risk! */
.layout, .layout * {display: none !important;}
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/s5/ui/default/s5-core.css b/vendor/plugins/maruku/tests/s5/ui/default/s5-core.css
new file mode 100644
index 00000000..86444e04
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/ui/default/s5-core.css
@@ -0,0 +1,9 @@
+/* Do not edit or override these styles! The system will likely break if you do. */
+
+div#header, div#footer, div#controls, .slide {position: absolute;}
+html>body div#header, html>body div#footer, 
+  html>body div#controls, html>body .slide {position: fixed;}
+.handout {display: none;}
+.layout {display: block;}
+.slide, .hideme, .incremental {visibility: hidden;}
+#slide0 {visibility: visible;}
diff --git a/vendor/plugins/maruku/tests/s5/ui/default/slides.css b/vendor/plugins/maruku/tests/s5/ui/default/slides.css
new file mode 100644
index 00000000..0786d7db
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/ui/default/slides.css
@@ -0,0 +1,3 @@
+@import url(s5-core.css); /* required to make the slide show run at all */
+@import url(framing.css); /* sets basic placement and size of slide components */
+@import url(pretty.css);  /* stuff that makes the slides look better than blah */
\ No newline at end of file
diff --git a/vendor/plugins/maruku/tests/s5/ui/default/slides.js b/vendor/plugins/maruku/tests/s5/ui/default/slides.js
new file mode 100644
index 00000000..07f40ff8
--- /dev/null
+++ b/vendor/plugins/maruku/tests/s5/ui/default/slides.js
@@ -0,0 +1,552 @@
+// S5 v1.1 slides.js -- released into the Public Domain
+//
+// Please see http://www.meyerweb.com/eric/tools/s5/credits.html for information 
+// about all the wonderful and talented contributors to this code!
+
+var undef;
+var slideCSS = '';
+var snum = 0;
+var smax = 1;
+var incpos = 0;
+var number = undef;
+var s5mode = true;
+var defaultView = 'slideshow';
+var controlVis = 'visible';
+
+var isIE = navigator.appName == 'Microsoft Internet Explorer' ? 1 : 0;
+var isOp = navigator.userAgent.indexOf('Opera') > -1 ? 1 : 0;
+var isGe = navigator.userAgent.indexOf('Gecko') > -1 && navigator.userAgent.indexOf('Safari') < 1 ? 1 : 0;
+
+function hasClass(object, className) {
+	if (!object.className) return false;
+	return (object.className.search('(^|\\s)' + className + '(\\s|$)') != -1);
+}
+
+function hasValue(object, value) {
+	if (!object) return false;
+	return (object.search('(^|\\s)' + value + '(\\s|$)') != -1);
+}
+
+function removeClass(object,className) {
+	if (!object) return;
+	object.className = object.className.replace(new RegExp('(^|\\s)'+className+'(\\s|$)'), RegExp.$1+RegExp.$2);
+}
+
+function addClass(object,className) {
+	if (!object || hasClass(object, className)) return;
+	if (object.className) {
+		object.className += ' '+className;
+	} else {
+		object.className = className;
+	}
+}
+
+function GetElementsWithClassName(elementName,className) {
+	var allElements = document.getElementsByTagName(elementName);
+	var elemColl = new Array();
+	for (var i = 0; i< allElements.length; i++) {
+		if (hasClass(allElements[i], className)) {
+			elemColl[elemColl.length] = allElements[i];
+		}
+	}
+	return elemColl;
+}
+
+function isParentOrSelf(element, id) {
+	if (element == null || element.nodeName=='BODY') return false;
+	else if (element.id == id) return true;
+	else return isParentOrSelf(element.parentNode, id);
+}
+
+function nodeValue(node) {
+	var result = "";
+	if (node.nodeType == 1) {
+		var children = node.childNodes;
+		for (var i = 0; i < children.length; ++i) {
+			result += nodeValue(children[i]);
+		}		
+	}
+	else if (node.nodeType == 3) {
+		result = node.nodeValue;
+	}
+	return(result);
+}
+
+function slideLabel() {
+	var slideColl = GetElementsWithClassName('*','slide');
+	var list = document.getElementById('jumplist');
+	smax = slideColl.length;
+	for (var n = 0; n < smax; n++) {
+		var obj = slideColl[n];
+
+		var did = 'slide' + n.toString();
+		obj.setAttribute('id',did);
+		if (isOp) continue;
+
+		var otext = '';
+		var menu = obj.firstChild;
+		if (!menu) continue; // to cope with empty slides
+		while (menu && menu.nodeType == 3) {
+			menu = menu.nextSibling;
+		}
+	 	if (!menu) continue; // to cope with slides with only text nodes
+
+		var menunodes = menu.childNodes;
+		for (var o = 0; o < menunodes.length; o++) {
+			otext += nodeValue(menunodes[o]);
+		}
+		list.options[list.length] = new Option(n + ' : '  + otext, n);
+	}
+}
+
+function currentSlide() {
+	var cs;
+	if (document.getElementById) {
+		cs = document.getElementById('currentSlide');
+	} else {
+		cs = document.currentSlide;
+	}
+	cs.innerHTML = '' + snum + '<\/span> ' + 
+		'\/<\/span> ' + 
+		'' + (smax-1) + '<\/span>';
+	if (snum == 0) {
+		cs.style.visibility = 'hidden';
+	} else {
+		cs.style.visibility = 'visible';
+	}
+}
+
+function go(step) {
+	if (document.getElementById('slideProj').disabled || step == 0) return;
+	var jl = document.getElementById('jumplist');
+	var cid = 'slide' + snum;
+	var ce = document.getElementById(cid);
+	if (incrementals[snum].length > 0) {
+		for (var i = 0; i < incrementals[snum].length; i++) {
+			removeClass(incrementals[snum][i], 'current');
+			removeClass(incrementals[snum][i], 'incremental');
+		}
+	}
+	if (step != 'j') {
+		snum += step;
+		lmax = smax - 1;
+		if (snum > lmax) snum = lmax;
+		if (snum < 0) snum = 0;
+	} else
+		snum = parseInt(jl.value);
+	var nid = 'slide' + snum;
+	var ne = document.getElementById(nid);
+	if (!ne) {
+		ne = document.getElementById('slide0');
+		snum = 0;
+	}
+	if (step < 0) {incpos = incrementals[snum].length} else {incpos = 0;}
+	if (incrementals[snum].length > 0 && incpos == 0) {
+		for (var i = 0; i < incrementals[snum].length; i++) {
+			if (hasClass(incrementals[snum][i], 'current'))
+				incpos = i + 1;
+			else
+				addClass(incrementals[snum][i], 'incremental');
+		}
+	}
+	if (incrementals[snum].length > 0 && incpos > 0)
+		addClass(incrementals[snum][incpos - 1], 'current');
+	ce.style.visibility = 'hidden';
+	ne.style.visibility = 'visible';
+	jl.selectedIndex = snum;
+	currentSlide();
+	number = 0;
+}
+
+function goTo(target) {
+	if (target >= smax || target == snum) return;
+	go(target - snum);
+}
+
+function subgo(step) {
+	if (step > 0) {
+		removeClass(incrementals[snum][incpos - 1],'current');
+		removeClass(incrementals[snum][incpos], 'incremental');
+		addClass(incrementals[snum][incpos],'current');
+		incpos++;
+	} else {
+		incpos--;
+		removeClass(incrementals[snum][incpos],'current');
+		addClass(incrementals[snum][incpos], 'incremental');
+		addClass(incrementals[snum][incpos - 1],'current');
+	}
+}
+
+function toggle() {
+	var slideColl = GetElementsWithClassName('*','slide');
+	var slides = document.getElementById('slideProj');
+	var outline = document.getElementById('outlineStyle');
+	if (!slides.disabled) {
+		slides.disabled = true;
+		outline.disabled = false;
+		s5mode = false;
+		fontSize('1em');
+		for (var n = 0; n < smax; n++) {
+			var slide = slideColl[n];
+			slide.style.visibility = 'visible';
+		}
+	} else {
+		slides.disabled = false;
+		outline.disabled = true;
+		s5mode = true;
+		fontScale();
+		for (var n = 0; n < smax; n++) {
+			var slide = slideColl[n];
+			slide.style.visibility = 'hidden';
+		}
+		slideColl[snum].style.visibility = 'visible';
+	}
+}
+
+function showHide(action) {
+	var obj = GetElementsWithClassName('*','hideme')[0];
+	switch (action) {
+	case 's': obj.style.visibility = 'visible'; break;
+	case 'h': obj.style.visibility = 'hidden'; break;
+	case 'k':
+		if (obj.style.visibility != 'visible') {
+			obj.style.visibility = 'visible';
+		} else {
+			obj.style.visibility = 'hidden';
+		}
+	break;
+	}
+}
+
+// 'keys' code adapted from MozPoint (http://mozpoint.mozdev.org/)
+function keys(key) {
+	if (!key) {
+		key = event;
+		key.which = key.keyCode;
+	}
+	if (key.which == 84) {
+		toggle();
+		return;
+	}
+	if (s5mode) {
+		switch (key.which) {
+			case 10: // return
+			case 13: // enter
+				if (window.event && isParentOrSelf(window.event.srcElement, 'controls')) return;
+				if (key.target && isParentOrSelf(key.target, 'controls')) return;
+				if(number != undef) {
+					goTo(number);
+					break;
+				}
+			case 32: // spacebar
+			case 34: // page down
+			case 39: // rightkey
+			case 40: // downkey
+				if(number != undef) {
+					go(number);
+				} else if (!incrementals[snum] || incpos >= incrementals[snum].length) {
+					go(1);
+				} else {
+					subgo(1);
+				}
+				break;
+			case 33: // page up
+			case 37: // leftkey
+			case 38: // upkey
+				if(number != undef) {
+					go(-1 * number);
+				} else if (!incrementals[snum] || incpos <= 0) {
+					go(-1);
+				} else {
+					subgo(-1);
+				}
+				break;
+			case 36: // home
+				goTo(0);
+				break;
+			case 35: // end
+				goTo(smax-1);
+				break;
+			case 67: // c
+				showHide('k');
+				break;
+		}
+		if (key.which < 48 || key.which > 57) {
+			number = undef;
+		} else {
+			if (window.event && isParentOrSelf(window.event.srcElement, 'controls')) return;
+			if (key.target && isParentOrSelf(key.target, 'controls')) return;
+			number = (((number != undef) ? number : 0) * 10) + (key.which - 48);
+		}
+	}
+	return false;
+}
+
+function clicker(e) {
+	number = undef;
+	var target;
+	if (window.event) {
+		target = window.event.srcElement;
+		e = window.event;
+	} else target = e.target;
+	if (target.getAttribute('href') != null || hasValue(target.rel, 'external') || isParentOrSelf(target, 'controls') || isParentOrSelf(target,'embed') || isParentOrSelf(target,'object')) return true;
+	if (!e.which || e.which == 1) {
+		if (!incrementals[snum] || incpos >= incrementals[snum].length) {
+			go(1);
+		} else {
+			subgo(1);
+		}
+	}
+}
+
+function findSlide(hash) {
+	var target = null;
+	var slides = GetElementsWithClassName('*','slide');
+	for (var i = 0; i < slides.length; i++) {
+		var targetSlide = slides[i];
+		if ( (targetSlide.name && targetSlide.name == hash)
+		 || (targetSlide.id && targetSlide.id == hash) ) {
+			target = targetSlide;
+			break;
+		}
+	}
+	while(target != null && target.nodeName != 'BODY') {
+		if (hasClass(target, 'slide')) {
+			return parseInt(target.id.slice(5));
+		}
+		target = target.parentNode;
+	}
+	return null;
+}
+
+function slideJump() {
+	if (window.location.hash == null) return;
+	var sregex = /^#slide(\d+)$/;
+	var matches = sregex.exec(window.location.hash);
+	var dest = null;
+	if (matches != null) {
+		dest = parseInt(matches[1]);
+	} else {
+		dest = findSlide(window.location.hash.slice(1));
+	}
+	if (dest != null)
+		go(dest - snum);
+}
+
+function fixLinks() {
+	var thisUri = window.location.href;
+	thisUri = thisUri.slice(0, thisUri.length - window.location.hash.length);
+	var aelements = document.getElementsByTagName('A');
+	for (var i = 0; i < aelements.length; i++) {
+		var a = aelements[i].href;
+		var slideID = a.match('\#slide[0-9]{1,2}');
+		if ((slideID) && (slideID[0].slice(0,1) == '#')) {
+			var dest = findSlide(slideID[0].slice(1));
+			if (dest != null) {
+				if (aelements[i].addEventListener) {
+					aelements[i].addEventListener("click", new Function("e",
+						"if (document.getElementById('slideProj').disabled) return;" +
+						"go("+dest+" - snum); " +
+						"if (e.preventDefault) e.preventDefault();"), true);
+				} else if (aelements[i].attachEvent) {
+					aelements[i].attachEvent("onclick", new Function("",
+						"if (document.getElementById('slideProj').disabled) return;" +
+						"go("+dest+" - snum); " +
+						"event.returnValue = false;"));
+				}
+			}
+		}
+	}
+}
+
+function externalLinks() {
+	if (!document.getElementsByTagName) return;
+	var anchors = document.getElementsByTagName('a');
+	for (var i=0; i' +
+	'