1
0
-1

If DigitalPrintingParams @PageDelivery was specified in partitions where there are RunIndex ranges, is it applied to each range, or just one for the whole job? The spec talks about turning the whole stack upside down etc. and does not reference if PageDelivery was specified in partitions turning ranges upside down. If it is only allowed in the parent, it should be noted in the spec that it is an error to specify it in a partition.

    CommentAdd your comment...

    3 answers

    1.  
      1
      0
      -1

      I agree that this would be an exception to standard behavior.  It would seem possible that some implementation could support this at the page range level, so why add words trying to prevent it?  It seems like there are so many, many types of partitioning that can be done in so many places, that only some subset of the partitioning possibilities (maybe even a small subset?) will ever be supported by a given implementation.

        CommentAdd your comment...
      1.  
        1
        0
        -1

        I would interpret the same, but a spec needs to be clear and this would be an exception to standard JDF behavior (since with standard JDF behavior, a parent keyword populates to children and should normally be applied on/by the child page range). If it is the intended behavior (whichis what I have implemente), there should be an error condition if a RunList exists that is not for the whole job and PageDelivery (other than SameOrderFaceDown - the default) is specified either at the parent or at the child.

          CommentAdd your comment...
        1.  
          1
          0
          -1

          I would interpret the spec to mean it would apply to the whole job, not per range.  My main reasoning is from this comment in the Notes: 

          these values refer to the orientation of the entire stack
          being output from the press, not individual sheets.

            CommentAdd your comment...