public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: Sam Roberts <sam@cogent.ca>
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: <38F65807.4905D5C@cybercable.tm.fr> (raw)
In-Reply-To: <Voyager.000413114314.27688B@sam.cogent.ca>

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

Sam Roberts wrote:
> 
> 
> (define (graphic-file filename)
>     (let ((ext (file-extension filename)))
>         (if (or tex-backend   ;; TeX can work this out itself
>             (not filename)
>             (not %graphic-default-extension%)
>             (member ext %graphic-extensions%))
>         filename
>         (string-append filename "." %graphic-default-extension%))))
> 

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.

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.

-- 
 É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 [this message]
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
2000-12-27  6:36                   ` Jochem Huhmann
2000-12-27  6:36                     ` godoy
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                       ` 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
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=38F65807.4905D5C@cybercable.tm.fr \
    --to=ebisch@cybercable.tm.fr \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=pto@sslug.dk \
    --cc=sam@cogent.ca \
    /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).