Re: [Python-markdown-discuss] A couple more tests for some edge cases

[John S. <jo...@sz...>]

On Mon, Nov 10, 2008 at 10:12 AM, Waylan Limberg <wa...@gm...> wrote:
> On Thu, Nov 6, 2008 at 5:28 AM, John Szakmeister <jo...@sz...> wrote:
>> did find that if I embed a header into a list like so:
>>  1. My list
>>
>>     ## blah, blah
>>
>
> Ah, yes, this one. You only have three spaces of indent.
> Python-Markdown requires four or its not a child of the list item. If
> you check Babelmark [1], about half the implementations require four
> spaces and the other half just require indentation of any kind. This
> has been a hotly debated topic on the markdown dicussion list in the
> past which I'd rather not see repeated here.

Heh.  I didn't realize that... but you're right, it's there in the syntax guide.

> Regardless of which side of that argument you may fall on, I've taken
> the position that the current code base creates a technical limitation
> which forces us to require four spaces. So, I'm likely to set the
> ticket Yuri created for this as "wontfix" unless someone else can come
> up with a solution I'm not aware of. I realize that sounds a little
> harsh, but I don't have a better answer at this time.

No offense taken.

> Of course, there is the question as to why the header isn't parsed as
> a header, just *not* as a child of the list item. Well, all
> implementations require the hash to be the *very first* character on
> the line or it's not a header. Again, see Babelmark [2]. Obviously,
> that distinction becomes blurry when only whitespace defines children
> of list items. It's easy to see how there can be multiple views on the
> correct behavior here.

I understand.  Thanks for clearing that up.  It's also weird that the
space before the hash gets inserted into the HTML, rather than
stripped.  I'm not sure why that was happening.

-John