public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "tri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <tridral-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Dealing with non-unique footnote numbers in markdown
Date: Thu, 10 Jun 2021 20:53:39 -0700 (PDT)	[thread overview]
Message-ID: <e2f77b9d-ca57-47eb-9b29-111501019059n@googlegroups.com> (raw)


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

I have a markdown file where the footnote numbers restart for every chapter 
giving me non-unique footnote numbers and therefore warnings when 
processing MD->EPUB

I would like to know whether anyone has a simple method of renumbering the 
footnotes so that they are unique.

I'm using Ubuntu, and what I've done so far is to use 'csplit' to break the 
file into chapters, then 'sed' to find and prefix each footnote and 'cat' 
to append the whole thing back together again. 

Does anyone know of a simpler method for renumbering non-unique footnote 
numbers?

Many thanks for any help.

-- 
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/e2f77b9d-ca57-47eb-9b29-111501019059n%40googlegroups.com.

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

             reply	other threads:[~2021-06-11  3:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHXXnVf46smsnSqsEel1CdN612c0KsOqBiAgAAA0wCAAAF2IA==>
2021-06-11  3:53 ` tri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
     [not found]   ` <b8137dc5720443958f905128953acc55@unibe.ch>
     [not found]     ` <57737b2565d348a0b319e7c186c9e2dd@unibe.ch>
     [not found]       ` <57737b2565d348a0b319e7c186c9e2dd-NSENcxR/0n0@public.gmane.org>
2021-06-11 11:19         ` AW: " denis.maier-NSENcxR/0n0
     [not found]           ` <ca1ea08b7c2b426d988c7588691140f7-NSENcxR/0n0@public.gmane.org>
2021-07-29 14:16             ` tri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org

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=e2f77b9d-ca57-47eb-9b29-111501019059n@googlegroups.com \
    --to=tridral-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).