From: Craig Parker <craig.fossfolks-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Large Document
Date: Fri, 11 Nov 2022 07:52:20 -0800 (PST) [thread overview]
Message-ID: <4e3502ac-01bd-424f-9597-0e790f81f537n@googlegroups.com> (raw)
In-Reply-To: <2CBF2CCD-5F52-4719-B899-5BD72D120D04-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 3307 bytes --]
The plot thickens... I want to be able to make just one md into a pdf, and
but also merge a bunch (two different scripts), but I'm having a problem
with the TOC. TOC.md looks like this:
```
---
title: Wicked Awesome Title Here
subtitle: A catchy subtitle...
author: Me
email:
date:
---
```
I can call it with pandoc --toc TOC.md file1.md -o file.html
This is fine if I want one big merged file, but if I want to just make a
single one, then I have to have another TOC file (TOC-file1.md, for
example).
Yesterday I discovered that if I knocked the subtitle line out and just put
that in file1.md:
```
subtitle: A catchy subtitle...
```
I could call the same table of contents whether I was making one single
section file, or one big merged one.
Today I found out that it doesn't work when I'm doing multiple files.
But wait... While I was typing this, it appears that as long as all of the
individual files have a heading that is seven lines long and includes the
subtitle, I can either make a single small file or a large merged one. Is
the expected behavior? The header for doing this needs to be seven lines
long to work right?
On Thursday, October 6, 2022 at 2:00:52 PM UTC-4 fiddlosopher wrote:
> You can just put all of the markdown files (in order) on the command line,
> and pandoc will concatenate them before converting.
>
> pandoc --toc part1.md part2.md part3.md -t html --pdf-engine=weasyprint -o
> wholething.pdf
>
> > On Oct 6, 2022, at 10:24 AM, Craig Parker <craig.f...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> > 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-discus...-/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
> .
>
>
--
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/4e3502ac-01bd-424f-9597-0e790f81f537n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4629 bytes --]
next prev parent reply other threads:[~2022-11-11 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 17:24 Craig Parker
[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 [this message]
[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=4e3502ac-01bd-424f-9597-0e790f81f537n@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).