From: Paul R <paul.r.ml@gmail.com>
To: Scot Becker <scot03@streetgreek.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Footnotes and org-export, revisited
Date: Wed, 17 Dec 2008 14:28:56 +0100 [thread overview]
Message-ID: <873agnylpj.fsf@gmail.com> (raw)
In-Reply-To: <e0e1fe620812170452w7c4fcc78n5f8fd0db1bf0f278@mail.gmail.com> (Scot Becker's message of "Wed, 17 Dec 2008 12:52:59 +0000")
Hi Scot,
On Wed, 17 Dec 2008 12:52:59 +0000, "Scot Becker" <scot03@streetgreek.com> said:
Scot> But someone working in Muse did write an interesting extension to
Scot> Muse's footnote support. (The extension is explained here [5], and
Scot> the revised version of the code is here [6]). It is basically
Scot> a hook function which converts footnotes with reference
Scot> names[fn:named_note] to plain, numbered footnotes, like Muse and
Scot> org-mode support. It operates on a temporary buffer just before
Scot> export to LaTeX or HTML, so is transparent to the user.
I'm the author of this little hack. I've not found any other simple way
to handle footnote, and in particular in spite of my efforts, I did
never manage to have footnote+ working reliably.
I think all the suggestions you make in your mail make sens. In any
case, I think the solution must behave like latex (and like my hack).
This means in org documents footnotes sould be either anonymous, like in
latex \footnote{footnote content ...} or named by keyword, not by
ordered numbers. That way, you can preserve the flow of your writing and
keep easy to look both at the reference and the definition. And,
obviously, you don't renumber everything each time you insert a new
footnote.
My personnal vote goes to anonymous footnotes, like in latex.
--
Paul
next prev parent reply other threads:[~2008-12-17 13:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 12:52 Footnotes and org-export, revisited Scot Becker
2008-12-17 13:28 ` Paul R [this message]
2008-12-17 13:31 ` Carsten Dominik
2008-12-17 15:29 ` Paul R
2008-12-17 15:59 ` Scot Becker
2008-12-17 20:54 ` Matthew Lundin
2008-12-17 22:23 ` Scot Becker
2008-12-17 16:08 ` Carsten Dominik
2008-12-17 16:32 ` Paul R
2008-12-17 16:58 ` Carsten Dominik
2008-12-17 17:25 ` Paul R
2008-12-17 17:18 ` Sivaram Neelakantan
2008-12-18 8:08 ` Carsten Dominik
2008-12-18 17:13 ` Sivaram Neelakantan
2008-12-18 10:34 ` Peter Frings
2008-12-18 10:55 ` Peter Frings
2008-12-17 14:04 ` Jörg Hagmann
2009-01-01 9:07 ` Carsten Dominik
2009-01-01 16:48 ` Matthew Lundin
2009-01-01 17:10 ` Carsten Dominik
2009-01-02 15:10 ` Matthew Lundin
2009-01-03 8:17 ` Carsten Dominik
2009-01-03 22:53 ` Matthew Lundin
2009-01-04 7:39 ` Carsten Dominik
2009-01-12 11:29 ` Scot Becker
2009-01-12 14:21 ` Paul R
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=873agnylpj.fsf@gmail.com \
--to=paul.r.ml@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=scot03@streetgreek.com \
/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).