From: <denis.maier-NSENcxR/0n0@public.gmane.org>
To: <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: AW: is Pandoc to uniform PDF paper sizes
Date: Wed, 22 Jun 2022 15:01:43 +0000 [thread overview]
Message-ID: <27e3b225b4eb4e749647e2d48125cbca@unibe.ch> (raw)
In-Reply-To: <9f287bc9-2c22-427a-a740-5d99767b2ea5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]
That depends on how you produce your PDF. Assuming you use LaTeX, have a look at https://pandoc.org/MANUAL.html#variables-for-latex
Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> Im Auftrag von almaghfuur lahu
Gesendet: Mittwoch, 22. Juni 2022 16:51
An: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Betreff: is Pandoc to uniform PDF paper sizes
Pandoc is capable of working to uniform all PDF paper sizes isn't it
How's its command syntax such for usage ?
--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/9f287bc9-2c22-427a-a740-5d99767b2ea5n%40googlegroups.com<https://groups.google.com/d/msgid/pandoc-discuss/9f287bc9-2c22-427a-a740-5d99767b2ea5n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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/27e3b225b4eb4e749647e2d48125cbca%40unibe.ch.
[-- Attachment #2: Type: text/html, Size: 4171 bytes --]
next prev parent reply other threads:[~2022-06-22 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHYhkeBLinvswo9rE2hsj+F3RX0Ha1bhO7g>
2022-06-22 14:51 ` almaghfuur lahu
[not found] ` <9f287bc9-2c22-427a-a740-5d99767b2ea5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-22 15:01 ` denis.maier-NSENcxR/0n0 [this message]
[not found] ` <27e3b225b4eb4e749647e2d48125cbca-NSENcxR/0n0@public.gmane.org>
2022-06-22 23:07 ` almaghfuur lahu
[not found] ` <686ce57d-84aa-4dd5-8e40-e7d6ce79e091n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-01 10:17 ` AW: " denis.maier-NSENcxR/0n0
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=27e3b225b4eb4e749647e2d48125cbca@unibe.ch \
--to=denis.maier-nsencxr/0n0@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).