From: Christian <chanlists@googlemail.com>
To: printing-architecture@lists.linux-foundation.org
Subject: [Printing-architecture] windows, samba, cups, color and BW
Date: Wed, 18 Sep 2013 23:55:50 +0200 [thread overview]
Message-ID: <523A2166.8080004@googlemail.com> (raw)
Dear list,
I have CUPS 1.5.3 running under Debian wheezy. I use Samba, cupsaddsmb
and the Microsoft windows postscript printer driver for windows (7)
clients. I have a printer (RICOH Aficio MP C3502, could post PPD) which
is a rather big network multifunction device. From linux, everything
works fine. For windows, printing via samba, I have set up a special raw
queue in CUPS using appropriate Filter definitions in the PPD, and from
the logs, I can confirm that no filtering of the postscript is being
done on the linux side. From windows clients, using e. g. MSWORD, all of
the printer options (staple, B+W vs. color, ...) are available and work
as far as I can tell.
The only exception is printing from Adobe Reader under Windows. Most of
the options are honored, except the "Color vs. B + W" option. Under the
"Paper / Quality" tab in the printer options, there is a set of two
radio buttons with little pictures next to them for Color vs. Black +
White. Those do not work for me.
I can only get it to print B + W from Adobe reader under windows if,
rather than using those buttons, I go into "Advanced..." and then chose
"Color Mode: Black and White" in the list of printer options. I know
this, but it could be confusing to our users...
So I'd like to understand the background better, and why only Adobe
Reader does this, and whether this behavior can be fixed, e. g. by PPD
hacking or other tricks...
Sorry to ask here, but the "forums" link is dysfunctional. Let me know
if I can help. Best,
Christian
next reply other threads:[~2013-09-18 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 21:55 Christian [this message]
2013-09-19 18:10 ` [Printing-architecture] windows, samba, cups, color and BW Alex Korobkin
2013-09-26 13:13 ` Christian
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=523A2166.8080004@googlemail.com \
--to=chanlists@googlemail.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.