I have taken note of the FAQ inserted in the Second Ed of the iText In Action book about this, but would like to ask and understand the implications a little better...
If I wanted to try and automate the conversion of (various versions of) existing PDF files to PDF/A (level B), shouldn't this be "doable" in an automated fashion? I can understand the limitations that "Level A" might pose would probably need additional, manual intervention. But shouldn't we be able to parse an existing PDF file, strip any/all javascript, embedded images/video, etc., and read the required fonts and embed them into an output file to make it compliant? I know that might take a few steps to parse the input file to a legitimate, PDF/A output file, but it seems like there's no roadblock to doing so with the toolset contained in iText. Just a bit of work. What am I missing? What is there that iText "can't do" with regard to this objective? Thanks in advance, AJ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net 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
