From: Luis Rivera <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: wkhtmltopdf options
Date: Wed, 21 Sep 2022 15:25:13 -0500 [thread overview]
Message-ID: <CAOEhWT0YiUzFbcUoXJG6VQrUP0duXbJKRcEMQuuXSLw80Vm=+w@mail.gmail.com> (raw)
In-Reply-To: <CAEe_xxjr6GO3hwffXP=_0=idFOETtW4O0CicKiQXB0t-ZzNMrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Il giorno mer 21 set 2022 alle ore 10:17 William Lupton
<wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org> ha scritto:
>
> I think you have to use a separate --pdf-engine-opt for each word, e.g., this works for me on my Mac:
>
> pandoc -o simple.pdf --pdf-engine wkhtmltopdf simple.md --pdf-engine-opt=--footer-center --pdf-engine-opt=[page]
>
Indeed, this is the case: I arrived at the same conclusion after
examining the output of
pandoc --verbose -o simple.pdf --pdf-engine wkhtmltopdf simple.md
--pdf-engine-opt=--footer-center --pdf-engine-opt=[page]
before reading your reply, which in fact served as confirmation from a Mac user.
> PS, You might hope that this would work, but I guess wkhtmltopdf doesn't support equals signs between the option name and its value.
>
> pandoc -o simple.pdf --pdf-engine wkhtmltopdf simple.md --pdf-engine-opt=--footer-center=[page]
>
Again, indeed, this is the case.
I suggest putting this information right in the corresponding place in
the user's manual.
Cheers!
prev parent reply other threads:[~2022-09-21 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 14:55 jlr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <90439113-3c05-40bf-8748-6363d4178f76n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-21 15:17 ` William Lupton
[not found] ` <CAEe_xxjr6GO3hwffXP=_0=idFOETtW4O0CicKiQXB0t-ZzNMrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-21 20:25 ` Luis Rivera [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='CAOEhWT0YiUzFbcUoXJG6VQrUP0duXbJKRcEMQuuXSLw80Vm=+w@mail.gmail.com' \
--to=jlrn77-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).