From: Bill Brooks <wbrooks@lug.ee.calpoly.edu>
To: Eric Bischoff <ebisch@cybercable.tm.fr>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: .pdf generation error using the "newer" tools
Date: Wed, 11 Oct 2000 15:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10010111047290.19560-100000@lug.calpoly.edu> (raw)
Message-ID: <20001011152800.jBlBMYHsXkK1C2yPFU8BEmHu_UiRr5HRb9_CrrbxlnA@z> (raw)
In-Reply-To: <39E45487.12751DB0@cybercable.tm.fr>
On Wed, 11 Oct 2000, Eric Bischoff wrote:
> The two -c and -d flags should not be necessary. But they ensure you use
> "bare bones" Norman Walsh's stuff, and not our default stylesheet.
Okay, I tried it again by just using the docbook2pdf helloworld.docbook
and still ran into some problems. Here's what I get with the same
helloworld document:
docbook2pdf helloworld.docbook
Using catalogs: /etc/sgml/sgml-docbook-3.0.cat
Using stylesheet:
/usr/share/sgml/docbook/utils-0.5.5/docbook-utils.dsl#print
Working on: /home/wbrooks/box/work/foo/helloworld.docbook
This is pdfTeX, Version 3.14159-13d (Web2C 7.3.1)
(Fatal format file error; I'm stymied)
So it looks like the correct version of the DTD and stylesheets are
getting used for this document, but it can't get pdfTeX to even begin
generating a .pdf file.
> If you volunteer to update the web pages, to me you're welcome ;-).
> Mark?
Absolutely, I can either mail a patch to the existing web page or change
something in a CVS repository somewhere.
> TeX classical problem. The default configuration files do not allow
> enough resources for docbook.
> [...]
>
> I think we have a corrected version on the web site. Attached is also a
> patch we use at KDE.
My texmf.cnf file is substantially different than yours so applying the
patch failed. Can you send the whole file? Thanks in advance.
Bill
next prev parent reply other threads:[~2000-10-11 15:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 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
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 ` Bill Brooks [this message]
2000-10-11 15:28 ` .pdf generation error using the "newer" tools Bill Brooks
2000-12-27 6:36 ` Eric Bischoff
2000-10-12 4:54 ` Eric Bischoff
2000-12-27 6:36 Alan W. Irwin
2000-12-02 19:17 ` Alan W. Irwin
2000-12-27 6:36 ` Alan W. Irwin
2000-12-02 22:58 ` Alan W. Irwin
2000-12-27 6:36 ` Bill Brooks
2000-12-08 18:16 ` Bill Brooks
2000-12-27 6:36 ` Eric Bischoff
2000-12-09 3:49 ` Eric Bischoff
2000-12-27 6:36 ` Tim Waugh
2000-12-09 3:56 ` Tim Waugh
2000-12-27 6:36 ` Mirko Streckenbach
2000-12-13 1:32 ` Mirko Streckenbach
2000-12-27 6:36 ` Eric Bischoff
2000-12-13 2:45 ` Eric Bischoff
2000-12-27 6:36 ` Alan W. Irwin
2000-12-08 19:39 ` Alan W. Irwin
2000-12-27 6:36 ` Eric Bischoff
2000-12-09 4:05 ` 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.10.10010111047290.19560-100000@lug.calpoly.edu \
--to=wbrooks@lug.ee.calpoly.edu \
--cc=docbook-tools-discuss@sources.redhat.com \
--cc=ebisch@cybercable.tm.fr \
/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).