[reportlab-users] PDFs generated by ReportLab not printing

King Simon-NFHD78 simon.king at motorola.com
Fri May 22 05:31:07 EDT 2009

> -----Original Message-----

> From: reportlab-users-bounces at reportlab.com

> [mailto:reportlab-users-bounces at reportlab.com] On Behalf Of

> Andy Robinson

> Sent: 21 May 2009 13:12

> To: Support list for users of Reportlab software

> Subject: Re: [reportlab-users] PDFs generated by ReportLab

> not printing


> 2009/5/21 King Simon-NFHD78 <simon.king at motorola.com>:

> >

> > Unfortunately, I can't reproduce the error myself. Does

> anyone know of

> > any tools for analysing PDF files that might help in

> tracking down the

> > problem?


> I'm told that one should use Acrobat Professional, which has a

> "pre-flight tool". This is something Adobe bought from Callas

> Software which checks hundreds of things printers have been known to

> have problems with in the past.


Hi Andy,

Thanks a lot for getting back to me. I generated two PDFs from our
application, 1 using the patched version of Reportlab, and the other
using an unpatched version (2.2), and asked the user who was having
problems to try printing both. He reported that he was unable to print
either of them, so that implies that the problem is probably not due to
my patch, and is either in Reportlab itself, or in the way we use it.

It turns out that we have an old version of Acrobat Professional (v6) in
the office, so I ran the preflighting tool on the PDF generated using
the unpatched version of Reportlab. It reported 3 problems:

1. Device process color used but no OutputIntent (253 matches on 2
2. Font not embedded (and text rendering mode not 3) (4 matches on 2
3. Metadata entry missing

I don't know how serious any of these errors are. I can post both the
problematic PDF and the preflight report if you like, or if a 269Kb
attachment is not suitable for the list I can send it to you directly.

Thanks again for your help,


More information about the reportlab-users mailing list