From: Till Kamppeter <till.kamppeter@gmail.com>
To: Joseph Simon <jsimon383@gmail.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: [Printing-architecture] "no-color-management" not a good idea for a name of a boolean CUPS option
Date: Thu, 12 Jun 2014 12:13:19 +0200 [thread overview]
Message-ID: <53997D3F.2060803@gmail.com> (raw)
Hi,
I have encountered a problem with the "no-color-management" and
cupsGetOption() not be able to recognize that the user has supplied "-o
no-color-management" on the command line.
If you have an arbitrary boolean option in CUPS filters or backends,
like "xxx" the variants
-o xxx
-o xxx=1
-o xxx=on
-o xxx=yes
-o xxx=true
are supposed to let it be interpreted as set and
-o noxxx
-o xxx=0
-o xxx=off
-o xxx=no
-o xxx=false
let it be interpreted as not set. To support the "-o noxxx" case
cupsGetOption() seems to split a "no" in the beginning of the name off
if there is no '='. Therefore "no-color-management=" works but
"no-color-management" not. The latter is probably interpreted as
"-color-management=false".
Mike, am I right with this?
So I suggest something like "calibration-mode", "cm-calibration-mode",
"cm-calibration", or similar.
WDYT?
Till
next reply other threads:[~2014-06-12 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 10:13 Till Kamppeter [this message]
2014-06-12 12:17 ` [Printing-architecture] "no-color-management" not a good idea for a name of a boolean CUPS option Michael Sweet
2014-06-12 17:06 ` Chris Murphy
2014-06-12 18:15 ` Joseph Simon
2014-06-12 21:22 ` Till Kamppeter
2014-06-12 23:52 ` Joseph Simon
2014-06-15 9:10 ` Till Kamppeter
2014-06-15 12:56 ` Joseph Simon
2014-06-15 14:59 ` Till Kamppeter
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=53997D3F.2060803@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=jsimon383@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.