This is a set of tests for pandoc. Most of them are adapted from John Gruber’s markdown test suite. ---- ====== Headers ====== ===== Level 2 with an embedded link ===== ==== Level 3 with emphasis ==== === Level 4 === == Level 5 == ====== Level 1 ====== ===== Level 2 with emphasis ===== ==== Level 3 ==== with no blank line ===== Level 2 ===== with no blank line ---- ====== Paragraphs ====== Here’s a regular paragraph. 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. There should be a hard line break\\ here. ---- ====== Block Quotes ====== E-mail style: > This is a block quote. It is pretty short.
Code in a block quote:
sub status {
print "working";
}
A list:
- item one
- item two
Nested block quotes:
> nested
> nested
This should not be a block quote: 2 > 1.
And a following paragraph.
----
====== Code Blocks ======
Code:
---- (should be four hyphens)
sub status {
print "working";
}
this code block is indented by one tab
And:
this code block is indented by two tabs
These should not be escaped: \$ \\ \> \[ \{
----
====== Lists ======
===== 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:
- First
- Second
- Third
and:
- One
- Two
- Three
Loose using tabs:
- First
- Second
- Third
and using spaces:
- One
- Two
- Three
Multiple paragraphs:
Item 1, graf one.
Item 1. graf two. The quick brown fox jumped over the lazy dog’s back.
Item 2.
Item 3.
and now 3
with a continuation
red fruit
contains seeds, crisp, pleasant to taste
orange fruit
{ orange code block }
> orange block quote
This is //emphasized// | And this is **strong** |
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:
[not]: /url
Foo [[url/|bar]].
Foo [[url/|biz]].
===== With ampersands =====
Here’s a [[http://example.com/?foo=1&bar=2|link with an ampersand in the URL]].
Here’s a link with an amersand in the link text: [[http://att.com/|AT&T]].
Here’s an [[script?foo=1&bar=2|inline link]].
Here’s an [[script?foo=1&bar=2|inline link in pointy braces]].
===== Autolinks =====
With an ampersand: http://example.com/?foo=1&bar=2
* In a list?
* http://example.com/
* It should.
An e-mail address: or here:
----
====== Images ======
From “Voyage dans la Lune” by Georges Melies (1902):
{{:lalune.jpg|Voyage dans la Lune lalune}}
Here is a movie {{:movie.jpg|movie}} icon.
----
====== Footnotes ======
Here is a footnote reference,((Here is the footnote. It can go anywhere after the footnote reference. It need not be placed at the end of the document.
)) and another.((Here’s the long note. This one contains multiple blocks.
Subsequent blocks are indented to show that they belong to the footnote (as with list items).
{ }
If you want, you can indent every line, but you can also be lazy and just indent the first line of each block.
)) This should //not// be a footnote reference, because it contains a space.[^my note] Here is an inline note.((This is //easier// to type. Inline notes may contain [[http://google.com|links]] and ''%%]%%'' verbatim characters, as well as [bracketed text].
))
> Notes can go in quotes.((In quote.
))
- And in list items.((In list.))
This paragraph should not be part of the note, as it is not indented.