To: Jambunathan K <email@example.com>, John Tait <firstname.lastname@example.org>
Subject: Re: Re: Images in included files
Date: Fri, 08 Apr 2011 12:21:39 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2477 bytes --]
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>
The source Org file is called (in Windows)
Where folder "site" contains all the files.
Manual1.org calls a dozen #+INCLUDEd Org files arrranged like this:
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".
The images are arranged like this:
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
When I export from filename.org (to LateX and html), the images obligingly
However when I export from Manual.org, there is the standard broken picture
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
On , Jambunathan K <firstname.lastname@example.org> wrote:
> > Hi
> > I am trying to export html from an Org file "A.org". The Org file is
> > 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 --]
next prev parent reply other threads:[~2011-04-08 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 11:12 Images in included files John Tait
2011-04-08 11:54 ` Jambunathan K
2011-04-08 12:21 ` johngtait [this message]
2011-05-01 22:37 ` Robert Goldman
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).