Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx018.isp.belgacom.be (inmx018.isp.belgacom.be [195.238.2.79])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id j2MII0U1000402
        for <joris.at.lebbeke@skynet.be>; Tue, 22 Mar 2005 19:18:00 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx018.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j2MIHg0u029054
        for <joris.at.lebbeke@skynet.be>; Tue, 22 Mar 2005 19:17:46 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id 92F291720FA1; Tue, 22 Mar 2005 13:17:21 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198])
	by xserve.flids.com (Postfix) with ESMTP id D6C731720F8D
	for <tiff@remotesensing.org>; Tue, 22 Mar 2005 13:17:19 -0500 (EST)
Received: by wproxy.gmail.com with SMTP id 69so897367wra
	for <tiff@remotesensing.org>; Tue, 22 Mar 2005 10:17:19 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=U22DtA0hGKgXfgRcUx2ZUe2Tr/Sr3SNWl5/jPDRyohAuGXd1zVlK7+wmh3DClScmAQLTHfRDUcXOVdeLgSgCrqI4OoQbQpwzO9Hhn76HxI+CJ/Lu6IOccGkOV7hL0l+quBbxaDbqCr+tWbJ7OOD+o2aP0YEntOMo4ip3lZyqv9A=
Received: by 10.54.96.9 with SMTP id t9mr78786wrb;
	Tue, 22 Mar 2005 10:17:19 -0800 (PST)
Received: by 10.54.13.2 with HTTP; Tue, 22 Mar 2005 10:17:18 -0800 (PST)
Message-ID: <931f8ea9050322101729289cb7@mail.gmail.com>
Date: Tue, 22 Mar 2005 13:17:18 -0500
From: Frank Warmerdam <fwarmerdam@gmail.com>
To: Lee Howard <faxguy@howardsilvan.com>
Subject: Re: [Tiff] tif_jpeg.c and 12bit JPEG Files
In-Reply-To: <42405DDB.5070507@howardsilvan.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <931f8ea905032209207728feb5@mail.gmail.com>
	<42405DDB.5070507@howardsilvan.com>
Cc: libtiff-Mailinglist <tiff@remotesensing.org>,
        David Gilbert <dgilbert@dclg.ca>
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: warmerdam@pobox.com
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: 82b7a18e9aeaa9a805f7d5eeb212408f

On Tue, 22 Mar 2005 10:03:07 -0800, Lee Howard <faxguy@howardsilvan.com> wrote:
> There was also some discussion on the JPEG mailing list about adding
> support for CIELAB JPEG (fax).  Patches to enable this support are
> available.  I believe that this discussion occurred a week or two
> earlier than David's post to that list.  In the end, however, it sounded
> like the libjpeg maintainers were not interested in applying such
> patches to libjpeg6, and indicated that they would not be looking at
> including them until "v7".  I have done some work to libtiff to allow
> libtiff to make use of CIELAB JPEG in a "patched" libjpeg.  I am
> interested in seeing this work make it into the libtiff CVS.  See:
> 
>   http://bugzilla.remotesensing.org/show_bug.cgi?id=736

Lee, 

I have read this over, and it looks ... complicated.  However, it seems
that all the information needed is there to incorporate changes as
time permits. 
 
> As it appears to me that libjpeg development is essentially comatose, I
> think that a successful fork would be relatively easy to accomplish, and
> I fully support this endeavor.  I don't envision the future "v7" coming
> from that group of people anytime soon (years).

There was discussion of Tom Lane handing off libjpeg leadership to 
someone new and Dave and I don't want to interfere with that as long
as the new libjpeg7 stream includes some reasonable approach to 
support 8 and 12 bit files in a single build of libjpeg.  Ideally such v7
work might start from Mk1, or a slightly different approach to the same
thing that Dave is considering after feedback on the libjpeg list. 

My point here is that I don't think either Dave or I are especially keen to
be responsible for ongoing active development on libjpeg if we can avoid
it, so we don't really want to usurp control from others.  However, we
have immediate commercial needs - hence the Mk1 implementation.  And
we want to make it available to others to use or build on if so desired. 
If a "natural successor" to Tom does not emerge, we are willing to maintain
the Mk1 as v7 but we would likely need additional help since we don't
want to become to tied down with libjpeg.  It is easy to see that I am 
already quite negligent when it comes to libtiff maintenance!  

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent
_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
