Free Support Forum - aspose.com

PDF/A-1b validation fails


#1

Hello,



We have several PDF files, which we are converting to PDF/A-1b format with next code:

using (var inputDocument = new Aspose.Pdf.Document(inputFilePath))

{

new Aspose.Pdf.DocumentInfo(inputDocument) { ModDate = DateTime.Now };



var report = new MemoryStream();

inputDocument.Convert(report, PdfFormat.PDF_A_1B, ConvertErrorAction.Delete);



inputDocument.Save(outputFilePath);

}



The results of conversion do not pass validation of compliance with PDF/A-1b in Preflight of Adobe Acrobat Pro 9.5.5.

We are using Aspose.Pdf.dll of 16.12.0.0 version.



Please find the source and converted files in attachment.



Thanks in advance.

Valeriy


#2

Hi Valeriy,


Thanks for your inquiry. I have tested the PDF to PDFA scenario using Aspose.Pdf for .NET 17.2.0 and noticed reported issue against most of your shared files. We have logged following tickets in our issue tracking system for further investigation and rectification. We will notify you as soon as these issues are resolved.

However, I am unable to notice issue against 7-Src.pdf. The resultant PDFA is passing PDFA compliance successfully.

PDFNET-42343: 1-Src.pdf resultant PDFA document does not claim PDFA compliance
PDFNET-42344: 3-Src.pdf resultant PDFA document does not claim PDFA compliance
PDFNET-42345: 4-Src.pdf resultant PDFA document does not claim PDFA compliance
PDFNET-42346: 5-Src.pdf resultant PDFA document does not claim PDFA compliance

We are sorry for the inconvenience.

Best Regards,

#3

Hi Ahmad,

Thank you for the answer.
I have checked conversion of 7-Src.pdf file with Aspose.Pdf 17.2.0 and have found that it is really converted correctly with this version. Thus 7-Src.pdf file is not an issue any more.

Will wait for the fixes for other files.

Thanks
Valeriy


#4

Hi Valeriy,


Thanks for the acknowledgment about 7-Src.pdf file. We will keep you updated about resolution progress of other logged tickets, in this forum thread.

Best Regards,

#5

The issues you have found earlier (filed as PDFNET-42343) have been fixed in Aspose.PDF for .NET 18.3. This message was posted using BugNotificationTool from Downloads module by asad.ali


#6

The issues you have found earlier (filed as PDFNET-42344) have been fixed in Aspose.PDF for .NET 18.3. This message was posted using BugNotificationTool from Downloads module by asad.ali


#7

The issues you have found earlier (filed as PDFNET-42345) have been fixed in Aspose.PDF for .NET 18.3. This message was posted using BugNotificationTool from Downloads module by asad.ali


#8

The issues you have found earlier (filed as PDFNET-42346) have been fixed in Aspose.PDF for .NET 18.3. This message was posted using BugNotificationTool from Downloads module by asad.ali


#9

Hello Team.

We have verified the announced fixes on Aspose 18.12 and 19.1 versions.
Unfortunately, validation issue for PDFNET-42343, PDFNET-42344 and PDFNET-42345 are still there.
Probably they’ve been affected by some other changes that you’ve fixed since then.

We trully hope you could deliver the fixes for the mentioned above fixes in the nearest future. We really expected to get them in these latest versions of Aspose and it’s kind of sad because we never know which other earlier fixed defects might be reopen with this approach.
Can you please comment on what have caused such high rate of reopenings and your plans for these issues fixes?

Best wishes,
Liza Holovina


#10

@uaprogrammer

Thanks for contacting support.

We apologize for the inconvenience faced. We have checked these issues in our environment and re-opened them for investigation. We will look into details of the issue and let you know in case of we have some definite updates. Please be patient and spare us little time.

We are sorry for the inconvenience.


#11

Thank you Asad!

Do you know why we don’t see the change in the issues status on this thread?
We still see all these issues as ‘Closed’.
See attached.
image.png (66.7 KB)

Best wishes,
Liza


#12

@uaprogrammer

Thanks for sharing your concerns.

You were checking our older issue status module which is in progress to get obsolete. Please find new issue status panel which is right below the older one (as shown in attached screenshot) and you could see the issue statuses as “Reopened”.

IssueStatuses.png (13.8 KB)


#13

Interesting. No_new_status_block.png (68.8 KB)
I don’t see it on my view. Are you sure it’s available for our types of users?

Best wishes,
Liza


#14

@uaprogrammer

Thanks for writing back.

As this module is currently in the phase of implementation, it might not be visible. However, as soon as it is finalized, we will share details with you. Furthermore, your issues have definitely been re-opened and currently are under investigation. We will let you know in case of additional updates.


#15

@uaprogrammer

We have converted your documents with Aspose.PDF for .NET 19.1 and run conformance test using Adobe Reader XI. All documents were looked fine and showed no errors. For your kind reference, attached are documents and screenshots of conformance results.

2019-01-17_19-55-37.png (15.8 KB)
2019-01-17_19-54-02.png (15.8 KB)
2019-01-17_19-45-10.png (17.5 KB)
42345_PDF_A_1B_Output.pdf (4.8 MB)
42343_PDF_A_1B_Output.pdf (4.4 MB)

Could you please share which tool you are using at your side to test the PDF/A-1B compliance. Also, it will be helpful if you can please share the screenshots of the results.


#16

Hi,

You can find the result files and the validation screenshots below. We converted these documents with Aspose.PDF for .NET 19.1 and validated it using Adobe Reader 9

PDFNET-42343_errors.png (19.5 KB)
PDFNET-42343.pdf (5.5 MB)
PDFNET-42345_errors.png (38.5 KB)
PDFNET-42345.pdf (6.1 MB)


#17

@uaprogrammer

Thanks for sharing further information.

Aspose.PDF API currently follows the standards of Adobe Reader XI and conformance tests were fine using that version of Adobe Reader. However, we have recorded your concerns under re-opened tickets and will definitely further investigate why Adobe Reader 9 is failing the tests. We will let you know in case of additional updates.

We are sorry for the inconvenience.