You my surround your html code ind your markdown document with:

```{=html}
<your>html comes</here>
```

I do it in my markdown files often with LaTeX snippets, for example if I need a picture with text floating around:

```{=latex}
\begin{wrapfigure}[12]{l}{2.5in}
\centering
\includegraphics[width=2in]{pix/portrait_troeper.jpg}
\end{wrapfigure}
```

Best greetings


marek

On Wednesday, September 28, 2022 at 5:49:04 PM UTC+2 Antonio Piccolboni wrote:


> On Sep 27, 2022, at 11:04 PM, John MacFarlane <fiddlo...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>
>
>> On Sep 27, 2022, at 8:41 PM, Antonio Piccolboni <picc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>
>> Until now I had assumed that markdown was a superset of html. It wasn't a pandoc extension, it is what the Markdown format says: you can mix in html when markdown syntax is not enough. It was the backstop that made it easy to pick markdown without future regret. So not converting the html in markdown is not in keeping with the format definition according to my assumptions. That said, markdown doesn't have an official standard and I may very well be wrong.
>
> Well, original Markdown.pl was just a markdown -> HTML converter, with no aspirations to support any other formats. So the HTML was passed through literally to the output, and that is what we still do. I think either approach would be equally consistent with the original. But the literal passthrough approach is what we stick with, for a number of reasons.
>
> The main one is that HTML is strictly more expressive than what can be represented with pandoc's types. Allowing HTML in markdown was a way of avoiding expressive limitations; if you want to do something fancy, you can pass through HTML. If we parsed the HTML and re-rendered, we'd often lose something (although over time pandoc's types have gotten more expressive, they are still not as expressive as HTML).

It makes sense.

>
>> In my specific case the solution is to use just markdown as Martin suggested. The reason I had switched to html is that, for some reason, the calibre epub viewer ignores the caption when using the Markdown syntax. Apple books doesn't have this problem. So I will just ignore the calibre viewer. I had a few other uses for html tags like sup and span, but I can work around those, mostly. Thanks!
>
> You could use a filter to generate special HTML from pandoc figures, for HTML output only.
>
> Note also that pandoc's markdown includes syntax for sup and span.


Thanks, my bad for not RFM.


Antonio



>
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/pandoc-discuss/-yzmZBWG818/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to pandoc-discus...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ADAB9DB0-E0D5-4933-A83A-589C7EF14F61%40gmail.com.

--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/6e4901ec-64bd-4d19-a532-2dde1f315900n%40googlegroups.com.