From: JT Moree <email@example.com>
Subject: Re: docbook 2 html with images
Date: Sat, 04 Feb 2006 22:05:00 -0000 [thread overview]
Message-ID: <43E525AB.firstname.lastname@example.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
>>>And why should the images be precisely in the same directory as the
>>>docbook source ?
>>Where else would they be?
> For example, at my place, they are in images/ ...
Does your docbook link to them with the 'images' in the path?
In my case the Blender guide is not just referring to images but images
under subdirectories so that the src looks like
src="boo/bar/baz/image.png" in the resulting html. the original docbook
>>if they are being referred to in the docbook
>>files and they are not external?
> In fact, they could be anywhere.
> You would at least need to pass a parameter like --images-dir to your script.
> That could default to ".".
That's fine but I'm not sure that it makes sense. How could the docbook
stuff use images from anywhere without specifiying where that is in the
And if it is specified it results in an <img src= after conversion to html?
And if it can be found by the docbook stuff why wouldn't it be findable
by the html conversion stuff and my utility as well?
PC Xperience, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
next prev parent reply other threads:[~2006-02-04 22:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 14:27 JT Moree
2006-02-03 13:44 ` Éric Bischoff
2006-02-03 18:18 ` JT Moree
2006-02-03 18:29 ` JT Moree
2006-02-03 20:36 ` Éric Bischoff
2006-02-04 13:42 ` JT Moree
2006-02-04 15:05 ` Éric Bischoff
2006-02-04 22:05 ` JT Moree [this message]
2006-02-05 8:47 ` Éric Bischoff
2006-02-06 1:50 ` JT Moree
2006-02-06 6:31 ` Éric Bischoff
2006-02-03 20:39 ` Éric Bischoff
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:
* 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.
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).