DDAP PPD Project Disclaimer Even when using the DDAP PPD, with the recommended Print Drivers and procedures for application programs, there still can be problems with creating Postscript files that will process correctly. This is because the PPD and the Printer Driver affect only a small portion of the data in the Postscript file; the rest being generated by the page layout application itself. Nevertheless, if inappropriate information is embedded in the prolog or setup of the Postscript file, it can make the Postscript file unusable. The primary goal of this project was to develop a "universal" PPD file that does not contain device specific features and select recommended Printer Drivers, and finally, to develop procedures for application programs that will minimize any problems with creating a "good" file. The scope of this project was not to eliminate every Postscript error that could occur in a file. For example, even with the use of the DDAP PPD with the recommended procedures, an EPS file could still be included which may contain PostScript data or fonts that have problems, or conditional attributes which could cause errors at any point in the process. However, it is our belief that by creating a "universal" PPD with recommended Printer Drivers and developing instructions for applications, the "mechanics" of creating the file can be standardized and the process of sending digital files will be greatly improved. Today, many publishers have created their own custom PPD file, and an agency, or its prepress service provider must use these PPD files to create a PostScript file. It is our hope that adopting and using the DDAP PPD file and procedures would make the sender's task of creating a PostScript file simpler by allowing all recipients to specify one PPD file in their digital specifications. Of course, good preflighting and file checking is important in any Postscript workflow. The DDAP PPD with the recommended drivers and applications instructions are not designed to eliminate the critical function of preflighting files. The DDAP Association recommends that preflight be performed by both the sender of a digital file and by the receiver of the digital file. It is the responsibility of all parties to use this information in the way it is intended. Often additional specifications will be included that would specify other attributes that have to be adhered to when creating the files. These attributes can included image types (i.e. TIFF or EPS, no PICT or GIF); color space (i.e. CMYK only, no RGB -- unless paid-for, all spot colors have to be converted to process); font types (i.e. Type 1 fonts only, do not include TrueType fonts or use any font substitutions) and compression (i.e. use ZIP-8-bit only, do not use JPEG). Please be aware that trim and bleed sizes vary across magazines, so please check before the file is made to ensure it conforms to all of the recipient's requirements. The DDAP Association recommends that the file's image size be made larger than the trim and bleed size and actual trim and bleed marks be included along with agency information and a colorbar.
|