You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2014-10-07 12:29:24
- pmlrosa
- Member
- Registered: 2014-10-07
- Posts: 3
Problem validating PDF/A format
Hello,
I have downloaded the SynPDF to test it for creating PDF/A files. I am already able to create the files but when I go to validate it always fail. Although Adobe Reader shows the blue panel informing that the file is a valid PDF/A. It's a little weird.
I tried to validate in:
- preFlight (Adobe Reader): Not valid
- The one that my client uses and needs to be valid: Not valid
- pdftools: Valid
These are the errors that I get:
Document information entry 'CreationDate' not synchronized with metadata property 'xmp:CreateDate'
Document information entry 'ModDate' not synchronized with metadata property 'xmp:ModifyDate'
The key 'StructTreeRoot' is required for PDF object 'Catalog'
Note:
I already made the changes posted in this ticket.
How can I fix this to get a valid PDF/A in the validator used by my client?
Offline
#3 2014-10-08 07:55:50
- pmlrosa
- Member
- Registered: 2014-10-07
- Posts: 3
Re: Problem validating PDF/A format
I received the below validation report from the validator that my client uses.
<?xml version="1.0" encoding="UTF-8"?>
<!-- Compliance Log Template -->
<compliance name="log" operation="validation" target="PDF/A-1a">
<version>8.0</version>
<tool name="Solid Framework" build="9.0.4823.1" />
<copyright>Copyright 2009-2012 Solid Documents LLC. All rights reserved.</copyright>
<date>2014-10-06T13:23:01Z</date>
<results file="QuickPDFA.pdf">
<catalog version="1.4" pages="1" />
<info creationDate="D:20141006145114" modDate="D:20141006145115" producer="Synopse PDF engine 1.18" />
<issues>
<metadata>
<problem severity="warning" objectID="5" clause="p32" standard="xmp">Recommended padding is not found in the XMP packet trailer</problem>
<problem severity="warning" objectID="5" clause=" TN0003" standard="pdfa">Recommended property 'format' for schema 'dc' missing</problem>
<problem severity="error" objectID="5" clause="6.7.3" standard="pdfa">Document information entry 'CreationDate' not synchronized with metadata property 'xmp:CreateDate'</problem>
<problem severity="error" objectID="5" clause="6.7.3" standard="pdfa">Document information entry 'ModDate' not synchronized with metadata property 'xmp:ModifyDate'</problem>
</metadata>
<logicalStructure>
<problem severity="error" objectID="1" clause="6.8.3.3" standard="pdfa">The key 'StructTreeRoot' is required for PDF object 'Catalog'</problem>
<problem severity="warning" clause="6.8.3.3" standard="pdfa">PDFA_LOG_MSG_TaggedStructureNotComplete</problem>
</logicalStructure>
</issues>
</results>
</compliance>Offline
#5 2014-10-10 09:35:49
- pmlrosa
- Member
- Registered: 2014-10-07
- Posts: 3
Re: Problem validating PDF/A format
Hello,
I already created a ticket, but I couldn't logged in with my account so I used the anonymous user to create it.
If it helps:
- Ticket UUID: 388d4c61816e3be3754ed5d956700ed6be97a1aa
- Title: Problem validating PDF/A format
Thanks.
Offline
#6 2015-10-23 05:37:17
- petrih
- Member
- Registered: 2015-10-22
- Posts: 8
Re: Problem validating PDF/A format
Hi!
I've studied the problem and the date synchronization issues come from CreationDate and ModDate lacking the timezone designator in the document information dictionary, which is 'Z' for the current xmp definition. I pushed this commit on Fossil.
StructTreeRoot validation for the site linked can be satisfied just by having an empty StructTreeRoot object in the document catalog dictionary, but I'm not sure if it's really required for the standard. What its purpose is, is explained in http://partners.adobe.com/public/develo … erence.pdf section 9.6.1 Structure Hierarchy.
Last edited by petrih (2015-10-23 05:38:10)
Offline
#8 2015-10-23 08:25:06
- petrih
- Member
- Registered: 2015-10-22
- Posts: 8
Re: Problem validating PDF/A format
Oops, sorry, fumbled with Fossil a bit. I made a pull request on Github instead. 
Offline
#9 2015-10-23 10:11:16
Re: Problem validating PDF/A format
Your patch has been included.
Online
#10 2017-01-18 17:57:29
Re: Problem validating PDF/A format
I've added missing "StructTreeRoot" entry...
Still complaining for a "Type" key I don't have a clue about...
See http://synopse.info/fossil/info/e4d46b66ec
Online
#11 2017-01-19 19:02:50
- Fritz
- Member
- Registered: 2015-05-08
- Posts: 13
Re: Problem validating PDF/A format
These should be used for Checking PDF/A i think
https://www.pdfa.org
and https://www.pdfa.org/new/verapdf-1-0-sh … ng-begins/
because they got the Money from the EU. They will be the "official" standard for validating PDF/A
PS i have done a quick test with the latest changes from today and it looks good. I have found 1 Output that fails. There is the Font "WingDings" involved. I will investigate further.
Last edited by Fritz (2017-01-19 19:31:29)
Offline
#12 2017-01-20 18:36:41
- Fritz
- Member
- Registered: 2015-05-08
- Posts: 13
Re: Problem validating PDF/A format
There is a problem with embedded Fonts.
If i have the WingDings Font it will not work as embedded Font. These is not specific to PDF/A. It is always. But my knowledge with Fonts and PDF is not deep so.....
Offline
#13 2017-01-22 09:15:57
Re: Problem validating PDF/A format
I've downloaded and tested output of SynPdf with the new verapdf tool.
All green, for PDF/A-1A and PDF/A-1B profiles.
veraPDF Logo
Validation Report
File: D:\Dev\Lib\SQLite3\Samples\05 - Report created from code\exe\test.pdf
Validation Profile: PDF/A-1B validation profile
Compliance status: Passed
Statistics
Version: 1.0.2
Build Date: 2017-01-10T02:34:00+01:00
Processing time: 00:00:00:170
Total rules in Profile: 102
Passed Checks: 5839
Failed Checks: 0
Features information
Feature
Information dictionaryAs expected, results are not compliant with PDF/A-2 and PDF/A-3.
But PDF/A-1 is enough for archival conformity.
Online
#14 2017-01-25 16:13:35
- fs999
- Member
- Registered: 2014-06-25
- Posts: 7
Re: Problem validating PDF/A format
Hello,
I have installed latest version (2017-01-18) from GitHub.
I try to generate a PDF/A-1a file of 2 pages report from QuickReport 4 like this :
Pdf := TPdfDocumentGDI.Create;
Pdf.GeneratePDF15File := False;
Pdf.PDFA1 := True;
Pdf.Info.Title := PrintName;
Pdf.Info.Author := UserName;
Pdf.Info.Creator := CompanyName;
try
for i := 1 to QRPreview.QRPrinter.PageCount do
begin
aMeta := QRPreview.QRPrinter.GetPage(i);
try
Pdf.DefaultPageWidth := MulDiv(aMeta.Width,72,Pdf.ScreenLogPixels);
Pdf.DefaultPageHeight := MulDiv(aMeta.Height,72,Pdf.ScreenLogPixels);
Pdf.AddPage;
Pdf.Canvas.RenderMetaFile(aMeta,1,0,0,0, tpKerningFromAveragePosition);
finally
aMeta.Free;
end;
end;
if SaveDialog.Execute then
Pdf.SaveToFile(SaveDialog.FileName);
finally
Pdf.Free;
end;The report consists of two b&w 200dpi scanned images on two pages.
When trying to validate the file with PDF Tools Online (https://www.pdf-online.com/osa/validate.aspx).
I get this result :
File Test.pdf
Compliance pdfa-1a
Result Document does not conform to PDF/A.
Details
Validating file "Test.pdf" for conformance level pdfa-1a
The key Type is required but missing.
The document does not conform to the requested standard.
The document doesn't provide appropriate logical structure information.
Done.
Offline
#15 2017-03-13 09:46:35
Re: Problem validating PDF/A format
pdf-online is made to validate... pdf-tools generated content... which is not standard, but self-conformant to a proprietary library.
As stated above, the official normalization is not pdf-online, but https://www.pdfa.org/
See https://synopse.info/forum/viewtopic.ph … 077#p23077
Online
Pages: 1