From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: problems with signature fields
Date: Thu, 12 Nov 2020 15:05:46 +0100 [thread overview]
Message-ID: <39ac3050-4dea-2b0b-d46b-3605394b8223@gmx.es> (raw)
In-Reply-To: <dfb2d0ed-c972-fdf4-9707-becc245debd2@xs4all.nl>
On 11/12/20 12:24 AM, Hans Hagen wrote:
> On 11/11/2020 9:46 PM, Pablo Rodriguez wrote:
>> Hans,
>
>> Back then, I thought it was an minor improvement. Now I realized that
>> this two objects for signature fiels are only valid for Acrobat.
>
> the other tools should be fixed ... indirect objects are pretty valid
Many thanks for your reply, Hans.
I totally agree, these tools need to be fixed.
I reported the issue to one of the projects more than two years ago. I’m
still waiting for a message about the issue report.
>> Would it be possible that signature fields may have only one object, so
>> that mupdf-gl and other tools have no problem signing fields PDF
>> documents generated by ConTeXt?
> all is possible but i'm not sure if i want to uglify the implementation
> for the sake of buggy viewers
In Windows (and I guess in macOS), saving a copy with Acrobat Reader DC
seems to unify both objects.
But I’m afraid Acrobat for Linux is too old for that (9.5.5).
Many thanks for your help,
Pablo
--
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-11-12 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 20:46 Pablo Rodriguez
2020-11-11 23:24 ` Hans Hagen
2020-11-12 14:05 ` Pablo Rodriguez [this message]
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=39ac3050-4dea-2b0b-d46b-3605394b8223@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).