default (Prinergy-defined) file names for output use the following
patterns:
For loose page proofs
%page%.%SeparationVersion<20>%.%signature%%surface%.%color%%dotversion%
%extension%
For imposition proofs and final output
%imposition%.%SeparationVersion<20>%.%signature%%surface%.%color%%dotversion%
%extension%
where,
%SeparationVersion%
is composed of the names of the versions
to which the separation applies.
For example, if a separation applies to the English and French versions,
but not the Spanish version, the file name component would be
English_French. Thus, a possible output file name would be
1VP_1.English_French.1A.K.1.pdf
, which is exactly 31
characters long.
%dotversion%
is a number that indicates the instance of the file
among files of the same name. The most recent file does not have a
dotversion component, for example,
1VP_1.common.1A.K.pdf
.
A higher dotversion number indicates an older instance. For example,
1VP_1.common.1A.K.2.pdf
is older than
1VP_1.common.
1A.K.1.pdf
.
For definitions of other components in the file name, see the Prinergy
Workshop online help.
Output file name best practices
If you are using Prinergy-defined file naming when outputting to file,
ensure that the 20 character limit on the
%SeparationVersion%
tag is sufficient for your output.
If you are using custom file naming when outputting to file, we
recommend that you use the
%dotversion%
tag to ensure that
output files are not accidently overwritten.
Note: If you rename a version, ensure that you regenerate all versioned pages that
have already been linked and generated.
Output file name best practices for AFP
If you use Apple Filing Protocol (AFP) and are outputting to file, you
must use custom file naming to ensure that filenames are 31 characters
or less.
Layered PDF Versioning
1003
