Best way to include references/license

Best way to include references/license

[Julien Cubizolles]

I want to include the copyright terms for images I include in
org documents and I'm wondering what would be a good way to go about
it. I would like to have a heading gathering all these references in a
list.

I first thought of using footnotes but according to Org documentation
they won't be exported if they are collected in a special heading.
Using standard links would need to have one heading by reference.

Bracket links (like <<link>>) 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 ?

Julien.

Re: Best way to include references/license

[Nicolas Goaziou]

Hello,

Julien Cubizolles <j.cubizolles@free.fr> writes:

> I want to include the copyright terms for images I include in
> org documents and I'm wondering what would be a good way to go about
> it. I would like to have a heading gathering all these references in a
> list.
>
> 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?

> Using standard links would need to have one heading by reference.
>
> 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.


Regards,

-- 
Nicolas Goaziou

Re: Best way to include references/license

[Julien Cubizolles]

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.

Re: Best way to include references/license

[Nicolas Goaziou]

Julien Cubizolles <j.cubizolles@free.fr> writes:

> Consider the following example, org-footnote-section being "Footnotes"
> #+STARTUP: nofinline
>
> * Premier heading
>
> + voici une photo [fn:1]
>
> * Footnotes
>
> + [fn:1] Crédit photo1
>
> 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.

Indeed. Anything in footnote section is ignored. All is good here.

> * Premier heading
>
> + voici une photo [[photo1]]
>
> * Références
>
> + <<photo1>> crédit photo 1
>
> I can't reproduce the \texttt{} I had yesterday. Now I get an
> \ref{photo1}/\hypertarget{photo2}{} pair. pdflatex complains about an
> undefined reference.

It should be \ref{photo1}/\label{photo1} in this case. I pushed a fix
for that in maint.


Regards,

Re: Best way to include references/license

[Julien Cubizolles]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:


> It should be \ref{photo1}/\label{photo1} in this case. I pushed a fix
> for that in maint.

Thanks for the fix.

Julien.

Re: Best way to include references/license

[Jacob Gerlach]

[-- Attachment #1: Type: text/plain, Size: 519 bytes --]

On Wed Nov 05 2014 at 4:22:06 AM Julien Cubizolles <j.cubizolles@free.fr>
wrote:

> Bracket links (like <<link>>) 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 ?
>
The \texttt{} is probably because org could not resolve a target from your
link. I can't help much with your problem, but see
C-h v org-latex-link-with-unknown-path-format RET
for an idea of where the \texttt{} comes from.

>
> Julien.
>
>
> Jake

[-- Attachment #2: Type: text/html, Size: 918 bytes --]

Re: Best way to include references/license

[Sebastien Vauban]

Jacob Gerlach wrote:
> On Wed Nov 05 2014 at 4:22:06 AM Julien Cubizolles wrote:
>
>> Bracket links (like <<link>>) 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 ?
>
> The \texttt{} is probably because org could not resolve a target from
> your link. I can't help much with your problem, but see C-h
> v org-latex-link-with-unknown-path-format RET for an idea of where the
> \texttt{} comes from.

FWIW, the value I set in my .emacs file is "\\colorbox{red}{%s}", so
that it stands out in the exported document.

Best regards,
  Seb

-- 
Sebastien Vauban

Re: Best way to include references/license

[Jacob Gerlach]

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

On Wed, Nov 5, 2014 at 9:11 AM, Sebastien Vauban <sva-news@mygooglest.com>
wrote:

> Jacob Gerlach wrote:
> > On Wed Nov 05 2014 at 4:22:06 AM Julien Cubizolles wrote:
> >
> >> Bracket links (like <<link>>) 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 ?
> >
> > The \texttt{} is probably because org could not resolve a target from
> > your link. I can't help much with your problem, but see C-h
> > v org-latex-link-with-unknown-path-format RET for an idea of where the
> > \texttt{} comes from.
>
> FWIW, the value I set in my .emacs file is "\\colorbox{red}{%s}", so
> that it stands out in the exported document.
>
I take it one step further and use \BADLINK. This causes pdflatex to
complain, so the export fails. No need to then try to catch it in the
exported document.

There was some recent discussion of patching the exporter to report errors
on unresolved links:
http://lists.gnu.org/archive/html/emacs-orgmode/2014-09/msg00880.html

Jake

[-- Attachment #2: Type: text/html, Size: 1700 bytes --]