This is a set of tests for pandoc. Most of them are adapted from John Gruber’s markdown test suite.

----
h1. {anchor:headers}Headers
h2. {anchor:level-2-with-an-embedded-link}Level 2 with an [embedded link|/url]
h3. {anchor:level-3-with-emphasis}Level 3 with _emphasis_
h4. {anchor:level-4}Level 4
h5. {anchor:level-5}Level 5
h1. {anchor:level-1}Level 1
h2. {anchor:level-2-with-emphasis}Level 2 with _emphasis_
h3. {anchor:level-3}Level 3
with no blank line

h2. {anchor:level-2}Level 2
with no blank line

----
h1. {anchor:paragraphs}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.

----
h1. {anchor:block-quotes}Block Quotes
E-mail style:

bq. This is a block quote. It is pretty short.
{quote}
Code in a block quote:

{code:java}
sub status {
    print "working";
}
{code}
A list:

# item one
# item two

Nested block quotes:

bq. nested
bq. nested
{quote}
This should not be a block quote: 2 > 1.

And a following paragraph.

----
h1. {anchor:code-blocks}Code Blocks
Code:

{code:java}
---- (should be four hyphens)

sub status {
    print "working";
}

this code block is indented by one tab
{code}
And:

{code:java}
    this code block is indented by two tabs

These should not be escaped:  \$ \\ \> \[ \{
{code}
----
h1. {anchor:lists}Lists
h2. {anchor:unordered}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

h2. {anchor:ordered}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.

h2. {anchor:nested}Nested
* Tab
** Tab
*** Tab

Here’s another:

# First
# Second:
#* Fee
#* Fie
#* Foe
# Third

Same thing but with paragraphs:

# First
# Second:
#* Fee
#* Fie
#* Foe
# Third

h2. {anchor:tabs-and-spaces}Tabs and spaces
* 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

h2. {anchor:fancy-list-markers}Fancy list markers
# begins with 2
# and now 3
with a continuation
## sublist with roman numerals, starting with 4
## more items
### a subsublist
### a subsublist

Nesting:

# Upper Alpha
## Upper Roman.
### Decimal start with 6
#### Lower alpha with paren

Autonumbering:

# Autonumber.
# More.
## Nested.

Should not be a list item:

M.A. 2007

B. Williams

----
h1. {anchor:definition-lists}Definition Lists
Tight using spaces:

* *apple*
red fruit
* *orange*
orange fruit
* *banana*
yellow fruit

Tight using tabs:

* *apple*
red fruit
* *orange*
orange fruit
* *banana*
yellow fruit

Loose:

* *apple*
red fruit
* *orange*
orange fruit
* *banana*
yellow fruit

Multiple blocks with italics:

* *_apple_*
red fruit
contains seeds, crisp, pleasant to taste
* *_orange_*
orange fruit
{code:java}
{ orange code block }
{code}
bq. orange block quote

Multiple definitions, tight:

* *apple*
red fruit
computer
* *orange*
orange fruit
bank

Multiple definitions, loose:

* *apple*
red fruit
computer
* *orange*
orange fruit
bank

Blank line after term, indented marker, alternate markers:

* *apple*
red fruit
computer
* *orange*
orange fruit
*# sublist
*# sublist

h1. {anchor:html-blocks}HTML Blocks
Simple block on one line:

foo

And nested without indentation:

foo

bar

Interpreted markdown in a table:

This is _emphasized_

And this is *strong*

Here’s a simple block:

foo

This should be a code block, though:

{code:java}
<div>
    foo
</div>
{code}
As should this:

{code:java}
<div>foo</div>
{code}
Now, nested:

foo

This should just be an HTML comment:

Multiline:

Code block:

{code:java}
<!-- Comment -->
{code}
Just plain comment, with trailing spaces on the line:

Code:

{code:java}
<hr />
{code}
Hr’s:

----
h1. {anchor:inline-markup}Inline Markup
This is _emphasized_, and so _is this_.

This is *strong*, and so *is this*.

An _[emphasized link|/url]_.

*_This is strong and em._*

So is *_this_* word.

*_This is strong and em._*

So is *_this_* word.

This is code: {{>}}, {{$}}, {{&bsol;}}, {{&bsol;$}}, {{<html>}}.

-This is _strikeout_.-

Superscripts: a{^}bc{^}d a{^}_hello_{^} a{^}hello there{^}.

Subscripts: H{~}2{~}O, H{~}23{~}O, H{~}many of them{~}O.

These should not be superscripts or subscripts, because of the unescaped spaces: a^b c^d, a~b c~d.

----
h1. {anchor:smart-quotes-ellipses-dashes}Smart quotes, ellipses, dashes
"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|http://example.com/?foo=1&bar=2]".

Some dashes: one—two — three—four — five.

Dashes between numbers: 5–7, 255–66, 1987–1999.

Ellipses…and…and….

----
h1. {anchor:latex}LaTeX
* 
* 2 + 2 = 4
* _x_ ∈ {_}y{_}
* _α_ ∧ {_}ω{_}
* 223
* _p_\-Tree
* Here’s some display math: 
$$\frac{d\}\{dx}f\(x)=\lim\_\{h\to 0\}&bsol;frac{f(x+h)-f\(x)\}\{h}$$

* Here’s one that has a line break in it: _α_ + {_}ω{_} × {_}x{_}^2^.

These shouldn’t be math:

* To get the famous equation, write {{$e = mc^2$}}.
* $22,000 is a _lot_ of money. So is $34,000. \(It worked if "lot" is emphasized.)
* Shoes \($20) and socks \($5).
* Escaped {{$}}: $73 _this should be emphasized_ 23$.

Here’s a LaTeX table:

----
h1. {anchor:special-characters}Special Characters
Here is some unicode:

* I hat: Î
* o umlaut: ö
* section: §
* set membership: ∈
* copyright: ©

AT&T has an ampersand in their name.

AT&T is another way to write it.

This & that.

4 < 5.

6 > 5.

Backslash: &bsol;

Backtick: `

Asterisk: \*

Underscore: \_

Left brace: \{

Right brace: \}

Left bracket: \[

Right bracket: \]

Left paren: \(

Right paren: )

Greater-than: >

Hash: #

Period: .

Bang: \!

Plus: \+

Minus: \-

----
h1. {anchor:links}Links
h2. {anchor:explicit}Explicit
Just a [URL|/url/].

[URL and title|/url/].

[URL and title|/url/].

[URL and title|/url/].

[URL and title|/url/]

[URL and title|/url/]

[with_underscore|/url/with_underscore]

[Email link|mailto:nobody@nowhere.net]

[Empty|].

h2. {anchor:reference}Reference
Foo [bar|/url/].

With [embedded \[brackets\]|/url/].

[b|/url/] by itself should be a link.

Indented [once|/url].

Indented [twice|/url].

Indented [thrice|/url].

This should \[not\]\[\] be a link.

{code:java}
[not]: /url
{code}
Foo [bar|/url/].

Foo [biz|/url/].

h2. {anchor:with-ampersands}With ampersands
Here’s a [link with an ampersand in the URL|http://example.com/?foo=1&bar=2].

Here’s a link with an amersand in the link text: [AT&T|http://att.com/].

Here’s an [inline link|/script?foo=1&bar=2].

Here’s an [inline link in pointy braces|/script?foo=1&bar=2].

h2. {anchor:autolinks}Autolinks
With an ampersand: [http://example.com/?foo=1&bar=2|http://example.com/?foo=1&bar=2]

* In a list?
* [http://example.com/|http://example.com/]
* It should.

An e-mail address: [nobody@nowhere.net|mailto:nobody@nowhere.net]

bq. Blockquoted: [http://example.com/|http://example.com/]
Auto-links should not occur here: {{<http://example.com/>}}

{code:java}
or here: <http://example.com/>
{code}
----
h1. {anchor:images}Images
From "Voyage dans la Lune" by Georges Melies \(1902):

!lalune.jpg|title=fig:Voyage dans la Lune!

Here is a movie !movie.jpg! icon.

----
h1. {anchor:footnotes}Footnotes
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]

bq. Notes can go in quotes.[4]
# And in list items.[5]

This paragraph should not be part of the note, as it is not indented.


\[1] Here is the footnote. It can go anywhere after the footnote reference. It need not be placed at the end of the document.


\[2] 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:java}
  { <code> }
{code}
If you want, you can indent every line, but you can also be lazy and just indent the first line of each block.


\[3] This is _easier_ to type. Inline notes may contain [links|http://google.com] and {{\]}} verbatim characters, as well as \[bracketed text].


\[4] In quote.


\[5] In list.