Thread

making pdf of docs

Dennis Björklund <db@zigo.dhs.org> — 2004-10-26T15:05:33Z

Is there something wrong that makes it impossible to build the doc as a 
pdf?

I started a build 4 hours ago, and it has still not finished (stuck at
100% CPU on my old 800Mhz 1G RAM machine).

I know that openjade is very slow so for the first 3 hours I didn't worry.
Now I'm starting to think that it will never finish.

-- 
/Dennis Björklund

Re: making pdf of docs

Kris Jurka <books@ejurka.com> — 2004-10-26T15:27:39Z

On Tue, 26 Oct 2004, Dennis Bjorklund wrote:

> Is there something wrong that makes it impossible to build the doc as a 
> pdf?

My experience is that the latest openjade crashes.  The latest jade takes 
about 10 days on an Athlon 1600, but I can build it in a very reasonable 
timeframe with an older version of jade.

Well scratch that.  I just checked the jade versions and they are
identical, perhaps different sytlesheets or something?  For now all I know
is that it works on debian stable, but takes forever on unstable.  I'll 
have to do some more investigating to try and find the real difference.

Kris Jurka

Re: making pdf of docs

Mike Mascari <mascarm@mascari.com> — 2004-10-26T15:34:56Z

Dennis Bjorklund wrote:
> Is there something wrong that makes it impossible to build the doc as a 
> pdf?
> 
> I started a build 4 hours ago, and it has still not finished (stuck at
> 100% CPU on my old 800Mhz 1G RAM machine).
> 
> I know that openjade is very slow so for the first 3 hours I didn't worry.
> Now I'm starting to think that it will never finish.

I've never tried building PDF from PostgreSQL DocBook source. However, 
in other DocBook documents, I've found that if there is an embedded 
image that is too large to fit on a single page, various PDF renderers 
will paginate the image onto the next page, discover it is too large to 
fit on the next page, generate a page break, and the process continues 
ad infinitum.

Maybe a recent large image was added to the docs?

FWIW,

Mike Mascari