From: JT Moree <moreejt@xperienceinc.com>
Cc: docbook-tools-discuss@sourceware.org
Subject: Re: docbook 2 html with images
Date: Sat, 04 Feb 2006 13:42:00 -0000 [thread overview]
Message-ID: <43E4AFBB.7000209@xperienceinc.com> (raw)
In-Reply-To: <200602032136.47456.ebischoff@nerim.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> OK. How do you do the difference between an <img src=""> that comes from the
> local files and an <img src=""> that comes from some other external source ?
see next message i sent. src with http:// or ftp:// etc are external
and would not be acted upon.
> And why should the images be precisely in the same directory as the docbook
> source ?
Where else would they be? if they are being referred to in the docbook
files and they are not external?
Can makefiles call external programs. Worst case could be that the
utility is called manually by the user or by the docbook2html wrapper.
- --
JT Morée
PC Xperience, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFD5K+7ucZ4lMT2d5IRAjC1AKCIWER1P/hVgFF/8RALZqxYLejL1QCcCKjq
YECzVkDxuTvqsNsqM5wQVfk=
=KE18
-----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 13:42 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 [this message]
2006-02-04 15:05 ` Éric Bischoff
2006-02-04 22:05 ` JT Moree
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
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E4AFBB.7000209@xperienceinc.com \
--to=moreejt@xperienceinc.com \
--cc=docbook-tools-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).