public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos-S0/GAf8tV78@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: filter for ePub footnotes
Date: Fri, 25 Aug 2017 19:40:22 +0200	[thread overview]
Message-ID: <e2accbab-d880-3232-4c39-1e1ad3d4d9a1@web.de> (raw)
In-Reply-To: <7d399a63-4157-0898-c88d-23a9d85c45de-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 08/25/2017 07:06 PM, BP Jonsson wrote:
> Den 2017-08-23 kl. 16:17, skrev John MacFarlane:
>> What you want isn't a filter, since the footnote marker is
>> only created by the writer.
> 
> I once wrote a filter which intercepted all notes and replaced 
> them with a note reference with a link to a div somewhere else in 
> the document which contained the note text, in an item of an 
> ordered list, with a link back to the note reference,
> i.e. essentially the kind of structure which the HTML writer 
> creates for links, except that you could put placeholder 
> paragraphs anywhere in the document which were replaced with a div 
> containing a list with the text of all notes since the last 
> placeholder, which allowed me to put notes at the end of sections,
> and to 'localize' notes in a table with the note texts below the 
> table and the notes numbered alphabetically rather than with 
> 'arabic' numbers. There were no Note objects at all in the JSON 
> returned to the writer. It could easily be adapted to use Unicode 
> superscripts if desired.

I’d be extremely interested in that filter.

I must admit that I don’t understand everything. But if I can place the
div with the all the notes text right after a  #footnotes element, this
would be really awesome.

Many thanks for your help,

Pablo
-- 
http://www.ousia.tk

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e2accbab-d880-3232-4c39-1e1ad3d4d9a1%40web.de.
For more options, visit https://groups.google.com/d/optout.


      parent reply	other threads:[~2017-08-25 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 14:08 Pablo Rodríguez
     [not found] ` <2665838a-f621-7d7d-8646-de7f780f4121-S0/GAf8tV78@public.gmane.org>
2017-08-23 14:17   ` John MacFarlane
     [not found]     ` <20170823141730.GC22331-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-23 14:35       ` Pablo Rodríguez
     [not found]         ` <8adc9ebe-b391-209e-29c6-a831438b8468-S0/GAf8tV78@public.gmane.org>
2017-08-23 16:01           ` Jan Ulrich Hasecke
     [not found]             ` <6b2c8ffe-418c-d7b2-7ea2-dbe8d93deb04-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2017-08-23 22:04               ` Pablo Rodríguez
2017-08-25 17:06       ` BP Jonsson
     [not found]         ` <7d399a63-4157-0898-c88d-23a9d85c45de-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-25 17:40           ` Pablo Rodríguez [this message]

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=e2accbab-d880-3232-4c39-1e1ad3d4d9a1@web.de \
    --to=oinos-s0/gaf8tv78@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).