Manulak, Manulak Dissanayake wrote > In last few mails, Michael said "It is not strictly impossible to use > iText to convert arbitrary PDFs to PDF/A as the iText low level API allows > you to nearly everything allowed in PDF" and as he explained, it is also > not a small fix to be done. > I always pointed to that point. I claimed out that it is impossible for > the moment to change the FOP side and make this fixed. So I expected a > help from you to do so.
I not merely said that it's not a small fix to be done, I actually pointed out that it's safe to assume that programming that as a single developer takes more than a year. And even that likely was an understatement, especially in case of really arbitrary PDFs. Therefore, only go this road if the FOP process cannot be changed for some years to come and your employer is willing to let you spend a large number of months on this. Manulak Dissanayake wrote > As I got many information on "what to read" and "why it is hard", I > didn't get any reply saying "How to do it" or "try this". The reason is that before even starting to "do" or "try" some conversion, you have to learn about PDF/A. And that means getting to know the current PDF specification (as it represents what you get), the specification version 1.4 (as the PDF/A spec is based on it), and the PDF/A spec itself really really well, far better than I do for example. There actually are some other documents referenced from these specs you should also read and understand. Only then you can seriously start trying and doing. But by then you very likely know better than I do how to even start. One thing may work out to your advantage, though: You actually have to do with only very special PDFs created by that FOP process. If you really "only" need to convert them, you should first take some representative sample PDFs from that process and check manually against both the PDF 1.4 spec (are they at least proper PDF 1.4 files?) and the PDF/A spec (what in them is not PDF/Aish?). By checking I really mean checking each and every object in the PDF, not merely running through some third party PDF/A checker. If you are lucky, you can safe some months this way. Regards, Michael PS: Of course you should use a more current iText version than 2.1.6 which you mentioned in your original posts. Quite a number of fixes have been introduced into iText since that version directly or indirectly improving the quality of the results. PPS: I just read again the validation error report from your initial post. Cleaning the properties should be fairly easy (if it's ok to loose some information) but the CIDSet related issues indicate that some interesting tasks (i.e. requiring some intimate knowledge of PDF and typesetting in general) will come up soon. And don't assume the list of issues in that report is complete. -- View this message in context: http://itext-general.2136553.n4.nabble.com/FW-SPAM-Re-PDF-Validation-error-with-PDF-A1b-complaince-tp4656183p4656206.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 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
