I am trying to create a PDF/A-2u compliant PDF file from a LaTEX version of my thesis. I am using the pdfx package set to a-2u and validating the generated PDF using the VeraPDF validator with a profile for PDF/A-2u, since it is what my university does when validating submitted files.

But when I run the validator the following test fails:

Specification: ISO 19005-2:2011, Clause:, Test number: 1

The font programs for all fonts used for rendering within a conforming file shall be embedded within that file, as defined in ISO 32000-1:2008, 9.9.

Subtype == "Type3" || Subtype == "Type0" || renderingMode == 3 || fontFile_size == 1

I have created a fairly minimal example, which I compile into pdf using pdflatex document















hello, \emph{world}


When I run pdffonts document.pdf, I can see that all the used fonts are embedded and of Type 1:

name                                 type              encoding         emb sub uni object ID
------------------------------------ ----------------- ---------------- --- --- --- ---------
YGPAOD+LMRoman12-Regular             Type 1            Custom           yes yes yes      9  0
OCNWPR+LMRoman12-Italic              Type 1            Custom           yes yes yes     10  0

Which means that the fonts do not match the desired renderingMode or fontFile_size requirement.

Is there a way to fix this, ideally within latex?

This is the full output of the validator:

<?xml version="1.0" encoding="utf-8"?>
    <releaseDetails id="core" version="1.10.2" buildDate="2017-11-30T12:47:00+01:00"></releaseDetails>
    <releaseDetails id="validation-model" version="1.10.5" buildDate="2017-12-28T11:51:00+01:00"></releaseDetails>
    <releaseDetails id="gui" version="1.10.6" buildDate="2017-12-28T11:58:00+01:00"></releaseDetails>
      <item size="40467">
      <validationReport profileName="PDF/A-2U validation profile" statement="PDF file is not compliant with Validation Profile requirements." isCompliant="false">
        <details passedRules="119" failedRules="1" passedChecks="615" failedChecks="1">
          <rule specification="ISO 19005-2:2011" clause="" testNumber="1" status="failed" passedChecks="0" failedChecks="1">
            <description>The font programs for all fonts used for rendering within a conforming file shall be embedded within that file, as defined in ISO 32000-1:2008, 9.9.</description>
            <test>Subtype == "Type3" || Subtype == "Type0" || renderingMode == 3 || fontFile_size == 1</test>
            <check status="failed">
              <context>root/document[0]/pages[0](5 0 obj PDPage)/contentStream[0](7 0 obj PDContentStream)/operators[9]/font[0](YGPAOD+LMRoman12-Regular)</context>
      <duration start="1523967257917" finish="1523967258155">00:00:00.238</duration>
  <batchSummary totalJobs="1" failedToParse="0" encrypted="0">
    <validationReports compliant="0" nonCompliant="1" failedJobs="0">1</validationReports>
    <featureReports failedJobs="0">0</featureReports>
    <repairReports failedJobs="0">0</repairReports>
    <duration start="1523967257908" finish="1523967258159">00:00:00.251</duration>

1 Answer 1


This has been fixed in veraPDF V1.11.19, see https://github.com/veraPDF/veraPDF-library/issues/957.

I confirm this has been an issue in PostScript font parser in the 1.10.6 release. It has been fixed in dev. Please check the latest dev version: http://software.verapdf.org/develop/1.11/verapdf-greenfield-1.11.19-installer.zip

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.