F185658 ~ validation errors in the PDF->PDF/A conversion

[Jesús]

Jesús replied to Jeyalakshmi Thangamarippandian

Oct 26, 2024 05:14 PM

Hi:

Sorry to come back to this issue. But I keep checking validation errors in the PDF->PDF/A conversion. In this case with PDF Reference v1.7. I attach the original file and the converted one. I have verified the non-compliance with Adobe Acrobat and VeraPDF.

I have used the following code:

​//await Task.Run(() => mDocument.ConvertToPDFA(PdfConformance));

await Task.Run(() => mDocument.Conformance = PdfConformance);

Version of Syncfusion.PDF.Base : 27.1462.48.0

Thank you very much

Jesus

Attachment: pdfreference1.7A_41c59ffa.rar

[Irfana Jaffer Sadhik]

Hi Jesus,

We were able to reproduce the reported issue with the provided details on our end. Currently we are analyzing this on our end and will provide the further details October 30th, 2024.

Regards,

Irfana J.

[RaashithAhamed SahulHameed]

Hi Jesus,

The reported issue still needs a lot more in-depth research; thus, we are looking into them. On 4^th November 2024, further information will be updated.

Regards,

Raashith Ahamed

[Antro James Loordhu Raj]

Hi Jesus,

The reported issues still need a lot more in-depth research. Thus, we are looking into them. We will provide proper details on 6th November 2024.

Regards,
Antro James L

[RaashithAhamed SahulHameed]

Hi Jesus,

Upon further analysis, we have determined that a device-independent DefaultCMYK color space has been set in the content stream of the document. Unfortunately, it cannot be removed from the content stream. We have also verified this issue with other PDF libraries, which similarly encounter errors when converting this particular document to PDF/A conformance. As a result, we are unable to proceed further in this matter.

Regards,

Raashith Ahamed

[Jesús]

Hi

Thanks for the response. I understand that after the conversion it is essential to verify the validation to be able to guarantee whether or not it is a document that meets the validation. The method that determines conformance only indicates whether or not it is a PDF/A document. Is there a way through the Syncfusion library to determine if the document is valid?. Other alternatives?

Best Regards,

Jesús

[RaashithAhamed SahulHameed]

Hi Jesus,

Thanks for the update

Currently, we do not support for validate the PDF standard conformance documents. We have logged the feature request called "Support for validate the PDF standard conformance documents" in our end. And we do not have any immediate plan to implement this feature. It will be available any of our upcoming releases.

You can track the status using the following feedback link:

https://www.syncfusion.com/feedback/22470/support-for-validate-the-pdf-standard-conformance-documents

Regards,

Raashith Ahamed

[Alessandro Nigro]

good morning, I'm also having the same type of problem, I use the latest version installed by nuget asp.net, any online validator tells me that the pdf/A-1b is not a valid pdf/a.

[RaashithAhamed SahulHameed]

Hi Alessandar Nigro,

Thanks for the response,

As we said earlier that a device-independent DefaultCMYK color space has been set in the content stream of the document. Unfortunately, it cannot be removed from the content stream. We have also verified this issue with other PDF libraries, which similarly encounter errors when converting this particular document to PDF/A conformance. As a result, we are unable to proceed further in this matter.

Regards,

Raashith Ahamed

[Alessandro Nigro]

thanks for the reply, since the original document is saved from a word -> pdf file, what are the guidelines to make it compliant for conversion using Syncfusion library?

regards

Alessandro

[Alessandro Nigro]

Hi Jesus,

did you solve it?

Regards

Alessandro

[Alessandro Nigro]

Hi, Anyway, I tried to convert the same document with ASPOSE.PDF and it is valid when opened with Adobe Reader.

[RaashithAhamed SahulHameed]

Hi Alessandaro,

Upon further analysis, we reviewed the document converted to PDF/A-1B using Aspose and then checked its compliance in Adobe. Errors were detected in Adobe as well. Please refer to the screenshot below for details.

Regards,

Raashith Ahamed