|AWARE [SYSTEMS]||Imaging expertise for the Delphi developer|
|TIFF and LibTiff Mailing List Archive|
LibTiff Mailing List
1999.06.11 01:48 "Re: Large File Support", by <firstname.lastname@example.org>
Yes and no. (These comments also apply to your other comment regarding a library interface.) Your points are well taken, but they caused me to realize something VERY fundamental: We really have _*_TWO_*_ TIFF specs! Obviously, there is the core file spec itself, to which your comments apply. But even MORE so, there is an "interface standard" (API in effect) also. Why more so? Look at the percentage of emails regarding the basic file format versus regarding the libtiff interface! So, yes we of course have to keep the implementation of a new version (or concept!) of libtiff separate from the file format itself. But let's not specify a file format that does not lend itself to a good library implementation or specify a good library implementation that is inconsistent with a good (smaller, simpler, more extensive, etc.) file format. Chris Hanson wrote: > glen <email@example.com> wrote: > > A nice way to handle it would be to add a layer to handle TIFF files like a > > Microsoft "COM" object. The idea is that you query the layer as to what > > interface > > (e.g., 64-bit vs. 32-bit) the object (i.e., TIFF file) supports. > > Please, let's keep the TIFF file format and the implementation of any > particular library separate. There are people who don't use libtiff to > handle TIFF images.