From: Gary Glass <garyglassphotography-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: setting css forces section numbering
Date: Sun, 1 Nov 2020 15:52:14 -0800 (PST) [thread overview]
Message-ID: <f36b6975-40e7-4ec8-ad2e-9d6e92b89a23o@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 980 bytes --]
I'm converting markdown files to an epub. I use a yaml file to set up the
options. I discovered that if I set a css value, TOC items will be
numbered, even if number-sections is false. Is this a bug or am I missing
something? Is my yaml:
from: commonmark+pipe_tables+smart
to: epub3
log-file: pandoc.log
wrap: none
metadata-files:
- meta.yaml
epub-metadata: meta.xml
resource-path:
- resources
css:
- ..\mss\swan.css
epub-chapter-level: 3
table-of-contents: true
number-sections: false
input-files:
- ..\mss\000 Main Front Matter\004 Illustrations.md
...
--
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/f36b6975-40e7-4ec8-ad2e-9d6e92b89a23o%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2569 bytes --]
next reply other threads:[~2020-11-01 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 23:52 Gary Glass [this message]
[not found] ` <f36b6975-40e7-4ec8-ad2e-9d6e92b89a23o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-02 19:01 ` John MacFarlane
[not found] ` <m25z6nmvl0.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-05 14:23 ` 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=f36b6975-40e7-4ec8-ad2e-9d6e92b89a23o@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).