Markdown generates invalid html for a list immediately followed by a quote

Michel Fortin michel.fortin at
Thu Jul 12 08:44:53 EDT 2007

Le 2007-07-09 à 15:28, John Gruber a écrit :

> One reason I've held off on major updates for so long is the idea

> that if I'm going to break compatibility with Markdown 1.0, it'd

> best to break it once, in multiple ways. Better for one Markdown

> 2.0 that breaks/changes/clarifies several things all at once than

> than a bunch of 1.1, 1.2, 1.3 updates that break things here and

> there.

That's a good plan.

> Plus, anything outright new, like tables, is by definition going to

> break compatibility with 1.0 implementations.

Anything, from the simplest bug fix to the most complex feature, is
by definition going to break compatibility with 1.0 implementations
because the output for a given input is going to change; there's no
way to avoid that. But many changes in 1.0.1 are more problematic
from a compatibility point of view than the addition of a table
syntax like the one in PHP Markdown Extra -- it's pretty difficult to
write a table by accident because it requires a lot of pipes and
dashes following a certain pattern; on the other side, backslashes in
code blocks and spans are not a rare occurrence.

In other words, I think adding a feature and changing (or fixing) a
feature are on two different scales for compatibility problems, the
later being generally much more risky than the former because the
syntax is already in use.

Michel Fortin
michel.fortin at

More information about the Markdown-Discuss mailing list