🚀 go-pugleaf

Dov,

I have to respectfully disagree on the performance aspect. I've
documented and submitted examples of substantial performance
differences in printing to the printer instance connected to the FILE
port and distilling vs. printing to the printer instance connected to
the Adobe PDF Port vs. using Save As PDF. I've seen this happen
through various versions of the products (FM and Acrobat) on different
machines, so it's not just a simple user/configuration issue. In an
automated workflow where (tens of) thousands of pages are being
produced on a regular basis, this is a real PITA.

There's something in the Adobe PDF Port that doesn't always play nice
and really slows things down to a crawl when creating the .(t)ps file.
I agree that logically, there shouldn't be a difference, but
factually, there is. 

Is there another explanation that you can shed some light on for the
differences in processing times that Janice has seen?

As an aside, for print production from FM, the SaveAsPDF route
triggers the "Generate Acrobat Data" option and embeds all sorts of
unnecessary crap that bloats both the postscript and resulting PDFs
which also adds a load to the processing. The latest incarnation in
FM9 for CMYK sounded good in theory, but so far is still very rough
around the edges and not quite ready for prime-time.

Any way you slice it, SaveAsPDF from FM is still a kludge until FM
gets the ability to natively generate the PDFs like other Adobe apps.