public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Sam Roberts" <sam@cogent.ca>
To: "Eric Bischoff" <ebisch@cybercable.tm.fr>
Cc: "Peter Toft" <pto@sslug.dk>,
	<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: <00af01bfa571$69317680$1403a8c0@cogent.ca> (raw)
In-Reply-To: <38F65807.4905D5C@cybercable.tm.fr>

> Such code trying to guess the graphic extension from within
> the stylesheet is a good idea. Anyway, it will always face
> the same problem : for publishing in HTML, for example, how
> to decide whether to add JPEG, PNG or GIF ? It's not easy.

It's only hard if you use more than one image format per
output type. Otherwise Norman's stylesheets allow you to
trivially set the extension for that format. This fails only
in the tex output case, because tex is formatted into both
pdf and ps.

> I'm currently using the following approach:
> 
> <graphic fileref="foo.&gif-eps;">
> 
> stands for:
> "use foo.gif when making HTML files, foo.eps when printing
> to TeX."
> 
> You can do create on the same model other entities like
> &jpg-eps;. It's not perfect, but it's simple and works.

I assume we're talking the same thing here, and that you
use this technique only because you use BOTH gifs and
jpegs in the same document when it's formatted as html?

Sam
 


  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 [this message]
2000-12-27  6:36     ` Eric Bischoff
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
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
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 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='00af01bfa571$69317680$1403a8c0@cogent.ca' \
    --to=sam@cogent.ca \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=ebisch@cybercable.tm.fr \
    --cc=pto@sslug.dk \
    /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).