cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Pietschmann <>
Subject Re: pdf problem
Date Mon, 30 Dec 2002 20:42:47 GMT
On Monday 30 December 2002 15:34, you wrote:
> In case of PDF-creation, Acrobat is starting to load the file but then a
> window pops up saying: "The file is damaged and could not be repaired".

Most probably the problem is caused by an unhandled exception
during PDF rendering, causing the error apge generator to kick in.

General hints for debugging this kind of problem:
1.) Save the file to disk instead of open it in IEx. Try to open the
asved file in Acrobat Reader. If this works, the problem is with your
IEx configuration.
2.) Search the Cocoon logs for log entries related to the URl for the
document. Look if there are exceptions.
In case of generating PDF, you'll also have to examine the stdout
and stderr log of the servlet container, the serializer writes a few
problem diagnostics there (a long standing bug).
3.) If there are problems logged (or even if there aren't any), check
whether your file(s) work with command line processors.
3a) Run your XML+XSL through the command line application
from Xalan or Saxon. This will tell you whether there are problems
with your source XML or the style sheet.
3b) Run the resulting FO file through the FOP command line application.
This will tell you whether there are problems with PDF rendering. Try
to open the generated PDF with Acrobat Reader.

BTW your problem is here:
      <fo:conditional-page-master-reference master-name="page"
The XSLFO spec has been changed between the final CR (apparently
used by your book) and the final RC, replace "master-name" with
"master-reference" (and get a more recent book).


Please check that your question  has not already been answered in the
FAQ before posting.     <>

To unsubscribe, e-mail:     <>
For additional commands, e-mail:   <>

View raw message