ZUGFeRD/ZUV

Issue writing A3

jstaerk opened this issue · 8 comments

Allegedly the 505 ZF1 sample does not validate on validator.zugferd.org

can't reproduce. ZUV 0.4.5 reports no errors and validator.zugferd.org says "ZUGFeRD-PDF und ZUGFeRD-xml sind valide."

The problem was the versionnumber from download (1...x) in the filename. Sorry!

invoice.pdf
invoice.ZUGFeRD.pdf
ZUGFeRD-invoice.txt

... sorry, but i can't get a valid ZUGFeRD-PDF with your testfiles or with my own-files :( I working on this problem since days.

mustangproject/src/test/resources/migration/input/ZUGFeRD1-invoice.xml
mustangproject/src/test/resources/MustangGnuaccountingBeispielRE-20171118_506blanko.pdf

With your testfiles i get:
"A file's name dictionary, as defined in PDF Reference 3.6.3, shall not contain the EmbeddedFiles key"
and with my files:
"A file specification dictionary, as defined in PDF 3.10.2, shall not contain the EF key."
checker
command

... i have no idea what this means. Please let me know if i should open a new issue.

http://www.preforma-project.eu/uploads/osw/veraPDF-Conformance-Checker.pdf

6.1.11 Embedded files
A file specification dictionary, as defined in PDF 3.10.2, shall not
contain the EF key. A file’s name dictionary, as defined in PDF
Reference 3.6.3, shall not contain the EmbeddedFiles key.
NOTE. These keys are used to encapsulate files containing arbitrary content within a
PDF file. The explicit prohibition of these keys has the implicit effect of disallowing
embedded files that can create external dependencies and complicate preservation
efforts.

I'll have a closer look, the input should be PDF/A-1 but the output should definitely not be PDF/A-1(B) but PDF/A-3

bild 220

... here a screenshot from your samplefile. I renamed the filename from ...blanko to invoice.pdf

... and here the output-file.
bild 221

I opened it as Mustangproject issue ZUGFeRD/mustangproject#57 and I'll close it here