Spending a few moments to prepare your files before bringing them to DPA can make all the difference. DPA takes pride in being able to work with just about any form of digital artwork however, applying a few simple principles when setting up your file will help simplify the process of preparing and, ultimately, delivering your job on time.

include a PDF file if possible

Today's print workflow systems are dependent on Acrobat PDF files, so there's a fair chance that we will convert your native document into PDF format for printing. You can speed up the prepress process by supplying a print ready PDF file with your job, since if it meets our requirements we will use the supplied PDF as art, rather than the native files.

PDF's should be made to the 'High Quality', 'Press Quality' or especially 'PDF/X-1a 2001' standard, and include bleeds and crops. Color Management options should be set to 'Color Unchanged', as this will preserve the document as you created it. We'll apply the necessary colour management options as part of the print process.

Even if your PDF is not to print standard, it will make a great visual reference for the integrity of the native files. Please be sure to check that the included PDF looks correct before sending it in - if there are any problems with your job they'll show up on the PDF.

It's also a good idea to set your Acrobat Pro or Reader (depending on which version you have - we recommend v8 for both) to always display using 'Overprint Preview' - some transparency features like InDesign drop shadows do not display correctly in Acrobat unless this is turned on.

Adobe Acrobat Distiller is the best method of creating PDF's if your design application can not do it natively. If you don't have Distiller, a free PDF converter is available from http://www.pdf995.com - it works like a physical printer, however it outputs to a PDF file instead of paper.

always supply the resource files

Supply all linked images (ie placed TIFF's, PSD's, EPS's, etc.) fonts and final laserproofs. Many modern design applications have a 'Collect for Output' function which can automate this process for you. In most cases this is sufficient, however there are cases where these functions do not completely collect every required file. We recommend that you follow up a 'collect' with this checklist before sending in your files.

• Check the links list of your document to ensure that all the images are included. Most design applications have a 'Links' palette or 'Usage' window which list all the placed files in the design file. Ensure that you've included all the listed files. Any files that are tagged 'PB' in the list can be safely ignored, as they have been placed on the pasteboard of the document and are not required for output.
• Check EPS files for nested images. Some EPS files require additional linked images, which usually do not show up in the Links palette. If any of your placed EPS have nested linked images, be sure to include them. This is mainly an issue for older EPS files - most EPS's created with current software will embed the nested images in the file.
• Check the font list of your document to ensure that all fonts are included. Most design applications have a 'Find Fonts' or 'Usage' window which list all the used fonts in the design file. Ensure that you've included all the listed fonts. The 'Collect' functions are well known for missing non-roman font styles, eg. bold, italic, bold-italic, and only copying the roman font file. These missing styles will need to be copied manually from your system font folder.
• Check that all required files for the type of font are present. Depending on your computer operating system and the type of fonts used, an individual font may consist of one or several files - all of which need to be provided. The document's application font list will usually display the type of font used for any specific font. Use the table below to identify the type of font and how many files will be needed for it.

OS	font type	notes	icon
Windows	TrueType	1 file per font style, suffix is .ttf. Icon appears as two capital T's - one grey and one blue.
	OpenType	1 file per font style, suffix is .otf. Icon appears as a green and black capital O.
	PostScript Type 1	2 files per font style, suffixes are .pfb and .pfm. PFM files have an icon of a red lowercase A. PFB files usually don't have a specific icon. Names are usually heavily truncated eg. HLVBD__.pfm
MacOSX	TrueType	1 file per font style, suffix is often .ttf. Icon appears with the letters TTF at the bottom of the icon. Its kind is described as 'Truetype font'.
	OpenType	1 file per font style, suffix is often .otf. Icon appears with the letters OTF at the bottom of the icon. Its kind is described as 'OpenType font'.
	D-Font	1 file per font style, suffix is. dfont. Icon appears with the letters DFONT at the bottom of the icon. Its kind is described as 'Datafork TrueType font'.
	PostScript Type 1	These can vary. Commonly there is one screen font suitcase file shared between all font styles. Icon appears with the letters FFIL at the bottom of the icon. Its kind is described as 'Font Suitcase' and usually has the font family name as the filename. Occasionally there is one font suitcase file for each font style. In addition there is 1 extra file for each font style. Its kind is described as 'PostScript Type1 outline font'. The icons vary but they are often branded with the font foundry or have the letters LWFN at the bottom. Names are usually condensed versions of the font style names.