From: Peter Toft <pto@sslug.dk>
To: Wookey <wookey@aleph1.co.uk>
Cc: "Edward C. Bailey" <ed@redhat.com>,
<docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: Docbook in Red Hat 7.1
Date: Thu, 26 Apr 2001 12:00:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0104262058570.12130-100000@pto.sslug> (raw)
In-Reply-To: <Marcel-1.50-0426170532-0e6h+Ty@chewy.aleph1.co.uk>
On Thu, 26 Apr 2001, Wookey wrote:
> 1) jade -t tex -d ${DB_STYLESHEET} -o ${TMPFN}.tex book
> pdfjadetex $TMPFN
> pdfjadetex $TMPFN
> pdfjadetex $TMPFN
>
> 2) jade -t tex -d ${DB_STYLESHEET} -o ${TMPFN}.tex book
> jadetex ${TMPFN}.tex
> jadetex ${TMPFN}.tex
> jadetex ${TMPFN}.tex
> dvips -o guide.ps book.dvi
> ps2pdf book.ps
>
> this second method has the advantage that it puts the pictures in. version 1
> ought to but gives an error saying 'unrecognised format .eps'.
>
> Can anyone give me a clue about how to fix/diagnose the index problem (or how
> to get pdfjadtex to put the pictures in).
I had some of those problems too, and switched to using
png-pictures then running for pdf-output. I got
excellent help from this list regarding handling this
issue. Now I run pdfjadetex directly with png's only.
--
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto
"Peace, Love, and Linux" -- IBM
next prev parent reply other threads:[~2001-04-26 12:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-21 14:35 Peter Toft
2001-04-21 14:39 ` Mark Galassi
2001-04-21 14:45 ` Peter Toft
2001-04-21 15:35 ` Tim Waugh
2001-04-21 17:48 ` Edward C. Bailey
2001-04-22 1:05 ` Peter Toft
2001-04-24 13:17 ` Edward C. Bailey
2001-04-26 10:26 ` Wookey
2001-04-26 12:00 ` Peter Toft [this message]
2001-04-27 12:01 ` Peter Toft
2001-04-30 2:22 ` Wookey
2001-04-26 11:47 ` Peter Toft
2001-04-26 11:54 ` Edward C. Bailey
2001-04-26 15:05 ` Hugo van der Kooij
2001-04-26 17:34 ` Edward C. Bailey
2001-04-29 8:15 ` Hugo van der Kooij
2001-04-26 3:04 ` 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.30.0104262058570.12130-100000@pto.sslug \
--to=pto@sslug.dk \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=ed@redhat.com \
--cc=wookey@aleph1.co.uk \
/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).