Sv translation | ||
---|---|---|
| ||
DCS is inherently a separated format, and, as such, in most workflows you can't trap it. The system can recomposite DCS use OPI to recombine separated DCS files that are referenced in composite PostScript by using OPI. OPI-ing a DCS in composite PostScript is desirable because the system recomposites the DCS on OPI into the composite page, allowing you to use trapping. In order for Prinergy Evo to recomposite the DCS, in the Refine to PDF process template dialog box, Normalize section, select the Do OPI Image Replacement check box and in the Search Path Order box, define the OPI replacement search paths. If you do not enable OPI replacement, Prinergy Evo produces a low-resolution preview if one exists in the DCS control file. Note: You don't necessarily always want to trap DCS; , particularly if the DCS files are copydot or otherwise pre-screened. In that case you never want to trap them. However, if your linework DCS contains linework, 1-bit, continuous tone, or vector information and you want to trap the DCS files against other page content, for example, type or linework elements, recompositing the DCS enables you to trap the separated input. See also Copydot scans and other DCS files | Bookmark173_concept2683__section_50DBA24 |
...
Sv translation | ||
---|---|---|
| ||
DCS es un formato separado y, como tal, no es posible solaparlo en la mayoría de los flujos de trabajo. El sistema puede volver a recomponer DCS a partir de PostScript compuesto por medio de OPI. | Bookmark173_concept2683__section_50DBA24 | Copydot scans and other DCS filesBookmark173_concept2683__section_50DBA24