2005.03.22 18:03 "Re: [Tiff] tif_jpeg.c and 12bit JPEG Files", by Lee Howard
Finally, the "Mk1" library is essentially a libjpeg fork. There is discussion on the JPEG mailing list about how to move to a libjpeg7 with similar capabilities. While it is likely that a libjpeg7 would take a somewhat different approach than the Mk1 library, it is hoped that the work being done now will help in that transition.
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:
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 are numerous enhancements and developments available for libjpeg (not limited to the CIELAB work I mention) that have been indefinitely "postponed" by the current libjpeg maintainers. It is my recommendation to you that you incorporate as much of these patches and developments as possible into this fork so as to gain whatever development momentum and strength that can be acquired from the developers of those works. I do not believe that it would take very long for the community as a whole to recognize the Mk1 library as libjpeg7.