emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Frings <peter.frings@agfa.com>
To: emacs-orgmode Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: Footnotes and org-export, revisited
Date: Thu, 18 Dec 2008 11:34:27 +0100	[thread overview]
Message-ID: <F9E9F348-19AC-4695-B549-E66F122C9C7E@agfa.com> (raw)
In-Reply-To: <ud4fqd8k9.fsf@gmail.com>

On Dec 17, 2008, at 6:18 PM, Sivaram Neelakantan wrote:

> Paul R <paul.r.ml@gmail.com> writes:
>
>> * Usage 1, anonymous footnotes
[snip]
>
> And then we will have that one feature request to cross reference a
> previous footnote!  :-)  In the above case, how would a person go
> about asking someone to refer to an earlier footnote?
>
>> * Usage 2, keyword named footnotes
[snip]
>>
> Unless I've got it wrong, wouldn't it be better to do something like
>
> [fn:kenpo { Kenpo is the name of several martial arts}]
> (keep the keyword and definition in one place?)
>
> And all future references go as 'see [fn:kenpo] to understand the
> meaning'.

Maybe re-use the same concepts of urls? And combine anonymous and  
labeled footnotes at once? And references?

labeled: [[fn:label][text]]
anonymous: [[fn:]][text]]
reference: [[fn:label]]

(In the reference form, the reference could become a clickable link.)

Example 1:
"This is the body of the text.[[fn:xyz][And this is the text of the  
footnote]] It indeed is a silly piece of text, but what would you  
expect?[[fn:abc][It's showing off references to previous footnotes, as  
well.[fn:xyz]]]"

Example 2:
"You can also use the references to put the footnote text out of the  
body text[[fn:xyzzy]].

[[fn:xyzzy][This footnote illustrates the out-of-the-body principle.]]"


Maybe too many brackets?

Cheers,
Peter.

  parent reply	other threads:[~2008-12-18 10:34 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
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 [this message]
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=F9E9F348-19AC-4695-B549-E66F122C9C7E@agfa.com \
    --to=peter.frings@agfa.com \
    --cc=emacs-orgmode@gnu.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.
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).