This is a set of tests for pandoc. Most of them are adapted from John Gruber’s markdown test suite.
with no blank line
with no blank line
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.
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:
---- (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: \$ \\ \> \[ \{
Asterisks tight:
Asterisks loose:
asterisk 1
asterisk 2
asterisk 3
Pluses tight:
Pluses loose:
Plus 1
Plus 2
Plus 3
Minuses tight:
Minuses loose:
Minus 1
Minus 2
Minus 3
Tight:
and:
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.
Here’s another:
Same thing but with paragraphs:
First
Second:
Third
this is a list item indented with tabs
this is a list item indented with spaces
this is an example list item indented with tabs
this is an example list item indented with spaces
and now 3
with a continuation
Nesting:
Autonumbering:
Should not be a list item:
M.A. 2007
B. Williams
Tight using spaces:
Tight using tabs:
Loose:
red fruit
orange fruit
yellow fruit
Multiple blocks with italics:
red fruit
contains seeds, crisp, pleasant to taste
orange fruit
{ orange code block }
orange block quote
Simple block on one line:
And nested without indentation:
Interpreted markdown in a table:
This is emphasized | And this is strong |
Here’s a simple block:
This should be a code block, though:
<div>
foo
</div>
As should this:
<div>foo</div>
Now, nested:
This should just be an HTML comment:
Multiline:
Code block:
<!-- Comment -->
Just plain comment, with trailing spaces on the line:
Code:
<hr />
Hr’s:
This is emphasized, and so is this.
This is strong, and so is this.
An emphasized link.
This is strong and em.
So is this word.
This is strong and em.
So is this word.
This is code: >
, $
, \
, \$
, <html>
.
This is strikeout.
Superscripts: abcd ahello ahello there.
Subscripts: H2O, H23O, Hmany of themO.
These should not be superscripts or subscripts, because of the unescaped spaces: a^b c^d, a~b c~d.
“Hello,” said the spider. “‘Shelob’ is my name.”
‘A’, ‘B’, and ‘C’ are letters.
‘Oak,’ ‘elm,’ and ‘beech’ are names of trees. So is ‘pine.’
‘He said, “I want to go.”’ Were you alive in the 70’s?
Here is some quoted ‘code
’ and a “quoted link”.
Some dashes: one—two — three—four — five.
Dashes between numbers: 5–7, 255–66, 1987–1999.
Ellipses…and…and….
These shouldn’t be math:
$e = mc^2$
.$
: $73 this should be emphasized 23$.Here’s a LaTeX table:
Here is some unicode:
AT&T has an ampersand in their name.
AT&T is another way to write it.
This & that.
4 < 5.
6 > 5.
Backslash: \
Backtick: `
Asterisk: *
Underscore: _
Left brace: {
Right brace: }
Left bracket: [
Right bracket: ]
Left paren: (
Right paren: )
Greater-than: >
Hash: #
Period: .
Bang: !
Plus: +
Minus: -
Just a URL.
Foo bar.
Foo bar.
Foo bar.
With embedded [brackets].
b by itself should be a link.
Indented once.
Indented twice.
Indented thrice.
This should [not][] be a link.
[not]: /url
Foo bar.
Foo biz.
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 in pointy braces.
With an ampersand: http://example.com/?foo=1&bar=2
http://example.com/
An e-mail address:
Blockquoted:
http://example.com/
Auto-links should not occur here: <http://example.com/>
or here: <http://example.com/>
From “Voyage dans la Lune” by Georges Melies (1902):
Here is a movie icon.
Here is a footnote reference,1 and another.2 This should not be a footnote reference, because it contains a space.[^my note] Here is an inline note.3
Notes can go in quotes.4
This paragraph should not be part of the note, as it is not indented.
Here is the footnote. It can go anywhere after the footnote reference. It need not be placed at the end of the document. ↩
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).
{ <code> }
If you want, you can indent every line, but you can also be lazy and just indent the first line of each block. ↩
This is easier to type. Inline notes may contain links and ]
verbatim characters, as well as [bracketed text]. ↩
In quote. ↩
In list. ↩