RE: FW: Postscript Error when RIPing document created with FOP
Hi Clay I updated the Jar files to 0.20.4 and still no solution. I have yet to try 0.20.5rc. Patrick -Original Message- From: Clay Leeds [mailto:[EMAIL PROTECTED] Sent: Friday, 7 February 2003 9:09 AM To: [EMAIL PROTECTED] Subject: Re: FW: Postscript Error when RIPing document created with FOP Patrick, I don't have a solution for you, but I'd suggest trying with fop-0.20.4 and 0.20.5rc to be certain it wasn't something that was resolved. Cheers, Web Maestro Clay Patrick Branley wrote: > -Original Message- > From: Patrick Branley > Sent: Thursday, 6 February 2003 3:20 PM > To: '[EMAIL PROTECTED]' > Subject: Postscript Error when RIPing document created with FOP > > Hi > > I have PDF document created with FOP that I sent to Xerox Docucolor > 2060 using a Scitex Spire RIP that failed with the following error: > >>>>Type Date&TimeStage Message >>>>Error Message Feb 05, 11.06.06 Process General postscript error. >>>>Please preview the job to ensure file validity. >>>> >>>>Type Date&TimeStage Message >>>>Error Message Feb 05, 11.06.06 Process %%[Error: syntaxerror; >>>>OffendingCommand: bin obj seq, type=128, elements=1, size=45318, >>>>non-zero unused field]%%| > > Initially I thought the problem was further on in the process with a > later step in our application where the file is merged with another > PDF using PDFLib, however sending just the pure FOP PDF and not the > PDFlib merged PDF still causes this error. However Thomas Merz at > pdflib gave me this information > >>This is a rarely used PostScript feature called "binary object >>encoding". I wonder which component in your workflow generates it? Do >>you print through Acrobat or send the PDF to the RIP directly? In the >>latter case I'll speculate that the RIP internally translates PDF to >>binary PostScript, and for some reason this conversion fails, and >>produces something which should be considered an internal error >>message. Type=128 is a floating point number, but size=45318 is >>definitely too much data for a float; This suggests that some data >>portion is severly messed up. > > There are no images in this file, just text using some embedded type 1 > fonts. The File was created with fop 0.20.4rc. Any suggestions on how > to solve this ? > > The printer has a workaround by first distilling the file in Acrobat > and then resending it to the RIP, but this affects their workflow and > we plan to send a large number of files to them per year so this isn't > a viable option. > > Any help would be greatly appreciated. > > Cheers, > > Patrick Branley > Systems Engineer > E-BisPrint Pty. Ltd. > www.ebisprint.com -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FW: Postscript Error when RIPing document created with FOP
Patrick, I don't have a solution for you, but I'd suggest trying with fop-0.20.4 and 0.20.5rc to be certain it wasn't something that was resolved. Cheers, Web Maestro Clay Patrick Branley wrote: -Original Message- From: Patrick Branley Sent: Thursday, 6 February 2003 3:20 PM To: '[EMAIL PROTECTED]' Subject: Postscript Error when RIPing document created with FOP Hi I have PDF document created with FOP that I sent to Xerox Docucolor 2060 using a Scitex Spire RIP that failed with the following error: Type Date&TimeStage Message Error Message Feb 05, 11.06.06 Process General postscript error. Please preview the job to ensure file validity. Type Date&TimeStage Message Error Message Feb 05, 11.06.06 Process %%[Error: syntaxerror; OffendingCommand: bin obj seq, type=128, elements=1, size=45318, non-zero unused field]%%| Initially I thought the problem was further on in the process with a later step in our application where the file is merged with another PDF using PDFLib, however sending just the pure FOP PDF and not the PDFlib merged PDF still causes this error. However Thomas Merz at pdflib gave me this information This is a rarely used PostScript feature called "binary object encoding". I wonder which component in your workflow generates it? Do you print through Acrobat or send the PDF to the RIP directly? In the latter case I'll speculate that the RIP internally translates PDF to binary PostScript, and for some reason this conversion fails, and produces something which should be considered an internal error message. Type=128 is a floating point number, but size=45318 is definitely too much data for a float; This suggests that some data portion is severly messed up. There are no images in this file, just text using some embedded type 1 fonts. The File was created with fop 0.20.4rc. Any suggestions on how to solve this ? The printer has a workaround by first distilling the file in Acrobat and then resending it to the RIP, but this affects their workflow and we plan to send a large number of files to them per year so this isn't a viable option. Any help would be greatly appreciated. Cheers, Patrick Branley Systems Engineer E-BisPrint Pty. Ltd. www.ebisprint.com -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FW: Postscript Error when RIPing document created with FOP
-Original Message- From: Patrick Branley Sent: Thursday, 6 February 2003 3:20 PM To: '[EMAIL PROTECTED]' Subject: Postscript Error when RIPing document created with FOP Hi I have PDF document created with FOP that I sent to Xerox Docucolor 2060 using a Scitex Spire RIP that failed with the following error: >>>Type Date&TimeStage Message >>>Error Message Feb 05, 11.06.06 Process General postscript error. >>>Please preview the job to ensure file validity. >>> >>>Type Date&TimeStage Message >>>Error Message Feb 05, 11.06.06 Process %%[Error: syntaxerror; >>>OffendingCommand: bin obj seq, type=128, elements=1, size=45318, >>>non-zero unused field]%%| Initially I thought the problem was further on in the process with a later step in our application where the file is merged with another PDF using PDFLib, however sending just the pure FOP PDF and not the PDFlib merged PDF still causes this error. However Thomas Merz at pdflib gave me this information > This is a rarely used PostScript feature called "binary object > encoding". I wonder which component in your workflow generates it? Do > you print through Acrobat or send the PDF to the RIP directly? In the > latter case I'll speculate that the RIP internally translates PDF to > binary PostScript, and for some reason this conversion fails, and > produces something which should be considered an internal error > message. Type=128 is a floating point number, but size=45318 is > definitely too much data for a float; This suggests that some data > portion is severly messed up. There are no images in this file, just text using some embedded type 1 fonts. The File was created with fop 0.20.4rc. Any suggestions on how to solve this ? The printer has a workaround by first distilling the file in Acrobat and then resending it to the RIP, but this affects their workflow and we plan to send a large number of files to them per year so this isn't a viable option. Any help would be greatly appreciated. Cheers, Patrick Branley Systems Engineer E-BisPrint Pty. Ltd. www.ebisprint.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
