From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: extended printing options in ConTeXt
Date: Thu, 4 Feb 2016 19:51:32 +0100 [thread overview]
Message-ID: <56B39DB4.4070404@wxs.nl> (raw)
In-Reply-To: <56AF07B0.4080806@gmx.es>
On 2/1/2016 8:22 AM, Pablo Rodriguez wrote:
> Hans,
>
> would it be possible to implement two extended printing options defined
> in the PDF specification?
remind me in a few weeks as i have other priorities now
> You have kindly implemented duplex printing and page scaling options.
> At my workplace, we are it on a daily basis for mail merging (I had to
> make an “extension” to distinguish between duplex printing and page
> scaling [it isn’t an option for me]).
>
> In the present implementation, page, portrait and landscape values sets
> page scaling to none. In most of the documents we generate, we have to
> fit page contents to printer margins. It is a must for us, since
> corporate templates are the way they are (wrong designed).
>
> Would it be possible to have the PDF printing options in different keys
> than the one used for the the viewing options?
>
> It would be also extremely useful to be able to specify the number of
> copies and select page size from PDF document. These are the keys
> /NumCopies and /PickTrayByPDFSize (described on page 365 from the PDF
> specification).
>
> The keys and their values would be:
>
> duplex page portrait landscape (only a duplex key required)
>
> fixed (no value is required)
>
> copies number
>
> pdfsize yes no
>
> This way, the user has only to press the OK button in the printing
> dialog or enter (and forget about selecting which kind of document
> requires which options).
>
> I’m asking this for my own needs (it is essential for us at work,
> where none knows what ConTeXt might be).
>
> But this implementation benefits any ConTeXt user.
>
> Many thanks for your help,
>
> Pablo
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.com | 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-02-04 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 7:22 Pablo Rodriguez
2016-02-04 18:51 ` Hans Hagen [this message]
2016-02-04 19:00 ` Pablo Rodriguez
2016-03-05 23:49 ` Pablo Rodriguez
2016-05-29 10:39 ` 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=56B39DB4.4070404@wxs.nl \
--to=pragma@wxs.nl \
--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).