From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Gabriel Volpe
<volpegabriel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: --epub-chapter-level option for PDF?
Date: Fri, 04 Oct 2019 10:47:57 -0700 [thread overview]
Message-ID: <yh480k1rvsz9ki.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <996131ba-41a3-4aca-b181-72ebe3c9bb4b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
One approach is outlined here:
https://tex.stackexchange.com/questions/153444/insert-newpage-before-section-but-prevent-pagebreak-after-part
Create a file sectionbreaks.tex containing the following:
%%%%
\usepackage{etoolbox}
\newtoggle{afterpart}
\pretocmd{\section}
{\iftoggle{afterpart}
{\global\togglefalse{afterpart}}% we're after a part
{\clearpage}% we're not immediately after a part
}{}{}
\pretocmd{\part}
{\clearpage % do a page break
\global\toggletrue{afterpart}% tell \section we're just after a part
}
{}{}\usepackage{etoolbox}
%%%%
Then call pandoc with -H sectionsbreaks.tex -o whatever.pdf
Gabriel Volpe <volpegabriel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Is there anything like --epub-chapter-level but for PDF outputs?
>
> I really like how I can set up the level in which to split the different
> pages and I would love if I could do the same for PDF.
>
> 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/996131ba-41a3-4aca-b181-72ebe3c9bb4b%40googlegroups.com.
next prev parent reply other threads:[~2019-10-04 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 4:18 Gabriel Volpe
[not found] ` <996131ba-41a3-4aca-b181-72ebe3c9bb4b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-04 17:47 ` John MacFarlane [this message]
[not found] ` <yh480k1rvsz9ki.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-10-05 0:31 ` Gabriel Volpe
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=yh480k1rvsz9ki.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=volpegabriel-Re5JQEeQqe8AvxtiuMwx3w@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).