LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
March 2005
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2005.03.22 18:17 "Re: tif_jpeg.c and 12bit JPEG Files", by Frank Warmerdam
On Tue, 22 Mar 2005 10:03:07 -0800, Lee Howard 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