AWARE [SYSTEMS]
AWare Systems, , Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
August 2009

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
Archive maintained by AWare Systems



New Datamatrix section



Valid HTML 4.01!



Thread

2009.08.27 18:13 "Libtiff 4.4.0beta4 Released", by Bob Friesenhahn
2009.08.27 18:35 "Old and New JPEG Compression with Single libtiff?", by Kevin Myers
2009.08.27 19:00 "Re: Old and New JPEG Compression with Single libtiff?", by Bob Friesenhahn
2009.08.27 18:55 "Re: Libtiff 4.4.0beta4 Released", by Edward Lam
2009.08.27 19:07 "Re: Libtiff 4.4.0beta4 Released", by Bob Friesenhahn
2009.08.27 19:14 "Re: Libtiff 4.4.0beta4 Released", by Frank Warmerdam
2009.08.27 19:01 "Re: Libtiff 4.4.0beta4 Released", by Edward Lam
2009.08.27 19:15 "Re: Libtiff 4.4.0beta4 Released", by Bob Friesenhahn

2009.08.27 18:35 "Old and New JPEG Compression with Single libtiff?", by Kevin Myers

Sometime within the past few months, I recall seeing a message posted on the 
Tiff list where the poster had some kind of idea regarding how to support 
both old and new JPEG compression in tiff files using the same libtiff, i.e. 
no need to compile separate versions.  Does anyone else recall this?  Does 
anyone know if or when this might get included in a release?

The reason I ask is that because I recently found that my high dollar Kodak 
i280 scanner produces *old* JPEG compressed grayscale images of standard 
documents, while on the other hand it also produces *new* JPEG compressed 
color images for stitched long documents (e.g. well logs).  Stuff like this 
just kills me.  What kind of developer would implement conflicting garbage 
like that, especially for a multi-thousand dollar scanner?  Anyway, I also 
found out that my irreplaceable legacy well log display application is only 
capable of displaying *old* JPEG compressed images, while most of my other 
image related applications expect to deal with *new* JPEG compressed images.

I hate to keep two separate versions of libtiff around just for dealing with 
these issues.  The libtiff message that I recall seeing appeared to be a 
potential solution to these problems, but I wasn't aware of the related 
problems with my own applications, and didn't realize how important this 
would end up being for my own usage.  Therefore I didn't keep the original 
message, and don't recall the poster's name or the actual subject of the 
message.

Hope I wasn't dreaming...

Thanks,
Kevin M.