AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2012.10.18 02:50 "[Tiff] Surprising Jhove output for TIFF produced by Kyocera 4550 workstation - Well Formed?", by Andrew Roughan
2012.10.18 17:57 "Re: [Tiff] Surprising Jhove output for TIFF produced by Kyocera, 4550 workstation - Well Formed?", by Gary McGath

2012.10.18 17:57 "Re: [Tiff] Surprising Jhove output for TIFF produced by Kyocera, 4550 workstation - Well Formed?", by Gary McGath

On a whim I had a look at what output JHOVE provides on the TIFF scanner output produced by the Kyocera 4550 workstation.

I was surprised to see the status as well-formed and valid.

JhoveView (Rel. 1.7, 2012-08-12)
2012-10-18 13:33:04 EST ?Date:
C:\Temp\Kyocera4550Scan.tif ?RepresentationInformation:
BYTESTREAM, Rel. 1.3 (2007-04-10) ? ReportingModule:
2012-10-16 13:31:32 EST ? LastModified:

>? Size: 185092
>? Format: bytestream
>? Status: Well-Formed and valid
>? SignatureMatches:
>?? TIFF-hul
>? MIMEtype: application/octet-stream

I was particularly surprised given the JHOVE TIFF module help includes the following "A TIFF file is well-formed if... all IFDs are 16-bit word aligned". But in addition, surely the use of compression code 6 warrants a warning of some kind?

Issues like this are best raised on the JHOVE list (http://sourceforge.net/mailarchive/forum.php?forum_name=jhove-discuss) or by entering a bug on SourceForge (http://sourceforge.net/projects/jhove/).

What it's actually saying is that it's a well-formed and valid bytestream. That's JHOVE's ultimate fallback, since anything made out of bytes is a bytestream. It's saying the signature (i.e., the characteristic first few bytes) matches TIFF, nothing more than that.

If you run JHOVE with just the TIFF module selected from the Edit menu, then it will tell you why it doesn't think it's a valid TIFF.

--
Gary McGath, Professional Software Developer http://www.garymcgath.com