From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: attachments working again (issue with /EmbeddedFiles)
Date: Thu, 13 Feb 2020 21:43:42 -0500 [thread overview]
Message-ID: <7f79f9c8-1672-6dda-a187-b6e1a5dda6f4@rik.users.panix.com> (raw)
In-Reply-To: <aaca0ca0-1a9d-a80b-9bb6-71626b62786c@xs4all.nl>
On 2/13/2020 03:56, Hans Hagen wrote:
> On 2/13/2020 12:45 AM, Rik Kabel wrote:
>
>> Perhaps there is something in the difference between annotations and
>> attachments that results in different treatments by the various viewers.
> it has always been that messy; there's also the annotation symbol
> treatment that can differ; it doesn't help that acrobat changed
> behaviour a couple of times i think
>
> this is why the whole attachment handling was as it is: some
> comprimise that kind of made them show up ok on the average; but
> validatin spoiled this and now we're stick with these incompatible
> viewer behaviour .. not much we can do about it i fear
>
> (For instance, i remember that at some point acrobat showed
> attachments twice in some lists. Often these features ended up in
> specs without viewer support yet so probably not well tested for
> interferences either.)
>
> Hans
>
>
The further I look into bookmark, annotation, and attachment handling by
a number of viewers, the more confusing things appear. And Acrobat still
shows attachments twice under some circumstances, with the helpful
flyover for one entry giving the location as the associated page number,
and for the other giving it as the attachments tab.
What is more troublesome on the ConTeXt side is the validation issue
with the appearance dictionary for visible attachments.
The difference between validators when looking at the hidden attachment
in my example hinges on the handling of the attachment mime type. I have
filed a defect report with VeraPDF, which appears to be rejecting valid
mime type that includes a charset clause.
--
Rik
___________________________________________________________________________________
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-14 2:43 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
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 [this message]
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=7f79f9c8-1672-6dda-a187-b6e1a5dda6f4@rik.users.panix.com \
--to=context@rik.users.panix.com \
--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).