Yuvi, Yuvi Masory wrote: > 3) The PDF's trailer includes a randomly generated String as its file ID - > solved by changing the appropriate method in PdfEncryption to always hash > the empty string.
That could turn out against you eventually: As the trailer IDs are meant to be identifiers for documents and your patched code calculates the identical one for ANY document, other applications may consider all the documents you generate with that patched iText to be identical. This might result in them rejecting or silently discarding your documents as duplicates. Therefore, I would advice you to reconsider this part of your patch: Either generate an ID which is unique for the generated document but reproducible, or change the patch to not include a trailer ID at all. Regards, Michael. -- View this message in context: http://itext-general.2136553.n4.nabble.com/how-to-get-zero-diff-on-two-consecutively-created-pdf-files-tp2718441p2718700.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.itextpdf.com/book/ Check the site with examples before you ask questions: http://www.1t3xt.info/examples/ You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
