public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Convention to follow to write frontmatter, body & backmatter of a book in markdown
Date: Wed, 13 Oct 2021 13:37:58 +0000	[thread overview]
Message-ID: <YWbhNs8G28oLFOYW@localhost> (raw)
In-Reply-To: <08c9532e-5688-4beb-aefd-e99999569d0cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Have you tried inserting \frontmatter, \mainmatter and \backmatter in the right places in your markdown document?

Le Wednesday 13 October 2021 à 06:23:19AM, Ashok Koyi a écrit :
> This looks like a pretty common requirement. Did anyone try this?
> 
> On Monday, September 27, 2021 at 8:39:20 PM UTC+5:30 Ashok Koyi wrote:
> 
>     I am writing a book in markdown & use pandoc to convert the book to pdf &
>     epub
> 
>     Is there a way to specify in the markdown document that a given section (`#
>     Preface`/`# Dedication`) belongs to `frontmatter` & `# Appendix` belongs to
>     the `backmatter`?
> 
>     Please note that I want to write `frontmatter`, `backmatter` & `mainmatter`
>     all in markdown
> 
>     PS: In the documentation, I see an option for [1]epub, but not for pdf
> 
>     (I have already posted this question in [2]tex stackexchage forum)
> 
> --
> 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 [3]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [4]https://groups.google.com/d/msgid/
> pandoc-discuss/08c9532e-5688-4beb-aefd-e99999569d0cn%40googlegroups.com.
> 
> References:
> 
> [1] https://pandoc.org/MANUAL.html#the-epubtype-attribute
> [2] https://tex.stackexchange.com/q/616905/195215
> [3] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [4] https://groups.google.com/d/msgid/pandoc-discuss/08c9532e-5688-4beb-aefd-e99999569d0cn%40googlegroups.com?utm_medium=email&utm_source=footer

-- 
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/YWbhNs8G28oLFOYW%40localhost.


  parent reply	other threads:[~2021-10-13 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 15:09 Ashok Koyi
     [not found] ` <85786528-2797-49ee-9643-c131a60ec523n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-10-13 13:23   ` Ashok Koyi
     [not found]     ` <08c9532e-5688-4beb-aefd-e99999569d0cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-10-13 13:37       ` Bastien DUMONT [this message]
2021-10-14  8:10         ` AW: " denis.maier-NSENcxR/0n0

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=YWbhNs8G28oLFOYW@localhost \
    --to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).