Another post provides a partial simplification of certain key points discussed below.
Even so, portions of this post may be useful for those seeking a tutorial in batch programming, as many steps are explained in detail. This testing proceeded in fits and starts over a period of months thus, some sections or comments may be inconsistent with others. The following notes may be haphazard in places. The largest set tested here consisted of about 55,000 random PDFs.
(I was using Windows 7, though other Windows and in some cases non-Windows operating systems would also be able to use techniques discussed here.) I tried these approaches on small and large sets of PDFs from various sources. Several years earlier, I had posted a writeup of similar efforts now I wanted to update that and see if there were any relevant new tools or techniques. I wanted to see if any of them were corrupt. I had a large number of PDF files scattered around my drive. In both the printing and non-printing approaches, the following text raises many thoughts and points out many technicalities that may be of interest to others who seek good PDF-testing tools.
That said, it appeared that the non-printing alternatives discussed below were at least representative if not dominant among the possible approaches available to most users. No doubt there are many other printing and non-printing approaches than are explored here. Some portions of this post explore non-printing alternatives, both free and commercial. It seemed that readable but partly corrupted PDFs would be especially susceptible of detection when every page of every PDF was being run through a printer, even if the output was purely digital. While I found those PDF-printing approaches to be far slower than the CorruptedPDFinder and Acrobat approaches, they had an advantage of thoroughness. Most of this post explores various PDF-printing approaches, leading up to the choice of that Adobe Reader approach as the best of the lot.
For more information on that command-line option, see the Recap at the end of this post. I found three that worked: CorruptedPDFinder the File > Create PDF > Batch Create Multiple Files procedure within Adobe Acrobat and a command-line PDF-printing approach using Adobe Reader. I looked for ways to test large numbers of PDFs in Windows 7. Note: a later post provides a short version of key points from this post.
0 kommentar(er)
