surplus <p> tags.

Sherwood Botsford sgbotsford at
Wed Mar 25 11:12:22 EDT 2009

I've run into a problem with multimarkdown, and would like advice: From
Fletcher's doc:



Unlike PHP Markdown Extra, all definitions are wrapped in <p> tags. First,

> I

was unable to get Markdown not to create paragraphs. Second, I didn’t see

where it mattered - the only difference seems to be aesthetic, and I

> actually

prefer the <p> tags in place. Let me know if this is a problem.

1. <p><div></p> causes W3C's xhtml checker to whine. All non-ancientbrowsers
do the right thing, so I can ignore it. 2. The combination of<p><img ....

></p> and the CSS code snippet p { text-indent: 1em; } causes the IMAGE

to be indented 1 em. (presumably since it's in thefirst line of text.) This
also adds an extra em of leading space to my headlings -- that I can live
with. This is solveable by putting an additional css snippet in
p img {
margin-left: -1em;
(img doesn't know about text-indent.
This is a hack, and makes for the potential of ugly side effects when
modifying the css code --
something already filled with surprises.
The ideal solution from my perspective is two modifications of MMD that I
can't figure out how to do:
1. Remove the extra <p> tagging.
2. Specify automatically that structural tags get passed through unchanged.
(Structural tags = div, body, html, and those tags that lurk in the head.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Markdown-Discuss mailing list