-
-* In a list?
-*
-* It should.
-
-> Blockquoted:
-
-Auto-links should not occur here: ``
-
- or here:
diff --git a/tests/markdown-test/backlash-escapes.html b/tests/markdown-test/backlash-escapes.html
deleted file mode 100644
index 876775f..0000000
--- a/tests/markdown-test/backlash-escapes.html
+++ /dev/null
@@ -1,67 +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: \-
\ No newline at end of file
diff --git a/tests/markdown-test/backlash-escapes.txt b/tests/markdown-test/backlash-escapes.txt
deleted file mode 100644
index 16447a0..0000000
--- a/tests/markdown-test/backlash-escapes.txt
+++ /dev/null
@@ -1,104 +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: `\-`
diff --git a/tests/markdown-test/benchmark.dat b/tests/markdown-test/benchmark.dat
deleted file mode 100644
index 3d549dd..0000000
--- a/tests/markdown-test/benchmark.dat
+++ /dev/null
@@ -1,20 +0,0 @@
-construction:0.000000:0.000000
-amps-and-angle-encoding:0.070000:131072.000000
-auto-links:0.080000:397312.000000
-backlash-escapes:0.270000:884736.000000
-blockquotes-with-dode-blocks:0.020000:0.000000
-hard-wrapped:0.020000:0.000000
-horizontal-rules:0.180000:135168.000000
-inline-html-advanced:0.070000:0.000000
-inline-html-comments:0.080000:0.000000
-inline-html-simple:0.210000:0.000000
-links-inline:0.140000:0.000000
-links-reference:0.170000:0.000000
-literal-quotes:0.090000:0.000000
-markdown-documentation-basics:0.690000:1806336.000000
-markdown-syntax:3.310000:6696960.000000
-nested-blockquotes:0.200000:0.000000
-ordered-and-unordered-list:0.530000:0.000000
-strong-and-em-together:0.200000:0.000000
-tabs:0.200000:0.000000
-tidyness:0.200000:0.000000
diff --git a/tests/markdown-test/blockquotes-with-code-blocks.html b/tests/markdown-test/blockquotes-with-code-blocks.html
deleted file mode 100644
index 5fc98b1..0000000
--- a/tests/markdown-test/blockquotes-with-code-blocks.html
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Example:
-sub status {
- print "working";
-}
-
-Or:
-sub status {
- return "working";
-}
-
-
\ No newline at end of file
diff --git a/tests/markdown-test/blockquotes-with-code-blocks.txt b/tests/markdown-test/blockquotes-with-code-blocks.txt
deleted file mode 100644
index c31d171..0000000
--- a/tests/markdown-test/blockquotes-with-code-blocks.txt
+++ /dev/null
@@ -1,11 +0,0 @@
-> Example:
->
-> sub status {
-> print "working";
-> }
->
-> Or:
->
-> sub status {
-> return "working";
-> }
diff --git a/tests/markdown-test/codeblock-in-list.html b/tests/markdown-test/codeblock-in-list.html
deleted file mode 100644
index 49edd56..0000000
--- a/tests/markdown-test/codeblock-in-list.html
+++ /dev/null
@@ -1,14 +0,0 @@
-
\ No newline at end of file
diff --git a/tests/markdown-test/codeblock-in-list.txt b/tests/markdown-test/codeblock-in-list.txt
deleted file mode 100644
index 87d4e3b..0000000
--- a/tests/markdown-test/codeblock-in-list.txt
+++ /dev/null
@@ -1,10 +0,0 @@
-* A list item with a code block
-
- Some *code*
-
-* Another list item
-
- More code
-
- And more code
-
diff --git a/tests/markdown-test/hard-wrapped.html b/tests/markdown-test/hard-wrapped.html
deleted file mode 100644
index e28e900..0000000
--- a/tests/markdown-test/hard-wrapped.html
+++ /dev/null
@@ -1,7 +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.
\ No newline at end of file
diff --git a/tests/markdown-test/hard-wrapped.txt b/tests/markdown-test/hard-wrapped.txt
deleted file mode 100644
index f8a5b27..0000000
--- a/tests/markdown-test/hard-wrapped.txt
+++ /dev/null
@@ -1,8 +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.
diff --git a/tests/markdown-test/horizontal-rules.html b/tests/markdown-test/horizontal-rules.html
deleted file mode 100644
index 478e8c5..0000000
--- a/tests/markdown-test/horizontal-rules.html
+++ /dev/null
@@ -1,39 +0,0 @@
-Dashes:
-
-
-
-
----
-
-
-
-
-
-- - -
-
-Asterisks:
-
-
-
-
-***
-
-
-
-
-
-* * *
-
-Underscores:
-
-
-
-
-___
-
-
-
-
-
-_ _ _
-
\ No newline at end of file
diff --git a/tests/markdown-test/horizontal-rules.txt b/tests/markdown-test/horizontal-rules.txt
deleted file mode 100644
index 1594bda..0000000
--- a/tests/markdown-test/horizontal-rules.txt
+++ /dev/null
@@ -1,67 +0,0 @@
-Dashes:
-
----
-
- ---
-
- ---
-
- ---
-
- ---
-
-- - -
-
- - - -
-
- - - -
-
- - - -
-
- - - -
-
-
-Asterisks:
-
-***
-
- ***
-
- ***
-
- ***
-
- ***
-
-* * *
-
- * * *
-
- * * *
-
- * * *
-
- * * *
-
-
-Underscores:
-
-___
-
- ___
-
- ___
-
- ___
-
- ___
-
-_ _ _
-
- _ _ _
-
- _ _ _
-
- _ _ _
-
- _ _ _
diff --git a/tests/markdown-test/inline-html-advanced.html b/tests/markdown-test/inline-html-advanced.html
deleted file mode 100644
index af1dec1..0000000
--- a/tests/markdown-test/inline-html-advanced.html
+++ /dev/null
@@ -1,12 +0,0 @@
-Simple block on one line:
-foo
-
-And nested without indentation:
-
\ No newline at end of file
diff --git a/tests/markdown-test/inline-html-advanced.txt b/tests/markdown-test/inline-html-advanced.txt
deleted file mode 100644
index 9d71ddc..0000000
--- a/tests/markdown-test/inline-html-advanced.txt
+++ /dev/null
@@ -1,14 +0,0 @@
-Simple block on one line:
-
-foo
-
-And nested without indentation:
-
-
diff --git a/tests/markdown-test/inline-html-comments.html b/tests/markdown-test/inline-html-comments.html
deleted file mode 100644
index 0d4cad9..0000000
--- a/tests/markdown-test/inline-html-comments.html
+++ /dev/null
@@ -1,11 +0,0 @@
-Paragraph one.
-
-
-
-
-Paragraph two.
-
-
-The end.
\ No newline at end of file
diff --git a/tests/markdown-test/inline-html-comments.txt b/tests/markdown-test/inline-html-comments.txt
deleted file mode 100644
index 41d830d..0000000
--- a/tests/markdown-test/inline-html-comments.txt
+++ /dev/null
@@ -1,13 +0,0 @@
-Paragraph one.
-
-
-
-
-
-Paragraph two.
-
-
-
-The end.
diff --git a/tests/markdown-test/inline-html-simple.html b/tests/markdown-test/inline-html-simple.html
deleted file mode 100644
index cb10451..0000000
--- a/tests/markdown-test/inline-html-simple.html
+++ /dev/null
@@ -1,58 +0,0 @@
-Here's a simple block:
-
- foo
-
-
-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:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/tests/markdown-test/inline-html-simple.txt b/tests/markdown-test/inline-html-simple.txt
deleted file mode 100644
index 14aa2dc..0000000
--- a/tests/markdown-test/inline-html-simple.txt
+++ /dev/null
@@ -1,69 +0,0 @@
-Here's a simple block:
-
-
- foo
-
-
-This should be a code block, though:
-
-
- foo
-
-
-As should this:
-
- foo
-
-Now, nested:
-
-
-
-This should just be an HTML comment:
-
-
-
-Multiline:
-
-
-
-Code block:
-
-
-
-Just plain comment, with trailing spaces on the line:
-
-
-
-Code:
-
-
-
-Hr's:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/tests/markdown-test/links-inline.html b/tests/markdown-test/links-inline.html
deleted file mode 100644
index 707937a..0000000
--- a/tests/markdown-test/links-inline.html
+++ /dev/null
@@ -1,5 +0,0 @@
-Just a URL.
-URL and title.
-URL and title.
-URL and title.
-Empty.
\ No newline at end of file
diff --git a/tests/markdown-test/links-inline.txt b/tests/markdown-test/links-inline.txt
deleted file mode 100644
index 4d0c1c2..0000000
--- a/tests/markdown-test/links-inline.txt
+++ /dev/null
@@ -1,9 +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").
-
-[Empty]().
diff --git a/tests/markdown-test/links-reference.html b/tests/markdown-test/links-reference.html
deleted file mode 100644
index 165c71a..0000000
--- a/tests/markdown-test/links-reference.html
+++ /dev/null
@@ -1,10 +0,0 @@
-Foo bar.
-Foo bar.
-Foo bar.
-With embedded [brackets].
-Indented once.
-Indented twice.
-Indented thrice.
-Indented [four][] times.
-[four]: /url
-
\ No newline at end of file
diff --git a/tests/markdown-test/links-reference.txt b/tests/markdown-test/links-reference.txt
deleted file mode 100644
index b2fa734..0000000
--- a/tests/markdown-test/links-reference.txt
+++ /dev/null
@@ -1,31 +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/
diff --git a/tests/markdown-test/literal-quotes.html b/tests/markdown-test/literal-quotes.html
deleted file mode 100644
index 0342589..0000000
--- a/tests/markdown-test/literal-quotes.html
+++ /dev/null
@@ -1,2 +0,0 @@
-Foo bar.
-Foo bar.
\ No newline at end of file
diff --git a/tests/markdown-test/literal-quotes.txt b/tests/markdown-test/literal-quotes.txt
deleted file mode 100644
index 29d0e42..0000000
--- a/tests/markdown-test/literal-quotes.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-Foo [bar][].
-
-Foo [bar](/url/ "Title with "quotes" inside").
-
-
- [bar]: /url/ "Title with "quotes" inside"
-
diff --git a/tests/markdown-test/markdown-documentation-basics.html b/tests/markdown-test/markdown-documentation-basics.html
deleted file mode 100644
index 3bcaea9..0000000
--- a/tests/markdown-test/markdown-documentation-basics.html
+++ /dev/null
@@ -1,243 +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 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 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.
-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.
-
-I wish SmartyPants used named entities like `—`
-instead of decimal-encoded entites like `—`.
-
-Output:
-<p>I strongly recommend against using any
-<code><blink></code> tags.</p>
-
-<p>I wish SmartyPants used named entities like
-<code>&mdash;</code> instead of decimal-encoded
-entites like <code>&#8212;</code>.</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>
-
\ No newline at end of file
diff --git a/tests/markdown-test/markdown-documentation-basics.txt b/tests/markdown-test/markdown-documentation-basics.txt
deleted file mode 100644
index 486055c..0000000
--- a/tests/markdown-test/markdown-documentation-basics.txt
+++ /dev/null
@@ -1,306 +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 `` and `` 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:
-
- 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
-
-
-
-
-### 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:
-
- 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.
-
-
-
-## 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:
-
-
- - Candy.
- - Gum.
- - Booze.
-
-
-Ordered (numbered) lists use regular numbers, followed by periods, as
-list markers:
-
- 1. Red
- 2. Green
- 3. Blue
-
-Output:
-
-
- - Red
- - Green
- - Blue
-
-
-If you put blank lines between items, you'll get `` 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:
-
-
-
-
-
-### 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:
-
- This is an
- example link.
-
-Optionally, you may include a title attribute in the parentheses:
-
- This is an [example link](http://example.com/ "With a Title").
-
-Output:
-
- This is an
- example link.
-
-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:
-
- I get 10 times more traffic from Google than from Yahoo or MSN.
-
-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:
-
- I start my morning with a cup of coffee and
- The New York Times.
-
-
-### 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:
-
-
-
-
-
-### 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 `