From: <denis.maier-NSENcxR/0n0@public.gmane.org>
To: <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: AW: Pandoc convention to follow to write frontmatter, body & backmatter of a book in markdown
Date: Tue, 28 Sep 2021 07:42:43 +0000 [thread overview]
Message-ID: <85025fff8fb94d74adfc79fc90c8653c@unibe.ch> (raw)
In-Reply-To: <792a6eb6-14cf-4549-ab91-5679fb96c93fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]
You can always use raw tex for these things.
https://pandoc.org/MANUAL.html#extension-raw_tex
Or, you can use a filter which is maybe too much for this case.
Von: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> Im Auftrag von Ashok Koyi
Gesendet: Montag, 27. September 2021 17:07
An: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Betreff: Pandoc convention to follow to write frontmatter, body & backmatter of a book in markdown
I am writing a book in markdown & use pandoc to convert the book to pdf (pandoc internally uses pdflatex/xelatex/lualatex) & 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 & mainbody 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org<mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/792a6eb6-14cf-4549-ab91-5679fb96c93fn%40googlegroups.com<https://groups.google.com/d/msgid/pandoc-discuss/792a6eb6-14cf-4549-ab91-5679fb96c93fn%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/85025fff8fb94d74adfc79fc90c8653c%40unibe.ch.
[-- Attachment #2: Type: text/html, Size: 5361 bytes --]
prev parent reply other threads:[~2021-09-28 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 15:06 Ashok Koyi
[not found] ` <792a6eb6-14cf-4549-ab91-5679fb96c93fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-28 7:42 ` denis.maier-NSENcxR/0n0 [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=85025fff8fb94d74adfc79fc90c8653c@unibe.ch \
--to=denis.maier-nsencxr/0n0@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).