From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: PDF/A-3a attachment support query
Date: Fri, 6 Dec 2019 18:08:39 +0100 [thread overview]
Message-ID: <8d44e991-e4d2-aa01-917c-c2128614594c@gmx.es> (raw)
In-Reply-To: <09449aa1-9be9-8b90-f8ae-dbc23c30f378@rik.users.panix.com>
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
___________________________________________________________________________________
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 17:08 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
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 [this message]
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=8d44e991-e4d2-aa01-917c-c2128614594c@gmx.es \
--to=oinos@gmx.es \
--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).