emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* Images in included files
@ 2011-04-08 11:12 John Tait
  2011-04-08 11:54 ` Jambunathan K
  0 siblings, 1 reply; 4+ messages in thread
From: John Tait @ 2011-04-08 11:12 UTC (permalink / raw)
  To: emacs-orgmode

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

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

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Images in included files
  2011-04-08 11:12 Images in included files John Tait
@ 2011-04-08 11:54 ` Jambunathan K
  2011-04-08 12:21   ` johngtait
  0 siblings, 1 reply; 4+ messages in thread
From: Jambunathan K @ 2011-04-08 11:54 UTC (permalink / raw)
  To: John Tait; +Cc: emacs-orgmode


John

> 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)?
>

Provide an example of dir organization, some simple orgfiles and the
generated html output samples.

The more the details and samples provided more there would be incentive
for someone to help you out.

Jambunathan K.

>  
>
> Thanks
>
> John

-- 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Re: Images in included files
  2011-04-08 11:54 ` Jambunathan K
@ 2011-04-08 12:21   ` johngtait
  2011-05-01 22:37     ` Robert Goldman
  0 siblings, 1 reply; 4+ messages in thread
From: johngtait @ 2011-04-08 12:21 UTC (permalink / raw)
  To: Jambunathan K, John Tait; +Cc: emacs-orgmode

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

Okay...

I'm no coder but the relevant html seems to be:

<div id="fig:threearrows" class="figure">
<p><img src="./images/threearrows.png" width="300" height="300"  
align="center" alt="./images/threearrows.png" /></p>
<p>Buried services suite</p>
</div>

The source Org file is called (in Windows)

\site\Experimental-manuals\Manual1.org

Where folder "site" contains all the files.

Manual1.org calls a dozen #+INCLUDEd Org files arrranged like this:

site\foldername\filename.org

using this format: in Manual1.org

---------

* Introduction to this manual :scope:

This is an experimental manual, with selected export. The selected text is  
based on the tag "scope".

#+INCLUDE: "../foldername/filename.org"

---------

The images are arranged like this:

\site\foldername\images\picture.png


All the image files are included in each of the filename.org files  
something like this:

#+ATTR_HTML: width="500" height="500" align="center"
#+CAPTION: My picture
#+LABEL: fig:mypicure
[[./images/mypicture.png]]

When I export from filename.org (to LateX and html), the images obligingly  
appear.

However when I export from Manual.org, there is the standard broken picture  
link.

I suspect that the exporter is looking for the image in

\site\Experimental-manuals\images\mypicture.png (which doesn't exist)

where it should be looking in

\site\foldername\images\mypicture.png


Phew!

John





On , Jambunathan K <kjambunathan@gmail.com> wrote:



> John





> > 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)?


> >





> Provide an example of dir organization, some simple orgfiles and the


> generated html output samples.





> The more the details and samples provided more there would be incentive


> for someone to help you out.





> Jambunathan K.





> >


> >


> > Thanks


> >


> > John





> --




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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Images in included files
  2011-04-08 12:21   ` johngtait
@ 2011-05-01 22:37     ` Robert Goldman
  0 siblings, 0 replies; 4+ messages in thread
From: Robert Goldman @ 2011-05-01 22:37 UTC (permalink / raw)
  To: Org Mode

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-05-01 22:37 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-08 11:12 Images in included files John Tait
2011-04-08 11:54 ` Jambunathan K
2011-04-08 12:21   ` johngtait
2011-05-01 22:37     ` Robert Goldman

Code repositories for project(s) associated with this 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).