From: Jambunathan K <email@example.com>
To: John Tait <firstname.lastname@example.org>
Subject: Re: Images in included files
Date: Fri, 08 Apr 2011 17:24:33 +0530 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <BANLkTinki_DhOVR+FV22Ne8FMLD7Kv9q+A@mail.gmail.com> (John Tait's message of "Fri, 8 Apr 2011 12:12:26 +0100")
> 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
> 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.
next prev parent reply other threads:[~2011-04-08 11:54 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 [this message]
2011-04-08 12:21 ` johngtait
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).