PDF/A 1b conversion problems

Hi,
having the need to buy a pdf conversion library, I tried the current Aspose PDf library 10.4 to convert in pdf/a 1b the included files, but every file (re)converted did not pass the Acrobat validation. This happen whether I start from a non pdf labeled file or not.

In the past I tested the 9.4 version, now you are on the on the 10.4 with several pdf/a conversion fixes, but however was unable to obtain files that pass validation by Acrobat.

You stated that are using Acrobat as reference to validation results, but I do not see any acknowledge on this; maybe I am using the wrong method?

Following here the function used to convert files:

static bool ConvetToPdfA(string infile, string outfile)
{
bool result = false;

if (File.Exists(outfile))
{
File.Delete(outfile);
}
Aspose.Pdf.Document document = new Aspose.Pdf.Document(infile);
try
{
result = document.Convert(outfile + “.log.xml”, Aspose.Pdf.PdfFormat.PDF_A_1B, Aspose.Pdf.ConvertErrorAction.Delete);
}
catch (Exception ex)
{
Console.Error.WriteLine("Catched exception " + ex.ToString());
}
if (result)
{
document.Save(outfile);
}
Console.Error.WriteLine( "Conversion " + (result ? “successful” : “failed”) + “\n”);
return result;
}

To conduct my tests I used following validators:
- Adobe Acrobat XI Professional with update 9
- Pdf-tools 3-Heights™ PDF Validator Online Tool (Pdftools | Developer SDKs & solutions for PDF and PDF/A)
- PDFTron PDF/A Manager (https://www.pdftron.com/downloads/pdfa.zip)


See the attached results table and pdf files.
Can you help me?

Best regards
Carlo


Hi Carlo,


Thanks for your inquiry. I have tested the PDF to PDFA1b conversion using Aspose.Pdf for .NET 10.4.0. Only js_api_reference.pdf file is not passing the PDFA1b compliance, other files are PDFA1b compliant as per preflight. So we have logged a ticket PDFNEWNET-38743 in our issue tracking system for further investigation and rectification.

Moreover, please note I have validated compliance using preflight, Adobe Acrobat XI version 11.0.0.

Best Regards,
Tilal, you are right, I was mislead by an Acrobat's feature and made the tests in the wrong manner by enabling editing on the pdf before and then making the validation.
Maybe that enabling editing force Acrobat to remove (judiciously) the pdf/a tag in the file.
Sorry for this.

Being curious I made two validation rounds of test (this time WITHOUT enabling editing before validation ;-) ).
First using Acrobat XI Professional with update 9; found only one file not passing validation after conversion:
js_api_reference.pdf

Second round using Acrobat Pro DC 2015 2015.006.30033. This test found two files not passing validation:
js_api_reference.pdf (CMYK-OutputIntent error)
opr049OL.pdf (invalid font)

Best.
Carlo

cmarsura:

Second round using Acrobat Pro DC 2015 2015.006.30033. This test found two files not passing validation:
js_api_reference.pdf (CMYK-OutputIntent error)
opr049OL.pdf (invalid font)



Hi Carlo,

Thanks for your feedback. We will appreciate it if you please share PDFA compliance results report of your both documents, failing the validation, using Acrobat Pro DC. We will investigate it and will guide you accordingly.

We are sorry for the inconvenience caused.

Best Regards,

No problem Tilal.

Included you can find .xml and .txt reports.

Carlo

Hi Carlo,


Thanks for sharing the reports. We have logged a ticket PDFNEWNET-38757 for further investigation and rectification. We will notify you as soon as we made some significant progress towards issue resolution.

We are sorry for the inconvenience caused.

Best Regards,

The issues you have found earlier (filed as PDFNET-38743) have been fixed in Aspose.PDF for .NET 19.2.