Brisque 3.0.38 and 4.0 does not protect CopyDot images after Merge


Product		Brisque 3.0.38 Update CD2 and Brisque 4.0
Platform		Version 3.0.38: E30 - Victory 43P-140 - Tiger1 43P-150 - Tiger2 F50 - Wildcat (2 and 4 CPUs) Version 4: E30 - Victory 43P-140 - Tiger1 43P-150 - Tiger2 F50 - Wildcat (2 and 4 CPUs) 44P-170 - Hammerhead 6F1 - Condor (2,4 and 6 CPUs)
Operating system		IBM AIX 4.2.1 or IBM AIX 4.3.3

Symptoms		In a pre-separated workflow using CopyDot files—for example: drag and drop a pre-separated PostScript file onto a template that contains RIP, Merge, and FAF parameters. CopyDot images in the file will not be protected after the Merge operation, and the images may be FAFed.

Cause		Merge does not retain all the protection comments the RIP applied. This is a known Brisque limitation. The following RIP and FAF parameters: Small Text Protection, White Frame Protection and Black Overprint, and Copy Dot Image (Prevent Trapping) are not available for, or do not apply on merged Jobs.

Solution		When saving the file in the desk top publishing application, save the file as a composite file.

Technical contact(s)		Viki Bar-On
Submitted by		Viki Bar-On
Date submitted		19 Aug 2001