We use FOP for generating different PDF documents. Several of our clients are not able to print one special type of these documents right after downloading them. The error message is kind of "Document could not be printed. Print job could not be started" (translated from German). It is possible after the document was saved. We could not yet reproduce the error. The XSL templates for the corresponding PDF doesn't seem to contain anything suspicious that is not contained by XSL templates for other PDFs. Does anyone has an idea what problem may be responsible for this behaviour?
I don't think this is FOP-related; we just create the PDF. I think your problem is with the Acrobat Reader. Do you see anything in common with those clients which aren't having a problem and anything in common with those who are? (i.e., browser type, version of AR on the client, etc.) Does the same problem occur if you send a PDF not made by FOP? If so, you may want to try the Acrobat site for help. Glen
(In reply to comment #1) > I don't think this is FOP-related; we just create the PDF. I think your > problem is with the Acrobat Reader. Do you see anything in common with those > clients which aren't having a problem and anything in common with those who > are? (i.e., browser type, version of AR on the client, etc.) > Does the same problem occur if you send a PDF not made by FOP? If so, you may > want to try the Acrobat site for help. > Glen Hi Glen, thanks for the immediate reply. You are right. We found out, that the problem is indeed an AR problem. The filenames of the generated documents are generated, too, and for some types of PDFs they become very long. Obviously there some AR versions which cannot handle printing of a document which such a long filename. At that point it also makes sense that printing after saving works. The user probably would have chosen a much shorter filename. Thank you, Stephan
batch transition to closed remaining pre-FOP1.0 resolved bugs