Libtiff vv3.9.4 / v4.0.0beta6

It provides support for the Tag Image File Format (TIFF), a widely used format for storing image data on the web and in desktop software.
Included in this software distribution is a library, libtiff, for reading and writing TIFF, a small collection of tools for doing simple manipulations of TIFF images, and documentation on the library and tools.
Libtiff is a portable software, it was built and tested on various systems: UNIX flavors (Linux, BSD, Solaris, MacOS X), Windows, OpenVMS. It should be possible to port libtiff and additional tools on other OSes.
The library, along with associated tool programs, should handle most of your needs for reading and writing TIFF images on 32- and 64-bit machines.
This software can also be used on older 16-bit systems though it may require some effort and you may need to leave out some of the compression support.
What's New in This Release:
· The options parameter in the TIFFOpen and TIFFClientOpen funcs has been extended. When creating new files, you can add option '4' to specify you want to create a ClassicTIFF file, though that is the default and the option is not strictly necessary. (As such, old calling code will continue to function and create ClassicTIFF files.) Or you can add option '8' to specify you want to create a BigTIFF file instead. This new option is also reflected in some of the tools we already upgraded. For instance, you can use the -8 option on tiffcp to have tiffcp produce BigTIFF files instead of the default ClassicTIFF. (Whilst on additional option is provided for version selection when creating new files, no such option is necessary when reading TIFF files. LibTiff reads ClassicTIFF and BigTIFF both, and the application does not need to be aware which TIFF version an opened file is.)
· Although the tag count in BigTIFF is 64bit, we restricted the count in the implementation to a much more reasonable size. This is necessary in current implementation, because all tag data gets read automatically in the IFD reading stage, so if there's half a dozen private tags with multiple gigabytes of data that causes considerable overhead even if the application level is never interested in these tags. Our choice to ignore tags with data longer then a certain sanity value is much needed as things stand. We also recommend to step away from writing tiles that are 8 kilobyte in their uncompressed form, or writing single-line strips, in really big files, resulting in mega's of tiles or strips. It's much more efficient to choose bigger tile or strip sizes, up to several megabyte if needed, and have a few kilo of tiles or strips instead.
· Although it's rare, some application code does directly access file offsets. Some of these are automatically upgraded because they used the toff_t type, others need to be aware that the datatype changed and need to start using toff_t or uint64. This impacts access to tags like the EXIF IFD tag, for example, or the SubIfds tag, or to StripOffsets or TileOffsets, the return type of functions like TIFFCurrentDirOffset, and a parameter type to functions like TIFFSetSubDirectory.
· Although it's rare, some application code does use structures like TIFFHeader or TIFFDirEntry that used to be an exact binary representation of TIFF structures. These need to change. The old TIFFHeader structure is replaced by the new TIFFHeaderClassic, TIFFHeaderBig, and TIFFHeaderCommon structures that are an exact binary representation of the ClassicTIFF and BigTIFF header, and of the part that is common to both. There is no new equivalent for the old TIFFDirEntry structure (or more precisely, there is still a TIFFDirEntry structure, but it is changed, moved to library-private definition, and no longer an exact binary representation of the tag structure of either TIFF version).
· Sizer functions, like TIFFTileSize or TIFFScanlineSize and the like, return a tmsize_t value (tmsize_t is defined as int32 on 32bit machines, and int64 on 64bit machines, and as such it is meant to represent signed memory sizes). This is because we figure 98% of the calling code uses the return value as sizes in allocations and the like. So, any overflow that is theoretically possible with BigTIFF when LibTiff is running on a 32bit system, is best detected inside the sizer functions and it is best to return a type that makes sense as a memory size. If your calling code is the exception and is interested in actual file size, you best use the newer TIFFTileSize64 or TIFFScanlineSize64 function that returns an uint64 type.

Related Scripts

  • Ezwgl 1.50
    EZWGL consists of two parts, a widget library and a graphics library. The widget library implements about a twenty or so commonly used widgets, includ...
  • Tumble 0.33
    Tumble is an utility to construct PDF files from one or more image files. Supported input image file formats are JPEG, and black and white TIFF files ...
  • Eman
    EMAN is a suite of scientific image processing tools aimed primarily at the transmission electron microscopy community, though it is beginning to be u...
DMCA Notice-Privacy Policy
2004 - 2013 DownScripts. All rights reserved.