Getting on the PDF Transit Bandwagon -- Waldman
The Transit Story
A number of factors make up the compelling story for PDF Transit. First, printers have become victims of clients taking over more and more of what we used to do. The profits are gone, but the blame isn’t. The customer sets the type, does the color separations, assembles the page and then sends the printer a bad file, which becomes the printer’s problem.
For years we’ve heard that a PDF workflow was eventually going to be the answer. But it was only the answer for printers with contract clients or repetitive jobs, which enabled client education so that the distilling process was controlled by the printer. For the rest of us, a PDF still meant bad files that were harder to fix. Plus, more and more, the quick turnaround and lower pricing of on-demand printing exacerbates the problem.
And, of course, there’s the rapid growth of Internet-based jobs that promises to be the dominant client submission method in the very near future. All this is leading to a rapid, automated workflow that could come to a screeching, expensive halt with bad files or very unhappy clients who received unexpected results.
PDF Transit solves these problems very nicely because you, the printer, have absolute control over the way the PDF is distilled by your client. In fact, the PDF can only be distilled one way—your way—because the client gets the custom-packaged PDF maker from your Web server.
In essence, PDF Transit is a PDF workflow that works; the PDF creation component in PDF Transit is the same core distiller software Acrobat uses to produce an Adobe PDF. The key difference is that you customize the PDF Transit client software and distribute it to your customers with your branding and distiller job options. Let’s take a look at how all of this happens.