Hmm..I had thought about this too and this would definetly work if i were working with a single PDF for which i could probably define the bounding box..but the point is that i would be dealing with a slew of PDFs , which would be downloaded and read by my application at runtime. So i am not sure if the bounding box strategy would work for this scenario since different PDFs may require different co-ordinates to be specified. However, i will definetly give this a try and check. -- View this message in context: http://itext-general.2136553.n4.nabble.com/Split-a-PDF-Page-into-header-footer-and-body-tp3308836p3312211.html Sent from the iText - General mailing list archive at Nabble.com.
------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions 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
