From: Gary Glass <garyglassphotography-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: how do files and pagebreaks work?
Date: Thu, 8 Dec 2022 00:28:55 -0800 (PST) [thread overview]
Message-ID: <9a572064-0b5a-4cc0-8eb7-493feade9106n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]
I'm converting from markdown to epub. I'm trying to understand how Pandoc
decides when to make a pagebreak. Here's the bit that has me confused:
I had a large markdown file, that I broke up into 5 smaller files. There is
one h3 header and 10 h4 headers. What I expected was that in the epub
either the different source files or the different header sections would be
emitted as separate xhtml files. What I have tho is that all 5 files are
combined into one xhtml. I made a test doc with the same structure and got
separate files for each header section. I can't figure out why I get
different results. Any ideas what I could look for?
The 5 files look like this:
1. file 1
### h3 header
text
#### h4 header 1
text
#### h4 header 2
text
2. file 2
#### h4 header 3
text
#### h4 header 4
text
3. file 3
#### h4 header 5
text
#### h4 header 6
text
4. file 4
#### h4 header 7
text
#### h4 header 8
text
5. file 5
#### h4 header 9
text
#### h4 header 10
text
--
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/9a572064-0b5a-4cc0-8eb7-493feade9106n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4432 bytes --]
next reply other threads:[~2022-12-08 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 8:28 Gary Glass [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-08 8:25 Gary Glass
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=9a572064-0b5a-4cc0-8eb7-493feade9106n@googlegroups.com \
--to=garyglassphotography-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).