From: CR <chuckr69-Wuw85uim5zDR7s880joybQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Pandoc creates new XHTML file in EPUB for every 1st level header, can we have option not to do this?
Date: Mon, 3 Jul 2017 08:37:36 -0700 (PDT) [thread overview]
Message-ID: <b4c70384-32a5-447b-a559-1209a4db27d8@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1140 bytes --]
- Pandoc 1.19.2.1 on Windows 8
- I'm making an EPUB book from multiple markdown file, which are
02intro.md, 10stuff.md, and 20stuff.md.
- Command line: pandoc -o %outname% -f markdown_mmd -t epub 02intro.md
10stuff.md 20stuff.md
In 10stuff.md there are multiple instances of header level 1 formatted like
"# header 1". Each time Pandoc finds this it creates a new XHTML file
inside the EPUB file. Is there an option to not do this? I only want to
create a new XHTML file inside the EPUB if a new markdown file is found by
Pandoc.
Thanks!
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b4c70384-32a5-447b-a559-1209a4db27d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1579 bytes --]
next reply other threads:[~2017-07-03 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 15:37 CR [this message]
[not found] ` <b4c70384-32a5-447b-a559-1209a4db27d8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-04 9:15 ` John MacFarlane
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=b4c70384-32a5-447b-a559-1209a4db27d8@googlegroups.com \
--to=chuckr69-wuw85uim5zdr7s880joybq@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).