Re: Running Prefligh PDF tools on PDF files produced by FOP
Matthew Brook O'Donnell schrieb: I've found that FOP 0.20.1 and 0.20.2 produce PDFs that do not cause a 'fatal PDF error' in PitStop, even without the modification of (_data.size() + 1) to _data.size() in the PDFStream class that Hansuli proposed. However, I haven't been able to produce PDF that pass with 0.20.3 (even with the proposed patch). [..] Were there significant change in the PDF output classes between 0.20.2 and 0.20.3? As already mentioned the following bug sounds suspect: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9054 Matt O'Donnell Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Running Prefligh PDF tools on PDF files produced by FOP
We are planning to move to FOP .20.3. Is there a version with the fixes in it to solve all these problems? Jim Urban - [EMAIL PROTECTED] Park City Solutions Inc. Clinical Connectivity Suite Product Manager Suite 295 500 Park Blvd. Itasca, IL 60143 Voice: (630) 250-3045 x106 Fax: (630) 250-3046 CONFIDENTIALITY NOTICE This message and any included attachments are from Park City Solutions Inc. and are intended only for the entity to which it is addressed. The contained information is confidential and privileged material. If you are not the intended recipient, you are hereby notified that any use, dissemination, or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error please notify the sender of the delivery error by e-mail or call Park City Solutions Inc. corporate offices at (435) 654-0621 -Original Message- From: J.U. Anderegg [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 3:49 PM To: [EMAIL PROTECTED] Subject: AW: Running Prefligh PDF tools on PDF files produced by FOP Matthew Brook O'Donnell schrieb: cause a 'fatal PDF error' in PitStop, even without the modification of (_data.size() + 1) to _data.size() in the PDFStream class that Hansuli proposed. However, I haven't been able to produce PDF that pass with 0.20.3 (even with the proposed patch). [..] Were there significant change in the PDF output classes between 0.20.2 and 0.20.3? As already mentioned the following bug sounds suspect: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9054 Christian It is this bug: inserts of Tc into the PDF stream Hansuli Anderegg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Running Prefligh PDF tools on PDF files produced by FOP
I've found that FOP 0.20.1 and 0.20.2 produce PDFs that do not cause a 'fatal PDF error' in PitStop, even without the modification of (_data.size() + 1) to _data.size() in the PDFStream class that Hansuli proposed. However, I haven't been able to produce PDF that pass with 0.20.3 (even with the proposed patch). I am still pursuing the nature of the 'fatal error' with Enfocus. Apparently these errors frequently occur when PostScript is inserted in various PDF objects - something that the spec allows, but shouldn't since it prevents the file from being printer-agnostic. I can understand what that means, but do not know how it relates to PDF render in FOP, or whether this is causing the reported problem. Were there significant change in the PDF output classes between 0.20.2 and 0.20.3? Matt O'Donnell - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Running Prefligh PDF tools on PDF files produced by FOP
Attached is the FO for a simple PDF. All the pdf is contains is the text hello world. I am using FOP 0.20.3 to create my PDFs. With Enfocus Pitstop (Win), I get an error of Fatal PDF error on page 1 when I try to process the file. When I try to open the PDF in Illustrator 8 9 (Mac), I get an error of Acrobat PDF File Format is having difficulties. Bad Parameter. However, I can open the file up fine in Photoshop 5.5 6 (Mac) and Flightcheck 3.73 (Mac). Matt Johnston Manager of Internet Content American Profile, http://www.americanprofile.com 341 Cool Springs Blvd., Ste. 400 Franklin, TN 37067 p: 615-468-6053 f: 615-468-6153 -Original Message- From: J.U. Anderegg [mailto:[EMAIL PROTECTED]] Sent: Friday, May 24, 2002 4:46 AM To: [EMAIL PROTECTED] Subject: AW: Running Prefligh PDF tools on PDF files produced by FOP Matt, Matthew, can you send me a sample doc in error - as small as possible? I will have a look at it. Hansuli Anderegg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] preflight_crash.fo Description: Binary data - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Running Prefligh PDF tools on PDF files produced by FOP
I have run into the exact same problem. I have personally tried Pitstop and had the same error occur. Other people that have several industrial strength preflight tools said that the PDFs I made out of FOP crashed all their programs. The only preflight program I can get to read the PDF is Flightcheck. Plus, certain versions of Photoshop(5.0) and Illustrator(8,9) also do not like the file format, while Acrobat Reader reads them fine. This is a problem that I too would like to see solved. Matt Johnston Manager of Internet Content American Profile, http://www.americanprofile.com 341 Cool Springs Blvd., Ste. 400 Franklin, TN 37067 p: 615-468-6053 f: 615-468-6153 -Original Message- From: Matthew Brook O'Donnell [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 23, 2002 3:32 PM To: [EMAIL PROTECTED] Subject: Running Prefligh PDF tools on PDF files produced by FOP I'm using FOP to produce PDF eBook files targeted for Adobe eBook Reader. It produces beautiful output, with internal links for the contents etc. These files can be viewed in both Acrobat and the eBook Reader without error. However, most eBook distributors place requirements upon submitted files and make checks with various preflight packages. PitStop by Enfocus (http://www.enfocus.com/products/overview.php?nr=3) is one of the most common tools used for this purpose. I am finding that for all PDFs produced by FOP (including those from the sample FO files) PitStop stops and complains of a 'Fatal PDF Error' on the first page. It does not provide anymore information than this. I am not experiencing the same errors with PDF files produced by XEP or Antenna. I realize that this query may be more appropriately targeted to Enfocus. However, any insights or help would be much appreciated. Regards Matt O'Donnell Publishing Dimensions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Running Prefligh PDF tools on PDF files produced by FOP
Matt, Matthew, Maybe you could try generating the most minimal possible PDF file which still crashes the preflight programs. Use the same fo: source file in XEP and Antenna and compare the output. Send these PDF files to Enfocus ior Adobe for comment. If someone there can tell us exactly what constructs are causing the problem, we will have a target. Peter Matt Johnston wrote: I have run into the exact same problem. I have personally tried Pitstop and had the same error occur. Other people that have several industrial strength preflight tools said that the PDFs I made out of FOP crashed all their programs. The only preflight program I can get to read the PDF is Flightcheck. Plus, certain versions of Photoshop(5.0) and Illustrator(8,9) also do not like the file format, while Acrobat Reader reads them fine. This is a problem that I too would like to see solved. -Original Message- From: Matthew Brook O'Donnell [mailto:[EMAIL PROTECTED]] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
