Hello,
We have recently purchased an Aspose.PDF and Aspose.Words licenses with support. We have refactored our form generation service to replace iText with Aspose.PDF. Unfortunately, after the work was completed we realized that Aspose.PDF is generating our forms almost 30 times slower than iText, and if we try to generate all the forms, which can consist of about 50 pages, it can take over an hour with Aspose.pdf vs iText where it takes about one minute and a half. We also realized that Aspose.PDF is generating a simple pdf form at 704 kb whereas iText generates the same form at 62 kb. I have tried to use OptimizationOptions to set setUnembedFonts(true), to somewhat optimize the size of the document, but the size didn’t change. I have attached an example code of how we generate Aspose.PDF document in our service. Hopefully we can get help solving this issue as we cannot use Aspose.PDF in our environments to generate forms
Example.zip (723 Bytes)
@ihandouk
Is it possible that you can share outputs with us from both Aspose.PDF and iText in your environment. This would help us in investigating the scenario accordingly. We will log an investigation ticket and share the ID with you.
Hello @asad.ali,
Thank you for responding. I have attached an example form generated by Aspose.PDF, and the second example is generated by iText. They are both generated from an XML file and data from our database. This issue is very critical for us, and we hope to have a solution as soon as possible, as this issue is preventing us from releasing Aspose.PDF to production. We were hoping to use Aspose.PDF with Aspose.Words to remediate a highly critically issue were Aspose.Words randomly print the following red text “Evaluation Only. Created with Aspose.Words. Copyright 2003-2018 Aspose Pty Ltd.” on a pdf even though we are licensed for Aspose.Words, and the license is called before the creation of each document.
15708356-Aspose.pdf (709.0 KB)
15708356-iText.pdf (64.8 KB)
@ihandouk
Your code snippet suggests that you are filling form fields in the PDF? Also, what below two method do?
populateFormSection(pdfPage, componentList, formData);
addFooterAndWatermarkToPage(pdfDocument, pageCount, formData, formFooter, watermark);
The code snippet is too generic that we cannot use it replicate the issue in our environment. The PDFs are also flattened. Is it possible to generate a case with minimal code snippet where we can fill the PDF document with the same code snippet that you are using and replicate the issue in our environment as well? A fillable template PDF would also be required (sorry for not asking in our previous message.). Please provide the requested details so that we can try to reproduce the scenario and address it accordingly.
Hello @asad.ali ,
I have attached a longer copy of the code used to generate the PDF form. We do generate this form from an xml and populate the data from the database.
DecForm.zip (4.0 KB)
@ihandouk
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): PDFNET-57231
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
Hello @asad.ali,
That is great. We do have paid support, what can I do to turn this ticket to the paid support service team? or do I have to submit a new ticket through the paid support account?
@ihandouk
You can create a post in the paid support forum with reference to the ticket ID attached here. Your ticket will be escalated accordingly.