From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: TOC indentation with multiple headers in one file
Date: Fri, 13 Oct 2023 07:52:04 -0700 [thread overview]
Message-ID: <FDF85629-458A-4651-B074-7A7644824048@gmail.com> (raw)
In-Reply-To: <fbd55d8c-e37b-4a7b-88f9-727688219248n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Using just this file, I can't reproduce the issue on my ebook reader.
Perhaps it's an issue with your reader? If you post a complete epub we could take a look.
> On Oct 13, 2023, at 2:40 AM, Gary Glass <garyglassphotography-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Here's a thing I didn't expect. My documents include a few files that have more than one heading in the same file:
>
> ```md
> ### heading 1a
>
> blah blah blah
>
> ### heading 1b
>
> blah blah blah
> ```
>
> I compile from markdown to epub. In the epub TOC I see this:
>
> ```
> - headering 1a
> - heading 1b
> ```
>
> Why is "heading 1b" indented? I would expect them to be at the same level, since they're both h3 headers.
>
> --
> 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/fbd55d8c-e37b-4a7b-88f9-727688219248n%40googlegroups.com.
next prev parent reply other threads:[~2023-10-13 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 9:40 Gary Glass
[not found] ` <fbd55d8c-e37b-4a7b-88f9-727688219248n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-13 14:52 ` John MacFarlane [this message]
[not found] ` <FDF85629-458A-4651-B074-7A7644824048-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-10-13 17:09 ` 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=FDF85629-458A-4651-B074-7A7644824048@gmail.com \
--to=fiddlosopher-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).