1
0
-1
  1. Rainer Prosi

    @Carl somehow you omitted the file in this question

  2. Carl Van Rooy

    XJDF file attached, see questions in the file.

    Regards

    Book_Test_20201001.xjdf

  3. Carl Van Rooy

    Hello rainer,

    Is it possible to discuss the topics? Can we do a zoom meeting ?

    I like to clear some issues together with Ton Gerrits (canon).

    Thank you

    Kind regards

    Carl


CommentAdd your comment...

5 answers

  1.  
    2
    1
    0

    <!-- 170x240mm book; use @FinishedDimensions in case the cover is designed for a specific book thickness? →

    See same answer for the entire book

    <!-- How to indicate that inside of cover needs not be printed with the empty page in the PDF? Via resource, as below? →

    leave ot the 2nd (empty page) and set LayoutIntent/@Sides="OneSided"

    <!-- If input PDF contains page for inside of cover; how to avoid that this is being printed in the BookBlock?→

    <!-- More general: how to define the intent of which PDF page comes where in the product? -->

    <!-- ==> can I somehow refer to the RunListIn part r1 here? -->

    See runlist examples above (or below depending on what confluence decides...)


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

      <!-- ==>Is actually the front for front and back for back. Use front only (meaning outside)? ==>is Matte also for laminates? →

      Front is defined as the outside of a wraparound cover and back as the inside. We had long discussions whether to clarify that in the spec and in the end decided it was unnecessary.

      Matte can also be used for laminates


      Note the typo in your example

      <Product Amount="1" ID="ICover" IsRoot="false" ProductType="WrapAroundCover">

      <Intent Name="CoverLaminatingIntent">

      <BindLaminatingIntent Surface="Front" Texture="Matte"/>

      </Intent>

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

        <!-- ==> Full bleed not just for the end product but specifically also in the book block because I want bleed tabs. How? →

        If you want really large bleed for tabs, you should specify it explicitly, but see also BindingIntent/Tabs for more details on tabs.

        <!-- ==> can I somehow refer to the RunListIn part r2 here? →

        In XJDF 2.1 Part/@ProductPart was deprecated and replaced with Part/@Product. You should provide Product/@ExternalID and use that in Resource/Part/@Product (see Q1)


        1. Carl Van Rooy

          I do not see any reference to bleed in Tabs in BindingIntent/Tabs. How/where should intent for full bleed tabs be defined?

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

        Q2.)

        <!-- ==>How to define the desired position of the scores?-->

        The positions of the scores are assumed to be calculated from the spine width. If you need detailed control, you will have to add a CoverApplication process and the respective ResourceSet/@Name="CoverApplicationParams" with the Score elements.

        <!-- ==>Via Creasing one must define in scope of end product. XJDF distinguishes here between creasing from front or back but not for the crease on front and back part of the book. →

        Intent typically defines the 90% case. If you want asymmetrical scoring, you will again need to provide a CoverApplication process and the respective ResourceSet/@Name="CoverApplicationParams" with the Score elements.


        1. Carl Van Rooy

          Has it been attempted to define intent more precise, up to 100%? Why, and what happened? Or why not?

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

        Q1.)

        <!--test intent description of a left bound perfect bound book with bleed tab info in the book block.

        input PDF assumed:

        134 pages:

        1st = preimposed outside of the book cover.

        2nd = blank

        3rd-134 = 132 book block pages;

        page 3(134) first(last) page of bookblock

        ==>where must I specify this to guarantee correct book block (so correct page on correct leaf)?

        and can that also be done intentwise for multiple input files (e.g. separate PDF for cover and block)?

        -->


        Answer 1.)

        All indexing and thus page order is defined in the RunList and not the pdf. Thus the number of pdfs is irelevant. In case you have multiple pdfs per <Product> RunList/Part/@Run would also have to be specified.

        In your example, it would look like:

        Note that a single pdf with a mix of spread and no-spread is messy and will probably not be correctly processed by simple digital printers.

        Single pdf:

        <ResourceSet Name="RunList" Usage="Input">
        <Resource>
        <Part Product="Cover">
        <RunList Pages="0 1" NPage="2">
        <FileSpec URL="file:///indir/file.pdf"/>
        </RunList>
        </Resource>
        <Resource>
        <Part Product="Body">
        <RunList Pages="2 133" NPage="132">
        <FileSpec URL="file:///indir/file.pdf"/>
        </RunList>
        </Resource>
        </ResourceSet>

        Single pdf with only one page printed for the cover:

        <ResourceSet Name="RunList" Usage="Input">
        <Resource>
        <Part Product="Cover">
        <RunList Pages="0 0" NPage="1">
        <FileSpec URL="file:///indir/file.pdf"/>
        </RunList>
        </Resource>
        <Resource>
        <Part Product="Body">
        <RunList Pages="2 133" NPage="132">
        <FileSpec URL="file:///indir/file.pdf"/>
        </RunList>
        </Resource>
        </ResourceSet>

        separate pdf (note the modified pages, which refernce into the pages of the pdf:

        <ResourceSet Name="RunList" Usage="Input">
        <Resource>
        <Part Product="Cover">
        <RunList Pages="0 1" NPage="2">
        <FileSpec URL="file:///indir/coverspread.pdf"/>
        </RunList>
        </Resource>
        <Resource>
        <Part Product="Body">
        <RunList Pages="0 131" NPage="132">
        <FileSpec URL="file:///indir/body.pdf"/>
        </RunList>
        </Resource>
        </ResourceSet>

        Note also that you can define a simplex cover and then only provide a single spread page for the cover.

        You have correctly provided LayoutIntent/@SpreadType - very important if you are working in mixed mode.

        1. Carl Van Rooy

          Already did in the “CoverLayoutIntent”. Or should it also be done in the Runlist?

        CommentAdd your comment...