public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Mattia Tezzele <zool.bib-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Is --section-divs activated by default and is there a way to turn it off?
Date: Thu, 2 Jun 2022 01:50:03 -0700 (PDT)	[thread overview]
Message-ID: <c1f56919-e2c9-47fb-99e5-1f0cedfe9181n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1034 bytes --]

Hi everyone,

I'm converting from docx to HTML and in my output all my sections get 
wrapped in <section> tags, even if I didn't specify --section-divs in my 
command. This somehow breaks the spacing before headings with the CSS I'm 
using (which I have no way to modify).

Is there a way to turn --section-divs off explicitly? I 
tried --section-divs=false but I'm getting "option `--section-divs' doesn't 
allow an argument".

This is the command I'm using:

pandoc document.docx -t html --number-sections --number-offset=1 
--shift-heading-level-by=1

Grateful for any pointer.

Best,

–Matt

-- 
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/c1f56919-e2c9-47fb-99e5-1f0cedfe9181n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1411 bytes --]

             reply	other threads:[~2022-06-02  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  8:50 Mattia Tezzele [this message]
     [not found] ` <c1f56919-e2c9-47fb-99e5-1f0cedfe9181n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-02  9:26   ` Albert Krewinkel
     [not found]     ` <8735gn5rdn.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-02 11:31       ` Mattia Tezzele

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=c1f56919-e2c9-47fb-99e5-1f0cedfe9181n@googlegroups.com \
    --to=zool.bib-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).