public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Ignacio Jonatan Hernández López" <ijoni.hl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: how to force pagebreaks
Date: Wed, 5 Feb 2020 06:18:12 -0800 (PST)	[thread overview]
Message-ID: <f93c5149-bdf9-476d-8d8f-3d0206efd776@googlegroups.com> (raw)
In-Reply-To: <4fadd2ef-820b-4dc9-b7b7-97aab7232543@default>


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

Use --epub-chapter-level=2

El viernes, 13 de septiembre de 2019, 21:04:55 (UTC+2), Don Raikes escribió:
>
> 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?
>
>  
>
> -- 
> Thanks, Donald 
>
> “As a leader, to be successful, is to help the people around you to be 
> successful.” – Kent Boucher
>
>  
>
> Accessibility, like security, is better when built-in from the beginning 
> rather than bolted on at the end.
>
>
> [image: Oracle] <http://www.oracle.com/>
> Donald Raikes | Accessibility Specialist
> Mobile: +15202717608 | VOIP: +15205744033 
> Oracle Accessibility Program Office
> | Tucson, Arizona 
>
> [image: Green Oracle] <http://www.oracle.com/commitment>
>
> Oracle is committed to developing practices and products that help protect 
> the environment
>
>  
>

-- 
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/f93c5149-bdf9-476d-8d8f-3d0206efd776%40googlegroups.com.

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

      parent reply	other threads:[~2020-02-05 14:18 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
     [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 [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=f93c5149-bdf9-476d-8d8f-3d0206efd776@googlegroups.com \
    --to=ijoni.hl-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).