<figure> and <figcaption> not available for epub2

Scrivener Markdown & LaTeX
1

I’m using MMD to generate epub format. It creates and tags that seem to be part of the epub3 standard, but are not recognized in epub2.

Is there a way to generate some other tag instead, such as

, at compile time so I don’t have to modify the html file that has been generated.

By the way, I’m using the Linux version of Scrivener.

Thanks for helping.

2

MultiMarkdown generates HTML5 documents, which yes, are not compatible with ePub2 (you need XHTML). I would consider using Pandoc to generate your ePub, actually. If you set Scrivener to compile to basic MultiMarkdown instead of going straight to HTML, then with only a few tweaks, in most cases, you can then make use of Pandoc against that file to generate an ePub (either ePub2 or ePub3). It does a pretty decent job, and has a good level of customisation so you that you can streamline the process going forward—such as providing meta-data XML files, CSS, and even supporting most MMD conventions (like the MMD meta-data block).

3

Thanks for your answer.
Unless I’ve missed something, Pandoc seems to be a command-line tool only. So, I think I’ll stick to Sigil, that can do the job perfectly well, too. I’ll just have to do a couple of Search-Replace commands to get the markup I need before applying customized stylesheets, and produce the final epub.

4

If you want to see what you have to type on the command line to convert from text markdown to epub, this is the version that I have used successfully on Windows:

pandoc -f markdown_strict -t epub -i -o --epub-stylesheet= --epub-cover-image=“cover.jpg” --toc-depth=1

The default pandoc stylesheet will look like this:
body { margin: 5%; text-align: justify; font-size: medium; }
code { font-family: monospace; }
h1 { text-align: left; }
h2 { text-align: left; }
h3 { text-align: left; }
h4 { text-align: left; }
h5 { text-align: left; }
h6 { text-align: left; }
h1.title { }
h2.author { }
h3.date { }
ol.toc { padding: 0; margin-left: 1em; }

Thats why its better to pre-define your own applied para styles for h1 to h6 throughout your ebook within your own CSS and use that.

You can even embed fonts in the above by using –epub-embed-font if you want.