pdf/a-validation fails

  • Case:

    Generated pdf/a is not accepted by validator

    Validator https://www.pdf-online.com/osa/validate.aspx says

    Setup

    Delphi RIO

    current wPDF 12/2019

    To generate layout-tags I call

    Code
    Inc(frwp.WP.Memo._WPDFParRun);

    before generating the PDF as documented in the manual.

    Are there other steps needed to generate logical structure information?

    Any idea about the P-key? Could not find any info on that.

    • Offizieller Beitrag

    This means tagged PDF which wPDF always was able to create, but it requires special graphic routines and will created by the WPTools export.

    At start the validators did not complain about those tags, in contrary, marked them as mistakes. Most PDF do not use tags.

    In "Modes" there is a switch: wpNoAutoTagsForPDFA

    Unless this flag is used a page tag is always added, mostly to disable error messages.

  • Thanks for the fast response.

    The Flag wpNoAutoTagsForPDFA is not set, Modes is empty.

    Here's my code which generates best results so far. Is the order in which the properties are set of any importance?

    This is the document generated

    https://polypoint.mount10.swiss/index.php/s/WCnP9aDgmJzzbLD

  • >Dieses Dokument besitzt tags.

    Wie prüfen sie, ob und welche Tags das Dokument enthält?

    Mit dieser Info kann ich mit dem Kunden in die Diskussion gehen weil die Validatoren sind sich uneinig

    3-Heights online unter https://www.pdf-online.com/osa/validate.aspx (vom Kunden als Referenz angegeben)

    PDFEN unter https://www.pdfen.com/pdf-a-validator

    Code
    CHECK FAILED
    THE DOCUMENT DOES NOT CONFORM TO THE PDF/A-1A STANDARD.

    BFO unter https://bfo.com/blog/2017/11/08/verify_pdfa_online/

    Hat nicht auszusetzen

    veraPDF (lokal installiert)

    Auch ok