Tissevert/pandoc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
pandoc/tests/writer.markdown

627 lines
7.7 KiB
Markdown
Raw Normal View History

initial import git-svn-id: https://pandoc.googlecode.com/svn/trunk@2 788f1e2b-df1e-0410-8736-df70ead52e1b
2006-10-17 16:22:29 +02:00
% Pandoc Test Suite
% John MacFarlane, Anonymous
% July 17, 2006
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](/url)
### 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:
>
> 1. item one
> 2. item two
>
> Nested block quotes:
>
> > nested
>
> > nested
This should not be a block quote: 2 > 1.
Box-style:
> Example:
>
> sub status {
> print "working";
> }
> 1. do laundry
> 2. take out the trash
Here's a nested one:
> Joe said:
>
> > Don't quote me.
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:
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 1. 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
## 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
* * * * *
# HTML Blocks
Simple block on one line:
<div>
foo
</div>
And nested without indentation:
<div>
<div>
<div>
foo
</div>
</div>
<div>
bar
</div>
</div>
Interpreted markdown in a table:
<table>
<tr>
<td>
This is *emphasized*
</td>
<td>
And this is **strong**
</td>
</tr>
</table>
<script type="text/javascript">document.write('This *should not* be interpreted as markdown');</script>
Here's a simple block:
<div>
foo
</div>
This should be a code block, though:
<div>
foo
</div>
As should this:
<div>foo</div>
Now, nested:
<div>
<div>
<div>
foo
</div>
</div>
</div>
This should just be an HTML comment:
<!-- Comment -->
Multiline:
<!--
Blah
Blah
-->
<!--
This is another comment.
-->
Code block:
<!-- Comment -->
Just plain comment, with trailing spaces on the line:
<!-- foo -->
Code:
<hr />
Hr's:
<hr>
<hr />
<hr />
<hr>
<hr />
<hr />
<hr class="foo" id="bar" />
<hr class="foo" id="bar" />
<hr class="foo" id="bar">
* * * * *
# 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: `>`, `$`, `\`, `\$`, `<html>`.
* * * * *
# 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][1]".
Some dashes: one---two --- three--four -- five.
Dashes between numbers: 5-7, 255-66, 1987-1999.
Ellipses...and. . .and . . . .
* * * * *
# LaTeX
- \cite[22-23]{smith.1899}
- \doublespacing
- $2+2=4$
- $x \in y$
- $\alpha \wedge \omega$
- $223$
- $p$-Tree
- $\frac{d}{dx}f(x)=\lim_{h\to 0}\frac{f(x+h)-f(x)}{h}$
- Here's one that has a line break in it:
$\alpha + \omega \times 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.)
- Escaped `$`: $73 *this should be emphasized* 23$.
Here's a LaTeX table:
\begin{tabular}{|l|l|}\hline
Animal & Number \\ \hline
Dog & 2 \\
Cat & 1 \\ \hline
\end{tabular}
* * * * *
# 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: \\
Backtick: \`
Asterisk: \*
Underscore: \_
Left brace: {
Right brace: }
Left bracket: [
Right bracket: ]
Left paren: (
Right paren: )
Greater-than: >
Hash: #
Period: .
Bang: !
Plus: +
Minus: -
* * * * *
# Links
## Explicit
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 with &quot;quotes&quot; in it")
[URL and title](/url/ "title with single quotes")
[Email link](mailto:nobody@nowhere.net)
[Empty]().
## Reference
Foo [bar][a].
Foo [bar][a].
Foo [bar][a].
[a]: /url/
With [embedded [brackets][]][b].
[b][] by itself should be a link.
Indented [once][].
Indented [twice][].
Indented [thrice][].
This should [not][] be a link.
[once]: /url
[twice]: /url
[thrice]: /url
[not]: /url
[b]: /url/
Foo [bar][].
Foo [biz](/url/ "Title with &quot;quote&quot; inside").
[bar]: /url/ "Title with &quot;quotes&quot; inside"
## With ampersands
Here's a [link with an ampersand in the URL][1].
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 in pointy braces](/script?foo=1&bar=2).
[1]: http://example.com/?foo=1&bar=2
[2]: http://att.com/ "AT&T"
## 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)
> Blockquoted: [http://example.com/](http://example.com/)
Auto-links should not occur here: `<http://example.com/>`
or here: <http://example.com/>
* * * * *
# Images
From "Voyage dans la Lune" by Georges Melies (1902):
![lalune]
[lalune]: lalune.jpg "Voyage dans la Lune"
Here is a movie ![movie](movie.jpg) icon.
* * * * *
# Footnotes
Changed footnote syntax to conform to the de facto standard for markdown footnotes. References are now like this[^1] rather than like this^(1). There are corresponding changes in the footnotes themselves. See the updated README for more details. git-svn-id: https://pandoc.googlecode.com/svn/trunk@230 788f1e2b-df1e-0410-8736-df70ead52e1b
2006-12-19 08:30:36 +01:00
Here is a footnote reference[^1], and another[^longnote]. This
initial import git-svn-id: https://pandoc.googlecode.com/svn/trunk@2 788f1e2b-df1e-0410-8736-df70ead52e1b
2006-10-17 16:22:29 +02:00
should *not* be a footnote reference, because it contains a
Changed footnote syntax to conform to the de facto standard for markdown footnotes. References are now like this[^1] rather than like this^(1). There are corresponding changes in the footnotes themselves. See the updated README for more details. git-svn-id: https://pandoc.googlecode.com/svn/trunk@230 788f1e2b-df1e-0410-8736-df70ead52e1b
2006-12-19 08:30:36 +01:00
space[\^my note].
[^1]: Here is the footnote. It can go anywhere in the document, not just
at the end.
[^longnote]: Here's the other 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.
initial import git-svn-id: https://pandoc.googlecode.com/svn/trunk@2 788f1e2b-df1e-0410-8736-df70ead52e1b
2006-10-17 16:22:29 +02:00
Reference in a new issue Copy permalink