public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Elias S <elias.storms-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Problem with footnotes in OrgMode
Date: Wed, 11 Oct 2017 01:30:44 -0700 (PDT)	[thread overview]
Message-ID: <d53cdef3-9040-411c-b367-6e637a1dff55@googlegroups.com> (raw)
In-Reply-To: <87efqd4yyr.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


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

Many thanks for your swift response. I'm glad to hear that you are working 
on it.

For others looking for an intermediate solution: I move all my footnotes 
down so that they appear just above a header. Pandoc does recognize that 
footnotes end at a header, so this works fine. Me personally, I like to 
keep my footnotes close to the paragraphs, so I'm looking forward to a real 
fix.

Best
Elias


On Sunday, 8 October 2017 14:16:57 UTC+2, Albert Krewinkel wrote:
>
> Hello Elias, 
>
> Elias S <elias....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes: 
>
> > According to the Org Manual, a footnote definition ends after two 
> > consecutive empty lines. Pandoc doesn't seem to respect this. 
>
> Indeed, this is a bug; thank you for reporting it! 
> I'm working on a fix. 
>
> Best, 
> Albert 
>

-- 
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/d53cdef3-9040-411c-b367-6e637a1dff55%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  parent reply	other threads:[~2017-10-11  8:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-07 14:49 Elias S
     [not found] ` <8f86db36-4b8b-457e-bd48-542b3a016ff1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-07 15:01   ` Elias S
2017-10-08 12:14   ` Albert Krewinkel
     [not found]     ` <87efqd4yyr.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2017-10-11  8:30       ` Elias S [this message]
2018-10-05 11:54       ` Dan
     [not found]         ` <26dacaa0-c520-44bd-8de3-c5edde9b5bb5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-10-05 16:41           ` Albert Krewinkel
     [not found]             ` <5597E075-8BC5-497F-B7DF-5E6CCE2B5C05-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2018-10-08 10:40               ` Dan
     [not found]                 ` <8de2707c-7e44-49a4-8664-9058c026f77a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-10-09 18:16                   ` Albert Krewinkel
     [not found]                     ` <87tvlvq92u.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2019-02-13 11:50                       ` Dan Elbro

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=d53cdef3-9040-411c-b367-6e637a1dff55@googlegroups.com \
    --to=elias.storms-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).