Kevin, Kevin Day wrote > While that would certainly be a test, it wouldn't be an automated unit > test. Automated tests are the key here...
Have you considered tests along the lines of the "marked-for-redaction" thread and its sample code and PDF here? Unfortunately the original project does not seem to be publicly available anymore but the technique used there gives rise to many test cases: Take a diversified selection of real-world PDFs and mark some passages for redaction. Then create unit tests which extract the text of those passages using the parser package applied to the areas of the associted annotations, and compare it to the respective initially marked text. Regards, Michael -- View this message in context: http://itext-general.2136553.n4.nabble.com/PdfContentStreamProcessor-not-handling-TJ-operator-correctly-maybe-tp4656117p4656438.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
