Product

Platform

Operating system

Error

Symptoms

You get some DCS files from a Rampage system and want to process them with Prinergy. The Rampage files have been output as a multi-file DCS set, that is, separated. You run into problems with the files when you attempt to process them in non-bypass mode.

Cause

Solution

IT IS STRONGLY RECOMMENDED THAT IF YOU NEED TO PROCESS RAMPAGE FILES THAT YOU USE THE POSTSCRIPT BYPASS FEATURE.

The PostScript Bypass feature is described in the document "Prinergy 1.1: Changes to the Normalizer", which is posted to the Technical Procedures section of the Prinergy 1.1 Technical Library site's Learning Center page (http://intranet.creo.com/support/html/workflow/prinergy/v1-1/learning.htm#tech_procedures). Note that this document is intended for an internal audience only.

The PostScript Bypass feature must be set up by a CreoScitex person; it cannot be configured by the customer.

The quick description of how to configure this feature is to edit the customer's %ARAXIHOME%\AdobeExtreme\bin\NormInputConfig (make sure you back it up first) ON ALL PRINERGY SERVERS and add the following lines to the end of the file:

# RAMPage DCS output

target RAMPage DCS

%%Creator: ~= RAMpage DCS Export

@bypass

NOTE: Prinergy Normalizer has been changed to anticipate Rampage DCS files in 2.0.7. In many cases, it is no longer necessary to bypass Rampage content. However, we have seen some Rampage pages which will still drop elements on output, even with the fix.

Additionally, artifacts can still occur when not Bypassing Rampage files. Therefore, in general, it is still recommended to bypass Rampage DCSes.

Permanent fix: Prinergy 2.0

See also

Keywords

file formats

Technical contact(s)

James Bredenhof

Submitted by

Date submitted