ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: upload ... new feature
Date: Fri, 10 Dec 2021 11:46:41 +0100	[thread overview]
Message-ID: <a4ea07bd-2700-c4d0-00c0-52d1cfb49d58@xs4all.nl> (raw)

Hi,

This time the lmtx upload has a (for some maybe) interesting new 
features: runtime pdf encryption.

context
    --ownerpassword=foo
   [--userpassword=bar]
   [--permissions="see context --help --expert"]

One can also use the document banner line, like:

% ownerpassword="foo" userpassword="" permissions="print,extract,quality"

Now, this is a feature that relies on the viewer to deal properly with 
it as we only support the not depricated method (why bother with the old 
stuff).

acrobat  : it took some effort (and trial and error) to make that one 
happy but it seems to work ok

summatra : the one i use, it works ok in the latest greatest (i use 
3.3.13418)

mutool   : okay but sometimes with a warning (i have a workearound but 
not enabled it because i consider it to be a bug)

qpdf     : happy but check gives a permissions warning (understandable 
as that is a real mess)

firefox  : opens ok in the latest version (pdf.js)

chrome   : can't handle the revision level we use (the rest is 
depricated so i consider it a lack of feature for now)

edge     : idem

okular   : my (windows) version is too old

xpdf     : not up to it yet

foxit    : (i never use it, but tried ... it's code seems to be what is 
used in chrome) doesn't work with this revision

I would be surprised if the native apple viewer works but I can't test that.

Given earlier pdf threads, I wanna check with Michal Vlasák what can be 
improved.

Performance is okay, the luametatex manual takes 1% more runtime and 
that's within the runtime measurement margin that I use. I didn't test 
with external images yet but will do that so don't expection yet. It 
will probably take a few months to reach a stable state anyway. (But ... 
afaiks tikz pdf generation, which is also somewhat alien to context, 
seems to work).

Hopefully I didn't mess up the unrelated code,

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
___________________________________________________________________________________

             reply	other threads:[~2021-12-10 10:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 10:46 Hans Hagen via ntg-context [this message]
2021-12-10 11:20 ` Taco Hoekwater via ntg-context
2021-12-10 17:04 ` Pablo Rodriguez via ntg-context
2021-12-10 17:37   ` Hans Hagen via ntg-context
2021-12-10 19:44     ` Pablo Rodriguez via ntg-context

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=a4ea07bd-2700-c4d0-00c0-52d1cfb49d58@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).