Conversion to PDFA-2A is not compliant

GroupDocs.Conversion Product Family
1

Wen we use .NET Conversion (23.8) to convert an existing PDF to PDFA-2A the result ist not compliant to this standard. Some files work, but many are not compliant.

Check with a online tool revealed the following error:

  • ISO 19005-2:2011
  • 6.6.2.3
  • The Schema type is an XMP structure containing the definition of an extension schema. The field namespace URI is “http://www.aiim.org/pdfa/ns/schema#”. The required field namespace prefix is pdfaSchema. The Schema type includes the following fields: pdfaSchema:schema (Text), pdfaSchema:namespaceURI (URI), pdfaSchema:prefix (Text), pdfaSchema:property (Seq Property), pdfaSchema:valueType (Seq ValueType).

DocPdfANotCompliant.pdf (328.7 KB)

2

@systemengineering
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CONVERSIONNET-6350

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

3

@systemengineering

Could you kindly provide the Conversion code? Additionally, it would be greatly appreciated if you could share the specifics of your development environment where the issue can be replicated.

4

this is pretty straight forward:

        using var converter = new Converter(() => source, () => null);
        var convertOptions = new PdfConvertOptions
            {
                Format = PdfFileType.Pdf,
                PdfOptions = new PdfOptions
                {
                    PdfFormat = PdfFormats.PdfA_2A,
                },
          };

        var pdfStream = new MemoryStream();

	converter.Convert(() => pdfStream, convertOptions);
5

@systemengineering

We appreciate the information you’ve provided. We will proceed with our investigation and keep you informed with any updates.

6

Why is status Blocked? it is very important to have documents compliant to PDF/A standard as result of the conversion

7

@systemengineering

Ticket CONVERSIONNET-6350 is waiting for the resolution of another internal issue. Once that issue is fixed, we will provide an update on the progress of CONVERSIONNET-6350.

8

The issues you have found earlier (filed as CONVERSIONNET-6350) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov