From: Tim Waugh <twaugh@redhat.com>
To: Peter Toft <pto@sslug.dk>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: Red Hat 7.0 PNG problem
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <20001111123950.D16038@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011110034280.2243-100000@pto.sslug>
On Sat, Nov 11, 2000 at 12:35:36AM +0100, Peter Toft wrote:
> On Wed, 11 Oct 2000, Peter Toft wrote:
>
> > I wanted to try the new Red Hat 7.0 with the DocBook
> > tools in there - it seems that the db2html stuff is
> > working fine, but generating db2pdf jams, due to PNG
> > images:
Could you send me (not the list) a DocBook document and db2pdf command
line that causes this problem?
Thanks,
Tim.
*/
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6DT4WONXnILZ4yVIRAttlAJ9bXDRPBkyHOt8tGAaxJ440CAIGaQCfYSkm
g2S6yCf+1o0QOUya+tzhP9Y=
=hMum
-----END PGP SIGNATURE-----
WARNING: multiple messages have this Message-ID
From: Tim Waugh <twaugh@redhat.com>
To: Peter Toft <pto@sslug.dk>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: Red Hat 7.0 PNG problem
Date: Sat, 11 Nov 2000 04:39:00 -0000 [thread overview]
Message-ID: <20001111123950.D16038@redhat.com> (raw)
Message-ID: <20001111043900.szndgW7suSgFHbhM25qLYilmiNPDwwaYe8t8LnN9cd4@z> (raw)
In-Reply-To: <Pine.LNX.4.21.0011110034280.2243-100000@pto.sslug>
On Sat, Nov 11, 2000 at 12:35:36AM +0100, Peter Toft wrote:
> On Wed, 11 Oct 2000, Peter Toft wrote:
>
> > I wanted to try the new Red Hat 7.0 with the DocBook
> > tools in there - it seems that the db2html stuff is
> > working fine, but generating db2pdf jams, due to PNG
> > images:
Could you send me (not the list) a DocBook document and db2pdf command
line that causes this problem?
Thanks,
Tim.
*/
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6DT4WONXnILZ4yVIRAttlAJ9bXDRPBkyHOt8tGAaxJ440CAIGaQCfYSkm
g2S6yCf+1o0QOUya+tzhP9Y=
=hMum
-----END PGP SIGNATURE-----
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 .pdf generation error using the "newer" tools Bill Brooks
2000-10-10 21:52 ` Bill Brooks
2000-12-27 6:36 ` Eric Bischoff
2000-10-11 4:53 ` Eric Bischoff
2000-12-27 6:36 ` Red Hat 7.0 PNG problem Peter Toft
2000-10-11 12:24 ` Peter Toft
2000-12-27 6:36 ` Peter Toft
2000-11-10 15:36 ` Peter Toft
2000-12-27 6:36 ` Tim Waugh [this message]
2000-11-11 4:39 ` Tim Waugh
2000-12-27 6:36 ` Peter Toft
2000-11-11 15:18 ` Peter Toft
2000-12-27 6:36 ` Tim Waugh
2000-11-13 2:11 ` Tim Waugh
2000-12-27 6:36 ` Peter Toft
2000-11-13 10:48 ` Peter Toft
2000-12-27 6:36 ` Tim Waugh
2000-11-13 13:21 ` Tim Waugh
2000-12-27 6:36 ` Peter Toft
2000-11-13 13:53 ` Peter Toft
2000-12-27 6:36 ` .pdf generation error using the "newer" tools Bill Brooks
2000-10-11 15:28 ` Bill Brooks
2000-12-27 6:36 ` Eric Bischoff
2000-10-12 4:54 ` 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=20001111123950.D16038@redhat.com \
--to=twaugh@redhat.com \
--cc=docbook-tools-discuss@sources.redhat.com \
--cc=pto@sslug.dk \
/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).