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: Possible Pandoc development - Inline footnote output format for markdown
Date: Sat, 21 Oct 2023 02:13:30 -0700 (PDT)	[thread overview]
Message-ID: <280d8b25-dbf8-4fab-b096-e5d6dc5342fcn@googlegroups.com> (raw)


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

Pandoc can read both Markdown reference footnotes and inline footnotes, but 
is only able to write reference footnotes when producing a Markdown file.

Is it possible to enable Pandoc to write inline footnotes in Markdown?

Last year i received help in converting reference footnotes to inline 
footnotes from Christophe Demko, who produced a combination of a Lua filter 
and sed editor code which enabled me to convert reference footnotes to 
inline.  I'm very grateful to Christophe for this facility.

(See https://groups.google.com/g/pandoc-discuss/c/_5-8TRJhhqo/m/NDvoWc-XAQAJ
)

I would like to know whether it would be possible for Pandoc to directly 
support the writing of inline footnotes. Could this be a future development?

Many thanks,

'ö-Dzin





-- 
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/280d8b25-dbf8-4fab-b096-e5d6dc5342fcn%40googlegroups.com.

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

             reply	other threads:[~2023-10-21  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21  9:13 tri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
     [not found] ` <280d8b25-dbf8-4fab-b096-e5d6dc5342fcn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-21 16:57   ` John MacFarlane
     [not found]     ` <D3C797FF-7075-4D22-9F3D-04F2EFD79756-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-10-24 14:41       ` 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=280d8b25-dbf8-4fab-b096-e5d6dc5342fcn@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).