xmlgraphics-fop-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Leeds <cle...@medata.com>
Subject Re: FW: Postscript Error when RIPing document created with FOP
Date Thu, 06 Feb 2003 22:08:31 GMT
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: 'fop-user@xml.apache.org'
> 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&Time        Stage   Message
>>>>Error Message Feb 05, 11.06.06 Process General postscript error.
>>>>Please preview the job to ensure file validity.
>>>>
>>>>Type          Date&Time        Stage   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 - cleeds@medata.com
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org


Mime
View raw message