Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: OT: Is there a "Great Paper Chase" for Colour Photographs?

2006-03-27 by G Guhan Gunaratnam

Thanks a lot Sam.

I didn't know of that colour group, thanks for passing it on.  I'll see you
there

Guhan





On 3/26/06 10:31 AM, "DigitalBlackandWhiteThePrint@yahoogroups.com"
<DigitalBlackandWhiteThePrint@yahoogroups.com> wrote:

> Message: 25      
>    Date: Sun, 26 Mar 2006 07:30:19 -0800
>    From: Sam McCandless <samcc@...>
> Subject: Re: OT:  Is there a "Great Paper Chase" for Colour Photographs?
> 
> My goal, Guhan, is to use the same - and few - matte (I don't like
> glossy) papers for color as for B&W (including BO). But my old
> printers died only recently. And I don't yet know enough about the
> 2400 or the 200/220 to have any idea whether this is realistic even
> as a goal, much less in actual practice. If not, I hope someone will
> "wave me off" before I try to land on so simple a field.
> 
> Not that I mind your asking on this list, Guhan, especially since you
> started with "OT", but there's another Yahoo list,
> archivalcolor@yahoogroups.com, which Antonis, a founder of this list
> along with Martin, also started. It's never been as robust a list,
> but it's still alive and sometimes kicks. The only thread active on
> it right now is one about Lyson's ink sets. But I hope you'll start
> one about papers for archival color prints printed with the ink
> set(s) in which you (and I) are most interested. In about a week, I'm
> going away for a week, but I'll chip in there too as soon as I can. I
> hope other subscribers to this list will too.
> 
> Another possibility, if you're on a Mac, is the Mac Epson list,
> macepsonlist@yahoogroups.com, (what a surprise). It is quite general
> within the Mac context, but it is a nice, small, active list
> nevertheless.
> --
> Sam

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.