Multi-paragraph list items in Markdown not recognised on HTML conversion

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Have the following Markdown contents in a file

A list follows:
 * This is element one
 * The second element.

   This is still the second element, which happens
   to expand across multiple paragraphs.
 * The third element.

2. Convert from Markdown to HTML

What is the expected output? What do you see instead?

This is the expected output:
<p>A list follows:</p>
<ul>
<li>This is element one</li>
<li><p>The second element.</p>
    <p>This is still the second element, which happens to expand across multiple paragraphs.</p></li>
<li>The third element.</li>
</ul>

This is what I get instead:

<p>A list follows:</p>
<ul>
<li>This is element one</li>
<li>The second element.</li></ul>
<p>This is still the second element, which happens to expand across multiple 
paragraphs.</p>
<ul>
<li>The third element.</li>
</ul>

The second paragraph in the second item is generated outside the list and 
causes the list to end and then restart for the third item. This is not 
consistent with the syntax specified here: 
http://daringfireball.net/projects/markdown/syntax#list

What version of the product are you using? On what operating system?
pandoc 1.6 on Ubuntu 10.4

Please provide any additional information below.

Original issue reported on code.google.com by jdev...@gmail.com on 30 Aug 2010 at 11:40

[GoogleCodeExporter]

This is a place where pandoc's output diverges from Markdown.pl's, but it is 
not a bug. Pandoc is in accord with the spec (I quote here from the the syntax 
description on daringfireball.net):  "List items may consist of multiple 
paragraphs. Each subsequent paragraph in a list item must be indented by either 
4 spaces or one tab:"

Note that you only have 3 spaces before your continuation paragraph.

Markdown.pl doesn't rigorously enforce this 4-space rule, but pandoc does.

Original comment by fiddloso...@gmail.com on 30 Aug 2010 at 5:47

• Changed state: Invalid

[GoogleCodeExporter]

Ah, my bad, thanks for clarifying.

Original comment by jdev...@gmail.com on 30 Aug 2010 at 6:08