public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: egcs@cygnus.com
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: <38F779E7.9C0CA04D@cybercable.tm.fr> (raw)
In-Reply-To: <m3r9c86bvn.fsf@nova.revier.com>

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

Jochem Huhmann wrote:

> I didn't meant it this way. The wrapping shell-backend knows the target
> format and therefore it should know which file-type for images is the
> best for this target format. So it could pass this format (as in "png",
> "eps", "gif", ...) in a variable to jade and make it available in the
> stylesheet.

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

But what happens if some pictures are PNG, others GIF,
others JPEG ?

> The stylesheet has the blank filename (from the SGML source) and the
> needed extension (from that variable) of the image-file then. This leads
> me to the assumption that this should be enough to build the right
> file-name (name + extension) in the stylesheet.

Again, there's no need of such a variable to know the
backend.

> It wouldn't be enough to make sure that the file in the needed format
> really exists, yes. But if it exists this could work. I haven't got the
> time right now to dig through the stylesheets to see how this could be
> done in a driver file and I may well have missed something important,
> though.

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

But this would assume we would have a way to know from DSSSL
whether a file exists or not. Norm said it was impossible.

-- 
 É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   ` 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       ` 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                 ` 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
2000-12-27  6:36       ` David C. Mason
2000-12-27  6:36       ` Sam Roberts
2000-12-27  6:36         ` Norman Walsh
2000-12-27  6:36           ` David C. Mason
  -- 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=38F779E7.9C0CA04D@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=egcs@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).