View Single Post
Old 01-25-2011, 09:19 AM   #11
ldolse
Wizard
ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.ldolse is an accomplished Snipe hunter.
 
Posts: 1,337
Karma: 123455
Join Date: Apr 2009
Location: Malaysia
Device: PRS-650, iPhone
Quote:
Originally Posted by itimpi View Post
Actually not quite true! The Markdown spec specifically says that it does not process text inside an HTML block tag - and both the <DIV> and (I think) <P> fall into this category. I went looking when trying to process the Comments stored in Calibre was failing and found this statement. If Calibre had not stored the comment in a hybrid form of Markdown syntax inside an HTML block tag I would have been OK. That was why one of the options I mentioned in my original post was the brute force one of programatically removing the Calibre enclosing tags before applying the Markdown processing.

Interestingly enough - I notice the markdown spec says that text inside <SPAN> tags is subject to markdown processing.
Actually - now that I think about it, I've got lots of markdown formatted content inside of Div tags in the book I've been editing and it gets converted fine. I don't have any <p> tags though, they may be the real killer - I wonder if the rich text editor could be changed to use <br />?

Span tags don't surprise me - very much an inline element.
ldolse is offline   Reply With Quote