From: bruno.grenet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Conversion to LaTeX: --resource-path and \includegraphics
Date: Sun, 12 Feb 2023 17:13:44 +0100 [thread overview]
Message-ID: <bf864ce5-e2ea-d1fc-3876-d6ae62bbe397@gmail.com> (raw)
In-Reply-To: <87k00om2je.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
Thanks, I was unaware of this --extract-media, seems to be what I need!
Best,
Bruno
On 11/02/2023 20:14, Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org> wrote:
> Hello Bruno,
>
> Bruno Grenet <bruno.grenet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > When converting to LaTeX (say from markdown in my case), it seems
> > that the --resource-path option has no effect for \includegraphics
> > commands. Let's assume for instance the following markdown file
> > image.md:
> >
> > An image: ![My image](image.jpg)
> >
> > Then the commands
> >> pandoc image.md -s -o image.tex
> > and
> >> pandoc image.md -s --resource-path=img/ -o image.tex
> > produce the exact same file. It means that if you put image.jpg in
> > the directory img/, the resulting LaTeX file will fail to compile
> > even with the --resource-path option.
>
> The resource path takes effect when pandoc tries to actually grab and
> use the image, e.g. when converting to PDF or docx. You can let pandoc
> collect all images and place them in the target directory by passing
> `--extract-media=.`
>
>
>
prev parent reply other threads:[~2023-02-12 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 9:20 Bruno Grenet
[not found] ` <bca89deb-5e4d-4506-9262-b6b034340b14n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-11 19:14 ` Albert Krewinkel
[not found] ` <87k00om2je.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-02-12 16:13 ` bruno.grenet-Re5JQEeQqe8AvxtiuMwx3w [this message]
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=bf864ce5-e2ea-d1fc-3876-d6ae62bbe397@gmail.com \
--to=bruno.grenet-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: link
Be 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).