Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space PREPS and version 9.0

...

This is a Preps 9.0.2 limitation only. There have been no reports of these messages causing spoilage.

Workaround: Click OK.

...

Page Mark properties are not retained when saved with legacy anchor positions in Preps 9.0.0 or 9.0.1.

This is a Preps 9.0.2 limitation only for impositions using some Page Marks created/edited in previous versions of Preps 9.0.0 or 9.0.1.

Workaround: To retain legacy mark positions from Preps 9.0.0 or 9.0.1, add “-RETAINLEGACYANCHORMARK:YES” to the "PrepsPrinergy.cfg.template" profile located on the Prinergy server.

Instructions: Setting Integrated Preps preferences - We recommend updating with a Windows text editor (eg. Notepad ++).

Please Note:

In most cases, “-RETAINLEGACYANCHORMARK:YES” is a viable solution. But, it has been reported that some Page Marks are shifted in Preps 9.0.2 and on VPS Output. For example, in one known case, Page Marks anchored to the Binding Edge on the back of the Signature with “-RETAINLEGACYANCHORMARK:YES” can inadvertently move the mark into the content area. Please check your VPS carefully. We are addressing these issues in Preps 9.5 (scheduled for early 2022 release).

...

When you use "Odd" or "Even" keywords in the SmartMark Range field, the mark will be applied only for the first press run.

...