Important: Use page name patterns to match refined page names; not to match
input file names. For example, the single page input file,
RC_English.pdf
becomes
RC_English.p1.pdf
after refining.
Wild cards
The following wild cards are supported:
●
#—match numbers
●
%—match letters
●
$—match letters and/or numbers
Wild card rules
●
All wild cards must be enclosed in square brackets. For example,
[#]
●
You can use one or more wild cards in a page name pattern.
Important: Although the pattern matching wild cards are very similar to that used
in APA (Advanced Production Automation), you cannot use the APA Editor in
Prinergy to create the pattern matching expressions for LPV. You must use the
version plan.
Page name pattern errors
If no refined pages match the page name pattern, the refine process
completes, the refined pages are added to the
Pages
view, but
versioned pages are not created, and the refined pages are not linked.
After a failed auto-linking process, do one of the following to link your
refined pages:
●
Fix the page name pattern
—After correcting the page name
pattern, perform a minimal rerefine to apply automatic linking.
Ensure that the
Build Versioned Pages
check box (
Normalize
pane)
is selected in the refine process template.
●
Link refined pages to versioned pages manually
Names of automatically created versioned pages
When using page name patterns without back references, versioned
pages that are automatically created are named with the ‘VP’ prefix.
For example, versioned page one is named
VP_1.pdf
.
If you use back references, you can define the versioned page name
prefix.
Page name pattern examples
The following examples illustrate the results of different page name
patterns.
1008
Chapter 19—Versions
