In trying to detect corrupt PDF's from an outside source before they are accepted and loaded into our system, I was provided a tip and later noticed it within the iText book that by using the PdfReader class to open the PDF file I will get an exception if it is overall invalid. This works well.
However, we have also received files that are not initially detected by Adobe Reader as corrupt but instead provide an error later when viewing the content and a problem occurs. Error messages such as: "A Drawing Error Occurred" "Insufficient data for an Image" These types of errors are also not detected by the iText PdfReader class upon initially opening the file. Would iText throw and exception later in a process of scanning the file structure that I could trap? I'm interested to find out but I could use some initial direction on how to scan through all the objects within the PDF structure to test my theory. Being new to iText and PDF file structures could someone point me in the right direction on how to programmically scan through the structure of a PDF file (i.e., what objects are involved). Thanks for any help you might be able to provide -- View this message in context: http://www.nabble.com/New-corrupt-PDF-detection-issue-tf4882259.html#a13972417 Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://itext.ugent.be/itext-in-action/
