Page tree
Skip to end of metadata
Go to start of metadata

Refining is a Prinergy Evo process that includes normalizing, spot color mapping, color matching, overprint conversion, and trapping to convert input files into safe, reliable PDF files ready for printing. Since refined PDF files are complete and already have all fonts and images embedded, there are no external files or pieces to manage.

The refine to PDF process template requires you to normalize and optimize your files. As a result, Normalize is always enabled in a refine to PDF process template and cannot be disabled. The other four sections in the refine to PDF process template are optional.

Prinergy Evo can refine the following input file formats: PostScript, EPS, DCS, and PDF Brisque CT/LW, and TIFF/IT-P1, and TIFF. When you refine files, you select a refine to PDF process template that contains predetermined settings, activated by a series of JTPs (job ticket processors).

Although Prinergy Evo supports TIFF/IT-P1, CT/LW (generated by Brisque software or PS/M 5 and later), and "handshake pages" (from PS/M 4 and earlier, and other sources) during refining, it does not handle other forms of these files. You must convert types of CT/LW and TIFF/IT files to PostScript before you input them to Prinergy Evo. Various third-party tools or the PDF2Go function of the Brisque software can do this.

The refine to PDF process template determines how Prinergy Evo handles the following:

  • Brisque CT/LW or TIFF/IT-P1 input files
  • Images and fonts for PostScript and PDF input files
  • Spot colors in input files
    The Spot Color Handling, Match Colors, and Overprint Conversion sections of a refine to PDF process template define how Prinergy Evo handles spot colors and overprints, and uses ICC profiles to transform color data from the input color space to the output color space.
  • Information necessary to map, match, and convert color data from the input color space to the output color space
  • Trapping in input files
  • Optimizing images in input files

What is the output from refining?

When the system refines input files, it can create either a single PDF file, which contains multiple pages, or a PDF file of each page in the input file. Prinergy Evo stores the PDF files in either the <hot folder name>/Processed folder, the same folder as the source PostScript file, or in a specified folder location.
When the system refines a multi-page input file, it creates either a single PDF or, if specified, splits the input file by page and names the PDF files it creates as follows: filename.p0001.pdf, where p0001 is the page number. This enables you to sort your pages in numeric order. For example, if the two-page file test.ps is refined, the system creates the following two files: test.p0001.pdf and test.p0002.pdf. If the same file is rerefined, the system overwrites the original PDF files: test.p0001.pdf and test.p0002.pdf.

When do I re-refine input files?

You may want to re-refine files in two circumstances:

  • You want to re-refine input files using a different process template. In this case, simply select a new process template and submit the input files again.
  • You want to re-refine PDF pages to do color mapping.

When you re-refine PDF pages, the system preserves any page geometry values that you set using the Prinergy Geometry Editor plug-in.

How does Prinergy Evo handle font and OPI replacement?

The image search path specifies the location of the high-resolution images for the file. Prinergy Evo uses the image search path when images for the process are not embedded in the input file.

When Prinergy Evo processes a file and detects missing fonts, it automatically looks in the path specified in the Normalizer section, Font Search Path box. Prinergy Evo only uses the font search path when a file is missing fonts.

When the fonts or images for an input file are located in two or more folders, you must add a search path for each folder you want Prinergy Evo to search. Then you must specify the order in which you want Prinergy Evo to search the folders. You do not need to set a font path when fonts are embedded in input files.

  • No labels