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 07:22 "BigTIFF extension issue", by Joris Van Damme

People,

The current proposal for BigTIFF mentions 'tf8' as extension for BigTIFF. I'd
like your opinions on using 'tif' as an extension, instead. If feel this might
be more appropriate, for these reasons:

- The specification of BigTIFF largely relies on the TIFF specification. I can't
see how it can be more then just a few pages on top of the 121 page TIFF
specification. This seems to support that BigTIFF is much more a new version of
TIFF, rather then a new file format.

- The same statement seems supported by our future codec works to support
BigTIFF. Rather then building a new codec, it'll involve changing the existing
one, and needed changes will probably not be very extensive.

- The 'new version' statement seems to also be supported by the changes in what
is commonly said to be the version number in the TIFF header. 42 becomes 43.
Again, BigTIFF seems much more of a new version of TIFF, not really a new file
format.

- I believe there are precedents. GIF at one time went through a change that was
quite drastic. It nevertheless did not change name or extension, version number
87a became 89a (IIRC), but gif remained gif. Jpeg at one time added the
'progressive jpeg' feature. But extension did not change. I believe that
probably the change in TIFF, when it acquired the tiles scheme and added this to
the strips scheme, was probably a change that was comparable in size. But the
file format stayed labelled the same 'TIFF', and the extension remained the
same. Rather, people talked about 'tiled' tiffs and such much like we now talk
about 'Classic TIFF' and 'BigTIFF'.

- Where file format name and extension really does change, changes in
specification are much more huge. In fact, most often, it's not the same
specification basis - not the same file format. I'm thinking of jpg/jp2, and
png/mng. Png and Mng belong to the same family, but the difference between them
is much more huge then the difference between Classic TIFF and BigTIFF. Same
goes for Jpeg and Jpeg2000.

- I believe average users often have a hard time finding their way in the
confusing Fangorn forest of file format. Let's help 'em. What they know about
files labelled '.tif', pretty much goes for our new BigTIFF, too. So let's stick
with '.tif'.

- One final good reason to stick with '.tif', is, I believe, the acceptance of
the file format, and the support for it. If/when a file called 'yada.tif' does
not work in an application XY SuperViewer that claims to support TIFF, users are
more likely to contact the XY vendor. This one may then reply 'OK, I see this is
a BigTIFF, we don't yet support that', but the vendor will at least be made
aware of the user needs, and the vendor's psychology implies that he will fear
SuperViewer might become known as having inadequate TIFF support. But if/when a
file called 'yada.tf8' does not work in XY SuperViewer, a whole other scenario
is much more likely. The user will scratch his head, wonder 'what is .tf8 in the
first place' for half a second, and next either forget about it, or go looking
for another viewer. The XY vendor is most probably not being nagged. I thus
believe that it is important to stick with the extension '.tif' in order to
facilitate growing support for BigTIFF.


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