Re: Gutenprint curves
Re: Gutenprint curves
- Subject: Re: Gutenprint curves
- From: Robert L Krawitz <email@hidden>
- Date: Mon, 4 Dec 2006 07:08:27 -0500
Date: Mon, 4 Dec 2006 10:15:14 +0100
From: "edmund ronald" <email@hidden>
I have a suggestion, just document the place the files live, and
allow people to provide prebaked files easily (eg. a Tetenal
superglossy Epson 2400 settings file from E.R.) - Most people know
they need to download an ICC profile to some strange place in their
system and then select a rendering intent, so they can live with
the idea of downloading print settings and then customising them,
even by editing the profile. Doesn't mean they know the binary
details of what actually goes into the profile (I don't).
Unfortunately, right now most of these settings live in C source code
(actually, it's data written in C). They're also not based on a "one
file per printer/paper" model -- the paper settings (for all printers)
are in one file, the resolutions are in another file, the ink channels
are in yet another file, and the drop sizes in yet another (see
print-escp2-data.c and escp2-*.c in our src/main directory to
understand what I mean). This is something I want to change (put
everything into some kind of XML format), but it's going to take some
time.
When I actually get around to this, I'm probably not going to change
the overall layout all that much. Separate files for each
printer/resolution/paper combination will be combinatorially messy to
generate, much less maintain, and a lot of the data is shared between
many printers. We certainly won't try to hide where any of this
lives, but it may not be that easy for people to find their way
around.
Certainly if I can come up with a schema for which it's easy for users
to edit I'll do so, but it's not that easy of a problem.
Once setting files can be passed around end-users will throw
themselves at them as it takes the intimidating options out of the
equation.
That would certainly be very desirable. We might create a wiki or
something to allow people to share their settings.
The problem then becomes one of creating these files, and I am sure
some of us will come up with creative solutions. I've just
discovered that the most used print program, Photoshop has a simple
graphical editor for transfer functions built into the Print with
Preview dialog - I am sure this could be used to create
linearisation curves, with a simple script then copying the values
into the right place in a settings file. One could also imagine
simple Javascript web pages that make a file ready to cut and paste
or download.
These are all good suggestions, and I'll have to see what I can do
with them.
> http://sourceforge.net/mailarchive/forum.php?forum_id=6142&max_rows=25&style=nested&viewmonth=200108
>
> Actually, a lot of this -- not everything (in particular, the drop
> sizes and light ink transfer curves), though -- is available in
> Gutenprint. I'd like to find a way to make these additional
> parameters available to users for customization, too. The problem is
> that CUPS provides no way of passing this data through, and PPD files
> in general are clumsy for passing composite data types. If you use
> the Print plugin for the GIMP, you'll find a lot of curve controls
> that aren't available in the CUPS driver.
>
> --
> Robert Krawitz <email@hidden>
>
> Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2
> Member of the League for Programming Freedom -- mail email@hidden
> Project lead for Gutenprint -- http://gimp-print.sourceforge.net
>
> "Linux doesn't dictate how I work, I dictate how Linux works."
> --Eric Crampton
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden