From: Jochem Huhmann <joh@gmx.net>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: images in Docbook with Red Hat 6.2
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <m366tk67gp.fsf@nova.revier.com> (raw)
In-Reply-To: <38F779E7.9C0CA04D@cybercable.tm.fr>
* Eric Bischoff <ebisch@cybercable.tm.fr> wrote:
> The stylesheet themselves have easy ways of determining the
> backend with no help of any shell script (Sam's very first
> message even shows how to do it in DSSSL).
Err, yes. That's right ;-) But from within a shell script you can
configure/request a specific file-format for a given output (as in
preferring PNG over GIF for HTML-output) and then pass this over to jade
and the stylesheets. You have to have all images in this format then,
yes. That's a "Not my problem, get your work done and I do mine" from
DSSSL point of view ;-)
> To summarize :
>
> We have files that may be GIF, JPEG, PNG, EPS, ... :
> flower.jpeg, cactus.gif, flower.eps, cactus.eps
> We have a selected backend (tex, pdf, html, ...) :
> html
> We have a filename from the docbook document :
> flower
>
> What would be nice if the stylesheet could say :
>
> "Well, this is html so I can accept JPG, JPEG, GIF, and PNG.
> The filename is "flower" so I should try "flower.jpg",
> "flower.jpeg", "flower.gif" and "flower.png". Hmmm, only
> "flower.jpeg" exists : I'll take it."
That would be nice indeed. Although one could ask if this is in DSSSL
scope anymore.
> But this would assume we would have a way to know from DSSSL
> whether a file exists or not. Norm said it was impossible.
DSSSL isn't a system programming language, it is for stylesheets. If
this means that you have to have all images in one format, well, convert
them ;-)
Jochem
--
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
next prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Sam Roberts
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Diego Sevilla Ruiz (dsevilla@um.es)
2000-12-27 6:36 ` Sam Roberts
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Sam Roberts
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Sam Roberts
2000-12-27 6:36 ` Norman Walsh
2000-12-27 6:36 ` David C. Mason
2000-12-27 6:36 ` David C. Mason
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Jochem Huhmann [this message]
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` godoy
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` godoy
2000-12-27 6:36 ` Jochem Huhmann
-- strict thread matches above, loose matches on Subject: below --
2000-12-27 6:36 Peter Toft
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=m366tk67gp.fsf@nova.revier.com \
--to=joh@gmx.net \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
/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).