Generating user docs

[Rick Hillegas <Ri...@Sun.COM>]

I am having trouble generating the postscript versions of most of our 
user docs. I can generate html and monohtml versions for all user 
guides. I can also generate postscript versions of the Reference and 
Tuning guides. However, I'm having trouble generating postscript 
versions of the other docs.

For instance, when I try to build the postscript version of the 
Developer's guide (ant -quiet pdf.devguide), I get a directory 
(out/devguide) with a derbydev.fo file and several gifs. But no .pdf file.

Would appreciate advice on what I am doing wrong.

Thanks,
-Rick

Re: Generating user docs

[Stanley Bradbury <St...@gmail.com>]

Rick Hillegas wrote:

> I am having trouble generating the postscript versions of most of our 
> user docs. I can generate html and monohtml versions for all user 
> guides. I can also generate postscript versions of the Reference and 
> Tuning guides. However, I'm having trouble generating postscript 
> versions of the other docs.
>
> For instance, when I try to build the postscript version of the 
> Developer's guide (ant -quiet pdf.devguide), I get a directory 
> (out/devguide) with a derbydev.fo file and several gifs. But no .pdf 
> file.
>
> Would appreciate advice on what I am doing wrong.
>
> Thanks,
> -Rick
>
Had a similar problem building the new doc I am working on - I believe 
it was caused by lines in a <codeblock> being too long.  The html build 
fine but the PDF created only the .fo file.  I modified the <codeblock> 
examples so the line were at most 60 char. (I picked this arbitrarily - 
might be able to be longer) and the doc built fine.

Re: Generating user docs

[Andrew McIntyre <mc...@gmail.com>]

On 3/3/06, Rick Hillegas <Ri...@sun.com> wrote:
>
> For instance, when I try to build the postscript version of the
> Developer's guide (ant -quiet pdf.devguide), I get a directory
> (out/devguide) with a derbydev.fo file and several gifs. But no .pdf file.
>
> Would appreciate advice on what I am doing wrong.

Hard to tell without an error, but clearly FOP is having some trouble.
Are there any obvious errors from FOP in the non-quiet ant output? Try
running with -verbose and make sure the call to FOP is actually
happening.

andrew