From: Eric Bischoff <ebisch@cybercable.tm.fr>
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: <38F66342.9FD5F778@cybercable.tm.fr> (raw)
In-Reply-To: <00af01bfa571$69317680$1403a8c0@cogent.ca>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]
Sam Roberts wrote:
>
> > 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,
Yes
> and that you
> use this technique only because you use BOTH gifs and
> jpegs in the same document when it's formatted as html?
Not necessarily in the same document. I'm using both gifs
and jpegs, but usually in different documents. Anyway, it
remains a problem if you hack the stylesheets.
What is really a problem is that the file extension depends
on the processing you apply to the document, while the
docbook file should remain a simple source. And since you
don't want to hack the document each time you use it
differently, the solution needs to simply work from the
command line. So I managed in a way that the only thing I
need is the following definition in some external file:
<!ENTITY % html "IGNORE">
<![%html; [
<!ENTITY % print "IGNORE">
<!ENTITY gif-eps "gif">
<!ENTITY jpg-eps "jpg">
<!ENTITY jpeg-eps "jpeg">
]]>
<!ENTITY % print "INCLUDE">
<![%print; [
<!ENTITY gif-eps "eps">
<!ENTITY jpg-eps "eps">
<!ENTITY jpeg-eps "eps">
]]>
The stylesheets solution could perfectly work if there was a
way to easily detect which extension(s) do exist for this
file from DSSSL.
--
Ãric Bischoff - mailto:ebisch@cybercable.tm.fr
__________________________________________________
\^o~_.
.~. ______ /( __ )
/V\ Toys story \__ \/ ( V
// \\ \__| (__=v
/( )\ |\___/ )
^^-^^ \_____( )
Tux Konqui \__=v
__________________________________________________
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 ` Sam Roberts
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 ` 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 ` 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
-- 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=38F66342.9FD5F778@cybercable.tm.fr \
--to=ebisch@cybercable.tm.fr \
--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).