PDF/A-3a attachment support query
Hello list, The following document fails PDF/A-3a validation. It passes without the attachment. \setuplanguage [en] \setuptagging [state=start] \setupinteraction [state=start] \setupbackend [format={pdf/a-3a},profile={default_gray.icc}, intent={ISO coated v2 300\letterpercent\space (ECI)}] \setupstructure [state=start,method=auto] \setupcolors [pagecolormodel=auto,start=yes,rgb=no,cmyk=no] \setupbodyfont [Palatino,10pt] \starttext Attaching a plain text file. % \attachment [file=test.tex, % type={text/plain;charset=UTF-8}] % The \ConTeXt\ source code for this document is attached here. \attachment [file=testa.pdf, type={application/pdf}] A successfully validated pdf/a-3a file is attached here. \stoptext pdf-online https://www.pdf-online.com/osa/validate.aspxreports: Validating file "test.pdf" for conformance level pdfa-3a The key F is required but missing. The appearance dictionary doesn't contain an entry. File specification 'testa.pdf' not associated with an object. The document does not conform to the requested standard. The document doesn't conform to the PDF reference (missing required entries, wrong value types, etc.). The document contains hidden, invisible, non-viewable or non-printable annotations. The document contains annotations or form fields with ambigous or without appropriate appearances. The document does not conform to the PDF/A-3a standard. Done. My understanding is that 3-a should support both pdf and non-pdf attachments. This fails in a similar manner with both pdf/a-3a-validated files and with plain text files. I also tested with verapdf, and it also rejected the document with an attachment. Is this my error, or is it not yet supported? -- Rik Kabel
Hi Rik, I guess it's not supported yet. In "lpdf-fmt.lua" it says: [..] ["pdf/a-3a"] = { -- untested; NEW: any type of attachment is allowed [..] I remember adding the "a-2a" and "a-3a" versions back when Hans and I added experimental support for "PDF/UA-1" (which is based on "PDF/A-3a", but much more limited). This all lies back a few years, can't remember the details. So we have only basic support for "PDF/A-3a", the more advanced features of that format are not supported yet. The main problem here is the lacking PDF/A documentation (ISO pay wall). I guess there is currently no real reason to use that format at all (?). Best wishes, Peter Am 06.12.2019 um 03:11 schrieb Rik Kabel:
Hello list,
The following document fails PDF/A-3a validation. It passes without the attachment.
\setuplanguage [en] \setuptagging [state=start] \setupinteraction [state=start] \setupbackend [format={pdf/a-3a},profile={default_gray.icc}, intent={ISO coated v2 300\letterpercent\space (ECI)}] \setupstructure [state=start,method=auto] \setupcolors [pagecolormodel=auto,start=yes,rgb=no,cmyk=no] \setupbodyfont [Palatino,10pt] \starttext
Attaching a plain text file.
% \attachment [file=test.tex, % type={text/plain;charset=UTF-8}] % The \ConTeXt\ source code for this document is attached here. \attachment [file=testa.pdf, type={application/pdf}] A successfully validated pdf/a-3a file is attached here.
\stoptext
pdf-online https://www.pdf-online.com/osa/validate.aspxreports:
Validating file "test.pdf" for conformance level pdfa-3a The key F is required but missing. The appearance dictionary doesn't contain an entry. File specification 'testa.pdf' not associated with an object. The document does not conform to the requested standard. The document doesn't conform to the PDF reference (missing required entries, wrong value types, etc.). The document contains hidden, invisible, non-viewable or non-printable annotations. The document contains annotations or form fields with ambigous or without appropriate appearances. The document does not conform to the PDF/A-3a standard. Done.
My understanding is that 3-a should support both pdf and non-pdf attachments. This fails in a similar manner with both pdf/a-3a-validated files and with plain text files. I also tested with verapdf, and it also rejected the document with an attachment.
Is this my error, or is it not yet supported?
-- Rik Kabel
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
On Fri, Dec 6, 2019 at 4:26 PM Peter Rolf
So we have only basic support for "PDF/A-3a", the more advanced features of that format are not supported yet. The main problem here is the lacking PDF/A documentation (ISO pay wall).
A complete installation of verapdf has a very detailed "documentation" (sort of, it's embedded in the code) based on the ISO standard. -- luigi
On 12/6/2019 4:21 PM, Peter Rolf wrote:
Hi Rik,
I guess it's not supported yet.
In "lpdf-fmt.lua" it says: [..] ["pdf/a-3a"] = { -- untested; NEW: any type of attachment is allowed [..]
I remember adding the "a-2a" and "a-3a" versions back when Hans and I added experimental support for "PDF/UA-1" (which is based on "PDF/A-3a", but much more limited). This all lies back a few years, can't remember the details.
So we have only basic support for "PDF/A-3a", the more advanced features of that format are not supported yet. The main problem here is the lacking PDF/A documentation (ISO pay wall). I guess there is currently no real reason to use that format at all (?). indeed (and to be honest, i never need these options myself)
anyway, i happily wait till you come up with an entry for it (i have no clue what 'advanced' features mean here, something we need to implement or just something that needs a flag) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------
Am 06.12.2019 um 16:56 schrieb Hans Hagen:
On 12/6/2019 4:21 PM, Peter Rolf wrote:
Hi Rik,
I guess it's not supported yet.
In "lpdf-fmt.lua" it says: [..] ["pdf/a-3a"] = { -- untested; NEW: any type of attachment is allowed [..]
I remember adding the "a-2a" and "a-3a" versions back when Hans and I added experimental support for "PDF/UA-1" (which is based on "PDF/A-3a", but much more limited). This all lies back a few years, can't remember the details.
So we have only basic support for "PDF/A-3a", the more advanced features of that format are not supported yet. The main problem here is the lacking PDF/A documentation (ISO pay wall). I guess there is currently no real reason to use that format at all (?). indeed (and to be honest, i never need these options myself)
anyway, i happily wait till you come up with an entry for it
(i have no clue what 'advanced' features mean here, something we need to implement or just something that needs a flag)
@Hans: I'll look into it. Give me some days to read the documentation (not that much anyway) and to play around with it. All the "new" features are already implemented as building blocks for the PDF/X variants, so I guess it's mostly just adding some new table entries ('b|u' variants). Attachments seem to need several extra PDF entries. Will report back to you and Luigi. @Luigi: mh, that really looks like a lot of fun https://docs.verapdf.org/validation/pdfa-parts-2-and-3/ @Pablo, Rik: We can put you in cc if you volunteer for testing. Just say aye :D Peter
On 12/6/19 3:11 AM, Rik Kabel wrote:
Hello list,
The following document fails PDF/A-3a validation. It passes without the attachment. [...]
Hi Rik, ConTeXt needs better handling of attachments to be PDF/A-3 compatible. BTW, attachments don’t need to be PDF/A-3 documents, even if they are PDF documents (afaIk). Attachments in PDF/A-3 need to be related (as an array) to the document with the /AF key. I already reported this and I think that the most sensible value is to relate them to the document. That would mean to include the /AF key in the /Catalog dictionary. I think this would be the easiest way to implement and to use it. Just in case it helps, Pablo PS: there is another issue with annotations (reported with other issues already solved at https://mailman.ntg.nl/pipermail/dev-context/2019/003558.html). -- http://www.ousia.tk
On 12/6/19 6:08 PM, Pablo Rodriguez wrote:
[...] I already reported this and I think that the most sensible value is to relate them to the document.
Rik, I have just discovered that the line 97 in lpdf-tag.lua contains: local embeddedfilelist = pdfarray() -- /AF But that "embeddedfilelist" is only used in commented lines (168 and 277). I’m afraid that the /AF array needs to be an entry in the /Catalog dictionary. Right now, it would be implemented included in the /MarkInfo dictionary. Hans, I wonder whether this could be implemented. Many thanks for yoryr help, Pablo -- http://www.ousia.tk
participants (5)
-
Hans Hagen -
luigi scarso -
Pablo Rodriguez -
Peter Rolf -
Rik Kabel