public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Éric Bischoff" <ebischoff@nerim.net>
To: docbook-tools-discuss@sourceware.org
Subject: Re: docbook 2 html with images
Date: Sun, 05 Feb 2006 08:47:00 -0000	[thread overview]
Message-ID: <200602050948.19691.ebischoff@nerim.net> (raw)
In-Reply-To: <43E525AB.4060901@xperienceinc.com>

Le Samedi 4 Février 2006 23:07, JT Moree a écrit :
> > For example, at my place, they are in images/ ...
>
> Does your docbook link to them with the 'images' in the path?

I suppose it has to reference them somehow, yes, otherwise how would the 
rendering engine calculate the images size for example for PDF output ?

> 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
> files use
> ref="boo/bar/baz/image.png" format="png"

Yes, you could base your algorithm on the path in the docbook source.

Beware it could be something vicious like "../../images/", in which case it 
might not be obvious to convert that to a HTML path and copy the files.

Example to show you why this could reasonably happen
(use fixed font to display) :
  project/
    +------ images/
    |          +----- illustration.png
    |
    +------ part 1/
    |         +------ chapter1/
    |         |          +-------- myfile.docbook
    |         |
    |         +------ chapter 2/

It could also be an absolute path, it is not necessarily a relative path.

> > 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
> ref tag?

Correct.

> 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?

If you find a valuable algorithm, I have nothing against, on the contrary, it 
would really be a *great* plus for the docbook-utils.

I just wanted to stress that the source images could be anywhere. You will 
have to think a lot about that in your algorithm. In fact, it's what has 
always prevented me from coding that...



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

  reply	other threads:[~2006-02-05  8:47 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
2006-02-05  8:47               ` Éric Bischoff [this message]
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=200602050948.19691.ebischoff@nerim.net \
    --to=ebischoff@nerim.net \
    --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).