Maintain PDF/A after modifying PDF file

Aspose.PDF Product Family
1

Hello,

We had logged an issue previously where modifying a PDF with PDF/A validation using Aspose was removing the PDF/A validation. This was issue PDFNEWNET-33379. We recently upgraded to Aspose.Cell 8.6.0.0 and the issue appears to have returned. Can you please confirm the bug has returned and let us know if a fix is scheduled?

Thank you,

Kim

2

Hi Kim,


Thanks for contacting support.

I have tested the scenario using Aspose.Pdf for .NET 8.8.0 where I have used the following code snippet and I am unable to notice any problem. The resultant file is PDF/A compliant. Can you please share some code snippet and sample PDF documents which can help us in replicating the issue in our environment.

[C#]

Aspose.Pdf.Facades.PdfFileInfo
fileInfo = new Aspose.Pdf.Facades.PdfFileInfo(@“c:\pdftest/PDF_A.pdf”);<o:p></o:p>

fileInfo.SaveNewInfo(@“c:\pdftest/PDF_A-Results.pdf”);



PS, the source and resultant PDF files are also attached.

3

Hi,

Can you please confirm this works correctly with version 8.6.0.0? That is the version we are currently using.

Thank you,

Kim

4

Hi Kim,


I have also tested the scenario using Aspose.Pdf for .NET 8.6.0 where I have used the same code snippet and resource files shared in earlier post and as per my observations, the PDF/A information is being retained in resultant file.
5

Hi. I would like to provide more clarification for this item. The file is OK when simply saving it. We see that modifying the file by removing specific elements causes the PDF/A validation to be removed. For example, edit the file by removing a property such as Author, Subject, or Title. In this case we expect the PDF/A validation to be retained.

Thank you,

Kim

6

Hi Kim,


Thanks for sharing the details.

One of the point from PDF/A standards states that contents of PDF document should not be modified. In case you are modifying the document (removing some information), you need to explicitly set the PDF/A compliance over the PDF file.
7

Hi,

I spoke with my developer and in the past we didn't have to detect PDF/A and reapply it. The PDF/A validation was retained after modifying and saving the file. We were using Aspose.PDF 7.5.0. Can you confirm if this has changed?

Thank you,
Kim

8

Hi Kim,


I have tested the scenario using following code snippet with Aspose.Pdf for .NET 8.6.0 and Aspose.Pdf for .NET 8.8.0 and as per my observations, the PDF/A_1b compliance remains in the PDF document after updating the Author information. Furthermore, when I have tested the same code snippet with Aspose.Pdf for .NET 7.6.0, I have observed that PDF/A_1b compliance is lost.

I am afraid we might not be able to fix this problem in earlier release and therefore we recommend you to please try using the latest release of Aspose.Pdf for .NET 8.8.0. In the event of any further query, please feel free to contact.

[C#]

Document doc = new
Document(“c:/pdftest/PDF_A
(1).pdf”);<o:p></o:p>

doc.Info.Author ="Nayyer Shahbaz";

doc.Save(“c:/pdftest/PDF_A_Check.pdf”);

9

We continue to investigate this issue and have discovered something of interest.


If you perform the suggested code above on the attached document, the resulting file opens in Adobe Acrobat 11 with the warning bar that the code may comply with PDF/A 1b. If you go to the compliance area and then verify, the resulting file of the code fails the verification.
10

Hi Kim,


Thanks for sharing the details.

I have again tested the scenario using PDF document which you have shared and as per my observations, when checking the compliance of PDF document with Adobe Acrobat 10.1.1, the results show that document is PDF/a_1b compliant. For your reference, I have also attached the resultant PDF generated over my end.

Can you please verify the compliance at your end and share your findings. We apologize for your inconvenience.
11

Just tested the document you sent back. I’ve attached my conformance check as a graphic to this reply. I see the conformance fail when I test it.

12

Hi Kim,


We have again tested the scenario where we have executed PDF/A compliance test over PDF document which I shared in my earlier post 521455 and we are unable to notice the problem. For testing purposes, we have used Adobe Acrobat 11.0.0. I have also attached the screenshot showing this behavior.
13

Which version of the PDF assembly are you using? I have tested with 8.6 and 8.8. Below is my sample code:


string filePath = @“C:\Users\michaelr\AppData\Local\Temp\2013-videoComment.pdf”;
Aspose.Pdf.Document doc = new Aspose.Pdf.Document(filePath);
doc.Info.Author = “Kim”;
doc.Save(@“C:\temp\setAuthor.pdf”);
14

Hi Kim,


Thanks for sharing the code snippet.

I have again tested the scenario using above shared code snippet where I have used Aspose.Pdf for .NET 8.8.0 in VisualStudio 2010 application with Target framework as .NET Framework 4.0 and when viewing the resultant PDF file in Adobe Acrobat 10.1.1 and Adobe Acrobat 11.0.0, I am able to see that PDF/A compliance over PDF document. For your reference, I have also attached the resultant PDF generated over my end. Please note that we have tested the scenario over two different machines and unable to notice the problem.

Can you please share some details regarding your working environment. We apologize for this inconvenience.