From: Julien Cubizolles <j.cubizolles@free.fr>
To: emacs-orgmode@gnu.org
Subject: Re: Best way to include references/license
Date: Thu, 06 Nov 2014 18:06:14 +0100 [thread overview]
Message-ID: <87oask9s3d.fsf@free.fr> (raw)
In-Reply-To: 87k33993ti.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> I first thought of using footnotes but according to Org documentation
>> they won't be exported if they are collected in a special heading.
>
> This doesn't sound right. What do you mean?
Consider the following example, org-footnote-section being "Footnotes"
--8<---------------cut here---------------start------------->8---
#+STARTUP: nofinline
* Premier heading
+ voici une photo [fn:1]
* Footnotes
+ [fn:1] Crédit photo1
--8<---------------cut here---------------end--------------->8---
The Beamer export pdf creates a footnote in the first frame, I'd like to
have it as an item in a frame named Footnotes. This section isn't
exported anyway.
>> Bracket links (like <<link>>)
>
> These are called targets.
>
>> create a \texttt{} \hypertarget{} pair instead of a \label{} \ref{}
>> pair in the latex file. Should I go with explicit \label{} \ref{} in
>> the org file ?
>
> An example would help understanding the issue.
--8<---------------cut here---------------start------------->8---
* Premier heading
+ voici une photo [[photo1]]
* Références
+ <<photo1>> crédit photo 1
--8<---------------cut here---------------end--------------->8---
I can't reproduce the \texttt{} I had yesterday. Now I get an
\ref{photo1}/\hypertarget{photo2}{} pair. pdflatex complains about an
undefined reference.
Julien.
next prev parent reply other threads:[~2014-11-06 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 9:21 Best way to include references/license Julien Cubizolles
2014-11-05 13:26 ` Nicolas Goaziou
2014-11-06 17:06 ` Julien Cubizolles [this message]
2014-11-06 18:27 ` Nicolas Goaziou
2014-11-09 20:51 ` Julien Cubizolles
2014-11-05 13:57 ` Jacob Gerlach
2014-11-05 14:11 ` Sebastien Vauban
2014-11-05 14:38 ` Jacob Gerlach
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=87oask9s3d.fsf@free.fr \
--to=j.cubizolles@free.fr \
--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).