Product

• Prepare 2.1
• Prepare Pro 2.1
• Prepare 2.0
• Prepare Pro 2.0

Platform

Macintosh

Operating system

Mac OS X

Error

It looks like the name of the imported Print Style differs from the name of the file containing this Print Style.

Symptoms

The error message above appears when the name of the Adobe InDesign Print Style does not match the saved name that Prepare uses. Multiple copies of the InDesign Print Preset are generated in the user’s copy of InDesign.

Cause

When you make and save an InDesign Print Style to Prepare Pro, you must be careful when naming the Print Style. There are two “saves” that are done for an InDesign Print Preset, one to InDesign and the other to Prepare. The names of the two must be identical.

On the first save to InDesign, you name the Print Preset, after which the name appears in the Print Presets window (for example, Prepare InDesign Preset). You must then export the Print Preset to Prepare, into the particular Directive Vendor set in the InDesign Print Preset folder. When you save the Print Preset to Prepare, the Save dialog box changes the Print Preset name to Saved Print Presets.prst. You must remove the .prst extension and change the name of the Print Preset to be identical to the name that you gave it in InDesign (in our example, Prepare InDesign Preset). If the .prst extension is included in the file name, the InDesign plug-in will present the error message above and will then generate a copy in the InDesign Print Preset window.

When using imported Directives and the InDesign plug-in in Prepare (not Prepare Pro), printers must ensure that any updated InDesign Print Presets have the same names as what already exists in the Print Preset folder. Mismatches will cause the same behavior as described above.

Solution

Ensure the InDesign Print Preset names match exactly. Since it appears that InDesign does not use the .prst extension internally, it is best to remove the extension when saving the Print Preset to Prepare.

Technical contact(s)

Todd Belcher

Submitted by

Todd Belcher

Date submitted

01 Feb 2006