2
1
0

Is it a true statement that FillForceFront / Back is illegal when imposition process and <Layout> is not automated, since the layout defines the front and back? If so and it appears in a JDF, should it be rejected with JDF/Schema validation or ignored at run time?

    CommentAdd your comment...

    2 answers

    1.  
      1
      0
      -1

      I agree with what you say, hence the question/clarification, but if FillForceFront / Back appears with <Layout> and @Automated False, should the function simply be ignored or should processing/printing be aborted (I am not sure what JDF standard processing behavior should be when illegal JDF combinations are detected)?

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

        Once you have a Layout that is non-automated, all @Ord references of the ContentObjects are normative and thus FillForceFront / Back has no effect.

        With LayoutPreparation, this is a different story since LayoutPreparation effectively fills the Layout/ContentObject/@Ord values and needs to take RunList FillForceFront / Back into account to correctly do so.

        Any mismatch in a modified ticket that subsequently contains a Layout would thus simply be inconsistent data.

          CommentAdd your comment...