From: Craig Parker <craig.fossfolks-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Large Document
Date: Thu, 6 Oct 2022 10:24:40 -0700 (PDT) [thread overview]
Message-ID: <6eb43189-eb50-416c-8f30-d2baf1dee459n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1260 bytes --]
I'm trying to document ALL of a piece of software's uses/features/etc. I
was wondering if there's a way to do each one individually, then merge them
in the end. I was hoping to just do one big doc, but really want section
title pages. I am running:
pandoc -s --template="templates/default.html" -f markdown-smart --toc -c
./style-landscape.css "$n.md" -o "./$n.html"
python3 -m weasyprint "./$n.html" "./$n.pdf"
on the individual markdown files, but then the page numbers don't match up
when I join them all together in the end. I'm not sure where to start
looking, so that H1 still behaves the way it does, but so that H2 also
creates kind of a title page, and the other headings get bumped down a peg
(so H3 acts like H2 does now, etc.)
I'm also not exactly crystal clear about how much of this is pandoc and how
much is Weasyprint...
--
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/6eb43189-eb50-416c-8f30-d2baf1dee459n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1557 bytes --]
next reply other threads:[~2022-10-06 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 17:24 Craig Parker [this message]
[not found] ` <6eb43189-eb50-416c-8f30-d2baf1dee459n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-06 18:00 ` John MacFarlane
[not found] ` <2CBF2CCD-5F52-4719-B899-5BD72D120D04-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-11 15:52 ` Craig Parker
[not found] ` <4e3502ac-01bd-424f-9597-0e790f81f537n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-11 22:37 ` John MacFarlane
[not found] ` <C62D6A20-D362-4B4D-97C0-B5DC08CFA65B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-11-11 22:41 ` Craig Parker
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=6eb43189-eb50-416c-8f30-d2baf1dee459n@googlegroups.com \
--to=craig.fossfolks-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).