From: Axel Rauschmayer <rauschma-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Specify two separate paths for --extract-media?
Date: Wed, 1 Aug 2018 10:17:19 -0700 (PDT) [thread overview]
Message-ID: <0c48e6e1-3fcd-4a72-a61b-166e6213a32c@googlegroups.com> (raw)
In-Reply-To: <m2h8kgy4l7.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1194 bytes --]
Alas, I spoke to soon: I need to be in the same directory as the content,
so that \includepdf{} works with relative paths. That is also a work-around
– for that command not handling spaces (in the latest version of XeLaTeX –
it did before, see (*)). And spaces in the path are something I can’t
change at the moment.
I think I’ll stick with my original approach: choose a long unique name for
the extracted media directory and then search-and-replace in the produced
HTML output and copying the original directory into the build location.
(*) https://github.com/ho-tex/oberdiek/issues/31
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/0c48e6e1-3fcd-4a72-a61b-166e6213a32c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1675 bytes --]
prev parent reply other threads:[~2018-08-01 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 13:39 Axel Rauschmayer
[not found] ` <2a6f3744-e2a7-4423-bb7c-ec83ddb3133f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-07-30 18:13 ` John MacFarlane
[not found] ` <m2h8kgy4l7.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-07-30 19:55 ` Axel Rauschmayer
2018-08-01 17:17 ` Axel Rauschmayer [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=0c48e6e1-3fcd-4a72-a61b-166e6213a32c@googlegroups.com \
--to=rauschma-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).