Hi,
We merge pdf files using such code
IEnumerable<KeyValuePair<string, string>> files;
Document outputDocument = null;
foreach (var documentName in files)
{
if (outputDocument == null)
{
outputDocument = new Document();
}
var inputDocument = new Document(documentName.Key);
if (inputDocument.Form.Type == FormType.Dynamic)
{
inputDocument.Form.Type = FormType.Standard;
}
outputDocument.Pages.Add(inputDocument.Pages);
}
if (outputDocument != null)
{
outputDocument.Convert(new MemoryStream(), PdfFormat.PDF_A_1B, ConvertErrorAction.Delete);
outputDocument.Save(resultFileName);
outputDocument.Dispose();
}
but after merging some data from input file are corrupted.
Please check attached file like an example of merging one file (input.pdf).
Also I’ve attached images with corrupted data.
Hi Mikhail,
Thanks for your inquriy. I have tested the scenario with Aspose.Pdf for .NET 11.5.0 and getting NullRefrence Exception. We already noticed the exception in Add() method of PageCollection class, so I have linked your thread to the ticket PDFNEWNET-40591. We will notify you as soon as it is resolved.
We are sorry for the inconvenience caused.
Best Regards,
Hi Mikhail,
In addition to above reply. I have tested direct conversion of PDF to PDFA with your shared document using Aspose.Pdf for .NET 11.5.0 and noticed the text corruption issue, so logged another ticket PDFNEWNET-40636 in our issue tracking system for further investigation and rectification. We will notify you as soon as it is resolved.
We are sorry for the inconvenience caused.
Best Regards,
Thanks.
Please find attached another file which also reproduce this issue (text corruption).
Hello Team!
This issue became a showstopper for our customers to use the latest version of the product. It is a critical issue for them.
Can you please prioritize this defect fix?
We would highly appreciate any information on when this issue can be resolved, even if it’s not a particular delivery date but an approximate time period, it’s still better than no information at all.
Do you think you can provide us with the timeframe?
We would highly appreciate any information on when this issue can be resolved, even if it’s not a particular delivery date but an approximate time period, it’s still better than no information at all.
Do you think you can provide us with the timeframe?
Best regards.
Liza
Hi Mikhail,uaprogrammer:Thanks.
Please find attached another file which also reproduce this issue (text corruption).
Thanks for sharing the resource files.
I have tested the scenario and have managed to reproduce same problem. For the sake of correction, I have separately logged it as PDFNEWNET-40682 in our issue tracking system. We will further look into the details of this problem and will keep you posted on the status of correction. Please be patient and spare us little time. We are sorry for this inconvenience.
uaprogrammer:Hello Team!
This issue became a showstopper for our customers to use the latest version of the product. It is a critical issue for them.Can you please prioritize this defect fix?Hi Liza,
We would highly appreciate any information on when this issue can be resolved, even if it’s not a particular delivery date but an approximate time period, it’s still better than no information at all.
Do you think you can provide us with the timeframe?Thanks for contacting support.We do understand the criticallity of issue and inconvenience which you and your customers are facing but as we recently have noticed this problem, so its pending for review and product team will surely consider fixing it as per their development schedule. However I have shared your concerns with product team and as soon as we have some definite updates regarding its resolution, we will let you know.Please be patient and spare us little time. We are sorry for this delay and inconvenience.
The issues you have found earlier (filed as PDFNEWNET-40591) have been fixed in Aspose.Pdf for .NET 11.6.0.
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
Hello Team,
Can you please update us on your plans for PDFNEWNET-40636; PDFNEWNET-40682 fixes? We truly need these defects fixed as soon as possible since they've become the showstoppers for selling the product.
Best regards,
Liza
Hi Liza,
Thanks for your inquriy. I am afraid the issues as still pending for investigation as product team is busy in resolving other issues in the queue. As soon as our product team completes the issues’ investigation then we will be in a good position to share some ETA/workaround with you. However we have recorded your concern and will notify you as soon as we made some signification progress towards issues’ resolution.
We are sorry for the inconvenience caused.
Best Regards,
The issues you have found earlier (filed as PDFNEWNET-40682;PDFNEWNET-40636) have been fixed in Aspose.Pdf for .NET 11.8.0.
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
The issues you have found earlier (filed as ) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by MuzammilKhan