11 | TIFF Test Images
12 |
15 | Test images are available for most formats supported by the library.
16 | Most of the images included in the test kit are also part of this
17 | documentation (albeit in TIFF rather than GIF or JFIF).
18 | The images are kept in a separate archive that should be located in
19 | the same directory as this software.
20 |
21 |
22 |
23 |
24 | The latest archive of test images is located at 25 | 26 | ftp://ftp.remotesensing.org/pub/libtiff/pics-3.8.0.tar.gz 27 | 28 |
29 | There are two other good sources for TIFF test images: 30 | the contributed software contrib/dbs includes several 31 | programs that generate test images suitable for debugging, and 32 | the tiffcp program can be used to generate a variety 33 | of images with different storage characteristics. 34 | 35 |
36 |
11 | TIFF Documentation
12 | 15 | A copy of the 6.0 specification is available from Adobe at 16 | http://partners.adobe.com/public/developer/en/tiff/TIFF6.pdf, or from the libtiff 17 | ftp site at 18 | ftp://ftp.remotesensing.org/pub/libtiff/doc/TIFF6.pdf.
19 | 20 |
21 | Draft TIFF Technical Note #2 covers problems 22 | with the TIFF 6.0 design for embedding JPEG-compressed data in TIFF, and 23 | describes an alternative.
24 | 25 | Other Adobe information on TIFF can be retrieved from: 26 | 27 | 28 | http://partners.adobe.com/public/developer/tiff/index.html 29 | 30 |
31 | Joris Van Damme maintains a list of known tags and their descriptions and 32 | definitions. It is available online at 33 | 34 | http://www.awaresystems.be/imaging/tiff/tifftags.html 35 | 36 |
37 | There is a FAQ, related both to TIFF format and libtiff library: 38 | 39 | http://www.awaresystems.be/imaging/tiff/faq.html 40 | 41 |
24 | This document describes the changes made to the software between the 25 | previous and current versions (see above). 26 | If you don't find something listed here, then it was not done in this 27 | timeframe, or it was not considered important enough to be mentioned. 28 | The following information is located here: 29 |
TIFF home page.24 | This document describes the changes made to the software between the 25 | previous and current versions (see above). 26 | If you don't find something listed here, then it was not done in this 27 | timeframe, or it was not considered important enough to be mentioned. 28 | The following information is located here: 29 |
TIFF home page.
TIFF home page.24 | This document describes the changes made to the software between the 25 | previous and current versions (see above). 26 | If you don't find something listed here, then it was not done in this 27 | timeframe, or it was not considered important enough to be mentioned. 28 | The following information is located here: 29 |
TIFF home page.
11 | Introduction to the TIFF Documentation
12 | 16 | The following definitions are used throughout this documentation. 17 | They are consistent with the terminology used in the TIFF 6.0 specification. 18 | 19 |
43 | In order to better understand how TIFF works (and consequently this 44 | software) it is important to recognize the distinction between the 45 | physical organization of image data as it is stored in a TIFF and how 46 | the data is interpreted and manipulated as pixels in an image. TIFF 47 | supports a wide variety of storage and data compression schemes that 48 | can be used to optimize retrieval time and/or minimize storage space. 49 | These on-disk formats are independent of the image characteristics; it 50 | is the responsibility of the TIFF reader to process the on-disk storage 51 | into an in-memory format suitable for an application. Furthermore, it 52 | is the responsibility of the application to properly interpret the 53 | visual characteristics of the image data. TIFF defines a framework for 54 | specifying the on-disk storage format and image characteristics with 55 | few restrictions. This permits significant complexity that can be 56 | daunting. Good applications that handle TIFF work by handling as wide 57 | a range of storage formats as possible, while constraining the 58 | acceptable image characteristics to those that make sense for the 59 | application. 60 | 61 | 62 |
63 |
26 | This document describes the changes made to the software between the 27 | previous and current versions (see above). 28 | If you don't find something listed here, then it was not done in this 29 | timeframe, or it was not considered important enough to be mentioned. 30 | The following information is located here: 31 |
37 |
TIFF home page.| 26 | |
27 | TIFFClose − close a previously opened 28 | TIFF file 29 | |
30 |
| 38 | |
39 | #include <tiffio.h> 40 | 41 |void TIFFClose(TIFF *tif) 42 | |
43 |
| 51 | |
52 | TIFFClose closes a file that was previously opened 53 | with TIFFOpen(3TIFF). Any buffered data are flushed 54 | to the file, including the contents of the current directory 55 | (if modified); and all resources are reclaimed. 56 | |
57 |
| 65 | |
66 | All error messages are directed to the routine. Likewise, 67 | warning messages are directed to the 68 | TIFFWarning(3TIFF) routine. 69 | |
70 |
| 78 | |
79 | libtiff(3TIFF), TIFFOpen(3TIFF) 80 | 81 |Libtiff library home page: 82 | http://www.remotesensing.org/libtiff/ 83 | |
84 |
9 | Bugs, Bugzilla, and the TIFF Mailing List
10 | 13 | This software is free. Please let us know when you find a problem or 14 | fix a bug. 15 | 16 |
17 | Thanks to MapTools.org, libtiff now uses 18 | bugzilla to track bugs. All bugs filed in the older bugzilla at 19 | bugzilla.remotesensing.org (pre April 2008) have unfortunately been lost. 20 |
21 | If you think you've discovered a bug, please first check to see if it is 22 | already known by looking at the list of already reported bugs. You can do so 23 | by visiting the buglist at 24 | http://bugzilla.maptools.org/buglist.cgi?product=libtiff. Also verify that 25 | the problem is still reproducable with the current development software 26 | from CVS. 27 |
28 | If you'd like to enter a new bug, you can do so at 29 | http://bugzilla.maptools.org/enter_bug.cgi?product=libtiff. 30 |
31 | If you'd like to inform us about some kind of security issue that should not 32 | be disclosed for a period of time, then you can contact maintainers directly. 33 | Send a copies of your report to the following people: Frank Warmerdam 34 | <warmerdam@pobox.com>, 35 | Andrey Kiselev 36 | <dron@ak4719.spb.edu>. 37 |
38 | 39 | Of course, reporting bugs is no substitute for discussion. The 40 | tiff@lists.maptools.org mailing 41 | list is for users of this software, and discussion TIFF issues in general. 42 | It is managed with the Mailman software, and the web interface for subscribing 43 | and managing your access to the list is at:
44 | 45 | http://lists.maptools.org/mailman/listinfo/tiff
46 | 47 | Posts to the list are only accepted from members of the list in order 48 | to limit the amount of spam propagated. Also, to be approved as a member 49 | you will need to email the list administrator with a brief description of 50 | why you are interested in TIFF so we can weed out spammers.
51 | 52 | A Long Term 53 | Archive including recent messages, and most messages back to 1993, 54 | with search capabilities is available, and 55 | has been prepared and hosted by AWare 56 | Systems.
57 | 58 | 59 |