public inbox for
 help / color / mirror / Atom feed
From: "Éric Bischoff" <>
Subject: Re: docbook 2 html with images
Date: Sat, 04 Feb 2006 15:05:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Le Samedi 4 Février 2006 14:44, JT Moree a écrit :
> > 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?

For example, at my place, they are in images/ ...

> 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 ".".

> Can makefiles call external programs.  Worst case could be that the
> utility is called manually by the user or by the docbook2html wrapper.

I see it best in docbook2html wrapper.

Heya, anybody listening us ? Any maintainer here ? ;-)

George W. Bush mentions "liberty" in every speech he does. But today, the USA 
exports war, torture, humiliation, secret prisons, arbitrary detention 
without any judgement, and telephone tapping. That has very little to do with 

  reply	other threads:[~2006-02-04 15: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 [this message]
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:

* 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).