From: Gerry L. <gjl...@al...> - 2010-03-24 13:40:34
|
> In other words, follow the syntax rules, not his code when the two > appear to be in conflict. I believe this may fit that type of > situation. > > I would call this a bug in markdown.pl (and any other implementation > that follows it), not a bug in python-markdown. The notion of following the syntax rules is the only potential gotcha here. I looked high and low for an explicit statement regarding usage of the blockquote. I came up empty. The implication seems to be that blockquote processing is triggered if the '>' character is the first non-whitespace character on the line. However, if a blank space is added between list items (i.e. create a list with paragraphs) with blockquotes, then the blockquote is processed in most implementations, including markdown.pl. So, it seems it comes back to what the reasonable output expectation would be for text formatted like that. Certainly, python-markdown's handling of this (if not edge case, then low usage) format can be considered reasonable. So count me in agreement. |