public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Sean Evans <daigidan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Can't make gfm_auto_identifiers work
Date: Thu, 24 Sep 2020 20:44:37 -0700 (PDT)	[thread overview]
Message-ID: <d7cdce51-3057-406d-a2d5-265ca08f3877n@googlegroups.com> (raw)


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


Howdy,

I am attempting to convert from docx to GFM, but seem to be missing 
something about how to enable gfm_auto_identifiers correctly. I have 
headers with periods in them (eg - "Step 1. Do This"), and the identifiers 
that get constructed for the TOC still contain these periods. This is the 
command I'm using:

$ pandoc -f docx -t gfm+gfm_auto_identifiers --toc -s SomeFile.docx -o 
SomeOtherFile.md

This results in TOC entries like: "[Step 1. Do This](#step-1.-do-this)"

Any ideas what I'm doing wrong?

Thanks,
Sean


-- 
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/d7cdce51-3057-406d-a2d5-265ca08f3877n%40googlegroups.com.

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

             reply	other threads:[~2020-09-25  3:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  3:44 Sean Evans [this message]
     [not found] ` <d7cdce51-3057-406d-a2d5-265ca08f3877n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-25 16:39   ` John MacFarlane
     [not found]     ` <m2pn69zu83.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-25 16:54       ` John MacFarlane

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=d7cdce51-3057-406d-a2d5-265ca08f3877n@googlegroups.com \
    --to=daigidan-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).