diff options
Diffstat (limited to 'macros/generic/markdown/tests/testfiles/Markdown_1.0.3')
19 files changed, 0 insertions, 3105 deletions
diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/README.md b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/README.md deleted file mode 100644 index 1a8fd15a48..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/README.md +++ /dev/null @@ -1,2 +0,0 @@ -This directory contains test files that were inherited from the -`tests/Markdown_1.0.3/` directory in the lunamark project. diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/amps-encoding.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/amps-encoding.test deleted file mode 100644 index da079fc68f..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/amps-encoding.test +++ /dev/null @@ -1,36 +0,0 @@ -<<< -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](</script?foo=1&bar=2>). - - -[1]: http://example.com/?foo=1&bar=2 -[2]: http://att.com/ "AT&T" ->>> -BEGIN link -- label: link -- URI: http://example.com/?foo=1(ampersand)bar=2 -- title: -END link -interblockSeparator -BEGIN link -- label: AT(ampersand)T -- URI: http://att.com/ -- title: AT(ampersand)T -END link -interblockSeparator -BEGIN link -- label: link -- URI: /script?foo=1(ampersand)bar=2 -- title: -END link -interblockSeparator -BEGIN link -- label: link -- URI: /script?foo=1(ampersand)bar=2 -- title: -END link diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/auto-links.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/auto-links.test deleted file mode 100644 index 765a85d3e2..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/auto-links.test +++ /dev/null @@ -1,52 +0,0 @@ -<<< -Link: <http://example.com/>. - -With an ampersand: <http://example.com/?foo=1&bar=2> - -* In a list? -* <http://example.com/> -* It should. - -> Blockquoted: <http://example.com/> - -Auto-links should not occur here: `<http://example.com/>` - - or here: <http://example.com/> ->>> -BEGIN link -- label: http://example.com/ -- URI: http://example.com/ -- title: -END link -interblockSeparator -BEGIN link -- label: http://example.com/?foo=1(ampersand)bar=2 -- URI: http://example.com/?foo=1(ampersand)bar=2 -- title: -END link -interblockSeparator -ulBeginTight -ulItem -ulItemEnd -ulItem -BEGIN link -- label: http://example.com/ -- URI: http://example.com/ -- title: -END link -ulItemEnd -ulItem -ulItemEnd -ulEndTight -interblockSeparator -blockQuoteBegin -BEGIN link -- label: http://example.com/ -- URI: http://example.com/ -- title: -END link -blockQuoteEnd -interblockSeparator -codeSpan: <http://example.com/> -interblockSeparator -inputVerbatim: ./_markdown_test/d65b41d110c17fbc771809f553258ff5.verbatim diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/backslash-escapes.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/backslash-escapes.test deleted file mode 100644 index 182a63747c..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/backslash-escapes.test +++ /dev/null @@ -1,192 +0,0 @@ -<<< -These should all get escaped: - -Backslash: \\ - -Backtick: \` - -Asterisk: \* - -Underscore: \_ - -Left brace: \{ - -Right brace: \} - -Left bracket: \[ - -Right bracket: \] - -Left paren: \( - -Right paren: \) - -Greater-than: \> - -Hash: \# - -Period: \. - -Bang: \! - -Plus: \+ - -Minus: \- - - - -These should not, because they occur within a code block: - - Backslash: \\ - - Backtick: \` - - Asterisk: \* - - Underscore: \_ - - Left brace: \{ - - Right brace: \} - - Left bracket: \[ - - Right bracket: \] - - Left paren: \( - - Right paren: \) - - Greater-than: \> - - Hash: \# - - Period: \. - - Bang: \! - - Plus: \+ - - Minus: \- - - -Nor should these, which occur in code spans: - -Backslash: `\\` - -Backtick: `` \` `` - -Asterisk: `\*` - -Underscore: `\_` - -Left brace: `\{` - -Right brace: `\}` - -Left bracket: `\[` - -Right bracket: `\]` - -Left paren: `\(` - -Right paren: `\)` - -Greater-than: `\>` - -Hash: `\#` - -Period: `\.` - -Bang: `\!` - -Plus: `\+` - -Minus: `\-` - - -These should get escaped, even though they're matching pairs for -other Markdown constructs: - -\*asterisks\* - -\_underscores\_ - -\`backticks\` - -This is a code span with a literal backslash-backtick sequence: `` \` `` - -This is a tag with unescaped backticks <span attr='`ticks`'>bar</span>. - -This is a tag with backslashes <span attr='\\backslashes\\'>bar</span>. ->>> -interblockSeparator -backslash -interblockSeparator -interblockSeparator -interblockSeparator -underscore -interblockSeparator -leftBrace -interblockSeparator -rightBrace -interblockSeparator -interblockSeparator -interblockSeparator -interblockSeparator -interblockSeparator -interblockSeparator -hash -interblockSeparator -interblockSeparator -interblockSeparator -interblockSeparator -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/127bce8785d826a9ba07a20f6ca866c9.verbatim -interblockSeparator -interblockSeparator -codeSpan: (backslash)(backslash) -interblockSeparator -codeSpan: (backslash)` -interblockSeparator -codeSpan: (backslash)* -interblockSeparator -codeSpan: (backslash)(underscore) -interblockSeparator -codeSpan: (backslash)(leftBrace) -interblockSeparator -codeSpan: (backslash)(rightBrace) -interblockSeparator -codeSpan: (backslash)[ -interblockSeparator -codeSpan: (backslash)] -interblockSeparator -codeSpan: (backslash)( -interblockSeparator -codeSpan: (backslash)) -interblockSeparator -codeSpan: (backslash)> -interblockSeparator -codeSpan: (backslash)(hash) -interblockSeparator -codeSpan: (backslash). -interblockSeparator -codeSpan: (backslash)! -interblockSeparator -codeSpan: (backslash)+ -interblockSeparator -codeSpan: (backslash)- -interblockSeparator -interblockSeparator -interblockSeparator -underscore -underscore -interblockSeparator -interblockSeparator -codeSpan: (backslash)` -interblockSeparator -codeSpan: ticks -interblockSeparator -backslash -backslash diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/blockquotes-with-code-blocks.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/blockquotes-with-code-blocks.test deleted file mode 100644 index 1fa09a34de..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/blockquotes-with-code-blocks.test +++ /dev/null @@ -1,21 +0,0 @@ -<<< -> Example: -> -> sub status { -> print "working"; -> } -> -> Or: -> -> sub status { -> return "working"; -> } - ->>> -blockQuoteBegin -interblockSeparator -inputVerbatim: ./_markdown_test/702e5d3a17f709c02cee3a2b5e106619.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/9d7d6b4bdbb0a57a705dc70e6c7f5612.verbatim -blockQuoteEnd diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/code-blocks.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/code-blocks.test deleted file mode 100644 index 5f4a0bb137..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/code-blocks.test +++ /dev/null @@ -1,18 +0,0 @@ -<<< - code block on the first line - -Regular text. - - code block indented by spaces - -Regular Text. - - code block on the last line ->>> -inputVerbatim: ./_markdown_test/757353c94a464c718394adbe349d6771.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/84469dcb7c065e457fc00040f5c96d8f.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/e0bb27efcfecc25309f165e0092a7434.verbatim diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/code-spans.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/code-spans.test deleted file mode 100644 index 94aab36b56..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/code-spans.test +++ /dev/null @@ -1,4 +0,0 @@ -<<< -Here's how you put `` `backticks` `` in a code span. ->>> -codeSpan: `backticks` diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/hard-wrapped-paragraphs-with-list-like-lines.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/hard-wrapped-paragraphs-with-list-like-lines.test deleted file mode 100644 index 6c6690877d..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/hard-wrapped-paragraphs-with-list-like-lines.test +++ /dev/null @@ -1,12 +0,0 @@ -<<< -In Markdown 1.0.0 and earlier. Version -8. This line turns into a list item. -Because a hard-wrapped line in the -middle of a paragraph looked like a -list item. - -Here's one with a bullet. -* criminey. - ->>> -interblockSeparator diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/horizontal-rules.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/horizontal-rules.test deleted file mode 100644 index e5d45d9dde..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/horizontal-rules.test +++ /dev/null @@ -1,132 +0,0 @@ -<<< -Dashes: - ---- - - --- - - --- - - --- - - --- - -- - - - - - - - - - - - - - - - - - - - - - - - - -Asterisks: - -*** - - *** - - *** - - *** - - *** - -* * * - - * * * - - * * * - - * * * - - * * * - - -Underscores: - -___ - - ___ - - ___ - - ___ - - ___ - -_ _ _ - - _ _ _ - - _ _ _ - - _ _ _ - - _ _ _ - ->>> -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -inputVerbatim: ./_markdown_test/6105347ebb9825ac754615ca55ff3b0c.verbatim -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -inputVerbatim: ./_markdown_test/162bbc959948880b7b81a0fe05afbe29.verbatim -interblockSeparator -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -inputVerbatim: ./_markdown_test/2bb6aed5111ef9726bcf6eef982ff32b.verbatim -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -inputVerbatim: ./_markdown_test/11de6126af81e6dc22594955105d9180.verbatim -interblockSeparator -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -inputVerbatim: ./_markdown_test/926225b865393c08438ddbfd89ff3d40.verbatim -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -horizontalRule -interblockSeparator -inputVerbatim: ./_markdown_test/c4775559353a17841cc9cde2eae040b2.verbatim diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/links-inline-style.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/links-inline-style.test deleted file mode 100644 index d956be1ede..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/links-inline-style.test +++ /dev/null @@ -1,50 +0,0 @@ -<<< -Just a [URL](/url/). - -[URL and title](/url/ "title"). - -[URL and title](/url/ "title preceded by two spaces"). - -[URL and title](/url/ "title preceded by a tab"). - -[URL and title](/url/ "title has spaces afterward" ). - - -[Empty](). - ->>> -BEGIN link -- label: URL -- URI: /url/ -- title: -END link -interblockSeparator -BEGIN link -- label: URL and title -- URI: /url/ -- title: title -END link -interblockSeparator -BEGIN link -- label: URL and title -- URI: /url/ -- title: title preceded by two spaces -END link -interblockSeparator -BEGIN link -- label: URL and title -- URI: /url/ -- title: title preceded by a tab -END link -interblockSeparator -BEGIN link -- label: URL and title -- URI: /url/ -- title: title has spaces afterward -END link -interblockSeparator -BEGIN link -- label: Empty -- URI: -- title: -END link diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/links-reference-style.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/links-reference-style.test deleted file mode 100644 index 793ea37dca..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/links-reference-style.test +++ /dev/null @@ -1,176 +0,0 @@ -<<< -Foo [bar] [1]. - -Foo [bar][1]. - -Foo [bar] -[1]. - -[1]: /url/ "Title" - - -With [embedded [brackets]] [b]. - - -Indented [once][]. - -Indented [twice][]. - -Indented [thrice][]. - -Indented [four][] times. - - [once]: /url - - [twice]: /url - - [thrice]: /url - - [four]: /url - - -[b]: /url/ - -* * * - -[this] [this] should work - -So should [this][this]. - -And [this] []. - -And [this][]. - -And [this]. - -But not [that] []. - -Nor [that][]. - -Nor [that]. - -[Something in brackets like [this][] should work] - -[Same with [this].] - -In this case, [this](/somethingelse/) points to something else. - -Backslashing should suppress \[this] and [this\]. - -[this]: foo - - -* * * - -Here's one where the [link -breaks] across lines. - -[link breaks]: /url/ - ->>> -BEGIN link -- label: bar -- URI: /url/ -- title: Title -END link -interblockSeparator -BEGIN link -- label: bar -- URI: /url/ -- title: Title -END link -interblockSeparator -BEGIN link -- label: bar -- URI: /url/ -- title: Title -END link -interblockSeparator -BEGIN link -- label: embedded [brackets] -- URI: /url/ -- title: -END link -interblockSeparator -BEGIN link -- label: once -- URI: /url -- title: -END link -interblockSeparator -BEGIN link -- label: twice -- URI: /url -- title: -END link -interblockSeparator -BEGIN link -- label: thrice -- URI: /url -- title: -END link -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/b0cba64633d2a9eac28ca9e3fa500018.verbatim -interblockSeparator -horizontalRule -interblockSeparator -BEGIN link -- label: this -- URI: foo -- title: -END link -interblockSeparator -BEGIN link -- label: this -- URI: foo -- title: -END link -interblockSeparator -BEGIN link -- label: this -- URI: foo -- title: -END link -interblockSeparator -BEGIN link -- label: this -- URI: foo -- title: -END link -interblockSeparator -BEGIN link -- label: this -- URI: foo -- title: -END link -interblockSeparator -interblockSeparator -interblockSeparator -interblockSeparator -BEGIN link -- label: this -- URI: foo -- title: -END link -interblockSeparator -BEGIN link -- label: this -- URI: foo -- title: -END link -interblockSeparator -BEGIN link -- label: this -- URI: /somethingelse/ -- title: -END link -interblockSeparator -interblockSeparator -horizontalRule -interblockSeparator -BEGIN link -- label: link breaks -- URI: /url/ -- title: -END link diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/links-shortcut-references.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/links-shortcut-references.test deleted file mode 100644 index 24b189d7c9..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/links-shortcut-references.test +++ /dev/null @@ -1,42 +0,0 @@ -<<< -This is the [simple case]. - -[simple case]: /simple - - - -This one has a [line -break]. - -[line break]: /foo - - -[this] [that] and the [other] - -[this]: /this -[that]: /that -[other]: /other - ->>> -BEGIN link -- label: simple case -- URI: /simple -- title: -END link -interblockSeparator -BEGIN link -- label: line break -- URI: /foo -- title: -END link -interblockSeparator -BEGIN link -- label: this -- URI: /that -- title: -END link -BEGIN link -- label: other -- URI: /other -- title: -END link diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/literal-quotes-in-titles.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/literal-quotes-in-titles.test deleted file mode 100644 index cd44028f8f..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/literal-quotes-in-titles.test +++ /dev/null @@ -1,21 +0,0 @@ -<<< -Foo [bar][]. - -Foo [bar](/url/ "Title with "quotes" inside"). - - - [bar]: /url/ "Title with "quotes" inside" - - ->>> -BEGIN link -- label: bar -- URI: /url/ -- title: Title with "quotes" inside -END link -interblockSeparator -BEGIN link -- label: bar -- URI: /url/ -- title: Title with "quotes" inside -END link diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/markdown-documentation-basics.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/markdown-documentation-basics.test deleted file mode 100644 index 4ce4b68028..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/markdown-documentation-basics.test +++ /dev/null @@ -1,436 +0,0 @@ -<<< -Markdown: Basics -================ - -Getting the Gist of Markdown's Formatting Syntax ------------------------------------------------- - -This page offers a brief overview of what it's like to use Markdown. -The [syntax page] [s] provides complete, detailed documentation for -every feature, but Markdown should be very easy to pick up simply by -looking at a few examples of it in action. The examples on this page -are written in a before/after style, showing example syntax and the -HTML output produced by Markdown. - -It's also helpful to simply try Markdown out; the [Dingus] [d] is a -web application that allows you type your own Markdown-formatted text -and translate it to XHTML. - -**Note:** This document is itself written using Markdown; you -can [see the source for it by adding '.text' to the URL] [src]. - - [s]: /projects/markdown/syntax "Markdown Syntax" - [d]: /projects/markdown/dingus "Markdown Dingus" - [src]: /projects/markdown/basics.text - - -## Paragraphs, Headers, Blockquotes ## - -A paragraph is simply one or more consecutive lines of text, separated -by one or more blank lines. (A blank line is any line that looks like a -blank line -- a line containing nothing spaces or tabs is considered -blank.) Normal paragraphs should not be intended with spaces or tabs. - -Markdown offers two styles of headers: *Setext* and *atx*. -Setext-style headers for `<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. - -Output: - - <p>I strongly recommend against using any - <code><blink></code> tags.</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><blockquote> - <p>For example.</p> - </blockquote> - </code></pre> - ->>> -headingOne: Markdown: Basics -interblockSeparator -headingTwo: Getting the Gist of Markdown's Formatting Syntax -interblockSeparator -BEGIN link -- label: syntax page -- URI: /projects/markdown/syntax -- title: Markdown Syntax -END link -interblockSeparator -BEGIN link -- label: Dingus -- URI: /projects/markdown/dingus -- title: Markdown Dingus -END link -interblockSeparator -strongEmphasis: Note: -BEGIN link -- label: see the source for it by adding '.text' to the URL -- URI: /projects/markdown/basics.text -- title: -END link -interblockSeparator -headingTwo: Paragraphs, Headers, Blockquotes -interblockSeparator -interblockSeparator -emphasis: Setext -emphasis: atx -codeSpan: <h1> -codeSpan: <h2> -codeSpan: = -codeSpan: - -codeSpan: (hash) -interblockSeparator -codeSpan: > -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/5ebdf3631f626dba5ee92ee773e97a8f.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/9347d3cfacf328e3d73c4fe1b4f76524.verbatim -interblockSeparator -headingThree: Phrase Emphasis -interblockSeparator -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/495d205391f56da33d355c43c81daa64.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/60195f0a7c825159eb9156947e6fb71b.verbatim -interblockSeparator -headingTwo: Lists -interblockSeparator -codeSpan: * -codeSpan: + -codeSpan: - -interblockSeparator -inputVerbatim: ./_markdown_test/30a921ea3110056dc221ed257b3c883b.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/674e077aa8994de8bf541093168d2e29.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/7ae61eceff910c380dbe3ee9af7b6c4a.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/b84dd49773de7abaeec71bfa32680045.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/2a1d33d66339f281e4a171d1eb084b07.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/430a75a1628ba89cc2b1005bb1e5d932.verbatim -interblockSeparator -codeSpan: <p> -interblockSeparator -inputVerbatim: ./_markdown_test/e6108616b0422dd64f485971e61ac69c.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/0bd4d7d78b1cd0e46e78a522f613a6a3.verbatim -interblockSeparator -headingThree: Links -interblockSeparator -emphasis: inline -emphasis: reference -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/20cfebed5272ba2f01c1aee798509f18.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/46124210265b51c9d470c0c70a598037.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/d56162c63107aadd63a5b6ca05f491e9.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/c62653fbfcf155bfe2912f066f242885.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/b996f30ba094126a05b4797a048ff2d2.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/0b1519420e84d1c754b52b25170d7213.verbatim -interblockSeparator -emphasis: not -interblockSeparator -inputVerbatim: ./_markdown_test/15e1c1abc08ec60d9181f9578c6cf172.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/440c1e901154984bf647fc152cb0971b.verbatim -interblockSeparator -headingThree: Images -interblockSeparator -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/602bb0e325271b2b4dce9175eaed15b1.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/e5b369214c819b9d9b476b7bb1f5aa53.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/885cbee5cc0e1fac9ce25c3a9d30034e.verbatim -interblockSeparator -headingThree: Code -interblockSeparator -codeSpan: (ampersand) -codeSpan: < -codeSpan: > -interblockSeparator -inputVerbatim: ./_markdown_test/fbcaafb68ad6405619da77e413788d6e.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/cfc57312a789ed7b4e14f3f56c88381a.verbatim -interblockSeparator -codeSpan: (ampersand) -codeSpan: < -codeSpan: > -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/fe59314852dc8de3165464ab451f44a0.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/3f58f44c2de7257eb42c24e7aee621c5.verbatim diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/markdown-documentation-syntax.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/markdown-documentation-syntax.test deleted file mode 100644 index 2942add07e..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/markdown-documentation-syntax.test +++ /dev/null @@ -1,1518 +0,0 @@ -<<< -Markdown: Syntax -================ - -* [Overview](#overview) - * [Philosophy](#philosophy) - * [Inline HTML](#html) - * [Automatic Escaping for Special Characters](#autoescape) -* [Block Elements](#block) - * [Paragraphs and Line Breaks](#p) - * [Headers](#header) - * [Blockquotes](#blockquote) - * [Lists](#list) - * [Code Blocks](#precode) - * [Horizontal Rules](#hr) -* [Span Elements](#span) - * [Links](#link) - * [Emphasis](#em) - * [Code](#code) - * [Images](#img) -* [Miscellaneous](#misc) - * [Backslash Escapes](#backslash) - * [Automatic Links](#autolink) - - -**Note:** This document is itself written using Markdown; you -can [see the source for it by adding '.text' to the URL][src]. - - [src]: /projects/markdown/syntax.text - -* * * - -## Overview - -### Philosophy - -Markdown is intended to be as easy-to-read and easy-to-write as is feasible. - -Readability, however, is emphasized above all else. A Markdown-formatted -document should be publishable as-is, as plain text, without looking -like it's been marked up with tags or formatting instructions. While -Markdown's syntax has been influenced by several existing text-to-HTML -filters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [4], -[Grutatext] [5], and [EtText] [6] -- the single biggest source of -inspiration for Markdown's syntax is the format of plain text email. - - [1]: http://docutils.sourceforge.net/mirror/setext.html - [2]: http://www.aaronsw.com/2002/atx/ - [3]: http://textism.com/tools/textile/ - [4]: http://docutils.sourceforge.net/rst.html - [5]: http://www.triptico.com/software/grutatxt.html - [6]: http://ettext.taint.org/doc/ - -To this end, Markdown's syntax is comprised entirely of punctuation -characters, which punctuation characters have been carefully chosen so -as to look like what they mean. E.g., asterisks around a word actually -look like \*emphasis\*. Markdown lists look like, well, lists. Even -blockquotes look like quoted passages of text, assuming you've ever -used email. - - - -### Inline HTML - -Markdown's syntax is intended for one purpose: to be used as a -format for *writing* for the web. - -Markdown is not a replacement for HTML, or even close to it. Its -syntax is very small, corresponding only to a very small subset of -HTML tags. The idea is *not* to create a syntax that makes it easier -to insert HTML tags. In my opinion, HTML tags are already easy to -insert. The idea for Markdown is to make it easy to read, write, and -edit prose. HTML is a *publishing* format; Markdown is a *writing* -format. Thus, Markdown's formatting syntax only addresses issues that -can be conveyed in plain text. - -For any markup that is not covered by Markdown's syntax, you simply -use HTML itself. There's no need to preface it or delimit it to -indicate that you're switching from Markdown to HTML; you just use -the tags. - -The only restrictions are that block-level HTML elements -- e.g. `<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. `<`, 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 `<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][bq] and multi-paragraph [list items][l] -work best -- and look better -- when you format them with hard breaks. - - [bq]: #blockquote - [l]: #list - - - -### Headers - -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: - - <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"> - © 2004 Foo Corporation - </div> - -will turn into: - - <pre><code><div class="footer"> - &copy; 2004 Foo Corporation - </div> - </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 - -### Links - -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><blink></code> tags.</p> - -You can write this: - - `—` is the decimal-encoded equivalent of `—`. - -to produce: - - <p><code>&#8212;</code> is the decimal-encoded - equivalent of <code>&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 - -### Automatic Links - -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="mailto:addre - ss@example.co - m">address@exa - mple.com</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 - ->>> -headingOne: Markdown: Syntax -interblockSeparator -ulBeginTight -ulItem -BEGIN link -- label: Overview -- URI: (hash)overview -- title: -END link -interblockSeparator -ulBeginTight -ulItem -BEGIN link -- label: Philosophy -- URI: (hash)philosophy -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Inline HTML -- URI: (hash)html -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Automatic Escaping for Special Characters -- URI: (hash)autoescape -- title: -END link -ulItemEnd -ulEndTight -ulItemEnd -ulItem -BEGIN link -- label: Block Elements -- URI: (hash)block -- title: -END link -interblockSeparator -ulBeginTight -ulItem -BEGIN link -- label: Paragraphs and Line Breaks -- URI: (hash)p -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Headers -- URI: (hash)header -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Blockquotes -- URI: (hash)blockquote -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Lists -- URI: (hash)list -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Code Blocks -- URI: (hash)precode -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Horizontal Rules -- URI: (hash)hr -- title: -END link -ulItemEnd -ulEndTight -ulItemEnd -ulItem -BEGIN link -- label: Span Elements -- URI: (hash)span -- title: -END link -interblockSeparator -ulBeginTight -ulItem -BEGIN link -- label: Links -- URI: (hash)link -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Emphasis -- URI: (hash)em -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Code -- URI: (hash)code -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Images -- URI: (hash)img -- title: -END link -ulItemEnd -ulEndTight -ulItemEnd -ulItem -BEGIN link -- label: Miscellaneous -- URI: (hash)misc -- title: -END link -interblockSeparator -ulBeginTight -ulItem -BEGIN link -- label: Backslash Escapes -- URI: (hash)backslash -- title: -END link -ulItemEnd -ulItem -BEGIN link -- label: Automatic Links -- URI: (hash)autolink -- title: -END link -ulItemEnd -ulEndTight -ulItemEnd -ulEndTight -interblockSeparator -strongEmphasis: Note: -BEGIN link -- label: see the source for it by adding '.text' to the URL -- URI: /projects/markdown/syntax.text -- title: -END link -interblockSeparator -horizontalRule -interblockSeparator -headingTwo: Overview -interblockSeparator -headingThree: Philosophy -interblockSeparator -interblockSeparator -BEGIN link -- label: Setext -- URI: http://docutils.sourceforge.net/mirror/setext.html -- title: -END link -BEGIN link -- label: atx -- URI: http://www.aaronsw.com/2002/atx/ -- title: -END link -BEGIN link -- label: Textile -- URI: http://textism.com/tools/textile/ -- title: -END link -BEGIN link -- label: reStructuredText -- URI: http://docutils.sourceforge.net/rst.html -- title: -END link -BEGIN link -- label: Grutatext -- URI: http://www.triptico.com/software/grutatxt.html -- title: -END link -BEGIN link -- label: EtText -- URI: http://ettext.taint.org/doc/ -- title: -END link -interblockSeparator -interblockSeparator -headingThree: Inline HTML -interblockSeparator -emphasis: writing -interblockSeparator -emphasis: not -emphasis: publishing -emphasis: writing -interblockSeparator -interblockSeparator -codeSpan: <div> -codeSpan: <table> -codeSpan: <pre> -codeSpan: <p> -codeSpan: <p> -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/6c0e67934e0358fd4071cf4247bcf221.verbatim -interblockSeparator -codeSpan: *emphasis* -interblockSeparator -codeSpan: <span> -codeSpan: <cite> -codeSpan: <del> -codeSpan: <a> -codeSpan: <img> -interblockSeparator -emphasis: is -interblockSeparator -headingThree: Automatic Escaping for Special Characters -interblockSeparator -codeSpan: < -codeSpan: (ampersand) -codeSpan: (ampersand)lt; -codeSpan: (ampersand)amp; -interblockSeparator -ampersand -codeSpan: AT(ampersand)amp;T -interblockSeparator -inputVerbatim: ./_markdown_test/01abe6d069cf62de251cf21f8df1d11f.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/3bb5e0b18bdd7c9688b9f5df139967f3.verbatim -interblockSeparator -codeSpan: href -interblockSeparator -codeSpan: (ampersand)amp; -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/9f3cb292eb01028cce569a08ef6f975b.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/7cdba89e6cc34bd4841c7c6a41bb4156.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/c79c1d6af747ea457d80ff723101137a.verbatim -interblockSeparator -BEGIN link -- label: inline HTML -- URI: (hash)html -- title: -END link -interblockSeparator -inputVerbatim: ./_markdown_test/e76bfed335c678dbe01b3982b9b46fdc.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/cc7bb6b7c24a66c62c969328036e8f7b.verbatim -interblockSeparator -emphasis: always -codeSpan: < -codeSpan: (ampersand) -interblockSeparator -horizontalRule -interblockSeparator -headingTwo: Block Elements -interblockSeparator -headingThree: Paragraphs and Line Breaks -interblockSeparator -interblockSeparator -codeSpan: <br /> -interblockSeparator -emphasis: do -codeSpan: <br /> -interblockSeparator -codeSpan: <br /> -codeSpan: <br /> -BEGIN link -- label: blockquoting -- URI: (hash)blockquote -- title: -END link -BEGIN link -- label: list items -- URI: (hash)list -- title: -END link -interblockSeparator -headingThree: Headers -interblockSeparator -BEGIN link -- label: Setext -- URI: http://docutils.sourceforge.net/mirror/setext.html -- title: -END link -BEGIN link -- label: atx -- URI: http://www.aaronsw.com/2002/atx/ -- title: -END link -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/4f59d4e23ef758fd94bd2324643e2f2b.verbatim -interblockSeparator -codeSpan: = -codeSpan: - -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/48058b850bf198c75e9571ef25b4174e.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/37d9f30690dba801bda9a65ec7cfd1be.verbatim -interblockSeparator -headingThree: Blockquotes -interblockSeparator -codeSpan: > -codeSpan: > -interblockSeparator -inputVerbatim: ./_markdown_test/a89055d359469d454a801830954a9c6f.verbatim -interblockSeparator -codeSpan: > -interblockSeparator -inputVerbatim: ./_markdown_test/944cb176339d03ac7508f0f66090979f.verbatim -interblockSeparator -codeSpan: > -interblockSeparator -inputVerbatim: ./_markdown_test/2a3331ca2a955f6ad7da2480f9cda089.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/539f94bbd698cb75fb0cd1ba51d297b2.verbatim -interblockSeparator -interblockSeparator -headingThree: Lists -interblockSeparator -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/7667e2408d637a1e3ca69ccc1ce50809.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/f9c93344b256fc419363b5137a49888e.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/0ae7b8161204fb8d79d287ece754d868.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/5159786425bde2cec7e20b79500dde54.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/9679de8f4110a0e2906694aa1804cbf0.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/68c7899020501a169d9e9ca810aff930.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/733b6752776567144548322ef66d67e6.verbatim -interblockSeparator -interblockSeparator -interblockSeparator -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/3915e80c9e2b1a87599797fb217c295b.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/35441140ac44d3c2c7b9611d18c6dca4.verbatim -interblockSeparator -codeSpan: <p> -interblockSeparator -inputVerbatim: ./_markdown_test/92f4628c14a10b92aead4a4ebd01936a.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/02afc9ab8392711baf578d89e8b624a8.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/ec0f57523c3541a14df8f17f3c822039.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/197c8667c0c0307c8174e6a6e07c2a48.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/a07ba2a71f8cd42180768463fa2e5dad.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/d56908f0f6e2476a6146ece0fa7e2f32.verbatim -interblockSeparator -codeSpan: > -interblockSeparator -inputVerbatim: ./_markdown_test/4c06d5a765803dd6f15378765020443c.verbatim -interblockSeparator -emphasis: twice -interblockSeparator -inputVerbatim: ./_markdown_test/d3f24a5ba4f9ebe7c97b690753fef199.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/d87e20aae0facc7fbbc293f790178cf4.verbatim -interblockSeparator -emphasis: number-period-space -interblockSeparator -inputVerbatim: ./_markdown_test/ea5e5fa61236c2e31ecb34d484caed78.verbatim -interblockSeparator -headingThree: Code Blocks -interblockSeparator -codeSpan: <pre> -codeSpan: <code> -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/80158a498770adf4d0617503ae558414.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/35dd5e3b1d316dec464fafbedf53439e.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/992aa3a21cc79d1a6a7b273173e1cc48.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/d37edcee91241df6034067902bf7ff5f.verbatim -interblockSeparator -interblockSeparator -codeSpan: (ampersand) -codeSpan: < -codeSpan: > -interblockSeparator -inputVerbatim: ./_markdown_test/bfd3b2e8e47a22fe0914d55781a73b7c.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/6a14fbcefad86826e777c27a9000b94a.verbatim -interblockSeparator -interblockSeparator -headingThree: Horizontal Rules -interblockSeparator -codeSpan: <hr /> -interblockSeparator -inputVerbatim: ./_markdown_test/b3a754721670b6236c8eb8159555f38b.verbatim -interblockSeparator -horizontalRule -interblockSeparator -headingTwo: Span Elements -interblockSeparator -headingThree: Links -interblockSeparator -emphasis: inline -emphasis: reference -interblockSeparator -interblockSeparator -emphasis: optional -interblockSeparator -inputVerbatim: ./_markdown_test/1414e8798e8df1116073e37e18480580.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/fee0581724d177221ef58d9e6a498b35.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/be45edb9cb5e6fb760f9805ffc37b64b.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/00842bca924b6e825c555a0866ba0488.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/525e6727b97cbbb73ce96c0ba62e8eb6.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/a35af952f6f3a307982ea5250cfb72de.verbatim -interblockSeparator -interblockSeparator -ulBeginTight -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEndTight -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/59be3295fa322e809f4138ef7500798a.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/a39ca11b40fca9daced4a3b44b1fc1a3.verbatim -interblockSeparator -interblockSeparator -emphasis: not -interblockSeparator -inputVerbatim: ./_markdown_test/a943d1cc49e6963c7bcb45acfebf321f.verbatim -interblockSeparator -interblockSeparator -emphasis: implicit link name -interblockSeparator -inputVerbatim: ./_markdown_test/c2c38dc7e1a41ddb3d50c965e569aab4.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/17194fe133f07ed35b959c9108de4cec.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/1a7658c341b463a9232093771a413acc.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/65aaecc2b48f0d27de8de608c27ed6e7.verbatim -interblockSeparator -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/31285fcec3a6ea99b4694d3e6750fc60.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/0810a7510b5a42a7ec77fd3d55be870e.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/28d0c5764a38e6b58409f9967ef91bcc.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/f39ac74789b190c9c1460bd06b2e5f66.verbatim -interblockSeparator -interblockSeparator -interblockSeparator -headingThree: Emphasis -interblockSeparator -codeSpan: * -codeSpan: (underscore) -codeSpan: * -codeSpan: (underscore) -codeSpan: <em> -codeSpan: * -codeSpan: (underscore) -codeSpan: <strong> -interblockSeparator -inputVerbatim: ./_markdown_test/ad2981010cf94e370ccb06c7233f0989.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/451a1d0edf74505402610a4bae7997d0.verbatim -interblockSeparator -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/3f3996b979db4e11ec6fd9b0232b3d83.verbatim -interblockSeparator -codeSpan: * -codeSpan: (underscore) -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/85d79dd13f594a1dc7dc5b2be403366a.verbatim -interblockSeparator -headingThree: Code -interblockSeparator -codeSpan: ` -interblockSeparator -inputVerbatim: ./_markdown_test/3013bb705f116d1bf7d7506a827cd6f1.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/0d572dc866bb6649bdedef400a32f2ee.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/000c6f567a8ecf3820cf43f6b248b303.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/a499280e33397f3bd9ec1415835a1c04.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/56cb72e47c0ff4e11b252117ed9d7c15.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/2624fb4324d31d847556b8cf06cc71a3.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/7e31b58c38fbe808c13ae0c21943fdbb.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/775e317bc6e9bac7e3a3a3f44dade6d1.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/b71470703a2237b352df145a688666b9.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/c7d2bf55eba7aa8ecd26cc75c0116ecd.verbatim -interblockSeparator -headingThree: Images -interblockSeparator -interblockSeparator -emphasis: inline -emphasis: reference -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/95e477e08806ad17333ef8c62ab1a9bf.verbatim -interblockSeparator -interblockSeparator -ulBeginTight -ulItem -codeSpan: ! -ulItemEnd -ulItem -codeSpan: alt -ulItemEnd -ulItem -codeSpan: title -ulItemEnd -ulEndTight -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/90c3fb2e48c6bc6b5139b7d9fefe33eb.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/a5bd86aacaa065512fabab353b4646b5.verbatim -interblockSeparator -codeSpan: <img> -interblockSeparator -horizontalRule -interblockSeparator -headingTwo: Miscellaneous -interblockSeparator -headingThree: Automatic Links -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/ba84105470e6c3ca4640b0165ba73e28.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/3d59db9474543617b421ad8938c9ad5f.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/7c01c9510936100673897e413a694f95.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/57dc30d4baafa58ac03c967e1ffe882b.verbatim -interblockSeparator -interblockSeparator -interblockSeparator -headingThree: Backslash Escapes -interblockSeparator -codeSpan: <em> -interblockSeparator -inputVerbatim: ./_markdown_test/ee5b9bd27735fe320e0eb1cd9218539d.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/4f5715933ffa8d2f20d0360598a68dbb.verbatim diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/nested-blockquotes.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/nested-blockquotes.test deleted file mode 100644 index bbc0f7e4c5..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/nested-blockquotes.test +++ /dev/null @@ -1,14 +0,0 @@ -<<< -> foo -> -> > bar -> -> foo - ->>> -blockQuoteBegin -interblockSeparator -blockQuoteBegin -blockQuoteEnd -interblockSeparator -blockQuoteEnd diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/ordered-and-unordered-lists.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/ordered-and-unordered-lists.test deleted file mode 100644 index 6a88122d16..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/ordered-and-unordered-lists.test +++ /dev/null @@ -1,323 +0,0 @@ -<<< -## Unordered - -Asterisks tight: - -* asterisk 1 -* asterisk 2 -* asterisk 3 - - -Asterisks loose: - -* asterisk 1 - -* asterisk 2 - -* asterisk 3 - -* * * - -Pluses tight: - -+ Plus 1 -+ Plus 2 -+ Plus 3 - - -Pluses loose: - -+ Plus 1 - -+ Plus 2 - -+ Plus 3 - -* * * - - -Minuses tight: - -- Minus 1 -- Minus 2 -- Minus 3 - - -Minuses loose: - -- Minus 1 - -- Minus 2 - -- Minus 3 - - -## Ordered - -Tight: - -1. First -2. Second -3. Third - -and: - -1. One -2. Two -3. Three - - -Loose using tabs: - -1. First - -2. Second - -3. Third - -and using spaces: - -1. One - -2. Two - -3. Three - -Multiple paragraphs: - -1. Item 1, graf one. - - Item 2. graf two. The quick brown fox jumped over the lazy dog's - back. - -2. Item 2. - -3. Item 3. - - - -## Nested - -* Tab - * Tab - * Tab - -Here's another: - -1. First -2. Second: - * Fee - * Fie - * Foe -3. Third - -Same thing but with paragraphs: - -1. First - -2. Second: - * Fee - * Fie - * Foe - -3. Third - - -This was an error in Markdown 1.0.1: - -* this - - * sub - - that - ->>> -headingTwo: Unordered -interblockSeparator -interblockSeparator -ulBeginTight -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEndTight -interblockSeparator -interblockSeparator -ulBegin -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEnd -interblockSeparator -horizontalRule -interblockSeparator -interblockSeparator -ulBeginTight -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEndTight -interblockSeparator -interblockSeparator -ulBegin -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEnd -interblockSeparator -horizontalRule -interblockSeparator -interblockSeparator -ulBeginTight -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEndTight -interblockSeparator -interblockSeparator -ulBegin -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEnd -interblockSeparator -headingTwo: Ordered -interblockSeparator -interblockSeparator -olBeginTight -olItemWithNumber: 1 -olItemEnd -olItemWithNumber: 2 -olItemEnd -olItemWithNumber: 3 -olItemEnd -olEndTight -interblockSeparator -interblockSeparator -olBeginTight -olItemWithNumber: 1 -olItemEnd -olItemWithNumber: 2 -olItemEnd -olItemWithNumber: 3 -olItemEnd -olEndTight -interblockSeparator -interblockSeparator -olBegin -olItemWithNumber: 1 -olItemEnd -olItemWithNumber: 2 -olItemEnd -olItemWithNumber: 3 -olItemEnd -olEnd -interblockSeparator -interblockSeparator -olBegin -olItemWithNumber: 1 -olItemEnd -olItemWithNumber: 2 -olItemEnd -olItemWithNumber: 3 -olItemEnd -olEnd -interblockSeparator -interblockSeparator -olBegin -olItemWithNumber: 1 -interblockSeparator -ampersand -hash -olItemEnd -olItemWithNumber: 2 -olItemEnd -olItemWithNumber: 3 -olItemEnd -olEnd -interblockSeparator -headingTwo: Nested -interblockSeparator -ulBeginTight -ulItem -interblockSeparator -ulBeginTight -ulItem -interblockSeparator -ulBeginTight -ulItem -ulItemEnd -ulEndTight -ulItemEnd -ulEndTight -ulItemEnd -ulEndTight -interblockSeparator -ampersand -hash -interblockSeparator -olBeginTight -olItemWithNumber: 1 -olItemEnd -olItemWithNumber: 2 -interblockSeparator -ulBeginTight -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEndTight -olItemEnd -olItemWithNumber: 3 -olItemEnd -olEndTight -interblockSeparator -interblockSeparator -olBegin -olItemWithNumber: 1 -olItemEnd -olItemWithNumber: 2 -interblockSeparator -ulBeginTight -ulItem -ulItemEnd -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEndTight -olItemEnd -olItemWithNumber: 3 -olItemEnd -olEnd -interblockSeparator -interblockSeparator -ulBegin -ulItem -interblockSeparator -ulBeginTight -ulItem -ulItemEnd -ulEndTight -interblockSeparator -ulItemEnd -ulEnd diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/strong-and-em-together.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/strong-and-em-together.test deleted file mode 100644 index 44c84cd6d1..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/strong-and-em-together.test +++ /dev/null @@ -1,17 +0,0 @@ -<<< -***This is strong and em.*** - -So is ***this*** word. - -___This is strong and em.___ - -So is ___this___ word. - ->>> -strongEmphasis: (emphasis: This is strong and em.) -interblockSeparator -strongEmphasis: (emphasis: this) -interblockSeparator -strongEmphasis: (emphasis: This is strong and em.) -interblockSeparator -strongEmphasis: (emphasis: this) diff --git a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/tabs.test b/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/tabs.test deleted file mode 100644 index 4737ab75e8..0000000000 --- a/macros/generic/markdown/tests/testfiles/Markdown_1.0.3/tabs.test +++ /dev/null @@ -1,39 +0,0 @@ -<<< -+ this is a list item - indented with tabs - -+ this is a list item - indented with spaces - -Code: - - this code block is indented by one tab - -And: - - this code block is indented by two tabs - -And: - - + this is an example list item - indented with tabs - - + this is an example list item - indented with spaces - ->>> -ulBegin -ulItem -ulItemEnd -ulItem -ulItemEnd -ulEnd -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/07112549a31e78f7efb64c16f22570db.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/385fbae90889669b105262d12987e9da.verbatim -interblockSeparator -interblockSeparator -inputVerbatim: ./_markdown_test/ce062b920c62d9e77aae68da221de295.verbatim |