How to fix path to figures in included files

How to fix path to figures in included files

[Nikolaus Rath]

Hi,

When using INCLUDE in an org-file to include a file in a sub-directory
(e.g. "#+INCLUDE: preamble/preamble.org"), and the included file in turn
refers to a file ("[[./figure1.png]]"), then the LaTeX export for the
top-level org file refers to the file with its path relative to the
included .org file rather than the top-level org file for which LaTeX is
generated.

Is there a way to fix this?

In other words, if I have a file "main.org" that contains just

,----
| #+INCLUDE: preamble/preamble.org"
`----

and preamble/preamble.org contains

,----
| * Preamble
| 
| Look at this amazing image:
| [[./file1.png]]
`----

Then the LaTeX that is generated for "main.org" is

,----
| \part{Preamble}
| \label{sec:orgheadline3}
| 
| Look at this amazing image:
| 
| \includegraphics[width=.9\linewidth]{./figure1.png}
`----

but I want it to be:

,----
| \part{Preamble}
| \label{sec:orgheadline3}
| 
| Look at this amazing image:
| 
| \includegraphics[width=.9\linewidth]{preamble/figure1.png}
`----

Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

Re: How to fix path to figures in included files

[Nicolas Goaziou]

Hello,

Nikolaus Rath <Nikolaus@rath.org> writes:

> When using INCLUDE in an org-file to include a file in a sub-directory
> (e.g. "#+INCLUDE: preamble/preamble.org"), and the included file in turn
> refers to a file ("[[./figure1.png]]"), then the LaTeX export for the
> top-level org file refers to the file with its path relative to the
> included .org file rather than the top-level org file for which LaTeX is
> generated.
>
> Is there a way to fix this?

I'm pretty sure that question was raised before on this ML, but, after
a cursory look, I cannot find any reference to it.

There is no way to fix this for the time being. I can think of two
solutions.

1. We could add a hook just before inserting included file in the master
   document, so you get a chance to rewrite links yourself.

2. We could do that rewriting every file link with a relative path
   ourselves.

Second option only makes sense if the behavior you suggest is always the
one needed. We may need some more feedback about this.

Also, it could fail for some link types, when the path is not obviously
a file, e.g. [[foo:a/b]]. IOW, if implemented, we would have to limit
ourselves to "file:" links.

OTOH, the first solution is easy to implement.

Regards,

-- 
Nicolas Goaziou