Re: [O] Images in included files

[Robert Goldman]

I'm having exactly this same problem.

I have a file, suggestions.org, in directory ~/x/y/z/top/child/ that
contains many images.  These are included by means of links such as

[[./foo.pdf]]

Now, I have a parent file in top/, manual.org, and I want to #+include
child/suggestions.org

Unfortunately, this breaks all the figure links in suggestions.org,
because . is interpreted as top/ and not top/child/.

Even more unfortunately, this is a shared document, and a number of
people are going to check it out from a source code repository
(subversion in this case).  This means that I cannot specify the images as

~/x/y/z/top/child/foo.pdf

because I cannot force my co-authors to check out the top/ to ~/x/y/z.
Indeed, I cannot even force my co-authors to have directories x/ x/y or
x/y/z...

So what is needed, I believe is some way of indicating that these
relative links should be resolved at *include* time, rather than later.

I am pretty sure that this is the same problem John Tait alludes to,
with some more details.

Best,
Robert

[O] Images in included files

[John Tait]

Hi

I am trying to export html from an Org file A.org. The Org file is largly
constructed from other Org files 1.org, 2.org, 3.org, etc. via
#+INCLUDE:. These 1.org, 2.org, 3.org, etc. files have a number of
images included.

However the images aren't included in the export of A.org.

What I think is happening is that the images are being looked for in the
relative path from A.org, whereas they should be looked at for in the
relative path from the 1.org, 2.org files. Am I correct, and is there a
workaround (other than using an absolute path)?

Thanks

John