From: Bastien <bastien.guerry@wikimedia.fr>
To: Ethan Glasser-Camp <glasse@cs.rpi.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting footnotes
Date: Sat, 12 Feb 2011 16:59:16 +0100 [thread overview]
Message-ID: <87fwrtnt0r.fsf@altern.org> (raw)
In-Reply-To: <4D4528A5.1020700@cs.rpi.edu> (Ethan Glasser-Camp's message of "Sun, 30 Jan 2011 04:00:21 -0500")
Hi Ethan,
Ethan Glasser-Camp <glasse@cs.rpi.edu> writes:
> I've been playing with the HTML export and it's pretty cool. I just have
> one quibble, which is that footnotes are always put at the end of the
> document. I'd like them to be at the end of each item, which is where I put
> them in my org file -- i.e. I've set org-footnote-section to nil.
>
> I poked around in the code and it looks like the footnotes are being
> normalized, and the normalization function is putting them all at the end
> of the document. Normalization is necessary for the names of footnotes, but
> I think it is too aggressive about moving footnotes.
I agree.
> Are there exporters for which collecting footnotes in one place is
> necessary? I think org-export-as-html could handle keeping the
> footnotes where they are with minimal changes.
>
> Attached is a sketchy patch that does what I want. It's an ugly hack. What
> do you think?
I tested the patch and it does what you want, thanks for it.
It doesn't break footnotes export in LaTeX (good thing!). I didn't
test for other exporters.
However, it seems to me that org-footnote-normalize does the right thing
when putting every footnotes at a single place -- at least, there should
be a footnote section, even when footnotes live within a subtree. It'll
make life easier for exporter.
If you don't mind, I first want to do some work on the generic exporter
to decide how to implement your idea.
Thanks!
--
Bastien
prev parent reply other threads:[~2011-02-12 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 9:00 Exporting footnotes Ethan Glasser-Camp
2011-02-12 15:59 ` Bastien [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fwrtnt0r.fsf@altern.org \
--to=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.org \
--cc=glasse@cs.rpi.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).