Yahoo Groups archive

Digital BW, The Print

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

Message

Re: 1160: UT-FS and which paper? or QTR? -Paul

2005-04-08 by dlruckus

Paul,
Thanks for your recent response on paper curves.

In regard to EEM yellowing in Florida.--It doesn't necessarily take
years. I had some of the Archival labeled paper yellow while sitting
on an open shelf for only a few days. I was making small test prints
and left a stack scattered on a shelf. The edges and corners exposed
yellowed in less than a week. I don't think it was warming but may
well have had something to do with OBA burnoff. I also have prints on
EEM that have been around now for a couple of years and have Not
yellowed, so it's anybodys guess. I did decide that any EEM prints I
gave away for display would be matted flush to the image and signed
directly on the print so as to avoid comparisons to the papers white
borders and matt whites.

Regards
Duane

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Paul Roark"
<paul.roark@v...> wrote:
> Peter,
> 
> > 
> > 1. How archival is EEM with UT-FS? ...
> 
> It is very lightfast, but since it is acidic, it is not archival. 
Wilhelm
> rates is as having a storage life of just over 100 years. However,
that is
> in ideal conditions.  In hot, humid environments, the life might be much
> shorter.  Wilhelm originally warned of yellowing in 30 years.  There are
> some stories of yellowing in Florida in just a few years, but if
that was
> with the older pigs, I wonder if that was the warming of the pigs
they were
> seeing. 
> 
> 
> > 2. I do need to mail the print. Rolling it is out of the question,
> > right? I plan to pack it in an archival polyethylene bag from
> > clearbags.com
> 
> Many roll prints.  I think it's tacky for anything above a poster.  I
> recommend spraying with Lascaux Fixativ before shipping.
> 
> 
> Paul
> www.PaulRoark.com

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.