I managed to compile the trunk but haven't tested it yet. PDFs getting created by FOP 0.95 are showing as v1.4.
I did have some errors in using FOP to send output directly to a printer (it sent to wrong printer, or wrong paper tray), so I worked around it by using FOP's PDF Mime on the format with the direct print Mime for the output which created output in PDF format but sent it to the ByteArrayOutputStream instead of a PDF file. I used that output as input to Apache's pdfbox program which converts it to document format which is able to be printed from the java.awt.print.PrinterJob using javax.print.PrintService. Pdfbox can also be used to create a PDF file, or read in a PDF file. If fop trunk can't create a PDF v1.5, maybe pdfbox can? -----Original Message----- From: Craig Ringer [mailto:[email protected]] Sent: Wednesday, June 23, 2010 9:36 AM To: [email protected] Cc: Mario Madunic Subject: Re: Compression of output question On 23/06/10 21:16, Mario Madunic wrote: > More info, > > While talking to a colleague we are going to run a test by removing all links. There are 17000+ links in the new workflow and around 500 in the old. We think this could be the issue and not an SVG thing. > > Any thoughts or insight? If links are the issue, you really need to generate PDF 1.5 with compressed object streams. PDF 1.5's object streams feature was primarily designed with things like links and other numerous annotations in mind. No idea if fop can do that, but if not there are post-processing options that can convert a PDF to use object streams without any degradation of quality. -- Craig Ringer --------------------------------------------------------------------- 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]
