From: Charles Richer Saint-Faure <richer.saint.faure-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: image that resizes automatically to screen size in epub
Date: Tue, 6 Oct 2020 15:15:26 -0700 (PDT) [thread overview]
Message-ID: <a0514cc8-560e-40b2-802e-aed2b58930a8o@googlegroups.com> (raw)
In-Reply-To: <b49a95c6-772c-43ac-9bc5-0011ed206c38o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 8106 bytes --]
On Sunday, June 14, 2020 at 6:15:47 PM UTC-4, Chris Jones wrote:
>
> I have an image meant to be fit exactly one page (or should I say
> screenful) that I would like the e-reading application to resize
> automatically to the size of the e-reader's screen while preserving aspect
> ration as is already done with the cover image.
>
> The image can be a png, jpeg, or svg (the png and jpeg are generated from
> the svg, itself created initially under latex as a pdf and converted to svg
> via inkscape).
>
> The svg file displays correctly under firefox and can be resized with no
> visible loss of crispness & resolution.
>
> Is there any way to do this currently in pandoc?
>
> Thanks,
>
> CJ
>
**Update**
I thought I'd experiment a little and use some "raw
latex":
| # Planche
7
| <div
id="cover-image">
| <svg xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" width="100%"
height="100%" viewBox="0 0 900 1200"
preserveAspectRatio="none">
| <image width="900" height="1200" xlink:href="images/planches/pl7.jpg"
/>
|
</svg>
|
</div>
This html snippet below the #h1 markdown title works as expected when I
manaually create the epub: the pl7.jpg image is automatically sized to the
full size of a 4:3 screen (by most ereader
software).
But when I run a "pandoc md/snippet.md -o snippet.epub" command or such the
ensuing epubcheck complains about not finding pl7.jpg in the epub. A quick
look inside the epub reveals that the jpeg image is not referenced in the
EPUB/content.opf (the "manifest", I believe they call it...) and that
pandoc did not
In effect it looks as if pandoc silently ignores the contents of the <image
... />
tag.
Is this the expected
behaviour?
If so what would be the recommended
workaround¹?
Thanks,
CJ
--
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/a0514cc8-560e-40b2-802e-aed2b58930a8o%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 14441 bytes --]
next prev parent reply other threads:[~2020-10-06 22:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-14 22:15 Chris Jones [not found] ` <b49a95c6-772c-43ac-9bc5-0011ed206c38o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2020-10-06 19:50 ` Chris Jones 2020-10-06 22:15 ` Charles Richer Saint-Faure [this message] [not found] ` <a0514cc8-560e-40b2-802e-aed2b58930a8o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2020-10-07 4:45 ` John MacFarlane 2020-10-26 19:06 ` Chris Jones [not found] ` <220286f4-8dab-4a80-9ad6-4794e15f1961o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2020-10-26 21:17 ` John MacFarlane [not found] ` <m27drcoffg.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org> 2020-10-28 18:31 ` cjns...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [not found] ` <04e6652d-6db6-4090-b2f1-db7acc33edd2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> 2020-10-29 0:09 ` John MacFarlane [not found] ` <m25z6tuc4a.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org> 2020-10-29 0:21 ` John MacFarlane [not found] ` <m2zh45swys.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org> 2020-10-31 20:34 ` cjns...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [not found] ` <20201031203402.gutswizwu477rh3y-611mE6nXTcHDOqzlkpFKJg@public.gmane.org> 2020-10-31 22:59 ` John MacFarlane -- strict thread matches above, loose matches on Subject: below -- 2020-06-12 20:00 Chris Jones
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=a0514cc8-560e-40b2-802e-aed2b58930a8o@googlegroups.com \ --to=richer.saint.faure-re5jqeeqqe8avxtiumwx3w@public.gmane.org \ --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).