Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Aardenburg-Imaging 30 MLux Hr results

2010-02-11 by Mark

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "horstenj" <j.h.j.h@...> wrote:
>
> 
> 
> --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Mark" <mark@> wrote:
> > 
> > Hence, I founded AaI&A to help fill the current print permanence information void for the end-user.  It is this individual photographer or printmaker whom I need to reach for financial support.  
> 
> Mark,
> 
> This week you've received mine. You have a great initiative and, like many others said already, we need to support you in our own interest.
> 
> Joost
>

To Joost, and the other digital BW readers who have recently joined, each new member that joins the AaI&A digital print research program gives me a real boost in spirit. It keeps me going, so I thank you all.

Joost, I note you are from the Netherlands, and FWIW, AaI&A's main population of members is understandably from the U.S, but I have members from all over the world now. Interestingly, there are now three rich pockets of geographical membership elsewhere;  the U.K., Australia, and the Netherlands!  I'm really curious about this. I understand the U.K demographic as Pro-imaging.org, an organization dedicated to professional photographers, became my first group sponsor. Australia is partly defined by a surge of interest in my research on cold storage of photographic collections, but there are likely other reasons as well. As for the Netherlands? I have no clue, but it may just be that my members in the Netherlands may well identify with the the name of my company. The name can indeed be attributed to the small city of Aardenburg in the Netherlands.  My wife's grandparents emigrated from Aardenburg to the U.S. at the turn of the 20th century. 

kind regards,
Mark

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.