From: Ashok Koyi <ashok.koyi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Convention to follow to write frontmatter, body & backmatter of a book in markdown
Date: Mon, 27 Sep 2021 08:09:19 -0700 (PDT) [thread overview]
Message-ID: <85786528-2797-49ee-9643-c131a60ec523n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 998 bytes --]
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 epub
<https://pandoc.org/MANUAL.html#the-epubtype-attribute>, but not for pdf
(I have already posted this question in tex stackexchage forum
<https://tex.stackexchange.com/q/616905/195215>)
--
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/85786528-2797-49ee-9643-c131a60ec523n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1436 bytes --]
next reply other threads:[~2021-09-27 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 15:09 Ashok Koyi [this message]
[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
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=85786528-2797-49ee-9643-c131a60ec523n@googlegroups.com \
--to=ashok.koyi-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).