AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2000.02.02 17:50 "Microsoft Imaging and Jpeg in TIFF", by Myers, Randall
2000.02.02 21:35 "Re: Microsoft Imaging and Jpeg in TIFF", by Andy
2000.02.03 01:42 "Re: Microsoft Imaging and Jpeg in TIFF", by Joris Van Damme
2000.02.03 01:55 "Re: Microsoft Imaging and Jpeg in TIFF", by Tom Lane
2000.02.03 16:24 "Re: Microsoft Imaging and Jpeg in TIFF", by Joris Van Damme
2000.02.05 20:46 "Re: Microsoft Imaging and Jpeg in TIFF", by Niles Ritter
2000.02.07 15:43 "Re: Microsoft Imaging and Jpeg in TIFF", by Joris Van Damme
2000.02.08 19:45 "Re: Microsoft Imaging and Jpeg in TIFF", by Joris Van Damme
[...]

2000.02.03 16:24 "Re: Microsoft Imaging and Jpeg in TIFF", by Joris Van Damme

Andy wrote:
> I use to make Wang JPEG images the freely available "Wang Imaging for
> Windows 95."

Yeah, I wasn't aware of it. Of course I have that fancy wang thing. Thank you for pointing that out.

> Could you send me your sample TIFF/J image? I would see how it is. Thank > you.

The only jpeg embedding tiff I've found is (or was?) part of the official testpics collection, it is (or was) called quad-jpeg. It's a good image, JPEG not OJPEG. I had some problems with it in the beginning, but it turns out the libtiff/libjpeg combination is perfectly able to read it *IF* you instruct libjpeg to ouput RGB instead of YCbCr through the appropriate TIFF pseudo-tag. Otherwise, it gets as bad as an access violation (but maybe I've made some bad changes or something, it could be MY problem and not a libtiff/libjpeg problem).

Anyway, I'll mail it to your private account.

As for the problem here, OJPEG images that in fact are not OJPEG as they should be... either we find a way to recognize them and decode them (both!) with 100% certainty; or either we give up on OJPEG, that will exclude these troublesome images too. At this point, I think I'll go for that second option.

Joris