Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Current »

Because the %SeparationVersion% tag is composed of names of the versions to which it applies, this file name component can be very long. Thus, we recommended that version names be as short as possible, especially if you have many versions in your job. See the example below.


Imposition separation output file name example for AFP

Before shortening file names:
You have four versions for which you use the following version names: Vancouver, Toronto, Montreal, and Calgary.
If you have a separation that applies to the Vancouver, Toronto, and Montreal versions, the separation name becomes Vancouver_Toronto_Montreal. The output file name would be the following if you are using the Prinergy-defined file naming:
Impo_8pg_W&T.Vancouver_Toronto_Mo.1A.K.1.pdf (44 characters)

After using custom file naming to limit the imposition and SeparationVersion components each to 9 characters,
%imposition<9>%.%SeparationVersion<9>%.%signature%%surface%.%color%.%dotversion%.%extension%
the file name is:
Impo_8pg_.Vancouver.1A.K.1.pdf (30 characters)

However, this name does not indicate that the separation also applies to the Toronto and Montreal versions.

After shortening version names:
If you use the version names: Va, To, Mn, and Ca, the imposition separation output file name would be:
Impo_8pg_.Va_To_Mt.1A.K.1.pdf (29 characters)
This output file name now indicates all the versions to which it applies.

  • No labels