From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: When exporting to PDF an Org file where multiple footnotes share the same definition, only the first footnote is clickable [8.3.4 (8.3.4-39-ge0acd8-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20160418/)]
Date: Mon, 25 Apr 2016 10:38:52 +0200 [thread overview]
Message-ID: <87h9eqt74z.fsf@gmx.us> (raw)
In-Reply-To: 1461444845.13483.6.camel@gmail.com
Jorge Peixoto de Morais Neto <jorge13515@gmail.com> writes:
> Line1.[fn:1]
>
> \pagebreak
>
> Line2.[fn:1]
> * Footnotes
> [fn:1] Footnote.
> ------------------------------------------------------------------------
> In the generated PDF, the second footnote reference (on page 2) is not
> clickable. If this happened on a large document, how would the reader
> locate the footnote definition?
Currently, that's not possible in Org. You could something like this,
Line1.[fn:1]
\pagebreak
Line2 (see footnote [[f1]])
* Footnotes
[fn:1] <<f1>> Footnote.
You could also settle for user labels,
# -*- org-latex-prefer-user-labels:t -*-
#+latex_header: \usepackage{scrextend}
#+macro: fnref (eval (if (org-export-derived-backend-p org-export-current-backend 'latex) (format "@@latex:\\footref{%s}@@" "$1") "<<$1>>"))
Line1.[fn:1]
#+latex: \pagebreak
Line2.{{{fnref(f1)}}}
* Footnotes
[fn:1] <<f1>> Footnote.
Ultimately, I think a decent fix would be to add a prefix to
org-latex--label for targets pointing to footnotes. They should be
prefixed with "fn:". Then, it should be easy to hack together a filter.
Rasmus
--
A page of history is worth a volume of logic
next prev parent reply other threads:[~2016-04-25 8:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 20:54 Bug: When exporting to PDF an Org file where multiple footnotes share the same definition, only the first footnote is clickable [8.3.4 (8.3.4-39-ge0acd8-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20160418/)] Jorge Peixoto de Morais Neto
2016-04-25 8:38 ` Rasmus [this message]
2016-04-25 8:58 ` Nicolas Goaziou
2016-04-25 10:53 ` Rasmus
2016-04-25 11:41 ` Nicolas Goaziou
2016-04-25 13:36 ` Rasmus
2016-04-25 13:57 ` Nicolas Goaziou
2016-04-25 14:04 ` Rasmus
2016-04-25 14:07 ` Rasmus
2016-05-22 20:16 ` Rasmus
2016-05-23 21:41 ` Nicolas Goaziou
2016-05-24 20:59 ` [patch] more robust footnotes (was: Bug: When exporting to PDF an Org file where multiple footnotes share the same definition, only the first footnote is clickable [8.3.4 (8.3.4-39-ge0acd8-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20160418/)]) Rasmus
2016-05-24 21:31 ` [patch] more robust footnotes Nicolas Goaziou
2016-05-24 21:38 ` Rasmus
2016-05-24 21:54 ` Nicolas Goaziou
2016-05-25 7:16 ` Rasmus
2016-05-25 16:50 ` Nicolas Goaziou
2016-05-25 17:51 ` Rasmus
2016-08-10 21:09 ` Bug: When exporting to PDF an Org file where multiple footnotes share the same definition, only the first footnote is clickable [8.3.4 (8.3.4-39-ge0acd8-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20160418/)] Kaushal Modi
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=87h9eqt74z.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).