public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Rudi C <rudiwillalwaysloveyou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How can I create a TOC based on input files?
Date: Sun, 14 Jul 2019 04:17:47 -0700 (PDT)	[thread overview]
Message-ID: <9509e078-b391-49c6-8a60-8066e49f95dc@googlegroups.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]

I use mercury-parser to save web pages as clean HTML. I like to merge some of these pages into a single epub. I currently use this command:
pandoc --toc -s *.html -o fruit2.epub
But this creates an empty toc, as the files themselves don’t have whatever formatting hints pandoc uses to detect sections; I’d like to have a toc based on the input file themselves (each input file = a section). How do I go about achieving that?

-- 
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/9509e078-b391-49c6-8a60-8066e49f95dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

             reply	other threads:[~2019-07-14 11:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14 11:17 Rudi C [this message]
     [not found] ` <9509e078-b391-49c6-8a60-8066e49f95dc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-07-14 15:55   ` 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=9509e078-b391-49c6-8a60-8066e49f95dc@googlegroups.com \
    --to=rudiwillalwaysloveyou-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).