From: Peter Rolf <indiego@gmx.net>
To: ntg-context@ntg.nl
Subject: Re: PDF/A-3a attachment support query
Date: Fri, 6 Dec 2019 16:21:20 +0100 [thread overview]
Message-ID: <6761a756-b1ad-5448-24f7-6dc344f3159c@gmx.net> (raw)
In-Reply-To: <09449aa1-9be9-8b90-f8ae-dbc23c30f378@rik.users.panix.com>
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.aspx>reports:
>
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2019-12-06 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 2:11 Rik Kabel
2019-12-06 15:21 ` Peter Rolf [this message]
2019-12-06 15:37 ` luigi scarso
2019-12-06 15:56 ` Hans Hagen
2019-12-07 14:09 ` Peter Rolf
2019-12-06 17:08 ` Pablo Rodriguez
2019-12-07 13:21 ` Pablo Rodriguez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6761a756-b1ad-5448-24f7-6dc344f3159c@gmx.net \
--to=indiego@gmx.net \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).