From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Non-Printing PDFs with ConTeXt
Date: Fri, 4 May 2012 12:51:48 +0200 [thread overview]
Message-ID: <CAG5iGsAq5R4ipOn-uRDdJYq-Ap9Yxg_vq5oO5=ta7kX_9cQwWg@mail.gmail.com> (raw)
In-Reply-To: <38DAF987-9C7F-435F-9846-50EC3F10EC16@stien.de>
On Fri, May 4, 2012 at 12:37 PM, Malte Stien <malte@stien.de> wrote:
> Hi all,
>
> Is there a way I can get ConTeXt to produce PDFs that are not-printable? Just as a background to my question: This is not about copyright. Rather, I am using ConTeXt to produce quality process documents. The quality management system requires that all quality process documents be "controlled", that is one must prevent folks from printing copies of their own that then keep floating around the place and cannot be retracted when a new version of the quality process document is issued.
>
> Hence, I am aiming for a paper-less scenario where everyone reads the documents on screen. Therefore, I would like to make printing impossible, or at least hard. The only one who should be able to print the document is the Document Manager; maybe the documents could be encrypted (PDF supports that, I believe), such that the Document Manager can print them knowing the password.
>
> So far, I have only seen Word and Acrobat Distiller being able to do this. Is there a way I can setup ConTeXt to do this? Or are there some command line tools, that can do that after the PDF has been produced?
>
> Any hints would be great.
see also
http://qpdf.sourceforge.net/
--
luigi
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-04 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 10:37 Malte Stien
2012-05-04 10:44 ` Andreas Schneider
2012-05-04 10:51 ` luigi scarso [this message]
2012-05-04 11:35 ` Martin Schröder
2012-05-04 11:57 ` Mojca Miklavec
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='CAG5iGsAq5R4ipOn-uRDdJYq-Ap9Yxg_vq5oO5=ta7kX_9cQwWg@mail.gmail.com' \
--to=luigi.scarso@gmail.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).