The jpg image is invoked via "xlink:href="
Unless I'm getting confused with the relative path the nightly version
still does not pull the referenced file: it's nowhere to be found either in
the EPUB/content.opf manifest nor does it get copied over to EPUB/media/*
On the other hand pandoc does understand the tag: in the
content.opf manifest of the resulting EPUB the description of the
ch001.xhtml that contains the above code includes the "properties=svg"
attribute.
My guess is that pandoc does not understand the "xlink:ref=" syntax.
CJ
On Monday, October 26, 2020 at 5:17:42 PM UTC-4 John MacFarlane wrote:
> Chris Jones writes:
>
> > What I see is the following processing of raw HTML when creating an EPUB:
> >
> > 1. Tags of the form:
> >
> >
> >
> > are processed to some extent insofar as the description of the file is
> > added to the resulting content.opf manifest and the image is copied to
> the
> > EPUB/media/ directory
> >
> > 2. tabs are also partially processed: their presence in a
> file
> > (book chapter) automatically causes pandoc to add "properties=svg"
> > qualifier to the file's description in the manifest. On the other hand
> what
> > lives inside the svg wrapper is ignored.
>
> I believe this was just fixed a couple days ago:
>
> commit 4bf171e11dd324f5c65e15da17717b701e961b17
> Author: John MacFarlane
> Date: Fri Oct 23 21:56:12 2020 -0700
>
> HTML reader: parse inline svg as image...
>
> ...unless `raw_html` is set in the reader (in which case
> the svg is passed through as raw HTML).
>
> Closes #6770.
>
> You can try with a nightly.
>
>
--
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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/04e6652d-6db6-4090-b2f1-db7acc33edd2n%40googlegroups.com.