From: Eric Lee Green <eric@badtux.org>
To: Peter Toft <pto@sslug.dk>, Bill Brooks <wbrooks@lug.ee.calpoly.edu>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: db2pdf chokes: LaTeX Error: Unknown graphics extension: .eps
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <00060106384200.18643@ehome.inhouse> (raw)
In-Reply-To: <Pine.LNX.4.21.0006011353180.830-100000@pto.linus.dk>
On Thu, 01 Jun 2000, Peter Toft wrote:
> On Wed, 31 May 2000, Bill Brooks wrote:
> > If I have the following fragment in a document:
> >
> > <figure>
> > <title>Picture's Title</title>
> > <graphic fileref="images/foo"></graphic>
> > </figure>
Hmm.... here's a fragment from one of my documents for what you're doing with
the <graphic> tag:
<mediaobject>
<imageobject>
<imagedata fileref="tserv_overview.eps">
</imageobject>
<imageobject>
<imagedata fileref="tserv_overview.png">
</imageobject>
<textobject>
<para>[Image of tape server overview SHOULD be here]</para>
</textobject>
</mediaobject>
At least w/ the version of the docbook tools that comes with Red Hat 6.2, the
appropriate back end chooses the appropriate graphic format.
Note, though, that I'm no expert in DocBOOK or docbook-tools by any means,
and I have no idea whether that's the way it should work or not! (For one
thing, I'm still getting @#$%@ -999 as the page number in half the entries in
my index, sigh).
--
Eric Lee Green There is No Conspiracy
eric@badtux.org http://www.badtux.org
WARNING: multiple messages have this Message-ID
From: Eric Lee Green <eric@badtux.org>
To: Peter Toft <pto@sslug.dk>, Bill Brooks <wbrooks@lug.ee.calpoly.edu>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: db2pdf chokes: LaTeX Error: Unknown graphics extension: .eps
Date: Thu, 01 Jun 2000 06:31:00 -0000 [thread overview]
Message-ID: <00060106384200.18643@ehome.inhouse> (raw)
Message-ID: <20000601063100.hgKD4wzf7Z6FNWfdKG9UbVmKkANvLNHD6Kzb2VtvpUM@z> (raw)
In-Reply-To: <Pine.LNX.4.21.0006011353180.830-100000@pto.linus.dk>
On Thu, 01 Jun 2000, Peter Toft wrote:
> On Wed, 31 May 2000, Bill Brooks wrote:
> > If I have the following fragment in a document:
> >
> > <figure>
> > <title>Picture's Title</title>
> > <graphic fileref="images/foo"></graphic>
> > </figure>
Hmm.... here's a fragment from one of my documents for what you're doing with
the <graphic> tag:
<mediaobject>
<imageobject>
<imagedata fileref="tserv_overview.eps">
</imageobject>
<imageobject>
<imagedata fileref="tserv_overview.png">
</imageobject>
<textobject>
<para>[Image of tape server overview SHOULD be here]</para>
</textobject>
</mediaobject>
At least w/ the version of the docbook tools that comes with Red Hat 6.2, the
appropriate back end chooses the appropriate graphic format.
Note, though, that I'm no expert in DocBOOK or docbook-tools by any means,
and I have no idea whether that's the way it should work or not! (For one
thing, I'm still getting @#$%@ -999 as the page number in half the entries in
my index, sigh).
--
Eric Lee Green There is No Conspiracy
eric@badtux.org http://www.badtux.org
next prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Bill Brooks
2000-05-31 22:40 ` Bill Brooks
2000-12-27 6:36 ` Peter Toft
2000-06-01 5:04 ` Peter Toft
2000-12-27 6:36 ` Eric Lee Green [this message]
2000-06-01 6:31 ` Eric Lee Green
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=00060106384200.18643@ehome.inhouse \
--to=eric@badtux.org \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=pto@sslug.dk \
--cc=wbrooks@lug.ee.calpoly.edu \
/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).