From: "Alastair M. Robinson" <blackfive@fakenhamweb.co.uk>
To: Robert Krawitz <rlk@alum.mit.edu>
Cc: printing-architecture@lists.linux-foundation.org,
Johannes Meixner <jsmeix@suse.de>,
mike@easysw.com, gimp-print-devel@lists.sourceforge.net
Subject: Re: [Printing-architecture] [Gimp-print-devel] Looking ahead to 5.3
Date: Fri, 31 Oct 2008 01:53:22 +0000 [thread overview]
Message-ID: <490A6512.4000108@fakenhamweb.co.uk> (raw)
In-Reply-To: <200810310048.m9V0mDYI005128@dsl092-065-009.bos1.dsl.speakeasy.net>
Hi :)
Robert Krawitz wrote:
> I've been reading all this, but not responding; partly I've been busy
> and partly I'm curious what other folks think.
Ditto - I've been following the posts but not taking part for the last
few days, though I have fleshed out the Wiki a little since my last mail
on the subject.
> I'm still not a fan of requiring administrative privileges to use
> particular driver options of this kind that don't affect persistent
> state within the printer (and hence might have security implications).
Security implications are something I've been thinking about, actually.
In theory, it's possible for a printer to be damaged by feeding it
pathological input. Colour laser printers respond badly, I believe, to
being asked to print a solid page of 100% C+M+Y+K. Malicious
linearization curves could potentially result in flooding an inkjet,
too, I'd imagine.
> If something doesn't affect the system configuration or integrity it
> shouldn't require administrative privilege.
Agreed. Our difficulty is allowing users to set these options in a way
that makes them accessible to the driver running on the server but
doesn't affect other users' jobs.
(Note that the current CUPS configuration as shipped by Ubuntu - at
least in 8.04 - fails on this point. Any user with lp privileges can
set printer options which affect all other users.)
Oh, one other thing I've been wondering - are there currently, or are
there likely to be in future, any printer models which support
head-alignment, but don't have built-in persistent storage for that
alignment?
> But I suppose I'm on the
> extreme end of maximum configurability and exposing (appropriately --
> which I might define differently from others) every possible option to
> the user, even if it allows someone to do absolutely absurd things.
"UNIX was not designed to stop its users from doing stupid things, as
that would also stop them from doing clever things." -- Doug Gwyn
> But there is a free RIP around Gutenprint (PhotoPrint) that could be
> extended to allow people to do this,
True - when I eventually get round to supporting curves!
> So the question is, how do we move along to that point?
Earlier today I began "thinking aloud" on that subject on the Wiki, and
took the first steps to adding "DeviceN" support to PhotoPrint's imaging
stack, in preparation for printing out raw per-channel linearization
targets.
Could you outline roughly how you currently go about tuning a new,
unknown printer, step-by-step? Understanding the steps and the order in
which they occur may be helpful in figuring out where the colour
instrument can help with the process, and how best to go about making
the results shareable.
All the best,
--
Alastair M. Robinson
next prev parent reply other threads:[~2008-10-31 1:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200810132357.m9DNvMRf015955@dsl092-065-009.bos1.dsl.speakeasy.net>
[not found] ` <48FB37A3.8090007@gmail.com>
[not found] ` <200810191602.m9JG2D84030719@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-22 14:49 ` [Printing-architecture] [Gimp-print-devel] Looking ahead to 5.3 Till Kamppeter
2008-10-22 15:17 ` peter sikking
[not found] ` <200810230019.m9N0JCIp018128@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-24 8:52 ` peter sikking
2008-10-24 10:08 ` Till Kamppeter
2008-10-24 12:35 ` Alastair M. Robinson
2008-10-24 18:34 ` Hal V. Engel
[not found] ` <49021D0B.4040708@apple.com>
2008-10-25 0:46 ` Alastair M. Robinson
[not found] ` <200810251458.m9PEwS6D029068@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-25 17:43 ` Alastair M. Robinson
[not found] ` <200810251857.m9PIvIdi030089@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-25 19:35 ` Alastair M. Robinson
[not found] ` <200810251950.m9PJoeFa030284@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-26 0:41 ` Alastair M. Robinson
[not found] ` <200810260049.m9Q0nTIw032617@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-26 1:18 ` Alastair M. Robinson
[not found] ` <49049DC3.8000405@apple.com>
[not found] ` <200810261653.m9QGrk2l014877@dsl092-065-009.bos1.dsl.speakeasy.net>
[not found] ` <490530BC.9090803@apple.com>
[not found] ` <200810271054.m9RAsDLs001975@dsl092-065-009.bos1.dsl.speakeasy.net>
[not found] ` <alpine.LNX.1.10.0810281134060.17582@nelson.suse.de>
2008-10-28 12:59 ` Till Kamppeter
2008-10-28 15:19 ` Till Kamppeter
[not found] ` <49074E92.5020809@apple.com>
[not found] ` <alpine.LNX.1.10.0810290940570.3548@nelson.suse.de>
[not found] ` <200810310048.m9V0mDYI005128@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-31 1:53 ` Alastair M. Robinson [this message]
2008-10-25 22:38 ` Till Kamppeter
[not found] ` <200810252249.m9PMnrSo030956@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-26 9:59 ` Till Kamppeter
[not found] ` <200810201403.26403.hvengel@astound.net>
[not found] ` <200810210026.m9L0Qnd5008431@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-22 17:15 ` [Printing-architecture] [Gimp-print-devel] [Openicc] " Hal V. Engel
[not found] ` <200810260141.m9Q1fdci000540@dsl092-065-009.bos1.dsl.speakeasy.net>
[not found] ` <4904A0EA.4030508@apple.com>
2008-10-26 18:40 ` [Printing-architecture] [Gimp-print-devel] " Hal V. Engel
[not found] ` <200810261904.m9QJ423w015373@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-26 21:23 ` Hal V. Engel
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=490A6512.4000108@fakenhamweb.co.uk \
--to=blackfive@fakenhamweb.co.uk \
--cc=gimp-print-devel@lists.sourceforge.net \
--cc=jsmeix@suse.de \
--cc=mike@easysw.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=rlk@alum.mit.edu \
/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.