public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: Jochem Huhmann <joh@gmx.net>
Cc: 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: <38F78E74.4F14B78D@cybercable.tm.fr> (raw)
In-Reply-To: <m366tk67gp.fsf@nova.revier.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]

Jochem Huhmann wrote:
> 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)

You can do this in the stylesheets as well, as Sam's code
snippet shows it.

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

True.

> 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 ;-)

... or use my entities-based solution ;-).

I also know there's an "imagelib" functionality in Jade, but
I don't know if this could address this problem.

-- 
 Éric Bischoff   -   mailto:ebisch@cybercable.tm.fr
 __________________________________________________
                                           \^o~_.
     .~.                           ______  /( __ )
     /V\         Toys story         \__  \/  (  V
   //   \\                            \__| (__=v
  /(     )\                        |\___/     )
    ^^-^^                           \_____(  )
     Tux                        Konqui     \__=v
 __________________________________________________

  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   ` Sam Roberts
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
2000-12-27  6:36             ` Eric Bischoff
2000-12-27  6:36               ` Jochem Huhmann
2000-12-27  6:36                 ` Eric Bischoff [this message]
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
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   ` Diego Sevilla Ruiz (dsevilla@um.es)
2000-12-27  6:36     ` Eric Bischoff
2000-12-27  6:36     ` Sam Roberts
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=38F78E74.4F14B78D@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=joh@gmx.net \
    /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).