From: Till Kamppeter <till.kamppeter@gmail.com>
To: Alex Korobkin <korobkin+op@gmail.com>
Cc: "printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Number of copies in pure PDF workflow
Date: Tue, 07 Oct 2014 22:03:19 +0200 [thread overview]
Message-ID: <54344707.4080604@gmail.com> (raw)
In-Reply-To: <CA+3RNfj6twoEN9y0k+dfxeQ+14jVyE_Tz9Fe5fdQSmOKcbg=_Q@mail.gmail.com>
On 10/06/2014 04:06 PM, Alex Korobkin wrote:
> Hi Till,
>
> You're right, JCLToPDFInterpreter is already set in the example PPDs
> shipped with cups-filters [1].
> But what needs to be added to those PPDs to have printers make copies in
> hardware instead of cupsManualCopies?
pdftopdf uses cupsManualCopies. If cupsManualCopies is set in the PPD
software copies are done, otherwise hardware copies. If the printer
supports PJL, an appropriate command to generate the copies is added to
the PJL header.
How can I make pdftopdf add an IPP attribute to the job which generates
the copies with the attribute being passed on to the printer by the IPP
backend (when output format is set to PDF or PWG Raster by a cupsFilter2
keyword in the PPD.
And for PPD-less printing, how do I set the FINAL_CONTENT_TYPE there? Is
it possible to do it out of a System V interface script?
Till
next prev parent reply other threads:[~2014-10-07 20:03 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 19:28 [Printing-architecture] Number of copies in pure PDF workflow Alex Korobkin
2014-10-03 19:49 ` Ira McDonald
2014-10-03 20:23 ` Alex Korobkin
2014-10-04 15:40 ` Michael Sweet
2014-10-04 17:36 ` Alex Korobkin
2014-10-04 19:47 ` Tobias Hoffmann
2014-10-05 4:58 ` Alex Korobkin
2014-10-04 19:48 ` Michael Sweet
2014-10-05 5:03 ` Alex Korobkin
2014-10-06 14:12 ` Michael Sweet
2014-10-06 15:07 ` Alex Korobkin
2014-10-06 15:32 ` Michael Sweet
2014-10-06 15:55 ` Alex Korobkin
2014-10-06 16:01 ` Michael Sweet
2014-10-07 11:49 ` Till Kamppeter
2014-10-07 11:55 ` Michael Sweet
2014-10-07 12:12 ` Till Kamppeter
2014-10-06 12:54 ` Till Kamppeter
2014-10-06 14:06 ` Alex Korobkin
2014-10-07 14:06 ` Alex Korobkin
2014-10-07 20:03 ` Till Kamppeter [this message]
2014-10-07 21:18 ` Alex Korobkin
2014-10-07 21:45 ` Tobias Hoffmann
2014-10-08 2:53 ` Alex Korobkin
2014-10-08 9:57 ` Till Kamppeter
2014-10-08 14:40 ` Tobias Hoffmann
2014-10-08 19:41 ` Alex Korobkin
2014-10-08 20:53 ` Tobias Hoffmann
2014-10-10 18:38 ` Alex Korobkin
2014-10-10 20:06 ` Tobias Hoffmann
2014-10-10 20:58 ` Till Kamppeter
2014-10-14 19:17 ` Alex Korobkin
2014-10-14 21:09 ` Tobias Hoffmann
2014-10-15 10:50 ` Tobias Hoffmann
2014-10-15 13:12 ` Till Kamppeter
2014-10-15 15:04 ` Till Kamppeter
2014-10-15 16:17 ` Till Kamppeter
2014-10-15 19:28 ` Tobias Hoffmann
2014-10-16 15:53 ` Till Kamppeter
2014-10-16 16:52 ` Alex Korobkin
2014-10-16 20:59 ` Tobias Hoffmann
2014-10-17 16:22 ` Alex Korobkin
2014-10-17 16:40 ` Till Kamppeter
2014-10-20 16:23 ` Alex Korobkin
2014-10-20 16:29 ` Till Kamppeter
2014-10-20 17:28 ` Alex Korobkin
2014-10-20 20:30 ` Till Kamppeter
2014-10-20 21:18 ` Alex Korobkin
2014-10-15 16:22 ` Tobias Hoffmann
2014-10-15 17:06 ` Alex Korobkin
2014-10-15 19:02 ` Tobias Hoffmann
2014-10-15 19:16 ` Tobias Hoffmann
2014-10-07 22:40 ` Michael Sweet
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=54344707.4080604@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=korobkin+op@gmail.com \
--cc=printing-architecture@lists.linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.