1
0
-1

We’re looking for a solution to provide PartVersions with different number of pages. For example the English brochure has 16 pages body and the German one has 20 pages body. As I understood versioning requires the same count of pages. I once heard the term ‘editions’ for this requirement.

Especially for the integration to prepress systems we need the ability to provide the information which pages and plates are the same in both versions and which are different. Also not every BinderySignature belongs to each PartVersion.

Can this somehow be handled with PartVersions, or is there a more handy solution?

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      JDF has no explicit restrictions on the usage of PartVersion only for black plate changes. Thus PartVersion can be used for any type of versions including varying page counts.

      That is the purist theoretical answer. Whether actual implementations make (incorrect) assumptions on the structure of versioned jobs and thus fall flat on their face, if you provide such a job is a different subject....

      In JDF, BinderySignatures are folding dummies anyhow and essentially can be mixed and matched as desired.

      Note again - this is the theoretical answer.

      It would probably be a lot safer to make one job per edition and use JDF/@ProjectID to group multiple editions. (Unless you actually want to reuse content over editions)

        CommentAdd your comment...