{"id":201,"date":"2010-09-01T10:37:30","date_gmt":"2010-09-01T05:07:30","guid":{"rendered":"http:\/\/www.cvr.cc\/?p=201"},"modified":"2010-09-01T10:37:30","modified_gmt":"2010-09-01T05:07:30","slug":"pdfpagediff","status":"publish","type":"post","link":"https:\/\/cvr.cc\/?p=201","title":{"rendered":"Pdfpagediff"},"content":{"rendered":"

We often encounter nightmarish scenario while generating final versions of a long document when one or more of the following happens:<\/p>\n

    \n
  1. New revised versions of packages used.<\/li>\n
  2. Smaller changes to a fewer number of pages of a long document. <\/li>\n
  3. No change in the document, but recompiled with revised page numbers as it happens during compilation of journal articles into an issue for printing.<\/li>\n
  4. Simply you happened to re-typeset for no reason and then you’re forced to check each page for surprises.<\/li>\n<\/ol>\n

    Now you are left with the job of comparing the PDF<\/small>s generated now and that of previous version and it is not fun. pdgpagediff<\/code> package helps to make your job easier.<\/p>\n

    Principles<\/h4>\n

    We have a version of document, say, file1.pdf<\/code> and we have its revised version, file2.pdf<\/code>. pdfpagediff<\/code> will create a composite PDF<\/small> by juxtaposing each page of file1.pdf<\/code> over the corresponding page of file2.pdf<\/code> or vice-versa. Since the PDF<\/small>s are transparent, you can notice the slightest change visually by simply flipping through the pages.<\/p>\n

    Dependencies<\/h4>\n

    pdfpagediff<\/code> depends on the following packages:<\/p>\n

      \n
    1. geometry.sty<\/code><\/li>\n
    2. graphicx.sty<\/code><\/li>\n
    3. color.sty<\/code><\/li>\n
    4. substr.sty<\/code><\/li>\n<\/ol>\n

      Package loading and commands<\/h4>\n

      Package can be loaded with the following command:<\/p>\n

        \\usepackage{pdfpagediff}<\/pre>\n
      Another command \\layerPages<\/code> has been defined to include two versions of the PDF<\/small> documents to create the composite document, the syntax is:<\/p>\n
        \\layerPages[<optional page numbers>]{<file1>}{<file2>}<\/pre>\n
      First one doesn’t have an optional argument of page numbers, which means all the pages will be used to create the composite document. Second one has comma separated page numbers and hyphen separated page ranges which can be mixed in any order as shown in subsequent examples of usage. The last one has 10-<\/code> which means from page 10<\/code> to end of the document.<\/p>\n
        \n
      1.  \\layerPages{file1.pdf}{file2}<\/code><\/li>\n
      2.  \\layerPages[1,2,4-6,8]{file1}{file2.pdf}<\/code><\/li>\n
      3.  \\layerPages[1,2,4-6,8,10-22]{file1.pdf}{file2.pdf}<\/code><\/li>\n
      4.  \\layerPages[1,2,4-6,8-13,17]{file1}{file2.pdf}<\/code><\/li>\n
      5.  \\layerPages[10-]{file1.pdf}{file2.pdf}<\/code><\/li>\n<\/ol>\n
        You need Adobe Reader to view the composite document which only provides to view each layer or all layers together or no layers at all.  There is a small layer button at top left hand side of the Adobe Reader window, see the figure below:<\/p>\n
        \"Composite<\/a>
        Clipping from the composite document.<\/figcaption><\/figure>\n
        You can see Layers<\/code> icon, clicking on the icon will show you the layers.  We have two layers in this example, namely, First<\/code> and Second<\/code> which are also the default.  These labels can be changed with FirstDoc<\/code> and SecondDoc<\/code> commands respectively.<\/p>\n
        First Document<\/h5>\n
        \"First<\/a>
        Clipping from the first document.<\/figcaption><\/figure>\n
        The above clipping shows the first document alone. You might note that icon for second layer is not visible now.<\/p>\n
        Second Document<\/h5>\n
        \"Second<\/a>
        Clipping from second document.<\/figcaption><\/figure>\n
        The second document is generated with 30% gray instead of black to facilitate easy indication of locations with differences. Also, note that icon for first layer is invisible since the second layer alone is made visible here.<\/p>\n
        You might take a look at composite document<\/a> which has a paragraph from the composite document. The last word of the paragraph has a mismatch. Now let us take a look at the last two lines of the above para from the first document<\/a> and the same location of the second document<\/a>. The difference is a space added before the last word \u2018concepts\u2019. If you look at the composite document now, you will get to know the difference quickly.<\/p>\n
        Further differences can be observed in pages 9 and 17 of the included document ltest.pdf<\/code>.<\/p>\n
        Limitations<\/h4>\n
        Following limitations apply:<\/p>\n
          \n
        1.  Documents with enormous changes cannot be compared.<\/li>\n
        2.  Documents with opaque backgrounds cannot be compared.<\/li>\n
        3.  Tables and figures with background will not provide any  meaningful information even if there are differences.<\/li>\n
        4.  This is not a character by character or word by word diff  program, instead it depends largely on your eyes very much.<\/li>\n
        5.  \\pdfpagediff<\/code> will work only with PDF<\/small>Te<\/span>X and will not work with  any other Te<\/span>X compilers.<\/li>\n<\/ol>\n
          Acknowledgments<\/h4>\n
          The test document is a chapter namely, Matrix manipulation<\/em>, taken from a freely available textbook, Matrix Overview<\/em> by Paul Hewson<\/a>, at: http:\/\/knowledgeforge.net\/opentextbook\/svn\/multivariatestatistics\/<\/a>. Permission to use this chapter to demonstrate the features of pdfpagediff<\/code> is gratefully acknowledged.<\/p>\n
          Download<\/h4>\n
          The package can be downloaded from http:\/\/download.river-valley.com\/cvr\/pdfpagediff-1.2.tar.gz<\/a>. Bug reports, feature requests and suggestions can be posted here in the comment box.  The author can be contacted at <cvr@river-valley.org><\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
          We often encounter nightmarish scenario while generating final versions of a long document when one or more of the following happens: New revised versions of packages used. Smaller changes to a fewer number of pages of a long document.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[31,15],"tags":[],"class_list":["post-201","post","type-post","status-publish","format-standard","hentry","category-pagediff","category-tex"],"_links":{"self":[{"href":"https:\/\/cvr.cc\/index.php?rest_route=\/wp\/v2\/posts\/201","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cvr.cc\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cvr.cc\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cvr.cc\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cvr.cc\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=201"}],"version-history":[{"count":0,"href":"https:\/\/cvr.cc\/index.php?rest_route=\/wp\/v2\/posts\/201\/revisions"}],"wp:attachment":[{"href":"https:\/\/cvr.cc\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=201"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cvr.cc\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=201"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cvr.cc\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}