emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Org-mode don't export to html footnotes references inside footnotes as such. [7.8.03]
Date: Sun, 04 Mar 2012 13:47:27 +0100	[thread overview]
Message-ID: <874nu4fs80.fsf@gmail.com> (raw)
In-Reply-To: <87pqcsvet9.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 04 Mar 2012 11:30:26 +0100")

Hello,

Achim Gratz <Stromeko@nexgo.de> writes:

>>> If one intends to export his Org file to ODT, then nested footnote
>>> construction should be avoided like plague.
>>
>> It isn't really supported in LaTeX too, but there are workarounds.
>
> There are always workarounds, but footnotes within footnotes aren't
> directly supported by any publishing system I know of, and with good
> reason.  A footnote, just like a marginal, is an expansion on the main
> text that can be skipped without loss of information (but maybe loss of
> detail).

That's what I thought before the OP request. Though, it appears that it
is a not so rare need. For example critical editions seem to use it
quite often.

> So whenever you feel that you need a footnote within a footnote, you
> could just as well have two footnotes at the original place.

I have never needed nested footnotes, so I feel like the Devil's
advocate but anyway...

Imagine a very large footnote, spanning over tens of lines.  You would
like to add a footnote next to a word in the middle of that
text. I suppose it wouldn't make sense to get out of that footnote and
be told there's another reference for a word you read many lines ago.

>> If such thing isn't possible, ODT back-end will ignore any footnote
>> contained in another footnote (i.e. whose genealogy contains an element
>> with an `footnote-reference' or `footnote-definition' type) and send
>> a message to the user.
>
> It would be better to not promote the idea of footnotes within footnotes
> and those who insist on using that construct should be required to
> explicitly request that feature and suffer the consequences.

Note that Org inherently supports nested footnotes.  Forbidding them
would be much like an artificial limitation.

I don't mind such limitation, but knowing that they may happen to be
useful, it's worth pondering if it really should be so.

> Much better would be if starting a footnote while within a footnote
> would simply open a new footnote and add the reference at the same place
> where the first one was opened.

That's a possible workaround I was talking about earlier. And it's
perfectly possible with the experimental exporter.  ODT back-end may
implement it.

That's mostly what I did with the LaTeX back-end. Nested footnotes
definitions are inserted right after the top level footnote definition
containing them.  Only footnotes markers are nested.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2012-03-04 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25  2:28 Bug: Org-mode don't export to html footnotes references inside footnotes as such. [7.8.03] Bruno Félix Rezende Ribeiro
2012-02-26 12:43 ` Nicolas Goaziou
2012-03-03 20:22   ` Jambunathan K
2012-03-03 20:36     ` Nicolas Goaziou
2012-03-04 10:30       ` Achim Gratz
2012-03-04 12:47         ` Nicolas Goaziou [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=874nu4fs80.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Stromeko@nexgo.de \
    --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).