public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Ghislain Vaillant <ghisvail-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: how to force pagebreaks
Date: Tue, 17 Sep 2019 06:47:29 -0700 (PDT)	[thread overview]
Message-ID: <26ece219-65a0-46ba-b10b-d3d8a7350c07@googlegroups.com> (raw)
In-Reply-To: <5c11e555-df2d-2a01-af29-9bdb7bf67c84-Jdbf3xiKgS8@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1144 bytes --]



Le vendredi 13 septembre 2019 21:14:32 UTC+2, Daniel Staal a écrit :
>
> On 9/13/19 3:04 PM, Don Raikes wrote: 
> > Hello, 
> > 
> > I am just getting started on my first pandoc project. I am breaking my 
> > project into multiple markdown files each of which starts with a level-2 
> > header “##”. 
> > 
> > How do I tell pandoc to force page breaks at each level-2 header? 
> > 
>
> What's your output format?  Markdown has no idea of 'pages', so a page 
> break in markdown doesn't really mean anything.
>

For instance, assuming your target format is docx, you can add:

```{=openxml}
<w:p><w:r><w:br w:type="page"/></w:r></w:p>
```

wherever a page break is needed in the Markdown document.

-- 
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/26ece219-65a0-46ba-b10b-d3d8a7350c07%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2116 bytes --]

  parent reply	other threads:[~2019-09-17 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13 19:04 Don Raikes
2019-09-13 19:14 ` Daniel Staal
     [not found]   ` <5c11e555-df2d-2a01-af29-9bdb7bf67c84-Jdbf3xiKgS8@public.gmane.org>
2019-09-17 13:47     ` Ghislain Vaillant [this message]
     [not found]       ` <26ece219-65a0-46ba-b10b-d3d8a7350c07-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-25  8:01         ` Agustín Martín
2019-09-13 19:29 ` BP Jonsson
2020-02-05 14:18 ` Ignacio Jonatan Hernández López

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=26ece219-65a0-46ba-b10b-d3d8a7350c07@googlegroups.com \
    --to=ghisvail-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).