public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Martin Post
	<martinpostberlin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Multiple HTML files (split at H1 or H2 level) from one source?
Date: Tue, 16 Apr 2019 21:39:44 -0700	[thread overview]
Message-ID: <m28sw91bzj.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <5749e9e9-205c-4b67-9dd1-f5e37d4d891f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Martin Post <martinpostberlin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> I think a generic chapters features would be great. I am writing and 
> translating product manuals. Being able to convert the same source file to 
> a printable PDF and web-friendly short chapters (or knowledge base 
> articles) would make Pandoc the perfect single source publishing solution 
> for the rest of us.
>
> (And while I’m dreaming: a separate TOC file and “Previous” / “Next” links 
> at the end of each chapter would complete the picture. :)

Have you considered using pandoc to produce docbook or
texinfo, then using docbook or texinfo tools to
produce chaptered HTML?

Here's an example from pandoc's online demos, going
pandoc -> texinfo -> chunked HTML:

http://pandoc.org/demo/example19/

Commands:

pandoc MANUAL.txt -s -o example19.texi
makeinfo --no-validate --force example19.texi --html -o example19

-- 
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/m28sw91bzj.fsf%40johnmacfarlane.net.
For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2019-04-17  4:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13 22:24 Martin Post
     [not found] ` <caeb876c-6393-45d6-92b5-e7f3bee17f49-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-04-14  9:59   ` Albert Krewinkel
     [not found]     ` <87o958c3fm.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2019-04-14 19:54       ` Martin Post
2019-04-15 15:44   ` John MacFarlane
     [not found]     ` <m21s232ryh.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-04-15 15:55       ` Alexander Krotov
     [not found]         ` <319987c6-f761-841f-3c98-47f56b0993cb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-15 15:58           ` John MacFarlane
     [not found]             ` <m2pnpn1crg.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-04-16 20:44               ` Martin Post
     [not found]                 ` <5749e9e9-205c-4b67-9dd1-f5e37d4d891f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-04-17  4:39                   ` John MacFarlane [this message]
     [not found]                     ` <m28sw91bzj.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-04-17  8:28                       ` Martin Post
2019-04-18 15:54                   ` BP Jonsson
     [not found]                     ` <a5eac512-0951-2b0c-c2fc-a9239bc3c553-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-20  9:18                       ` Martin Post
2019-04-19 20:05                   ` John Gabriele
     [not found]                     ` <3bcc67bf-59a4-49ad-9a0a-ec5e6a39f7b3-jFIJ+Wc5/Vo7lZ9V/NTDHw@public.gmane.org>
2019-04-20  9:46                       ` Martin Post

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=m28sw91bzj.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=martinpostberlin-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).