Bug#551239: libtext-multimarkdown-perl: FTBFS: failed test
Lucas Nussbaum
lucas at lucas-nussbaum.net
Fri Oct 16 16:32:21 UTC 2009
Source: libtext-multimarkdown-perl
Version: 1.0.27-2
Severity: serious
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20091016 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[2]: Entering directory `/build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27'
> PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'inc', 'blib/lib', 'blib/arch')" t/*.t
> t/01use.t ................................. ok
> t/02pod.t ................................. ok
> t/03podcoverage.t ......................... ok
> t/03podspelling.t ......................... skipped: Test::Spelling 0.11 not installed
>
> # Failed test at t/04markdown.t line 14.
> # got: 'Foo
> #
> # Bar
> # '
> # expected: '<p>Foo</p>
> #
> # <p>Bar</p>
> # '
>
> # Failed test at t/04markdown.t line 26.
> # got: 'Foo
> #
> # Bar
> # '
> # expected: '<p>Foo</p>
> #
> # <p>Bar</p>
> # '
> # Looks like you failed 2 tests of 3.
> t/04markdown.t ............................
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 2/3 subtests
>
> # Failed test at t/05options.t line 12.
> # got: '<p>[test][] the link!</p>
> # '
> # expected: '[test][] the link!
> # '
>
> # Failed test at t/05options.t line 20.
> # got: '<p><a href="http://example.com">test</a> the link!</p>
> # '
> # expected: '<a href="http://example.com">test</a> the link!
> # '
> # Looks like you failed 2 tests of 3.
> t/05options.t .............................
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 2/3 subtests
> t/06wiki.t ................................ ok
>
> # Failed test 'Output matches expected'
> # at t/07fulldoc.t line 27.
> # got: '<h1 id="heading1">Heading 1</h1>
> #
> # <h2 id="heading2">Heading 2</h2>
> #
> # <h3 id="heading3">Heading 3</h3>
> #
> # <h2 id="othertypeofheadinglevel2">Other type of heading (level 2)</h2>
> #
> # <h1 id="andanotheronelevel1">And another one (level 1)</h1>
> #
> # A paragraph, of <em>text</em>.
> #
> # <ul>
> # <li>UL item 1</li>
> # <li>UL item 2</li>
> # </ul>
> #
> # Another paragraph *Not bold text*.
> #
> # <ol>
> # <li>OL, item 1</li>
> # <li>OL, item 2</li>
> # </ol>
> #
> # A third paragraph
> #
> # <ul>
> # <li>Second list, item 1
> # <ul>
> # <li>Sub list item 1</li>
> # <li>Sub list item 2</li>
> # </ul></li>
> # <li>Second list, item 2</li>
> # </ul>
> #
> # Within a paragraph <code>code block</code>, followed by one which needs <code>extra escapeing`</code> © t0m.
> # & note <strong>ampersands</strong> and > or < <em>are</em> escaped <strong>properly</strong> in output
> #
> # This paragraph has <a href="http://www.test.com/" title="Test dot Com website">a link</a> and <a href="http://www.test2.com/">another link</a>.. This is <a href="http://example.com/" title="Title">an example</a> inline link.
> #
> # Or, we could use <a href="http://wuto-links.com/">http://wuto-links.com/</a>. Or shortcut links like this: <a href="http://google.com/">Google</a>
> #
> # <blockquote>
> # <p>block quoted text</p>
> #
> # <p>in multiple paragraphs
> # and across multiple lines</p>
> #
> # <blockquote>
> # <p>and at
> # multiple levels.</p>
> # </blockquote>
> # </blockquote>
> #
> # <pre><code>This is a code block here...
> # </code></pre>
> #
> # <hr />
> #
> # <hr />
> #
> # <hr />
> #
> # un*fucking*believable - *this text is surrounded by literal asterisks*, but the text before that should be bold according to the docs, but isn't FIXME!
> #
> # <img src="/path/to/img.jpg" alt="Alt text" id="alttext" />
> #
> # <img src="/path/to/img2.jpg" alt="Alt text2" title="Optional title" id="alttext2" />
> #
> # <img src="url/to/image" alt="Alt text for ref mode" title="Optional title attribute" id="alttextforrefmode" />
> #
> # <hr />
> # '
> # expected: '<h1 id="heading1">Heading 1</h1>
> #
> # <h2 id="heading2">Heading 2</h2>
> #
> # <h3 id="heading3">Heading 3</h3>
> #
> # <h2 id="othertypeofheadinglevel2">Other type of heading (level 2)</h2>
> #
> # <h1 id="andanotheronelevel1">And another one (level 1)</h1>
> #
> # <p>A paragraph, of <em>text</em>. </p>
> #
> # <ul>
> # <li>UL item 1</li>
> # <li>UL item 2</li>
> # </ul>
> #
> # <p>Another paragraph *Not bold text*.</p>
> #
> # <ol>
> # <li>OL, item 1</li>
> # <li>OL, item 2</li>
> # </ol>
> #
> # <p>A third paragraph</p>
> #
> # <ul>
> # <li>Second list, item 1
> # <ul>
> # <li>Sub list item 1</li>
> # <li>Sub list item 2</li>
> # </ul></li>
> # <li>Second list, item 2</li>
> # </ul>
> #
> # <p>Within a paragraph <code>code block</code>, followed by one which needs <code>extra escapeing`</code> © t0m.
> # & note <strong>ampersands</strong> and > or < <em>are</em> escaped <strong>properly</strong> in output</p>
> #
> # <p>This paragraph has <a href="http://www.test.com/" title="Test dot Com website">a link</a> and <a href="http://www.test2.com/">another link</a>.. This is <a href="http://example.com/" title="Title">an example</a> inline link.</p>
> #
> # <p>Or, we could use <a href="http://wuto-links.com/">http://wuto-links.com/</a>. Or shortcut links like this: <a href="http://google.com/">Google</a></p>
> #
> # <blockquote>
> # <p>block quoted text</p>
> #
> # <p>in multiple paragraphs
> # and across multiple lines</p>
> #
> # <blockquote>
> # <p>and at
> # multiple levels.</p>
> # </blockquote>
> # </blockquote>
> #
> # <pre><code>This is a code block here...
> # </code></pre>
> #
> # <hr />
> #
> # <hr />
> #
> # <hr />
> #
> # <p>un*fucking*believable - *this text is surrounded by literal asterisks*, but the text before that should be bold according to the docs, but isn't FIXME!</p>
> #
> # <p><img src="/path/to/img.jpg" alt="Alt text" id="alttext" /></p>
> #
> # <p><img src="/path/to/img2.jpg" alt="Alt text2" title="Optional title" id="alttext2" /></p>
> #
> # <p><img src="url/to/image" alt="Alt text for ref mode" title="Optional title attribute" id="alttextforrefmode" /></p>
> #
> # <hr />
> # '
> # Looks like you failed 1 test of 2.
> t/07fulldoc.t .............................
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/2 subtests
>
> # Failed test 'exported markdown function works'
> # at t/08exporter.t line 17.
> # got: 'A trivial block of text'
> # expected: '<p>A trivial block of text</p>'
> # Looks like you failed 1 test of 5.
> t/08exporter.t ............................
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/5 subtests
>
> # Failed test 'Markdown with wiki links, no base url'
> # at t/09base_url.t line 12.
> # got: 'A trivial block of text with a <a href="WikiWord">WikiWord</a>
> # '
> # expected: '<p>A trivial block of text with a <a href="WikiWord">WikiWord</a></p>
> # '
>
> # Failed test 'Markdown with wiki links, with base url in instance'
> # at t/09base_url.t line 22.
> # got: 'A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a>
> # '
> # expected: '<p>A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a></p>
> # '
>
> # Failed test 'Markdown with wiki links, with base url in metadata'
> # at t/09base_url.t line 33.
> # got: 'base url: http://www.test.com/<br />
> #
> # A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a>
> # '
> # expected: 'base url: http://www.test.com/<br />
> #
> # <p>A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a></p>
> # '
> # Looks like you failed 3 tests of 4.
> t/09base_url.t ............................
> Dubious, test returned 3 (wstat 768, 0x300)
> Failed 3/4 subtests
>
> # Failed test 'Markdown with wiki links, and base url, metadata switched on in instance'
> # at t/10use_metadata.t line 15.
> # got: 'base url: http://www.test.com/<br />
> # use wikilinks: on<br />
> #
> # A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a>
> # '
> # expected: 'base url: http://www.test.com/<br />
> # use wikilinks: on<br />
> #
> # <p>A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a></p>
> # '
>
> # Failed test 'Markdown with wiki links, with base url in instance (no metadata)'
> # at t/10use_metadata.t line 24.
> # got: 'use wikilinks: on
> # base url: http://www.test.com/
> #
> # A trivial block of text with a WikiWord
> # '
> # expected: '<p>use wikilinks: on
> # base url: http://www.test.com/</p>
> #
> # <p>A trivial block of text with a WikiWord</p>
> # '
>
> # Failed test 'Markdown with wiki links, and base url, metadata switched on in options'
> # at t/10use_metadata.t line 28.
> # got: 'base url: http://www.test.com/<br />
> # use wikilinks: on<br />
> #
> # A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a>
> # '
> # expected: 'base url: http://www.test.com/<br />
> # use wikilinks: on<br />
> #
> # <p>A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a></p>
> # '
>
> # Failed test 'Markdown with wiki links, with base url in instance (no metadata) - try 2 to ensure option to markdown does not frob setting'
> # at t/10use_metadata.t line 32.
> # got: 'use wikilinks: on
> # base url: http://www.test.com/
> #
> # A trivial block of text with a WikiWord
> # '
> # expected: '<p>use wikilinks: on
> # base url: http://www.test.com/</p>
> #
> # <p>A trivial block of text with a WikiWord</p>
> # '
>
> # Failed test 'Markdown with wiki links, with metadata off and stripped'
> # at t/10use_metadata.t line 42.
> # got: 'A trivial block of text with a WikiWord
> # '
> # expected: '<p>A trivial block of text with a WikiWord</p>
> # '
>
> # Failed test 'Markdown with wiki links, with metadata on but stripped'
> # at t/10use_metadata.t line 48.
> # got: 'A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a>
> # '
> # expected: '<p>A trivial block of text with a <a href="http://www.test.com/WikiWord">WikiWord</a></p>
> # '
> # Looks like you failed 6 tests of 7.
> t/10use_metadata.t ........................
> Dubious, test returned 6 (wstat 1536, 0x600)
> Failed 6/7 subtests
>
> # Failed test 'Markdown'
> # at t/11docment_format.t line 12.
> # got: 'A trivial block of text
> # '
> # expected: '<p>A trivial block of text</p>
> # '
>
> # Failed test 'Markdown with complete xhtml doc'
> # at t/11docment_format.t line 21.
> # got: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> # <html>
> # <head>
> # </head>
> # <body>
> # A trivial block of text
> # </body>
> # </html>'
> # expected: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> # <html>
> # <head>
> # </head>
> # <body>
> # <p>A trivial block of text</p>
> # </body>
> # </html>'
>
> # Failed test 'Markdown with complete xhtml doc (and metadata)'
> # at t/11docment_format.t line 37.
> # got: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> # <html>
> # <head>
> # <link type="text/css" rel="stylesheet" href="somestyle.css" />
> # <meta name="other" content="some metadata" />
> # <title>A page title</title>
> # </head>
> # <body>
> # A trivial block of text
> # </body>
> # </html>'
> # expected: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> # <html>
> # <head>
> # <link type="text/css" rel="stylesheet" href="somestyle.css" />
> # <meta name="other" content="some metadata" />
> # <title>A page title</title>
> # </head>
> # <body>
> # <p>A trivial block of text</p>
> # </body>
> # </html>'
>
> # Failed test 'Markdown withmetadata, but no complete doc'
> # at t/11docment_format.t line 45.
> # got: 'css: somestyle.css<br />
> # other: some metadata<br />
> # title: A page title<br />
> #
> # A trivial block of text
> # '
> # expected: 'css: somestyle.css<br />
> # other: some metadata<br />
> # title: A page title<br />
> #
> # <p>A trivial block of text</p>
> # '
> # Looks like you failed 4 tests of 5.
> t/11docment_format.t ......................
> Dubious, test returned 4 (wstat 1024, 0x400)
> Failed 4/5 subtests
>
> # Failed test 'Normal element suffix as expected'
> # at t/12empty_element_suffix.t line 11.
> # got: 'some metadata: here<br />
> #
> # Some text
> # '
> # expected: 'some metadata: here<br />
> #
> # <p>Some text</p>
> # '
>
> # Failed test 'HTML element suffix also as expected'
> # at t/12empty_element_suffix.t line 17.
> # got: 'some metadata: here<br>
> #
> # Some text
> # '
> # expected: 'some metadata: here<br>
> #
> # <p>Some text</p>
> # '
> # Looks like you failed 2 tests of 3.
> t/12empty_element_suffix.t ................
> Dubious, test returned 2 (wstat 512, 0x200)
> Failed 2/3 subtests
>
> # Failed test at t/13multimarkdown-nometadata-firstpara.t line 17.
> # got: 'Simple block on one line:
> #
> # <div>foo</div>
> # '
> # expected: '<p>Simple block on one line:</p>
> #
> # <div>foo</div>
> # '
> # Looks like you failed 1 test of 2.
> t/13multimarkdown-nometadata-firstpara.t ..
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/2 subtests
>
> # Failed test at t/14unicode.t line 21.
> Wide character in print at /usr/share/perl/5.10/Test/Builder.pm line 1472.
> # got: '<blockquote>
> # <p>Fo—o</p>
> # </blockquote>
> #
> # μορεοϋερ
> #
> # <blockquote>
> # <p>ßåř</p>
> # </blockquote>
> # '
> # expected: '<blockquote>
> # <p>Fo—o</p>
> # </blockquote>
> #
> # <p>μορεοϋερ</p>
> #
> # <blockquote>
> # <p>ßåř</p>
> # </blockquote>
> # '
> # Looks like you failed 1 test of 3.
> t/14unicode.t .............................
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/3 subtests
> t/15inlinehtmldoenoturnoffmarkdown.t ...... ok
> t/16headingsinlists.t ..................... ok
> t/17olulreportedonlist.t .................. ok
>
> # Failed test at t/18codespanextra.t line 18.
> # got: '<code>cpan Module::Install</code>
> # <code>cpan Task::Catalyst</code>
> # '
> # expected: '<p><code>cpan Module::Install</code>
> # <code>cpan Task::Catalyst</code></p>
> # '
>
> # Failed test at t/18codespanextra.t line 29.
> # got: '<code>cpan Module::Install</code>
> #
> # <code>cpan Task::Catalyst</code>
> # '
> # expected: '<p><code>cpan Module::Install</code></p>
> #
> # <p><code>cpan Task::Catalyst</code></p>
> # '
>
> # Failed test at t/18codespanextra.t line 40.
> # got: '<code>cpanp -i Module::Install</code>
> # <code>cpanp -i Task::Catalyst</code>
> # '
> # expected: '<p><code>cpanp -i Module::Install</code>
> # <code>cpanp -i Task::Catalyst</code></p>
> # '
> # Looks like you failed 3 tests of 4.
> t/18codespanextra.t .......................
> Dubious, test returned 3 (wstat 768, 0x300)
> Failed 3/4 subtests
>
> # Failed test 'Docs test: Wiki_Features'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Tabs'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Tables'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Strong_and_em_together'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Special_Characters'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: PHP-ASP_tags'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Ordered_and_unordered_lists'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Metadata_(Snippet)'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Metadata_(Complete)'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Markdown_Documentation_-_Syntax'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Markdown_Documentation_-_Basics'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Literal_quotes_in_titles'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Lists'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Links_reference_style'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Links_multiline_bugs_2'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Links_multiline_bugs_1'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Links_inline_style'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Links_brackets'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Link_Attributes'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Inline_HTML_comments'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Inline_HTML_(Simple)'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Inline_HTML_(Advanced)'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Images'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: HTML-Comment-encoding'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Horizontal_rules'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Hard-wrapped_paragraphs_with_list-like_lines'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Footnotes'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Emphasis'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Cross-References'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: complex_escaping'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Citations'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Backslash_escapes'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Auto_links'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Amps_and_angles_encoding-advanced'
> # at t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Amps_and_angle_encoding'
> # at t/20fulldocs-text-multimarkdown.t line 28.
> # Looks like you failed 35 tests of 41.
> t/20fulldocs-text-multimarkdown.t .........
> Dubious, test returned 35 (wstat 8960, 0x2300)
> Failed 35/41 subtests
> t/22fulldocs-multimarkdown-todo.t ......... ok
>
> # Failed test 'Docs test: Ordered_and_unordered_lists'
> # at /build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27/t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Literal_quotes_in_titles'
> # at /build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27/t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Links_reference_style'
> # at /build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27/t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Links_inline_style'
> # at /build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27/t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Inline_HTML_comments'
> # at /build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27/t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Inline_HTML_(Simple)'
> # at /build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27/t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Inline_HTML_(Advanced)'
> # at /build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27/t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Footnotes'
> # at /build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27/t/20fulldocs-text-multimarkdown.t line 28.
>
> # Failed test 'Docs test: Backslash_escapes'
> # at /build/user-libtext-multimarkdown-perl_1.0.27-2-amd64-vg_Jbf/libtext-multimarkdown-perl-1.0.27/t/20fulldocs-text-multimarkdown.t line 28.
> # Looks like you failed 9 tests of 11.
> t/23afulldocs-multimarkdown.t .............
> Dubious, test returned 9 (wstat 2304, 0x900)
> Failed 9/11 subtests
> t/24fulldocs-pythonmarkdown2-tm.t ......... ok
> t/29fulldocs-maruku-unittest.t ............ ok
>
> # Failed test 'disable_footnotes works as expected'
> # at t/30disable_multimarkdown_features.t line 21.
> # got: 'Here is some text containing a footnote.[^somesamplefootnote]
> #
> # [^somesamplefootnote]: Here is the text of the footnote itself
> # '
> # expected: '<p>Here is some text containing a footnote.[^somesamplefootnote]</p>
> #
> # <p>[^somesamplefootnote]: Here is the text of the footnote itself</p>
> # '
>
> # Failed test 'disable_bibliography works as expected'
> # at t/30disable_multimarkdown_features.t line 32.
> # got: 'This is a borrowed idea[p. 23][#Doe:1996].
> # '
> # expected: '<p>This is a borrowed idea[p. 23][#Doe:1996].</p>
> # '
>
> # Failed test 'disable_tables works as expected'
> # at t/30disable_multimarkdown_features.t line 40.
> # got: '------------ | :-----------: | -----------: |
> # Content | Long Cell ||
> # Content | Cell | Cell |
> # '
> # expected: '<p>------------ | :-----------: | -----------: |
> # Content | Long Cell ||
> # Content | Cell | Cell |</p>
> # '
> # Looks like you failed 3 tests of 4.
> t/30disable_multimarkdown_features.t ......
> Dubious, test returned 3 (wstat 768, 0x300)
> Failed 3/4 subtests
>
> # Failed test 'MultiMarkdown.pl does the right thing with the syntax guide'
> # at t/35commandlinemultimarkdown.t line 15.
> # got: '<h1 id="markdown:syntax"> Markdown: Syntax</h1>
> #
> # <ul id="ProjectSubmenu">
> # <li><a href="/projects/markdown/" title="Markdown Project Page">Main</a></li>
> # <li><a href="/projects/markdown/basics" title="Markdown Basics">Basics</a></li>
> # <li><a class="selected" title="Markdown Syntax Documentation">Syntax</a></li>
> # <li><a href="/projects/markdown/license" title="Pricing and License Information">License</a></li>
> # <li><a href="/projects/markdown/dingus" title="Online Markdown Web Form">Dingus</a></li>
> # </ul>
> #
> # <ul>
> # <li><a href="#overview">Overview</a>
> # <ul>
> # <li><a href="#philosophy">Philosophy</a></li>
> # <li><a href="#html">Inline HTML</a></li>
> # <li><a href="#autoescape">Automatic Escaping for Special Characters</a></li>
> # </ul></li>
> # <li><a href="#block">Block Elements</a>
> # <ul>
> # <li><a href="#p">Paragraphs and Line Breaks</a></li>
> # <li><a href="#header">Headers</a></li>
> # <li><a href="#blockquote">Blockquotes</a></li>
> # <li><a href="#list">Lists</a></li>
> # <li><a href="#precode">Code Blocks</a></li>
> # <li><a href="#hr">Horizontal Rules</a></li>
> # </ul></li>
> # <li><a href="#span">Span Elements</a>
> # <ul>
> # <li><a href="#link">Links</a></li>
> # <li><a href="#em">Emphasis</a></li>
> # <li><a href="#code">Code</a></li>
> # <li><a href="#img">Images</a></li>
> # </ul></li>
> # <li><a href="#misc">Miscellaneous</a>
> # <ul>
> # <li><a href="#backslash">Backslash Escapes</a></li>
> # <li><a href="#autolink">Automatic Links</a></li>
> # </ul></li>
> # </ul>
> #
> # <strong>Note:</strong> This document is itself written using Markdown; you
> # can <a href="/projects/markdown/syntax.text">see the source for it by adding '.text' to the URL</a>.
> #
> # <hr />
> #
> # <h2 id="overview">Overview</h2>
> #
> # <h3 id="philosophy">Philosophy</h3>
> #
> # Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
> #
> # Readability, however, is emphasized above all else. A Markdown-formatted
> # document should be publishable as-is, as plain text, without looking
> # like it's been marked up with tags or formatting instructions. While
> # Markdown's syntax has been influenced by several existing text-to-HTML
> # filters -- including <a href="http://docutils.sourceforge.net/mirror/setext.html">Setext</a>, <a href="http://www.aaronsw.com/2002/atx/">atx</a>, <a href="http://textism.com/tools/textile/">Textile</a>, <a href="http://docutils.sourceforge.net/rst.html">reStructuredText</a>,
> # <a href="http://www.triptico.com/software/grutatxt.html">Grutatext</a>, and <a href="http://ettext.taint.org/doc/">EtText</a> -- the single biggest source of
> # inspiration for Markdown's syntax is the format of plain text email.
> #
> # To this end, Markdown's syntax is comprised entirely of punctuation
> # characters, which punctuation characters have been carefully chosen so
> # as to look like what they mean. E.g., asterisks around a word actually
> # look like *emphasis*. Markdown lists look like, well, lists. Even
> # blockquotes look like quoted passages of text, assuming you've ever
> # used email.
> #
> # <h3 id="html">Inline HTML</h3>
> #
> # Markdown's syntax is intended for one purpose: to be used as a
> # format for <em>writing</em> for the web.
> #
> # Markdown is not a replacement for HTML, or even close to it. Its
> # syntax is very small, corresponding only to a very small subset of
> # HTML tags. The idea is <em>not</em> to create a syntax that makes it easier
> # to insert HTML tags. In my opinion, HTML tags are already easy to
> # insert. The idea for Markdown is to make it easy to read, write, and
> # edit prose. HTML is a <em>publishing</em> format; Markdown is a <em>writing</em>
> # format. Thus, Markdown's formatting syntax only addresses issues that
> # can be conveyed in plain text.
> #
> # For any markup that is not covered by Markdown's syntax, you simply
> # use HTML itself. There's no need to preface it or delimit it to
> # indicate that you're switching from Markdown to HTML; you just use
> # the tags.
> #
> # The only restrictions are that block-level HTML elements -- e.g. <code><div></code>,
> # <code><table></code>, <code><pre></code>, <code><p></code>, etc. -- must be separated from surrounding
> # content by blank lines, and the start and end tags of the block should
> # not be indented with tabs or spaces. Markdown is smart enough not
> # to add extra (unwanted) <code><p></code> tags around HTML block-level tags.
> #
> # For example, to add an HTML table to a Markdown article:
> #
> # <pre><code>This is a regular paragraph.
> #
> # <table>
> # <tr>
> # <td>Foo</td>
> # </tr>
> # </table>
> #
> # This is another regular paragraph.
> # </code></pre>
> #
> # Note that Markdown formatting syntax is not processed within block-level
> # HTML tags. E.g., you can't use Markdown-style <code>*emphasis*</code> inside an
> # HTML block.
> #
> # Span-level HTML tags -- e.g. <code><span></code>, <code><cite></code>, or <code><del></code> -- can be
> # used anywhere in a Markdown paragraph, list item, or header. If you
> # want, you can even use HTML tags instead of Markdown formatting; e.g. if
> # you'd prefer to use HTML <code><a></code> or <code><img></code> tags instead of Markdown's
> # link or image syntax, go right ahead.
> #
> # Unlike block-level HTML tags, Markdown syntax <em>is</em> processed within
> # span-level tags.
> #
> # <h3 id="autoescape">Automatic Escaping for Special Characters</h3>
> #
> # In HTML, there are two characters that demand special treatment: <code><</code>
> # and <code>&</code>. Left angle brackets are used to start tags; ampersands are
> # used to denote HTML entities. If you want to use them as literal
> # characters, you must escape them as entities, e.g. <code>&lt;</code>, and
> # <code>&amp;</code>.
> #
> # Ampersands in particular are bedeviling for web writers. If you want to
> # write about 'AT&T', you need to write '<code>AT&amp;T</code>'. You even need to
> # escape ampersands within URLs. Thus, if you want to link to:
> #
> # <pre><code>http://images.google.com/images?num=30&q=larry+bird
> # </code></pre>
> #
> # you need to encode the URL as:
> #
> # <pre><code>http://images.google.com/images?num=30&amp;q=larry+bird
> # </code></pre>
> #
> # in your anchor tag <code>href</code> attribute. Needless to say, this is easy to
> # forget, and is probably the single most common source of HTML validation
> # errors in otherwise well-marked-up web sites.
> #
> # Markdown allows you to use these characters naturally, taking care of
> # all the necessary escaping for you. If you use an ampersand as part of
> # an HTML entity, it remains unchanged; otherwise it will be translated
> # into <code>&amp;</code>.
> #
> # So, if you want to include a copyright symbol in your article, you can write:
> #
> # <pre><code>&copy;
> # </code></pre>
> #
> # and Markdown will leave it alone. But if you write:
> #
> # <pre><code>AT&T
> # </code></pre>
> #
> # Markdown will translate it to:
> #
> # <pre><code>AT&amp;T
> # </code></pre>
> #
> # Similarly, because Markdown supports <a href="#html">inline HTML</a>, if you use
> # angle brackets as delimiters for HTML tags, Markdown will treat them as
> # such. But if you write:
> #
> # <pre><code>4 < 5
> # </code></pre>
> #
> # Markdown will translate it to:
> #
> # <pre><code>4 &lt; 5
> # </code></pre>
> #
> # However, inside Markdown code spans and blocks, angle brackets and
> # ampersands are <em>always</em> encoded automatically. This makes it easy to use
> # Markdown to write about HTML code. (As opposed to raw HTML, which is a
> # terrible format for writing about HTML syntax, because every single <code><</code>
> # and <code>&</code> in your example code needs to be escaped.)
> #
> # <hr />
> #
> # <h2 id="block">Block Elements</h2>
> #
> # <h3 id="p">Paragraphs and Line Breaks</h3>
> #
> # 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 but spaces or tabs is considered
> # blank.) Normal paragraphs should not be intended with spaces or tabs.
> #
> # The implication of the "one or more consecutive lines of text" rule is
> # that Markdown supports "hard-wrapped" text paragraphs. This differs
> # significantly from most other text-to-HTML formatters (including Movable
> # Type's "Convert Line Breaks" option) which translate every line break
> # character in a paragraph into a <code><br /></code> tag.
> #
> # When you <em>do</em> want to insert a <code><br /></code> break tag using Markdown, you
> # end a line with two or more spaces, then type return.
> #
> # Yes, this takes a tad more effort to create a <code><br /></code>, but a simplistic
> # "every line break is a <code><br /></code>" rule wouldn't work for Markdown.
> # Markdown's email-style <a href="#blockquote">blockquoting</a> and multi-paragraph <a href="#list">list items</a>
> # work best -- and look better -- when you format them with hard breaks.
> #
> # <h3 id="header">Headers</h3>
> #
> # Markdown supports two styles of headers, <a href="http://docutils.sourceforge.net/mirror/setext.html">Setext</a> and <a href="http://www.aaronsw.com/2002/atx/">atx</a>.
> #
> # Setext-style headers are "underlined" using equal signs (for first-level
> # headers) and dashes (for second-level headers). For example:
> #
> # <pre><code>This is an H1
> # =============
> #
> # This is an H2
> # -------------
> # </code></pre>
> #
> # Any number of underlining <code>=</code>'s or <code>-</code>'s will work.
> #
> # Atx-style headers use 1-6 hash characters at the start of the line,
> # corresponding to header levels 1-6. For example:
> #
> # <pre><code># This is an H1
> #
> # ## This is an H2
> #
> # ###### This is an H6
> # </code></pre>
> #
> # Optionally, you may "close" atx-style headers. This is purely
> # cosmetic -- you can use this if you think it looks better. The
> # closing hashes don't even need to match the number of hashes
> # used to open the header. (The number of opening hashes
> # determines the header level.) :
> #
> # <pre><code># This is an H1 #
> #
> # ## This is an H2 ##
> #
> # ### This is an H3 ######
> # </code></pre>
> #
> # <h3 id="blockquote">Blockquotes</h3>
> #
> # Markdown uses email-style <code>></code> characters for blockquoting. If you're
> # familiar with quoting passages of text in an email message, then you
> # know how to create a blockquote in Markdown. It looks best if you hard
> # wrap the text and put a <code>></code> before every line:
> #
> # <pre><code>> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
> # > consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
> # > Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
> # >
> # > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
> # > id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # Markdown allows you to be lazy and only put the <code>></code> before the first
> # line of a hard-wrapped paragraph:
> #
> # <pre><code>> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
> # consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
> # Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
> #
> # > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
> # id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
> # adding additional levels of <code>></code>:
> #
> # <pre><code>> This is the first level of quoting.
> # >
> # > > This is nested blockquote.
> # >
> # > Back to the first level.
> # </code></pre>
> #
> # Blockquotes can contain other Markdown elements, including headers, lists,
> # and code blocks:
> #
> # <pre><code>> ## This is a header.
> # >
> # > 1. This is the first list item.
> # > 2. This is the second list item.
> # >
> # > Here's some example code:
> # >
> # > return shell_exec("echo $input | $markdown_script");
> # </code></pre>
> #
> # Any decent text editor should make email-style quoting easy. For
> # example, with BBEdit, you can make a selection and choose Increase
> # Quote Level from the Text menu.
> #
> # <h3 id="list">Lists</h3>
> #
> # Markdown supports ordered (numbered) and unordered (bulleted) lists.
> #
> # Unordered lists use asterisks, pluses, and hyphens -- interchangably
> # -- as list markers:
> #
> # <pre><code>* Red
> # * Green
> # * Blue
> # </code></pre>
> #
> # is equivalent to:
> #
> # <pre><code>+ Red
> # + Green
> # + Blue
> # </code></pre>
> #
> # and:
> #
> # <pre><code>- Red
> # - Green
> # - Blue
> # </code></pre>
> #
> # Ordered lists use numbers followed by periods:
> #
> # <pre><code>1. Bird
> # 2. McHale
> # 3. Parish
> # </code></pre>
> #
> # It's important to note that the actual numbers you use to mark the
> # list have no effect on the HTML output Markdown produces. The HTML
> # Markdown produces from the above list is:
> #
> # <pre><code><ol>
> # <li>Bird</li>
> # <li>McHale</li>
> # <li>Parish</li>
> # </ol>
> # </code></pre>
> #
> # If you instead wrote the list in Markdown like this:
> #
> # <pre><code>1. Bird
> # 1. McHale
> # 1. Parish
> # </code></pre>
> #
> # or even:
> #
> # <pre><code>3. Bird
> # 1. McHale
> # 8. Parish
> # </code></pre>
> #
> # you'd get the exact same HTML output. The point is, if you want to,
> # you can use ordinal numbers in your ordered Markdown lists, so that
> # the numbers in your source match the numbers in your published HTML.
> # But if you want to be lazy, you don't have to.
> #
> # If you do use lazy list numbering, however, you should still start the
> # list with the number 1. At some point in the future, Markdown may support
> # starting ordered lists at an arbitrary number.
> #
> # List markers typically start at the left margin, but may be indented by
> # up to three spaces. List markers must be followed by one or more spaces
> # or a tab.
> #
> # To make lists look nice, you can wrap items with hanging indents:
> #
> # <pre><code>* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
> # Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
> # viverra nec, fringilla in, laoreet vitae, risus.
> # * Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
> # Suspendisse id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # But if you want to be lazy, you don't have to:
> #
> # <pre><code>* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
> # Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
> # viverra nec, fringilla in, laoreet vitae, risus.
> # * Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
> # Suspendisse id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # If list items are separated by blank lines, Markdown will wrap the
> # items in <code><p></code> tags in the HTML output. For example, this input:
> #
> # <pre><code>* Bird
> # * Magic
> # </code></pre>
> #
> # will turn into:
> #
> # <pre><code><ul>
> # <li>Bird</li>
> # <li>Magic</li>
> # </ul>
> # </code></pre>
> #
> # But this:
> #
> # <pre><code>* Bird
> #
> # * Magic
> # </code></pre>
> #
> # will turn into:
> #
> # <pre><code><ul>
> # <li><p>Bird</p></li>
> # <li><p>Magic</p></li>
> # </ul>
> # </code></pre>
> #
> # List items may consist of multiple paragraphs. Each subsequent
> # paragraph in a list item must be intended by either 4 spaces
> # or one tab:
> #
> # <pre><code>1. This is a list item with two paragraphs. Lorem ipsum dolor
> # sit amet, consectetuer adipiscing elit. Aliquam hendrerit
> # mi posuere lectus.
> #
> # Vestibulum enim wisi, viverra nec, fringilla in, laoreet
> # vitae, risus. Donec sit amet nisl. Aliquam semper ipsum
> # sit amet velit.
> #
> # 2. Suspendisse id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # It looks nice if you indent every line of the subsequent
> # paragraphs, but here again, Markdown will allow you to be
> # lazy:
> #
> # <pre><code>* This is a list item with two paragraphs.
> #
> # This is the second paragraph in the list item. You're
> # only required to indent the first line. Lorem ipsum dolor
> # sit amet, consectetuer adipiscing elit.
> #
> # * Another item in the same list.
> # </code></pre>
> #
> # To put a blockquote within a list item, the blockquote's <code>></code>
> # delimiters need to be indented:
> #
> # <pre><code>* A list item with a blockquote:
> #
> # > This is a blockquote
> # > inside a list item.
> # </code></pre>
> #
> # To put a code block within a list item, the code block needs
> # to be indented <em>twice</em> -- 8 spaces or two tabs:
> #
> # <pre><code>* A list item with a code block:
> #
> # <code goes here>
> # </code></pre>
> #
> # It's worth noting that it's possible to trigger an ordered list by
> # accident, by writing something like this:
> #
> # <pre><code>1986. What a great season.
> # </code></pre>
> #
> # In other words, a <em>number-period-space</em> sequence at the beginning of a
> # line. To avoid this, you can backslash-escape the period:
> #
> # <pre><code>1986\. What a great season.
> # </code></pre>
> #
> # <h3 id="precode">Code Blocks</h3>
> #
> # Pre-formatted code blocks are used for writing about programming or
> # markup source code. Rather than forming normal paragraphs, the lines
> # of a code block are interpreted literally. Markdown wraps a code block
> # in both <code><pre></code> and <code><code></code> tags.
> #
> # To produce a code block in Markdown, simply indent every line of the
> # block by at least 4 spaces or 1 tab. For example, given this input:
> #
> # <pre><code>This is a normal paragraph:
> #
> # This is a code block.
> # </code></pre>
> #
> # Markdown will generate:
> #
> # <pre><code><p>This is a normal paragraph:</p>
> #
> # <pre><code>This is a code block.
> # </code></pre>
> # </code></pre>
> #
> # One level of indentation -- 4 spaces or 1 tab -- is removed from each
> # line of the code block. For example, this:
> #
> # <pre><code>Here is an example of AppleScript:
> #
> # tell application "Foo"
> # beep
> # end tell
> # </code></pre>
> #
> # will turn into:
> #
> # <pre><code><p>Here is an example of AppleScript:</p>
> #
> # <pre><code>tell application "Foo"
> # beep
> # end tell
> # </code></pre>
> # </code></pre>
> #
> # A code block continues until it reaches a line that is not indented
> # (or the end of the article).
> #
> # Within a code block, ampersands (<code>&</code>) and angle brackets (<code><</code> and <code>></code>)
> # are automatically converted into HTML entities. This makes it very
> # easy to include example HTML source code using Markdown -- just paste
> # it and indent it, and Markdown will handle the hassle of encoding the
> # ampersands and angle brackets. For example, this:
> #
> # <pre><code> <div class="footer">
> # &copy; 2004 Foo Corporation
> # </div>
> # </code></pre>
> #
> # will turn into:
> #
> # <pre><code><pre><code>&lt;div class="footer"&gt;
> # &amp;copy; 2004 Foo Corporation
> # &lt;/div&gt;
> # </code></pre>
> # </code></pre>
> #
> # Regular Markdown syntax is not processed within code blocks. E.g.,
> # asterisks are just literal asterisks within a code block. This means
> # it's also easy to use Markdown to write about Markdown's own syntax.
> #
> # <h3 id="hr">Horizontal Rules</h3>
> #
> # You can produce a horizontal rule tag (<code><hr /></code>) by placing three or
> # more hyphens, asterisks, or underscores on a line by themselves. If you
> # wish, you may use spaces between the hyphens or asterisks. Each of the
> # following lines will produce a horizontal rule:
> #
> # <pre><code>* * *
> #
> # ***
> #
> # *****
> #
> # - - -
> #
> # ---------------------------------------
> #
> # _ _ _
> # </code></pre>
> #
> # <hr />
> #
> # <h2 id="span">Span Elements</h2>
> #
> # <h3 id="link">Links</h3>
> #
> # Markdown supports two style of links: <em>inline</em> and <em>reference</em>.
> #
> # In both styles, the link text is delimited by [square brackets].
> #
> # To create an inline link, use a set of regular parentheses immediately
> # after the link text's closing square bracket. Inside the parentheses,
> # put the URL where you want the link to point, along with an <em>optional</em>
> # title for the link, surrounded in quotes. For example:
> #
> # <pre><code>This is [an example](http://example.com/ "Title") inline link.
> #
> # [This link](http://example.net/) has no title attribute.
> # </code></pre>
> #
> # Will produce:
> #
> # <pre><code><p>This is <a href="http://example.com/" title="Title">
> # an example</a> inline link.</p>
> #
> # <p><a href="http://example.net/">This link</a> has no
> # title attribute.</p>
> # </code></pre>
> #
> # If you're referring to a local resource on the same server, you can
> # use relative paths:
> #
> # <pre><code>See my [About](/about/) page for details.
> # </code></pre>
> #
> # Reference-style links use a second set of square brackets, inside
> # which you place a label of your choosing to identify the link:
> #
> # <pre><code>This is [an example][id] reference-style link.
> # </code></pre>
> #
> # You can optionally use a space to separate the sets of brackets:
> #
> # <pre><code>This is [an example] [id] reference-style link.
> # </code></pre>
> #
> # Then, anywhere in the document, you define your link label like this,
> # on a line by itself:
> #
> # <pre><code>[id]: http://example.com/ "Optional Title Here"
> # </code></pre>
> #
> # That is:
> #
> # <ul>
> # <li>Square brackets containing the link identifier (optionally
> # indented from the left margin using up to three spaces);</li>
> # <li>followed by a colon;</li>
> # <li>followed by one or more spaces (or tabs);</li>
> # <li>followed by the URL for the link;</li>
> # <li>optionally followed by a title attribute for the link, enclosed
> # in double or single quotes.</li>
> # </ul>
> #
> # The link URL may, optionally, be surrounded by angle brackets:
> #
> # <pre><code>[id]: <http://example.com/> "Optional Title Here"
> # </code></pre>
> #
> # You can put the title attribute on the next line and use extra spaces
> # or tabs for padding, which tends to look better with longer URLs:
> #
> # <pre><code>[id]: http://example.com/longish/path/to/resource/here
> # "Optional Title Here"
> # </code></pre>
> #
> # Link definitions are only used for creating links during Markdown
> # processing, and are stripped from your document in the HTML output.
> #
> # Link definition names may constist of letters, numbers, spaces, and punctuation -- but they are <em>not</em> case sensitive. E.g. these two links:
> #
> # <pre><code>[link text][a]
> # [link text][A]
> # </code></pre>
> #
> # are equivalent.
> #
> # The <em>implicit link name</em> shortcut allows you to omit the name of the
> # link, in which case the link text itself is used as the name.
> # Just use an empty set of square brackets -- e.g., to link the word
> # "Google" to the google.com web site, you could simply write:
> #
> # <pre><code>[Google][]
> # </code></pre>
> #
> # And then define the link:
> #
> # <pre><code>[Google]: http://google.com/
> # </code></pre>
> #
> # Because link names may contain spaces, this shortcut even works for
> # multiple words in the link text:
> #
> # <pre><code>Visit [Daring Fireball][] for more information.
> # </code></pre>
> #
> # And then define the link:
> #
> # <pre><code>[Daring Fireball]: http://daringfireball.net/
> # </code></pre>
> #
> # Link definitions can be placed anywhere in your Markdown document. I
> # tend to put them immediately after each paragraph in which they're
> # used, but if you want, you can put them all at the end of your
> # document, sort of like footnotes.
> #
> # Here's an example of reference links in action:
> #
> # <pre><code>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"
> # </code></pre>
> #
> # Using the implicit link name shortcut, you could instead write:
> #
> # <pre><code>I get 10 times more traffic from [Google][] than from
> # [Yahoo][] or [MSN][].
> #
> # [google]: http://google.com/ "Google"
> # [yahoo]: http://search.yahoo.com/ "Yahoo Search"
> # [msn]: http://search.msn.com/ "MSN Search"
> # </code></pre>
> #
> # Both of the above examples will produce the following HTML output:
> #
> # <pre><code><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>
> # </code></pre>
> #
> # For comparison, here is the same paragraph written using
> # Markdown's inline link style:
> #
> # <pre><code>I get 10 times more traffic from [Google](http://google.com/ "Google")
> # than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
> # [MSN](http://search.msn.com/ "MSN Search").
> # </code></pre>
> #
> # The point of reference-style links is not that they're easier to
> # write. The point is that with reference-style links, your document
> # source is vastly more readable. Compare the above examples: using
> # reference-style links, the paragraph itself is only 81 characters
> # long; with inline-style links, it's 176 characters; and as raw HTML,
> # it's 234 characters. In the raw HTML, there's more markup than there
> # is text.
> #
> # With Markdown's reference-style links, a source document much more
> # closely resembles the final output, as rendered in a browser. By
> # allowing you to move the markup-related metadata out of the paragraph,
> # you can add links without interrupting the narrative flow of your
> # prose.
> #
> # <h3 id="em">Emphasis</h3>
> #
> # Markdown treats asterisks (<code>*</code>) and underscores (<code>_</code>) as indicators of
> # emphasis. Text wrapped with one <code>*</code> or <code>_</code> will be wrapped with an
> # HTML <code><em></code> tag; double <code>*</code>'s or <code>_</code>'s will be wrapped with an HTML
> # <code><strong></code> tag. E.g., this input:
> #
> # <pre><code>*single asterisks*
> #
> # _single underscores_
> #
> # **double asterisks**
> #
> # __double underscores__
> # </code></pre>
> #
> # will produce:
> #
> # <pre><code><em>single asterisks</em>
> #
> # <em>single underscores</em>
> #
> # <strong>double asterisks</strong>
> #
> # <strong>double underscores</strong>
> # </code></pre>
> #
> # You can use whichever style you prefer; the lone restriction is that
> # the same character must be used to open and close an emphasis span.
> #
> # Emphasis can be used in the middle of a word:
> #
> # <pre><code>un*fucking*believable
> # </code></pre>
> #
> # But if you surround an <code>*</code> or <code>_</code> with spaces, it'll be treated as a
> # literal asterisk or underscore.
> #
> # To produce a literal asterisk or underscore at a position where it
> # would otherwise be used as an emphasis delimiter, you can backslash
> # escape it:
> #
> # <pre><code>\*this text is surrounded by literal asterisks\*
> # </code></pre>
> #
> # <h3 id="code">Code</h3>
> #
> # To indicate a span of code, wrap it with backtick quotes (<code>`</code>).
> # Unlike a pre-formatted code block, a code span indicates code within a
> # normal paragraph. For example:
> #
> # <pre><code>Use the `printf()` function.
> # </code></pre>
> #
> # will produce:
> #
> # <pre><code><p>Use the <code>printf()</code> function.</p>
> # </code></pre>
> #
> # To include a literal backtick character within a code span, you can use
> # multiple backticks as the opening and closing delimiters:
> #
> # <pre><code>``There is a literal backtick (`) here.``
> # </code></pre>
> #
> # which will produce this:
> #
> # <pre><code><p><code>There is a literal backtick (`) here.</code></p>
> # </code></pre>
> #
> # The backtick delimiters surrounding a code span may include spaces --
> # one after the opening, one before the closing. This allows you to place
> # literal backtick characters at the beginning or end of a code span:
> #
> # <pre><code>A single backtick in a code span: `` ` ``
> #
> # A backtick-delimited string in a code span: `` `foo` ``
> # </code></pre>
> #
> # will produce:
> #
> # <pre><code><p>A single backtick in a code span: <code>`</code></p>
> #
> # <p>A backtick-delimited string in a code span: <code>`foo`</code></p>
> # </code></pre>
> #
> # With a code span, ampersands and angle brackets are encoded as HTML
> # entities automatically, which makes it easy to include example HTML
> # tags. Markdown will turn this:
> #
> # <pre><code>Please don't use any `<blink>` tags.
> # </code></pre>
> #
> # into:
> #
> # <pre><code><p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>
> # </code></pre>
> #
> # You can write this:
> #
> # <pre><code>`&#8212;` is the decimal-encoded equivalent of `&mdash;`.
> # </code></pre>
> #
> # to produce:
> #
> # <pre><code><p><code>&amp;#8212;</code> is the decimal-encoded
> # equivalent of <code>&amp;mdash;</code>.</p>
> # </code></pre>
> #
> # <h3 id="img">Images</h3>
> #
> # Admittedly, it's fairly difficult to devise a "natural" syntax for
> # placing images into a plain text document format.
> #
> # Markdown uses an image syntax that is intended to resemble the syntax
> # for links, allowing for two styles: <em>inline</em> and <em>reference</em>.
> #
> # Inline image syntax looks like this:
> #
> # <pre><code>
> #
> # 
> # </code></pre>
> #
> # That is:
> #
> # <ul>
> # <li>An exclamation mark: <code>!</code>;</li>
> # <li>followed by a set of square brackets, containing the <code>alt</code>
> # attribute text for the image;</li>
> # <li>followed by a set of parentheses, containing the URL or path to
> # the image, and an optional <code>title</code> attribute enclosed in double
> # or single quotes.</li>
> # </ul>
> #
> # Reference-style image syntax looks like this:
> #
> # <pre><code>![Alt text][id]
> # </code></pre>
> #
> # Where "id" is the name of a defined image reference. Image references
> # are defined using syntax identical to link references:
> #
> # <pre><code>[id]: url/to/image "Optional title attribute"
> # </code></pre>
> #
> # As of this writing, Markdown has no syntax for specifying the
> # dimensions of an image; if this is important to you, you can simply
> # use regular HTML <code><img></code> tags.
> #
> # <hr />
> #
> # <h2 id="misc">Miscellaneous</h2>
> #
> # <h3 id="autolink">Automatic Links</h3>
> #
> # Markdown supports a shortcut style for creating "automatic" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:
> #
> # <pre><code><http://example.com/>
> # </code></pre>
> #
> # Markdown will turn this into:
> #
> # <pre><code><a href="http://example.com/">http://example.com/</a>
> # </code></pre>
> #
> # Automatic links for email addresses work similarly, except that
> # Markdown will also perform a bit of randomized decimal and hex
> # entity-encoding to help obscure your address from address-harvesting
> # spambots. For example, Markdown will turn this:
> #
> # <pre><code><address at example.com>
> # </code></pre>
> #
> # into something like this:
> #
> # <pre><code><a href="&#x6D;&#x61;i&#x6C;&#x74;&#x6F;:&#x61;&#x64;&#x64;&#x72;&#x65;
> # &#115;&#115;&#64;&#101;&#120;&#x61;&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;
> # &#109;">&#x61;&#x64;&#x64;&#x72;&#x65;&#115;&#115;&#64;&#101;&#120;&#x61;
> # &#109;&#x70;&#x6C;e&#x2E;&#99;&#111;&#109;</a>
> # </code></pre>
> #
> # which will render in a browser as a clickable link to "address at example.com".
> #
> # (This sort of entity-encoding trick will indeed fool many, if not
> # most, address-harvesting bots, but it definitely won't fool all of
> # them. It's better than nothing, but an address published in this way
> # will probably eventually start receiving spam.)
> #
> # <h3 id="backslash">Backslash Escapes</h3>
> #
> # Markdown allows you to use backslash escapes to generate literal
> # characters which would otherwise have special meaning in Markdown's
> # formatting syntax. For example, if you wanted to surround a word with
> # literal asterisks (instead of an HTML <code><em></code> tag), you can backslashes
> # before the asterisks, like this:
> #
> # <pre><code>\*literal asterisks\*
> # </code></pre>
> #
> # Markdown provides backslash escapes for the following characters:
> #
> # <pre><code>\ backslash
> # ` backtick
> # * asterisk
> # _ underscore
> # {} curly braces
> # [] square brackets
> # () parentheses
> # # hash mark
> # + plus sign
> # - minus sign (hyphen)
> # . dot
> # ! exclamation mark
> # </code></pre>
> # '
> # expected: '<h1 id="markdown:syntax"> Markdown: Syntax</h1>
> #
> # <ul id="ProjectSubmenu">
> # <li><a href="/projects/markdown/" title="Markdown Project Page">Main</a></li>
> # <li><a href="/projects/markdown/basics" title="Markdown Basics">Basics</a></li>
> # <li><a class="selected" title="Markdown Syntax Documentation">Syntax</a></li>
> # <li><a href="/projects/markdown/license" title="Pricing and License Information">License</a></li>
> # <li><a href="/projects/markdown/dingus" title="Online Markdown Web Form">Dingus</a></li>
> # </ul>
> #
> # <ul>
> # <li><a href="#overview">Overview</a>
> # <ul>
> # <li><a href="#philosophy">Philosophy</a></li>
> # <li><a href="#html">Inline HTML</a></li>
> # <li><a href="#autoescape">Automatic Escaping for Special Characters</a></li>
> # </ul></li>
> # <li><a href="#block">Block Elements</a>
> # <ul>
> # <li><a href="#p">Paragraphs and Line Breaks</a></li>
> # <li><a href="#header">Headers</a></li>
> # <li><a href="#blockquote">Blockquotes</a></li>
> # <li><a href="#list">Lists</a></li>
> # <li><a href="#precode">Code Blocks</a></li>
> # <li><a href="#hr">Horizontal Rules</a></li>
> # </ul></li>
> # <li><a href="#span">Span Elements</a>
> # <ul>
> # <li><a href="#link">Links</a></li>
> # <li><a href="#em">Emphasis</a></li>
> # <li><a href="#code">Code</a></li>
> # <li><a href="#img">Images</a></li>
> # </ul></li>
> # <li><a href="#misc">Miscellaneous</a>
> # <ul>
> # <li><a href="#backslash">Backslash Escapes</a></li>
> # <li><a href="#autolink">Automatic Links</a></li>
> # </ul></li>
> # </ul>
> #
> # <p><strong>Note:</strong> This document is itself written using Markdown; you
> # can <a href="/projects/markdown/syntax.text">see the source for it by adding '.text' to the URL</a>.</p>
> #
> # <hr />
> #
> # <h2 id="overview">Overview</h2>
> #
> # <h3 id="philosophy">Philosophy</h3>
> #
> # <p>Markdown is intended to be as easy-to-read and easy-to-write as is feasible.</p>
> #
> # <p>Readability, however, is emphasized above all else. A Markdown-formatted
> # document should be publishable as-is, as plain text, without looking
> # like it's been marked up with tags or formatting instructions. While
> # Markdown's syntax has been influenced by several existing text-to-HTML
> # filters -- including <a href="http://docutils.sourceforge.net/mirror/setext.html">Setext</a>, <a href="http://www.aaronsw.com/2002/atx/">atx</a>, <a href="http://textism.com/tools/textile/">Textile</a>, <a href="http://docutils.sourceforge.net/rst.html">reStructuredText</a>,
> # <a href="http://www.triptico.com/software/grutatxt.html">Grutatext</a>, and <a href="http://ettext.taint.org/doc/">EtText</a> -- the single biggest source of
> # inspiration for Markdown's syntax is the format of plain text email.</p>
> #
> # <p>To this end, Markdown's syntax is comprised entirely of punctuation
> # characters, which punctuation characters have been carefully chosen so
> # as to look like what they mean. E.g., asterisks around a word actually
> # look like *emphasis*. Markdown lists look like, well, lists. Even
> # blockquotes look like quoted passages of text, assuming you've ever
> # used email.</p>
> #
> # <h3 id="html">Inline HTML</h3>
> #
> # <p>Markdown's syntax is intended for one purpose: to be used as a
> # format for <em>writing</em> for the web.</p>
> #
> # <p>Markdown is not a replacement for HTML, or even close to it. Its
> # syntax is very small, corresponding only to a very small subset of
> # HTML tags. The idea is <em>not</em> to create a syntax that makes it easier
> # to insert HTML tags. In my opinion, HTML tags are already easy to
> # insert. The idea for Markdown is to make it easy to read, write, and
> # edit prose. HTML is a <em>publishing</em> format; Markdown is a <em>writing</em>
> # format. Thus, Markdown's formatting syntax only addresses issues that
> # can be conveyed in plain text.</p>
> #
> # <p>For any markup that is not covered by Markdown's syntax, you simply
> # use HTML itself. There's no need to preface it or delimit it to
> # indicate that you're switching from Markdown to HTML; you just use
> # the tags.</p>
> #
> # <p>The only restrictions are that block-level HTML elements -- e.g. <code><div></code>,
> # <code><table></code>, <code><pre></code>, <code><p></code>, etc. -- must be separated from surrounding
> # content by blank lines, and the start and end tags of the block should
> # not be indented with tabs or spaces. Markdown is smart enough not
> # to add extra (unwanted) <code><p></code> tags around HTML block-level tags.</p>
> #
> # <p>For example, to add an HTML table to a Markdown article:</p>
> #
> # <pre><code>This is a regular paragraph.
> #
> # <table>
> # <tr>
> # <td>Foo</td>
> # </tr>
> # </table>
> #
> # This is another regular paragraph.
> # </code></pre>
> #
> # <p>Note that Markdown formatting syntax is not processed within block-level
> # HTML tags. E.g., you can't use Markdown-style <code>*emphasis*</code> inside an
> # HTML block.</p>
> #
> # <p>Span-level HTML tags -- e.g. <code><span></code>, <code><cite></code>, or <code><del></code> -- can be
> # used anywhere in a Markdown paragraph, list item, or header. If you
> # want, you can even use HTML tags instead of Markdown formatting; e.g. if
> # you'd prefer to use HTML <code><a></code> or <code><img></code> tags instead of Markdown's
> # link or image syntax, go right ahead.</p>
> #
> # <p>Unlike block-level HTML tags, Markdown syntax <em>is</em> processed within
> # span-level tags.</p>
> #
> # <h3 id="autoescape">Automatic Escaping for Special Characters</h3>
> #
> # <p>In HTML, there are two characters that demand special treatment: <code><</code>
> # and <code>&</code>. Left angle brackets are used to start tags; ampersands are
> # used to denote HTML entities. If you want to use them as literal
> # characters, you must escape them as entities, e.g. <code>&lt;</code>, and
> # <code>&amp;</code>.</p>
> #
> # <p>Ampersands in particular are bedeviling for web writers. If you want to
> # write about 'AT&T', you need to write '<code>AT&amp;T</code>'. You even need to
> # escape ampersands within URLs. Thus, if you want to link to:</p>
> #
> # <pre><code>http://images.google.com/images?num=30&q=larry+bird
> # </code></pre>
> #
> # <p>you need to encode the URL as:</p>
> #
> # <pre><code>http://images.google.com/images?num=30&amp;q=larry+bird
> # </code></pre>
> #
> # <p>in your anchor tag <code>href</code> attribute. Needless to say, this is easy to
> # forget, and is probably the single most common source of HTML validation
> # errors in otherwise well-marked-up web sites.</p>
> #
> # <p>Markdown allows you to use these characters naturally, taking care of
> # all the necessary escaping for you. If you use an ampersand as part of
> # an HTML entity, it remains unchanged; otherwise it will be translated
> # into <code>&amp;</code>.</p>
> #
> # <p>So, if you want to include a copyright symbol in your article, you can write:</p>
> #
> # <pre><code>&copy;
> # </code></pre>
> #
> # <p>and Markdown will leave it alone. But if you write:</p>
> #
> # <pre><code>AT&T
> # </code></pre>
> #
> # <p>Markdown will translate it to:</p>
> #
> # <pre><code>AT&amp;T
> # </code></pre>
> #
> # <p>Similarly, because Markdown supports <a href="#html">inline HTML</a>, if you use
> # angle brackets as delimiters for HTML tags, Markdown will treat them as
> # such. But if you write:</p>
> #
> # <pre><code>4 < 5
> # </code></pre>
> #
> # <p>Markdown will translate it to:</p>
> #
> # <pre><code>4 &lt; 5
> # </code></pre>
> #
> # <p>However, inside Markdown code spans and blocks, angle brackets and
> # ampersands are <em>always</em> encoded automatically. This makes it easy to use
> # Markdown to write about HTML code. (As opposed to raw HTML, which is a
> # terrible format for writing about HTML syntax, because every single <code><</code>
> # and <code>&</code> in your example code needs to be escaped.)</p>
> #
> # <hr />
> #
> # <h2 id="block">Block Elements</h2>
> #
> # <h3 id="p">Paragraphs and Line Breaks</h3>
> #
> # <p>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 but spaces or tabs is considered
> # blank.) Normal paragraphs should not be intended with spaces or tabs.</p>
> #
> # <p>The implication of the "one or more consecutive lines of text" rule is
> # that Markdown supports "hard-wrapped" text paragraphs. This differs
> # significantly from most other text-to-HTML formatters (including Movable
> # Type's "Convert Line Breaks" option) which translate every line break
> # character in a paragraph into a <code><br /></code> tag.</p>
> #
> # <p>When you <em>do</em> want to insert a <code><br /></code> break tag using Markdown, you
> # end a line with two or more spaces, then type return.</p>
> #
> # <p>Yes, this takes a tad more effort to create a <code><br /></code>, but a simplistic
> # "every line break is a <code><br /></code>" rule wouldn't work for Markdown.
> # Markdown's email-style <a href="#blockquote">blockquoting</a> and multi-paragraph <a href="#list">list items</a>
> # work best -- and look better -- when you format them with hard breaks.</p>
> #
> # <h3 id="header">Headers</h3>
> #
> # <p>Markdown supports two styles of headers, <a href="http://docutils.sourceforge.net/mirror/setext.html">Setext</a> and <a href="http://www.aaronsw.com/2002/atx/">atx</a>.</p>
> #
> # <p>Setext-style headers are "underlined" using equal signs (for first-level
> # headers) and dashes (for second-level headers). For example:</p>
> #
> # <pre><code>This is an H1
> # =============
> #
> # This is an H2
> # -------------
> # </code></pre>
> #
> # <p>Any number of underlining <code>=</code>'s or <code>-</code>'s will work.</p>
> #
> # <p>Atx-style headers use 1-6 hash characters at the start of the line,
> # corresponding to header levels 1-6. For example:</p>
> #
> # <pre><code># This is an H1
> #
> # ## This is an H2
> #
> # ###### This is an H6
> # </code></pre>
> #
> # <p>Optionally, you may "close" atx-style headers. This is purely
> # cosmetic -- you can use this if you think it looks better. The
> # closing hashes don't even need to match the number of hashes
> # used to open the header. (The number of opening hashes
> # determines the header level.) :</p>
> #
> # <pre><code># This is an H1 #
> #
> # ## This is an H2 ##
> #
> # ### This is an H3 ######
> # </code></pre>
> #
> # <h3 id="blockquote">Blockquotes</h3>
> #
> # <p>Markdown uses email-style <code>></code> characters for blockquoting. If you're
> # familiar with quoting passages of text in an email message, then you
> # know how to create a blockquote in Markdown. It looks best if you hard
> # wrap the text and put a <code>></code> before every line:</p>
> #
> # <pre><code>> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
> # > consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
> # > Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
> # >
> # > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
> # > id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # <p>Markdown allows you to be lazy and only put the <code>></code> before the first
> # line of a hard-wrapped paragraph:</p>
> #
> # <pre><code>> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
> # consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus.
> # Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus.
> #
> # > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse
> # id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # <p>Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by
> # adding additional levels of <code>></code>:</p>
> #
> # <pre><code>> This is the first level of quoting.
> # >
> # > > This is nested blockquote.
> # >
> # > Back to the first level.
> # </code></pre>
> #
> # <p>Blockquotes can contain other Markdown elements, including headers, lists,
> # and code blocks:</p>
> #
> # <pre><code>> ## This is a header.
> # >
> # > 1. This is the first list item.
> # > 2. This is the second list item.
> # >
> # > Here's some example code:
> # >
> # > return shell_exec("echo $input | $markdown_script");
> # </code></pre>
> #
> # <p>Any decent text editor should make email-style quoting easy. For
> # example, with BBEdit, you can make a selection and choose Increase
> # Quote Level from the Text menu.</p>
> #
> # <h3 id="list">Lists</h3>
> #
> # <p>Markdown supports ordered (numbered) and unordered (bulleted) lists.</p>
> #
> # <p>Unordered lists use asterisks, pluses, and hyphens -- interchangably
> # -- as list markers:</p>
> #
> # <pre><code>* Red
> # * Green
> # * Blue
> # </code></pre>
> #
> # <p>is equivalent to:</p>
> #
> # <pre><code>+ Red
> # + Green
> # + Blue
> # </code></pre>
> #
> # <p>and:</p>
> #
> # <pre><code>- Red
> # - Green
> # - Blue
> # </code></pre>
> #
> # <p>Ordered lists use numbers followed by periods:</p>
> #
> # <pre><code>1. Bird
> # 2. McHale
> # 3. Parish
> # </code></pre>
> #
> # <p>It's important to note that the actual numbers you use to mark the
> # list have no effect on the HTML output Markdown produces. The HTML
> # Markdown produces from the above list is:</p>
> #
> # <pre><code><ol>
> # <li>Bird</li>
> # <li>McHale</li>
> # <li>Parish</li>
> # </ol>
> # </code></pre>
> #
> # <p>If you instead wrote the list in Markdown like this:</p>
> #
> # <pre><code>1. Bird
> # 1. McHale
> # 1. Parish
> # </code></pre>
> #
> # <p>or even:</p>
> #
> # <pre><code>3. Bird
> # 1. McHale
> # 8. Parish
> # </code></pre>
> #
> # <p>you'd get the exact same HTML output. The point is, if you want to,
> # you can use ordinal numbers in your ordered Markdown lists, so that
> # the numbers in your source match the numbers in your published HTML.
> # But if you want to be lazy, you don't have to.</p>
> #
> # <p>If you do use lazy list numbering, however, you should still start the
> # list with the number 1. At some point in the future, Markdown may support
> # starting ordered lists at an arbitrary number.</p>
> #
> # <p>List markers typically start at the left margin, but may be indented by
> # up to three spaces. List markers must be followed by one or more spaces
> # or a tab.</p>
> #
> # <p>To make lists look nice, you can wrap items with hanging indents:</p>
> #
> # <pre><code>* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
> # Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
> # viverra nec, fringilla in, laoreet vitae, risus.
> # * Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
> # Suspendisse id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # <p>But if you want to be lazy, you don't have to:</p>
> #
> # <pre><code>* Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
> # Aliquam hendrerit mi posuere lectus. Vestibulum enim wisi,
> # viverra nec, fringilla in, laoreet vitae, risus.
> # * Donec sit amet nisl. Aliquam semper ipsum sit amet velit.
> # Suspendisse id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # <p>If list items are separated by blank lines, Markdown will wrap the
> # items in <code><p></code> tags in the HTML output. For example, this input:</p>
> #
> # <pre><code>* Bird
> # * Magic
> # </code></pre>
> #
> # <p>will turn into:</p>
> #
> # <pre><code><ul>
> # <li>Bird</li>
> # <li>Magic</li>
> # </ul>
> # </code></pre>
> #
> # <p>But this:</p>
> #
> # <pre><code>* Bird
> #
> # * Magic
> # </code></pre>
> #
> # <p>will turn into:</p>
> #
> # <pre><code><ul>
> # <li><p>Bird</p></li>
> # <li><p>Magic</p></li>
> # </ul>
> # </code></pre>
> #
> # <p>List items may consist of multiple paragraphs. Each subsequent
> # paragraph in a list item must be intended by either 4 spaces
> # or one tab:</p>
> #
> # <pre><code>1. This is a list item with two paragraphs. Lorem ipsum dolor
> # sit amet, consectetuer adipiscing elit. Aliquam hendrerit
> # mi posuere lectus.
> #
> # Vestibulum enim wisi, viverra nec, fringilla in, laoreet
> # vitae, risus. Donec sit amet nisl. Aliquam semper ipsum
> # sit amet velit.
> #
> # 2. Suspendisse id sem consectetuer libero luctus adipiscing.
> # </code></pre>
> #
> # <p>It looks nice if you indent every line of the subsequent
> # paragraphs, but here again, Markdown will allow you to be
> # lazy:</p>
> #
> # <pre><code>* This is a list item with two paragraphs.
> #
> # This is the second paragraph in the list item. You're
> # only required to indent the first line. Lorem ipsum dolor
> # sit amet, consectetuer adipiscing elit.
> #
> # * Another item in the same list.
> # </code></pre>
> #
> # <p>To put a blockquote within a list item, the blockquote's <code>></code>
> # delimiters need to be indented:</p>
> #
> # <pre><code>* A list item with a blockquote:
> #
> # > This is a blockquote
> # > inside a list item.
> # </code></pre>
> #
> # <p>To put a code block within a list item, the code block needs
> # to be indented <em>twice</em> -- 8 spaces or two tabs:</p>
> #
> # <pre><code>* A list item with a code block:
> #
> # <code goes here>
> # </code></pre>
> #
> # <p>It's worth noting that it's possible to trigger an ordered list by
> # accident, by writing something like this:</p>
> #
> # <pre><code>1986. What a great season.
> # </code></pre>
> #
> # <p>In other words, a <em>number-period-space</em> sequence at the beginning of a
> # line. To avoid this, you can backslash-escape the period:</p>
> #
> # <pre><code>1986\. What a great season.
> # </code></pre>
> #
> # <h3 id="precode">Code Blocks</h3>
> #
> # <p>Pre-formatted code blocks are used for writing about programming or
> # markup source code. Rather than forming normal paragraphs, the lines
> # of a code block are interpreted literally. Markdown wraps a code block
> # in both <code><pre></code> and <code><code></code> tags.</p>
> #
> # <p>To produce a code block in Markdown, simply indent every line of the
> # block by at least 4 spaces or 1 tab. For example, given this input:</p>
> #
> # <pre><code>This is a normal paragraph:
> #
> # This is a code block.
> # </code></pre>
> #
> # <p>Markdown will generate:</p>
> #
> # <pre><code><p>This is a normal paragraph:</p>
> #
> # <pre><code>This is a code block.
> # </code></pre>
> # </code></pre>
> #
> # <p>One level of indentation -- 4 spaces or 1 tab -- is removed from each
> # line of the code block. For example, this:</p>
> #
> # <pre><code>Here is an example of AppleScript:
> #
> # tell application "Foo"
> # beep
> # end tell
> # </code></pre>
> #
> # <p>will turn into:</p>
> #
> # <pre><code><p>Here is an example of AppleScript:</p>
> #
> # <pre><code>tell application "Foo"
> # beep
> # end tell
> # </code></pre>
> # </code></pre>
> #
> # <p>A code block continues until it reaches a line that is not indented
> # (or the end of the article).</p>
> #
> # <p>Within a code block, ampersands (<code>&</code>) and angle brackets (<code><</code> and <code>></code>)
> # are automatically converted into HTML entities. This makes it very
> # easy to include example HTML source code using Markdown -- just paste
> # it and indent it, and Markdown will handle the hassle of encoding the
> # ampersands and angle brackets. For example, this:</p>
> #
> # <pre><code> <div class="footer">
> # &copy; 2004 Foo Corporation
> # </div>
> # </code></pre>
> #
> # <p>will turn into:</p>
> #
> # <pre><code><pre><code>&lt;div class="footer"&gt;
> # &amp;copy; 2004 Foo Corporation
> # &lt;/div&gt;
> # </code></pre>
> # </code></pre>
> #
> # <p>Regular Markdown syntax is not processed within code blocks. E.g.,
> # asterisks are just literal asterisks within a code block. This means
> # it's also easy to use Markdown to write about Markdown's own syntax.</p>
> #
> # <h3 id="hr">Horizontal Rules</h3>
> #
> # <p>You can produce a horizontal rule tag (<code><hr /></code>) by placing three or
> # more hyphens, asterisks, or underscores on a line by themselves. If you
> # wish, you may use spaces between the hyphens or asterisks. Each of the
> # following lines will produce a horizontal rule:</p>
> #
> # <pre><code>* * *
> #
> # ***
> #
> # *****
> #
> # - - -
> #
> # ---------------------------------------
> #
> # _ _ _
> # </code></pre>
> #
> # <hr />
> #
> # <h2 id="span">Span Elements</h2>
> #
> # <h3 id="link">Links</h3>
> #
> # <p>Markdown supports two style of links: <em>inline</em> and <em>reference</em>.</p>
> #
> # <p>In both styles, the link text is delimited by [square brackets].</p>
> #
> # <p>To create an inline link, use a set of regular parentheses immediately
> # after the link text's closing square bracket. Inside the parentheses,
> # put the URL where you want the link to point, along with an <em>optional</em>
> # title for the link, surrounded in quotes. For example:</p>
> #
> # <pre><code>This is [an example](http://example.com/ "Title") inline link.
> #
> # [This link](http://example.net/) has no title attribute.
> # </code></pre>
> #
> # <p>Will produce:</p>
> #
> # <pre><code><p>This is <a href="http://example.com/" title="Title">
> # an example</a> inline link.</p>
> #
> # <p><a href="http://example.net/">This link</a> has no
> # title attribute.</p>
> # </code></pre>
> #
> # <p>If you're referring to a local resource on the same server, you can
> # use relative paths:</p>
> #
> # <pre><code>See my [About](/about/) page for details.
> # </code></pre>
> #
> # <p>Reference-style links use a second set of square brackets, inside
> # which you place a label of your choosing to identify the link:</p>
> #
> # <pre><code>This is [an example][id] reference-style link.
> # </code></pre>
> #
> # <p>You can optionally use a space to separate the sets of brackets:</p>
> #
> # <pre><code>This is [an example] [id] reference-style link.
> # </code></pre>
> #
> # <p>Then, anywhere in the document, you define your link label like this,
> # on a line by itself:</p>
> #
> # <pre><code>[id]: http://example.com/ "Optional Title Here"
> # </code></pre>
> #
> # <p>That is:</p>
> #
> # <ul>
> # <li>Square brackets containing the link identifier (optionally
> # indented from the left margin using up to three spaces);</li>
> # <li>followed by a colon;</li>
> # <li>followed by one or more spaces (or tabs);</li>
> # <li>followed by the URL for the link;</li>
> # <li>optionally followed by a title attribute for the link, enclosed
> # in double or single quotes.</li>
> # </ul>
> #
> # <p>The link URL may, optionally, be surrounded by angle brackets:</p>
> #
> # <pre><code>[id]: <http://example.com/> "Optional Title Here"
> # </code></pre>
> #
> # <p>You can put the title attribute on the next line and use extra spaces
> # or tabs for padding, which tends to look better with longer URLs:</p>
> #
> # <pre><code>[id]: http://example.com/longish/path/to/resource/here
> # "Optional Title Here"
> # </code></pre>
> #
> # <p>Link definitions are only used for creating links during Markdown
> # processing, and are stripped from your document in the HTML output.</p>
> #
> # <p>Link definition names may constist of letters, numbers, spaces, and punctuation -- but they are <em>not</em> case sensitive. E.g. these two links:</p>
> #
> # <pre><code>[link text][a]
> # [link text][A]
> # </code></pre>
> #
> # <p>are equivalent.</p>
> #
> # <p>The <em>implicit link name</em> shortcut allows you to omit the name of the
> # link, in which case the link text itself is used as the name.
> # Just use an empty set of square brackets -- e.g., to link the word
> # "Google" to the google.com web site, you could simply write:</p>
> #
> # <pre><code>[Google][]
> # </code></pre>
> #
> # <p>And then define the link:</p>
> #
> # <pre><code>[Google]: http://google.com/
> # </code></pre>
> #
> # <p>Because link names may contain spaces, this shortcut even works for
> # multiple words in the link text:</p>
> #
> # <pre><code>Visit [Daring Fireball][] for more information.
> # </code></pre>
> #
> # <p>And then define the link:</p>
> #
> # <pre><code>[Daring Fireball]: http://daringfireball.net/
> # </code></pre>
> #
> # <p>Link definitions can be placed anywhere in your Markdown document. I
> # tend to put them immediately after each paragraph in which they're
> # used, but if you want, you can put them all at the end of your
> # document, sort of like footnotes.</p>
> #
> # <p>Here's an example of reference links in action:</p>
> #
> # <pre><code>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"
> # </code></pre>
> #
> # <p>Using the implicit link name shortcut, you could instead write:</p>
> #
> # <pre><code>I get 10 times more traffic from [Google][] than from
> # [Yahoo][] or [MSN][].
> #
> # [google]: http://google.com/ "Google"
> # [yahoo]: http://search.yahoo.com/ "Yahoo Search"
> # [msn]: http://search.msn.com/ "MSN Search"
> # </code></pre>
> #
> # <p>Both of the above examples will produce the following HTML output:</p>
> #
> # <pre><code><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>
> # </code></pre>
> #
> # <p>For comparison, here is the same paragraph written using
> # Markdown's inline link style:</p>
> #
> # <pre><code>I get 10 times more traffic from [Google](http://google.com/ "Google")
> # than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
> # [MSN](http://search.msn.com/ "MSN Search").
> # </code></pre>
> #
> # <p>The point of reference-style links is not that they're easier to
> # write. The point is that with reference-style links, your document
> # source is vastly more readable. Compare the above examples: using
> # reference-style links, the paragraph itself is only 81 characters
> # long; with inline-style links, it's 176 characters; and as raw HTML,
> # it's 234 characters. In the raw HTML, there's more markup than there
> # is text.</p>
> #
> # <p>With Markdown's reference-style links, a source document much more
> # closely resembles the final output, as rendered in a browser. By
> # allowing you to move the markup-related metadata out of the paragraph,
> # you can add links without interrupting the narrative flow of your
> # prose.</p>
> #
> # <h3 id="em">Emphasis</h3>
> #
> # <p>Markdown treats asterisks (<code>*</code>) and underscores (<code>_</code>) as indicators of
> # emphasis. Text wrapped with one <code>*</code> or <code>_</code> will be wrapped with an
> # HTML <code><em></code> tag; double <code>*</code>'s or <code>_</code>'s will be wrapped with an HTML
> # <code><strong></code> tag. E.g., this input:</p>
> #
> # <pre><code>*single asterisks*
> #
> # _single underscores_
> #
> # **double asterisks**
> #
> # __double underscores__
> # </code></pre>
> #
> # <p>will produce:</p>
> #
> # <pre><code><em>single asterisks</em>
> #
> # <em>single underscores</em>
> #
> # <strong>double asterisks</strong>
> #
> # <strong>double underscores</strong>
> # </code></pre>
> #
> # <p>You can use whichever style you prefer; the lone restriction is that
> # the same character must be used to open and close an emphasis span.</p>
> #
> # <p>Emphasis can be used in the middle of a word:</p>
> #
> # <pre><code>un*fucking*believable
> # </code></pre>
> #
> # <p>But if you surround an <code>*</code> or <code>_</code> with spaces, it'll be treated as a
> # literal asterisk or underscore.</p>
> #
> # <p>To produce a literal asterisk or underscore at a position where it
> # would otherwise be used as an emphasis delimiter, you can backslash
> # escape it:</p>
> #
> # <pre><code>\*this text is surrounded by literal asterisks\*
> # </code></pre>
> #
> # <h3 id="code">Code</h3>
> #
> # <p>To indicate a span of code, wrap it with backtick quotes (<code>`</code>).
> # Unlike a pre-formatted code block, a code span indicates code within a
> # normal paragraph. For example:</p>
> #
> # <pre><code>Use the `printf()` function.
> # </code></pre>
> #
> # <p>will produce:</p>
> #
> # <pre><code><p>Use the <code>printf()</code> function.</p>
> # </code></pre>
> #
> # <p>To include a literal backtick character within a code span, you can use
> # multiple backticks as the opening and closing delimiters:</p>
> #
> # <pre><code>``There is a literal backtick (`) here.``
> # </code></pre>
> #
> # <p>which will produce this:</p>
> #
> # <pre><code><p><code>There is a literal backtick (`) here.</code></p>
> # </code></pre>
> #
> # <p>The backtick delimiters surrounding a code span may include spaces --
> # one after the opening, one before the closing. This allows you to place
> # literal backtick characters at the beginning or end of a code span:</p>
> #
> # <pre><code>A single backtick in a code span: `` ` ``
> #
> # A backtick-delimited string in a code span: `` `foo` ``
> # </code></pre>
> #
> # <p>will produce:</p>
> #
> # <pre><code><p>A single backtick in a code span: <code>`</code></p>
> #
> # <p>A backtick-delimited string in a code span: <code>`foo`</code></p>
> # </code></pre>
> #
> # <p>With a code span, ampersands and angle brackets are encoded as HTML
> # entities automatically, which makes it easy to include example HTML
> # tags. Markdown will turn this:</p>
> #
> # <pre><code>Please don't use any `<blink>` tags.
> # </code></pre>
> #
> # <p>into:</p>
> #
> # <pre><code><p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>
> # </code></pre>
> #
> # <p>You can write this:</p>
> #
> # <pre><code>`&#8212;` is the decimal-encoded equivalent of `&mdash;`.
> # </code></pre>
> #
> # <p>to produce:</p>
> #
> # <pre><code><p><code>&amp;#8212;</code> is the decimal-encoded
> # equivalent of <code>&amp;mdash;</code>.</p>
> # </code></pre>
> #
> # <h3 id="img">Images</h3>
> #
> # <p>Admittedly, it's fairly difficult to devise a "natural" syntax for
> # placing images into a plain text document format.</p>
> #
> # <p>Markdown uses an image syntax that is intended to resemble the syntax
> # for links, allowing for two styles: <em>inline</em> and <em>reference</em>.</p>
> #
> # <p>Inline image syntax looks like this:</p>
> #
> # <pre><code>
> #
> # 
> # </code></pre>
> #
> # <p>That is:</p>
> #
> # <ul>
> # <li>An exclamation mark: <code>!</code>;</li>
> # <li>followed by a set of square brackets, containing the <code>alt</code>
> # attribute text for the image;</li>
> # <li>followed by a set of parentheses, containing the URL or path to
> # the image, and an optional <code>title</code> attribute enclosed in double
> # or single quotes.</li>
> # </ul>
> #
> # <p>Reference-style image syntax looks like this:</p>
> #
> # <pre><code>![Alt text][id]
> # </code></pre>
> #
> # <p>Where "id" is the name of a defined image reference. Image references
> # are defined using syntax identical to link references:</p>
> #
> # <pre><code>[id]: url/to/image "Optional title attribute"
> # </code></pre>
> #
> # <p>As of this writing, Markdown has no syntax for specifying the
> # dimensions of an image; if this is important to you, you can simply
> # use regular HTML <code><img></code> tags.</p>
> #
> # <hr />
> #
> # <h2 id="misc">Miscellaneous</h2>
> #
> # <h3 id="autolink">Automatic Links</h3>
> #
> # <p>Markdown supports a shortcut style for creating "automatic" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:</p>
> #
> # <pre><code><http://example.com/>
> # </code></pre>
> #
> # <p>Markdown will turn this into:</p>
> #
> # <pre><code><a href="http://example.com/">http://example.com/</a>
> # </code></pre>
> #
> # <p>Automatic links for email addresses work similarly, except that
> # Markdown will also perform a bit of randomized decimal and hex
> # entity-encoding to help obscure your address from address-harvesting
> # spambots. For example, Markdown will turn this:</p>
> #
> # <pre><code><address at example.com>
> # </code></pre>
> #
> # <p>into something like this:</p>
> #
> # <pre><code><a href="&#x6D;&#x61;i&#x6C;&#x74;&#x6F;:&#x61;&#x64;&#x64;&#x72;&#x65;
> # &#115;&#115;&#64;&#101;&#120;&#x61;&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;
> # &#109;">&#x61;&#x64;&#x64;&#x72;&#x65;&#115;&#115;&#64;&#101;&#120;&#x61;
> # &#109;&#x70;&#x6C;e&#x2E;&#99;&#111;&#109;</a>
> # </code></pre>
> #
> # <p>which will render in a browser as a clickable link to "address at example.com".</p>
> #
> # <p>(This sort of entity-encoding trick will indeed fool many, if not
> # most, address-harvesting bots, but it definitely won't fool all of
> # them. It's better than nothing, but an address published in this way
> # will probably eventually start receiving spam.)</p>
> #
> # <h3 id="backslash">Backslash Escapes</h3>
> #
> # <p>Markdown allows you to use backslash escapes to generate literal
> # characters which would otherwise have special meaning in Markdown's
> # formatting syntax. For example, if you wanted to surround a word with
> # literal asterisks (instead of an HTML <code><em></code> tag), you can backslashes
> # before the asterisks, like this:</p>
> #
> # <pre><code>\*literal asterisks\*
> # </code></pre>
> #
> # <p>Markdown provides backslash escapes for the following characters:</p>
> #
> # <pre><code>\ backslash
> # ` backtick
> # * asterisk
> # _ underscore
> # {} curly braces
> # [] square brackets
> # () parentheses
> # # hash mark
> # + plus sign
> # - minus sign (hyphen)
> # . dot
> # ! exclamation mark
> # </code></pre>
> # '
> # Looks like you failed 1 test of 2.
> t/35commandlinemultimarkdown.t ............
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/2 subtests
>
> # Failed test 'underscores in code in footnotes'
> # at t/36footnotes.t line 30.
> # got: 'This is buggy<a href="#fn:bug" id="fnref:bug" class="footnote">1</a>.
> #
> # <div class="footnotes">
> # <hr />
> # <ol>
> #
> # <li id="fn:bug">Use <code>MYAPP_CONFIG_LOCAL_SUFFIX</code>.<a href="#fnref:bug" class="reversefootnote"> ↩</a></li>
> #
> # </ol>
> # </div>
> # '
> # expected: '<p>This is buggy<a href="#fn:bug" id="fnref:bug" class="footnote">1</a>.</p>
> #
> # <div class="footnotes">
> # <hr />
> # <ol>
> #
> # <li id="fn:bug"><p>Use <code>MYAPP_CONFIG_LOCAL_SUFFIX</code>.<a href="#fnref:bug" class="reversefootnote"> ↩</a></p></li>
> #
> # </ol>
> # </div>
> # '
> # Looks like you failed 1 test of 2.
> Failed 16/27 test programs. 75/226 subtests failed.
> t/36footnotes.t ...........................
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/2 subtests
>
> Test Summary Report
> -------------------
> t/04markdown.t (Wstat: 512 Tests: 3 Failed: 2)
> Failed tests: 2-3
> Non-zero exit status: 2
> t/05options.t (Wstat: 512 Tests: 3 Failed: 2)
> Failed tests: 2-3
> Non-zero exit status: 2
> t/07fulldoc.t (Wstat: 256 Tests: 2 Failed: 1)
> Failed test: 2
> Non-zero exit status: 1
> t/08exporter.t (Wstat: 256 Tests: 5 Failed: 1)
> Failed test: 3
> Non-zero exit status: 1
> t/09base_url.t (Wstat: 768 Tests: 4 Failed: 3)
> Failed tests: 2-4
> Non-zero exit status: 3
> t/10use_metadata.t (Wstat: 1536 Tests: 7 Failed: 6)
> Failed tests: 2-7
> Non-zero exit status: 6
> t/11docment_format.t (Wstat: 1024 Tests: 5 Failed: 4)
> Failed tests: 2-5
> Non-zero exit status: 4
> t/12empty_element_suffix.t (Wstat: 512 Tests: 3 Failed: 2)
> Failed tests: 2-3
> Non-zero exit status: 2
> t/13multimarkdown-nometadata-firstpara.t (Wstat: 256 Tests: 2 Failed: 1)
> Failed test: 2
> Non-zero exit status: 1
> t/14unicode.t (Wstat: 256 Tests: 3 Failed: 1)
> Failed test: 3
> Non-zero exit status: 1
> t/18codespanextra.t (Wstat: 768 Tests: 4 Failed: 3)
> Failed tests: 2-4
> Non-zero exit status: 3
> t/20fulldocs-text-multimarkdown.t (Wstat: 8960 Tests: 41 Failed: 35)
> Failed tests: 2, 4-9, 11-16, 18-35, 37-40
> Non-zero exit status: 35
> t/23afulldocs-multimarkdown.t (Wstat: 2304 Tests: 11 Failed: 9)
> Failed tests: 2, 4-11
> Non-zero exit status: 9
> t/24fulldocs-pythonmarkdown2-tm.t (Wstat: 0 Tests: 41 Failed: 0)
> TODO passed: 22, 36
> t/29fulldocs-maruku-unittest.t (Wstat: 0 Tests: 60 Failed: 0)
> TODO passed: 4-5, 23, 29, 51
> t/30disable_multimarkdown_features.t (Wstat: 768 Tests: 4 Failed: 3)
> Failed tests: 2-4
> Non-zero exit status: 3
> t/35commandlinemultimarkdown.t (Wstat: 256 Tests: 2 Failed: 1)
> Failed test: 2
> Non-zero exit status: 1
> t/36footnotes.t (Wstat: 256 Tests: 2 Failed: 1)
> Failed test: 2
> Non-zero exit status: 1
> Files=27, Tests=226, 3 wallclock secs ( 0.33 usr 0.04 sys + 2.61 cusr 0.26 csys = 3.24 CPU)
> Result: FAIL
> make[2]: *** [test_dynamic] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2009/10/16/libtext-multimarkdown-perl_1.0.27-2_lsid64.buildlog
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--
| Lucas Nussbaum
| lucas at lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr GPG: 1024D/023B3F4F |
More information about the pkg-perl-maintainers
mailing list