From: Waylan L. <wa...@gm...> - 2008-08-31 16:27:08
|
On Fri, Aug 29, 2008 at 7:12 PM, Artem Yunusov <ne...@gm...> wrote: > Waylan Limberg wrote: >> On Wed, Aug 27, 2008 at 6:16 PM, Waylan Limberg <wa...@gm...> wrote: >> >>> >>> markdown.markdown('foo *bar __blah__* baz') >>> u'<p>foo <em>bar <strong>blah</strong>\n </em> baz</p>' >>> >>> What's up with the newline and space between the closing tags >>> ``</strong>`` & ``</em>``? Is that from the (IMO unnecessary) >>> ``IndentTree`` function or something in >>> ``Markdown._processPlaceholders``? I'm not sure. >>> >>> >> >> Ok, I just realized that that is the output we were getting before my >> change to the inline placeholder. Weird! IMO that is not correct. We >> need to loose that extra whitespace. I realize it's irrelevant in the >> browser, but no other markdown implementation does that. Either the >> indentTree function needs to only work on block level elements or it >> needs to go away. >> >> > > Yes, it's because of indentETree function. We don't have now any other > way of managing output, maybe in future releases ElementTree will get > some pretty print function, but there is no such for now. So we should > modify indentETree, but we shouldn't throw it away :) Yeah, I realize that now. Still getting used to ElementTree. > Looked at your > placeholder branch, now extractId looks much prettier and cleaner :) Good, then I understood how it works correctly. I'll merge it in when I get a chance. -- ---- Waylan Limberg wa...@gm... |