Mark
Description
$[SeparationVersion]
On all separations, this mark is replaced with the
names of the versions to which the separation
contributes. 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.
Note: This mark may be replaced with different text on
different separations. This means that once a printed
page is produced from the separations, the text will
overprint each other, for example,
. To avoid this,
use $[SeparationVersion_Offset].
$[SeparationVersion_Offset]
This mark is the same as $[SeparationVersion] except
that it is offset on different separations so that the
marks do not overprint each other once a printed page
is produced.
$[SeparationVersionUnique]
This mark is replaced with the name of the version to
which it contributes if the separation is unique to only
one version. For example, if a separation contributes to
only one version, this mark is replaced with the version
name. If a separation contributes to two versions, this
mark is replaced with an empty space.
$[SeparationVersionCommon]
On common separations (separations used in all
versions), this mark is replaced with the word
‘common’. On separations that are not used in all
versions, this mark is replaced with an empty space.
$[SeparationVersionNoCommon]
On non-common separations, this mark is replaced
with the names of the versions to which it applies. For
example, if a separation contributes to the English and
French versions, but not the Spanish version, the file
name component would be English_French. On
common separations, this mark is replaced with an
empty space.
Note: This mark may be replaced with different text on
different separations. This means that once a printed
page is produced from the separations, the text will
overprint each other, for example,
. To avoid this,
use $[SeparationVersionNoCommon_Offset].
$[SeparationVersionNoCommon_Offset]
This mark is the same as $
[SeparationVersionNoCommon] except that it is
offset on different separations so that the marks do
not overprint each other once a printed page is
produced.
Prinergy-defined output file names
When you output to file, for example, when creating soft proofs, ensure
that the output file names are unique and meaningful. In LPV jobs, the
1002
Chapter 19—Versions
