ꦫꦣꦺꦤ꧀ꦄꦤ꧀ꦠꦱꦺꦤ

PATH: usr / share / doc / libtiff-devel-4.0.3 / html

<HTML>
<HEAD>
<TITLE>
Introduction to the TIFF Documentation
</TITLE>
</HEAD>
<BODY BGCOLOR=white> 

<H1>
<IMG SRC=images/strike.gif WIDTH=128 HEIGHT=100 ALIGN=left HSPACE=6>
Introduction to the TIFF Documentation
</H1>

The following definitions are used throughout this documentation.
They are consistent with the terminology used in the TIFF 6.0 specification.

<DL>
<DT>Sample
<DD>The unit of information stored in an image; often called a
 channel elsewhere. Sample values are numbers, usually unsigned
 integers, but possibly in some other format if the SampleFormat
 tag is specified in a TIFF
<DT>Pixel
<DD>A collection of one or more samples that go together.
<DT>Row
<DD>An Nx1 rectangular collection of pixels.
<DT>Tile
<DD>An NxM rectangular organization of data (or pixels).
<DT>Strip
<DD>A tile whose width is the full image width.
<DT>Compression
<DD>A scheme by which pixel or sample data are stored in
 an encoded form, specifically with the intent of reducing the
 storage cost.
<DT>Codec
<DD>Software that implements the decoding and encoding algorithms
 of a compression scheme.
</UL>

In order to better understand how TIFF works (and consequently this
software) it is important to recognize the distinction between the
physical organization of image data as it is stored in a TIFF and how
the data is interpreted and manipulated as pixels in an image. TIFF
supports a wide variety of storage and data compression schemes that
can be used to optimize retrieval time and/or minimize storage space.
These on-disk formats are independent of the image characteristics; it
is the responsibility of the TIFF reader to process the on-disk storage
into an in-memory format suitable for an application. Furthermore, it
is the responsibility of the application to properly interpret the
visual characteristics of the image data. TIFF defines a framework for
specifying the on-disk storage format and image characteristics with
few restrictions. This permits significant complexity that can be
daunting. Good applications that handle TIFF work by handling as wide
a range of storage formats as possible, while constraining the
acceptable image characteristics to those that make sense for the
application.

<HR>

Last updated: $Date: 1999/08/09 20:21:21 $

</BODY>
</HTML>

[-] v3.7.3.html [edit]
[-] v3.4beta028.html [edit]
[-] v3.7.2.html [edit]
[-] misc.html [edit]
[-] v3.6.1.html [edit]
[-] v3.4beta024.html [edit]
[-] v3.7.1.html [edit]
[-] v3.8.1.html [edit]
[-] v3.4beta035.html [edit]
[+] ..
[-] v3.4beta016.html [edit]
[-] v3.4beta033.html [edit]
[-] intro.html [edit]
[-] index.html [edit]
[-] v4.0.0.html [edit]
[-] v4.0.1.html [edit]
[-] build.html [edit]
[-] v3.4beta007.html [edit]
[-] TIFFTechNote2.html [edit]
[-] v3.8.0.html [edit]
[-] v3.5.7.html [edit]
[-] v3.9.0beta.html [edit]
[-] v3.5.5.html [edit]
[-] v3.7.0.html [edit]
[-] document.html [edit]
[-] v3.7.0beta2.html [edit]
[-] v3.9.1.html [edit]
[-] images.html [edit]
[-] v3.5.3.html [edit]
[-] libtiff.html [edit]
[-] tools.html [edit]
[-] v3.7.0beta.html [edit]
[-] v3.5.1.html [edit]
[-] bugs.html [edit]
[-] v3.7.4.html [edit]
[-] v3.5.2.html [edit]
[-] v3.4beta034.html [edit]
[-] v3.6.0.html [edit]
[-] v3.4beta018.html [edit]
[+] images
[-] v3.4beta031.html [edit]
[-] v3.5.6-beta.html [edit]
[-] v3.8.2.html [edit]
[-] v3.4beta036.html [edit]
[-] addingtags.html [edit]
[-] contrib.html [edit]
[-] v3.9.2.html [edit]
[+] man
[-] v3.4beta032.html [edit]
[-] v4.0.2.html [edit]
[-] v3.5.4.html [edit]
[-] support.html [edit]
[-] internals.html [edit]
[-] v3.7.0alpha.html [edit]
[-] v3.4beta029.html [edit]