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]