From: Jeff Milton <jeff.milton-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: A couple of newbie questions
Date: Fri, 13 Sep 2019 04:09:12 -0400 [thread overview]
Message-ID: <CAEAbEdkCa9GyWWhe711zQFuYii7jTzMmXO3t+tRMWVF3U=-yCA@mail.gmail.com> (raw)
In-Reply-To: <98ac4921-3537-4189-8e98-7dfec2397102@default>
[-- Attachment #1: Type: text/plain, Size: 2546 bytes --]
I am also a newbie, so there may be a better answer than this, but if you
add "--top-level-division=chapter" as an argument on the command line it
will force a page break before every H1 element.
On Thu, Sep 12, 2019 at 1:23 PM Don Raikes <DON.RAIKES-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> wrote:
> Hello,
>
>
>
> I am starting to work on my first pandoc project. I am creating both a pdf
> and Microsoft word docx file from my markdown files (in the process of
> creating a book).
>
>
>
> I have two basic questions:
>
>
>
> 1. How can I format a cover page that includes just the
> title, author, and date the pdf//docx was generated?
>
> 2. How do I force pagebreaks between sections of the book?
> For example after the overview and before chapter 1.
>
> Any tips examples would be greatly appreciated.
>
>
>
>
>
> --
> 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/98ac4921-3537-4189-8e98-7dfec2397102%40default
> <https://groups.google.com/d/msgid/pandoc-discuss/98ac4921-3537-4189-8e98-7dfec2397102%40default?utm_medium=email&utm_source=footer>
> .
>
--
Jeff Milton: 212.388.9622
--
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/CAEAbEdkCa9GyWWhe711zQFuYii7jTzMmXO3t%2BtRMWVF3U%3D-yCA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 6673 bytes --]
next prev parent reply other threads:[~2019-09-13 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 17:22 Don Raikes
2019-09-13 8:09 ` Jeff Milton [this message]
2019-09-13 13:14 ` Agustín Martín
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='CAEAbEdkCa9GyWWhe711zQFuYii7jTzMmXO3t+tRMWVF3U=-yCA@mail.gmail.com' \
--to=jeff.milton-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).