From: "ivo....-xwz7R8GQi1g@public.gmane.org" <ivo.welch-xwz7R8GQi1g@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: powerpoint output to 169 format?
Date: Sun, 2 Jan 2022 13:37:38 -0800 (PST) [thread overview]
Message-ID: <1ed43dcc-b0ae-469e-a3c1-590b5eea0d33n@googlegroups.com> (raw)
In-Reply-To: <m24k757l6n.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1186 bytes --]
mille grazie.
given that powerpoint itself has moved to 16:9, I think it would probably
be a better default.
the template trick is supercool. I had not realized this. I will try to
stick a modified version into my .pandoc/templates folder. Is there a
standard name (like default.pptx) that pandoc picks up?
On Saturday, December 18, 2021 at 11:44:45 AM UTC-8 John MacFarlane wrote:
>
> You can change this by using a reference-doc.
>
> pandoc --print-default-data-file reference.pptx > reference.pptx
>
> Now open reference.pptx with Powerpoint.
>
> Go to Page Setup and change the aspect ratio.
>
> Save.
>
> Now use
>
> pandoc --reference-doc reference.pptx input.md -o output.pptx
>
> Maybe we should change the default to 16:9. Comments welcome on
> this.
>
--
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/1ed43dcc-b0ae-469e-a3c1-590b5eea0d33n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1868 bytes --]
next prev parent reply other threads:[~2022-01-02 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 16:59 ivo....-xwz7R8GQi1g@public.gmane.org
[not found] ` <e8eca892-c1f2-4209-9934-b679a5d93978n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-18 19:44 ` John MacFarlane
[not found] ` <m24k757l6n.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2022-01-02 21:37 ` ivo....-xwz7R8GQi1g@public.gmane.org [this message]
[not found] ` <1ed43dcc-b0ae-469e-a3c1-590b5eea0d33n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-02 22:01 ` ivo....-xwz7R8GQi1g@public.gmane.org
[not found] ` <94f00f2b-6407-4811-a5fb-250f4858d774n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-02 23:00 ` ivo....-xwz7R8GQi1g@public.gmane.org
[not found] ` <b9f2c295-a355-4bdc-90a7-58cd61694854n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-03 2:30 ` John MacFarlane
[not found] ` <m2fsq51rg0.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-01-03 18:36 ` ivo....-xwz7R8GQi1g@public.gmane.org
[not found] ` <34686c0e-c90a-4d27-82ed-28e950548c04n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-03 18:54 ` John MacFarlane
[not found] ` <m2h7aklkfc.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-01-04 17:34 ` ivo....-xwz7R8GQi1g@public.gmane.org
2022-01-02 22:59 ` John MacFarlane
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=1ed43dcc-b0ae-469e-a3c1-590b5eea0d33n@googlegroups.com \
--to=ivo.welch-xwz7r8gqi1g@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).