Re: Postscript Error when RIPing document created with FOP
Sorry for the delay. I've looked up that private discussion with Claes Bergsten. The theory is that that particular Xerox PDF RIP has a bug in the PDF to PostScript conversion which causes the subsequent PostScript RIP to choke on PDF XObjects (which are normally used to hold images). You don't seem to have exactly the same problem. As Victor suggested I'd contact technical support for the PDF RIP and ask them to analyze the problem. Either they can fix their bug or give us a pointer for us to find out what we're possibly doing wrong. On 11.02.2003 07:16:58 Jeremias Maerki wrote: I'm late for the show, sorry. I'd like to point you to a discussion I had with Claes Bergsten. I think he had the same problem (also on a Xerox RIP). We two had a private exchange then (so not the whole discussion is in the archive, I'll have to dig up the content of my old company account), but I haven't had the time then to really track it down and fix it. I'll have a look at it today, maybe I can come up with something. http://marc.theaimsgroup.com/?t=10238870541r=1w=2 On 11.02.2003 01:29:26 Victor Mote wrote: If anybody else recognizes this problem, please feel free to jump in. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Postscript Error when RIPing document created with FOP
Patrick Branley wrote: The RIP can accept a PDF file, which then im assuming converts it to postscript before output. If you open a PDF in Acrobat with distiller set up as a printer device you can print a PDF to another PDF file. Using this process the new PDF file will pass through the RIP with no problems. OK, that helps a bit. Here is how I would like to proceed: 1. Upgrade to 0.20.5rc (you said you were on 0.20.4rc in a previous posting) see whether you get the same results. Even if so, at least we can compare results with current code. This is generally a good rule to follow, as I doubt that any of the developers want to take the time to debug fix something that has already been debugged fixed. If this does not solve the problem, continue to step 2. 2. Open the original PDF file in Acrobat, and Save As PostScript. Send this PostScript file to your printer, and see whether they can handle it properly. If so, then there is probably a problem on their end, with whatever process their machine uses to convert PDF to PostScript. Otherwise, continue to step 3. 3. Distill the PostScript created in step 2 using Acrobat Distiller. Between steps 2 3, we have done (I think) the same thing that the PDF to PDF conversion does, but have broken it down. I therefore expect the Distill to finish successfully (please let me know if not) to create a new PDF. Send this PDF to the printer. Again, I would expect this to succeed (again, let me know if not). The question now becomes why their PostScript interpreter chokes on code that Distiller successfully distills. I would pose that question to your printer for them to take up with the device manufacturer. There are a bunch of interesting things we could do to troubleshoot the whole thing, which you can try (diffing the two PDF files, diffing the two PostScript files), but the likely result (absent other information or similar stories with other devices interpreters) is that their PostScript interpreter has a bug in it (or uses an incompatible version of PostScript) it would be difficult to justify the expense of proving this. In your previous posting you said: --- Start --- 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. --- End --- This suggests another possible workaround, which is that /you/ could do the PDF to PDF conversion before sending it to the printer. That would at least be a short-term fix that wouldn't affect their workflow. Another workaround to explore is to output PostScript from PDF see if it works better. If anybody else recognizes this problem, please feel free to jump in. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Postscript Error when RIPing document created with FOP
Victor Mote wrote: be a short-term fix that wouldn't affect their workflow. Another workaround to explore is to output PostScript from PDF see if it works better. Sorry, this should say output PostScript from FOP. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Postscript Error when RIPing document created with FOP
The RIP can accept a PDF file, which then im assuming converts it to postscript before output. If you open a PDF in Acrobat with distiller set up as a printer device you can print a PDF to another PDF file. Using this process the new PDF file will pass through the RIP with no problems. Patrick Branley -Original Message- From: Victor Mote [mailto:[EMAIL PROTECTED] Sent: Saturday, 8 February 2003 2:16 AM To: [EMAIL PROTECTED] Subject: RE: Postscript Error when RIPing document created with FOP Patrick Branley wrote: 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: ... 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. Hmmm. We're missing something here. When you say that your printer distilled the file in Acrobat, where did the printer get the PostScript code to do that job? Distiller is itself a PostScript device, so it should choke on the file the same way that the RIP does. If both PostScript devices (Distiller your RIP) are using the same input, then the RIP PostScript implementation is suspect. If they are using different input, then we need to know more about the tools that are being used to convert the PDF to PostScript. Victor Mote - 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: Postscript Error when RIPing document created with FOP
Patrick Branley wrote: 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: ... 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. Hmmm. We're missing something here. When you say that your printer distilled the file in Acrobat, where did the printer get the PostScript code to do that job? Distiller is itself a PostScript device, so it should choke on the file the same way that the RIP does. If both PostScript devices (Distiller your RIP) are using the same input, then the RIP PostScript implementation is suspect. If they are using different input, then we need to know more about the tools that are being used to convert the PDF to PostScript. Victor Mote - 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 DateTimeStage Message Error Message Feb 05, 11.06.06 Process General postscript error. Please preview the job to ensure file validity. Type DateTimeStage 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]
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 DateTimeStage Message Error Message Feb 05, 11.06.06 Process General postscript error. Please preview the job to ensure file validity. Type DateTimeStage 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]
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 DateTimeStage Message Error Message Feb 05, 11.06.06 Process General postscript error. Please preview the job to ensure file validity. Type DateTimeStage 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]
