** Maintenance of all services taking place on Saturday June 22, from 18:00 - 21:00 (GMT+2) **
 
2
1
0

With modern finishing equipment , time is saved when a sheet contains two signatures that first get one common fold, then cut in two, and then each assembly goes its own way (same content or different content).

Web presses did this already in the past but now also used for sheet fed.

Not easy to define with JDF.

Create a very specific FoldCatalog using SignatureCells where the same pages may occur more than one time? But then it is not possible to specify that these become two assemblies that each have a separate AssemblyIDs.

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      This is quite similar to the description of imposition for coming and going, which we have punted on for quite some time.

      The only currently viable solution is to explicitly create a set of grid (NOT FoldingCatalog) very explicit BinderySignatures.

      The general problem is that we are overloading BinderySignature with two aspects for BinderySignature/@Type="FoldCatalog":

      1.) the final (in this case post cutting) signature that is fed to the binding equipment. It contains one page per surface.

      2.) the folding sheet that gets folded (in this case pre cutting). It may contain more than one page per surface.

      this works fine fore the 90% case that we have one page per folded surface.

      Since the Assembly describes the final finished/bound product it always has to receive the one page per surface BinderySignatures.


      Possible solutions (to be discussed). Add a reference to the neighboring BinderySignatures - similar to the references for Foldout pages. Note - there is no reason to limit to a single final cut - there can be multiple)

      That needs to somehow include the orientation (e.g. flipped for coming and going).


      See https://jira.cip4.org/projects/JDF/issues/JDF-648 for further discussions

        CommentAdd your comment...