AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
October 2004

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



Valid HTML 4.01!



Thread

2004.10.01 07:22 "BigTIFF extension issue", by Joris Van Damme
2004.10.01 16:41 "Re: BigTIFF extension issue", by Ian Ameline
2004.10.01 16:53 "Re: BigTIFF extension issue", by Frank Warmerdam
2004.10.01 17:01 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.01 17:19 "Re: BigTIFF extension issue", by Steve Carlsen
2004.10.01 17:27 "Re: BigTIFF extension issue", by Chris Losinger
2004.10.01 17:48 "Re: BigTIFF extension issue", by Bob Friesenhahn
2004.10.01 17:48 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.01 17:50 "Re: BigTIFF extension issue", by Frank Warmerdam
2004.10.01 18:03 "Re: BigTIFF extension issue", by Chris Losinger
2004.10.01 22:22 "Re: BigTIFF extension issue", by Chris Cox
2004.10.02 01:21 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.02 01:45 "Re: BigTIFF extension issue", by Bob Friesenhahn
2004.10.02 03:19 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.02 10:20 "Re: BigTIFF extension issue", by Andy Cave
2004.10.03 15:59 "Re: BigTIFF extension issue", by Bob Friesenhahn
2004.10.04 08:53 "Re: BigTIFF extension issue", by Andy Cave
2004.10.04 11:56 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.02 03:43 "Re: BigTIFF extension issue", by Chris Cox
2004.10.02 04:10 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.02 04:41 "Re: BigTIFF extension issue", by Bob Friesenhahn
2004.10.02 04:53 "Re: BigTIFF extension issue", by Chris Cox
2004.10.02 10:28 "Re: BigTIFF extension issue", by Andy Cave
2004.10.03 00:39 "Re: BigTIFF extension issue", by Chris Cox
2004.10.04 08:34 "Re: BigTIFF extension issue", by Andy Cave
2004.10.04 14:02 "Re: BigTIFF extension issue", by Bob Friesenhahn
2004.10.04 14:21 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.04 14:57 "Re: BigTIFF extension issue", by Andy Cave
2004.10.04 23:11 "Re: BigTIFF extension issue", by Chris Cox
2004.10.05 08:43 "Re: BigTIFF extension issue", by Andy Cave
2004.10.05 13:27 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.04 11:29 "Re: BigTIFF extension issue", by Rob Tillaart
2004.10.04 14:54 "Re: BigTIFF extension issue", by Bob Friesenhahn
2004.10.04 15:04 "Re: BigTIFF extension issue", by Andy Cave
2004.10.04 15:23 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.04 15:43 "Re: BigTIFF extension issue", by Bob Friesenhahn
2004.10.04 15:54 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.04 16:50 "Re: BigTIFF extension issue", by Steve Carlsen
2004.10.04 18:20 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.04 18:30 "Re: BigTIFF extension issue", by Bill Bither
2004.10.04 18:36 "Re: BigTIFF extension issue", by Bob Friesenhahn
2004.10.04 18:46 "Re: BigTIFF extension issue", by Joris Van Damme
2004.10.04 18:59 "Re: BigTIFF extension issue", by Andy Cave
2004.10.05 14:41 "Re: BigTIFF extension issue", by Fernando Loygorri
2004.10.04 18:49 "Re: BigTIFF extension issue", by Andy Cave
2004.10.04 19:00 "Re: BigTIFF extension issue", by Bob Friesenhahn

2004.10.01 17:48 "Re: BigTIFF extension issue", by Joris Van Damme

> Nevertheless, I don't really mind using ".tif", especially if developers on
> this list and any other developers we can influence would attempt to use
> guidelines for new releases such as:
>
> When writing a BigTIFF file, we let the user know, with a warning something
> like:
>  "Given the file size, note that you are creating a special "Big" TIFF file,
> which may be incompatible with some applications."

I can agree with that. In fact, I think speaking Photoshopish now because it
really depends on the app, that writing Classic or Big TIFF should be a consious
user decision, just like today the byte order and compression scheme is. I think
this has been discussed before: due to the nature of TIFF, the LibTiff layer
cannot decide what flavor to write. When starting the writing, it cannot know
what is going to follow, nor with what ratio it is going to be able to compress.
Plus, any number of things may next happen on the written TIFF file, including
appending a huge number of huge pages. In many cases, the app has the same
problem. So, in many cases, including the Photoshopish class of apps, the user
should be able to make the final descision.

> When readers encounter such a file, if we can't deal with it yet, we let the
> user know in some helpful way such as "This type of TIFF file is not yet
> supported." rather than just reporting "Unknown Format" or some such thing.

While LibTiff does not yet support BigTIFF, it could be very easy to
nevertheless update it to already recognize at least the BigTIFF header already,
and return the appropriate error message you mention here, instead of a generic
'not a tiff file' - ish error. Since many apps stay reasonably up to LibTiff
date, that should already come a long way towards meeting your wish.

Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be
Download your free TIFF tag viewer for windows here:
http://www.awaresystems.be/imaging/tiff/astifftagviewer.html