From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Pablo Rodriguez <oinos@gmx.es>
Subject: Re: attachments working again (issue with /EmbeddedFiles)
Date: Fri, 7 Feb 2020 22:37:22 +0100 [thread overview]
Message-ID: <10b7abb5-70d6-e1a3-a083-1288e762ac9b@xs4all.nl> (raw)
In-Reply-To: <b0049403-ef29-4454-29a4-41792a8881ce@gmx.es>
On 2/7/2020 9:55 PM, Pablo Rodriguez wrote:
> On 2/7/20 9:19 PM, Rik Kabel wrote:
>>
>> On 2/7/2020 14:46, Pablo Rodriguez wrote:
>>> many thanks for having fixed the issues with attachments (in latest beta
>>> from 2020.02.07 18:36). I haven’t tested attachments with PDF/A-3a.
>>>
>> PDF/A-3a attachments still fail validation with the same issues.
>
> Hi Rik,
>
> it has way less issues, at least using verapdf-1.5.18 and the following
> sample:
>
> \setuptagging[state=start]
>
> \setupbodyfont[30pt]
>
> \setupbackend
> [format=PDF/A-3a,
> intent=sRGB IEC61966-2.1,
> profile={sRGB.icc,default_gray.icc},
> level=0]
>
> \setupcolors[pagecolormodel=auto]
>
> \setupinteraction[state=start]
> \starttext
> \startTEXpage[offset=1em]
> an attachment\attachment[file=xml-mkiv.pdf,
> type={application/pdf}]
> \stopTEXpage
> \stoptext
>
> With "method=hidden" (no attachment annotation) it has no issue.
>
> Both issues are related to annotations in general:
>
> - If the flag annotation is present (/F key), it should be set to print
> and disable everything else.
> - Annotations need an appearance dictionary (unless their /Rect is one
> and the same point, or /Popup or /Link annotations).
>
> Actual value of the annotation flag key is "/F null". I wonder whether
> this is a bug (for having wanted to avoid the presence of /F at all).
>
> Otherwise, I don’t think that setting all embedded file annotations to
> printable is a good default.
>
> Just in case it helps to the discussion,
Peter is stepwise looking into all these issues but we decided to also
see how that checking and standards evolve in cases where it's a
confusing mess. And these 'appearance dicts' are an example of a mess.
On the one hand there's predefined appearances and on the other hand
enforced renderings which gives some chicken-egg issue. It smells a lot
like bugs became features (standards) or 'acrobat behaviour' made the
standard or ... (like the zero rect thing, which, given t e plenty of
flags there are and verbosity there is in pdfm is pretty weird and
actually can make viewers bark. Irr the current approach we follow is
kind of a compromis.
Now, of course we can play safe and *always* have some fake appearance
(we could basically choose whatever funny shape we like as over time
people will interpret hard codes symbols for attachments differently)
and drop support for standardized renderings (that could adapt over
time).
So ... no changes etc till Peter gives his blessing as he is testing all
this in the framework we've set up for it.
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
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2020-02-07 21:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 19:46 Pablo Rodriguez
2020-02-07 20:19 ` Rik Kabel
2020-02-07 20:55 ` Pablo Rodriguez
2020-02-07 21:37 ` Hans Hagen [this message]
2020-02-08 8:20 ` Pablo Rodriguez
2020-02-08 12:45 ` Peter Rolf
2020-02-08 17:32 ` Pablo Rodriguez
2020-02-08 21:13 ` Rik Kabel
2020-02-12 19:20 ` Pablo Rodriguez
2020-02-12 22:22 ` Rik Kabel
2020-02-12 23:45 ` Rik Kabel
2020-02-13 8:56 ` Hans Hagen
2020-02-14 2:43 ` Rik Kabel
2020-02-14 21:23 ` 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=10b7abb5-70d6-e1a3-a083-1288e762ac9b@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).