From: Bruno Grenet <bruno.grenet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Conversion to LaTeX: --resource-path and \includegraphics
Date: Fri, 10 Feb 2023 01:20:45 -0800 (PST) [thread overview]
Message-ID: <bca89deb-5e4d-4506-9262-b6b034340b14n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1458 bytes --]
Dear all,
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.
I can see two solutions:
1. Produce a \graphicspath{{img/}} command when --resource-path is used;
2. Modify each \includegraphics to add the full path.
I expect the first one to be good in standalone document while the second
better for non-standalone ones. And the first one is probably usable with
multiple paths in option while the second is not.
My questions: It the current behavior the intended behavior for some reason
I do not understand? Is any of my solutions desirable?
Thanks!
--
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/bca89deb-5e4d-4506-9262-b6b034340b14n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2045 bytes --]
next reply other threads:[~2023-02-10 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 9:20 Bruno Grenet [this message]
[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
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=bca89deb-5e4d-4506-9262-b6b034340b14n@googlegroups.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).