public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Peter Toft <pto@sslug.dk>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: images in Docbook with Red Hat 6.2
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0004130055020.715-100000@pto.linus.dk> (raw)

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

Using Docbook with Red Hat 6.2 I have a hard time
generating the PDF file with images (HTML is working
fine). I have xterm.gif and xterm.eps available and my
simplified source is shown below (The real source gives
350 pages of text)

db2pdf complains

-------->
! LaTeX Error: Unknown graphics extension: .eps.

See the LaTeX manual or LaTeX Companion for
explanation.
Type  H <return>  for immediate help.
 ...                                              
                                                  
l.753 {0}}

\endNode{}\endNode{}\endSeq{}\endPar{}\endNode{}\endSeq{}\endDispl...
<--------

Any clues - I am very stuck here....
I am using 
tetex-1.0.6-11
jade-1.2.1-9
jadetex-2.7-2

-----------------
My sgml-source:

<!doctype book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
]>

<book id="index" lang="da">
  <bookinfo>
    <date>9. april 2000</date>
    <title>aargh</title>
    <AUTHORGROUP>

    <AUTHOR>
      <FIRSTNAME>Peter</FIRSTNAME>
      <SURNAME>Toft</SURNAME>
    </AUTHOR>

    </AUTHORGROUP>
    <COPYRIGHT>
      <YEAR>1998</YEAR>
      <HOLDER>Toft/HOLDER>
    </COPYRIGHT>
  </bookinfo>



<chapter id="intro">
<title>Linux?</title>

<sect1 id="OpenSource">
<title>Ã…ben kildetekst - Open Source</title>

<FIGURE ID="xterm" FLOAT="1">
<TITLE>xterm
</TITLE>
<GRAPHIC
FILEREF="xterm"  SCALE="60"></GRAPHIC>
</FIGURE>
</sect1>
</chapter>
</book>


Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto

... when men were men and wrote their own device driver ...
                    --- Linus Benedict Torvalds



             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 Peter Toft [this message]
  -- strict thread matches above, loose matches on Subject: below --
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       ` 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   ` Diego Sevilla Ruiz (dsevilla@um.es)
2000-12-27  6:36     ` Sam Roberts
2000-12-27  6:36     ` Eric Bischoff

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=Pine.LNX.4.21.0004130055020.715-100000@pto.linus.dk \
    --to=pto@sslug.dk \
    --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).