Re: [Python-markdown-discuss] Email-style blockquote formatter?

[Waylan L. <wa...@gm...>]

On Wed, Dec 24, 2008 at 4:36 PM, Yuri Takhteyev <qar...@gm...> wrote:
> Actually, it's the lack of spaces after blockquotes. If you change
> Matthias's example to make sure there is a space after every angle
> bracket, it works quite reasonably.

I disagree. The "whatever" and "right" lines in Mathias' example
should step out of the second level and according to babelmark, every
implementation except Maruku gets that wrong by including everything
past the first line of the second level in the second level. The only
way to avoid that is with blank lines. So the issue (not specific to
python) is blank lines more that spaces after >s.

To take this further it occurred to me after my last response, that
the last line of Mattias' example was not meant to be part of any
blockquote, but a response to the first level blockquote. Per the
syntax, the only way that will work is with a blank line.

Compare:

    > right
    wrong

to this:

    > rigth

    wrong

The syntax is very clear that the first example above must result in:

    <blockquote>
      <p>right
      wrong</p>
    </blockquote>

While I suspect the desired result was this (which is obtained by the
second example above):

    <blockquote>
      <p>right</p>
    </blockquote>

    <p>wrong</p>

So yeah, the issue is blank lines. However, this is *not* a bug in
markdown, but a feature. Yes it does restrict the author a little, but
it is necessary given the syntax rules as they are written.

> I think this is a bug, actually, because there is no reason we should
> require that space, and Matthias's example does work many (though not
> all) other implementations.

Personally, I prefer requiring the space - but then I always did
prefer stricter whitespace in the syntax than most people. Whatever.





-- 
----
Waylan Limberg
wa...@gm...