Go to file
2017-10-29 18:50:41 +00:00
archive * tools/Makefile.am: The libtiff tools bmp2tiff, gif2tiff, 2016-06-05 19:53:59 +00:00
build fax2tiff: Pass the FAX_Client_Data struct as client data 2017-10-29 18:28:43 +00:00
config * refresh autoconf/make stuff with what is on Ubuntu 16.04 (minor changes) 2017-07-11 09:10:28 +00:00
contrib fax2tiff: Pass the FAX_Client_Data struct as client data 2017-10-29 18:28:43 +00:00
html fax2tiff: Pass the FAX_Client_Data struct as client data 2017-10-29 18:28:43 +00:00
libtiff fax2tiff: Pass the FAX_Client_Data struct as client data 2017-10-29 18:28:43 +00:00
m4 * refresh autoconf/make stuff with what is on Ubuntu 16.04 (minor changes) 2017-07-11 09:10:28 +00:00
man fax2tiff: Pass the FAX_Client_Data struct as client data 2017-10-29 18:28:43 +00:00
port fax2tiff: Pass the FAX_Client_Data struct as client data 2017-10-29 18:28:43 +00:00
test fax2tiff: Pass the FAX_Client_Data struct as client data 2017-10-29 18:28:43 +00:00
tools tiff2pdf.c: Fix possible overflow in bounds check computation and eliminate signed/unsigned comparison. 2017-10-29 18:50:41 +00:00
.appveyor.yml * .appveyor.yml, .travis.yml, build/travis-ci: apply patches 2017-06-09 22:07:08 +00:00
.cvsignore added files 2005-11-21 01:07:19 +00:00
.travis.yml * .appveyor.yml, .travis.yml, build/travis-ci: apply patches 2017-06-09 22:07:08 +00:00
aclocal.m4 * html/bugs.html: Replace Andrey Kiselev with Bob Friesenhahn for 2016-04-08 02:34:00 +00:00
autogen.sh * libtiff 4.0.0alpha4 released. 2009-08-27 17:40:49 +00:00
ChangeLog tiff2pdf.c: Fix possible overflow in bounds check computation and eliminate signed/unsigned comparison. 2017-10-29 18:50:41 +00:00
CMakeLists.txt * .travis.yml, build/travis-ci: new files from 2017-06-08 20:46:10 +00:00
commit
COMMITTERS Add myself to COMMITTERS 2014-11-19 22:26:42 +00:00
configure fax2tiff: Pass the FAX_Client_Data struct as client data 2017-10-29 18:28:43 +00:00
configure.ac libtiff 4.0.8 released 2017-05-21 19:10:50 +00:00
configure.com Add accessor functions for the opaque type TIFFField. 2012-07-29 15:45:29 +00:00
COPYRIGHT
HOWTO-RELEASE * libtiff 4.0.6 released. 2015-09-12 19:46:23 +00:00
HOWTO-SECURITY-RELEASE note vs in topic and mailing list url 2012-04-06 16:45:55 +00:00
libtiff-4.pc.in * libtiff-4.pc.in: Added libtiff pkg-config .pc file support. 2010-11-27 20:54:51 +00:00
Makefile.am * Makefile.am: Added a 'coverity' rule to assist with Coverity 2015-09-06 19:34:06 +00:00
Makefile.in fax2tiff: Pass the FAX_Client_Data struct as client data 2017-10-29 18:28:43 +00:00
Makefile.vc Fix clean rules to be more precise, avoiding warnings from "del" 2008-01-01 15:53:10 +00:00
nmake.opt * nmake.opt: support a DEBUG=1 option, so as to adjust OPTFLAGS and use 2017-10-10 14:39:43 +00:00
README Record changes for libtiff 4.0.1 2012-02-18 21:53:27 +00:00
README.vms Added support for OpenVMS by Alexey Chupahin, elvis_75@mail.ru. 2006-04-21 14:22:57 +00:00
RELEASE-DATE libtiff 4.0.8 released 2017-05-21 19:10:50 +00:00
SConstruct Regenerated. 2007-02-24 15:03:47 +00:00
tiff.spec
TODO
VERSION libtiff 4.0.8 released 2017-05-21 19:10:50 +00:00

$Header: /cvs/maptools/cvsroot/libtiff/README,v 1.7 2012-02-18 21:53:27 bfriesen Exp $


TIFF Software Distribution
--------------------------
This file is just a placeholder; all the documentation is now in
HTML in the html directory.  To view the documentation point your
favorite WWW viewer at html/index.html; 

e.g.

    firefox html/index.html

If you don't have an HTML viewer then you can read the HTML source
or fetch a PostScript version of this documentation from the directory

    ftp://ftp.remotesensing.org/pub/libtiff/

If you can't hack either of these options then basically what you
want to do is:

    % ./configure
    % make
    % su
    # make install

More information, email contacts, and mailing list information can be 
found online at http://www.remotesensing.org/libtiff/.


Use and Copyright
-----------------
Silicon Graphics has seen fit to allow us to give this work away.  It
is free.  There is no support or guarantee of any sort as to its
operations, correctness, or whatever.  If you do anything useful with
all or parts of it you need to honor the copyright notices.   I would
also be interested in knowing about it and, hopefully, be acknowledged.

The legal way of saying that is:

Copyright (c) 1988-1997 Sam Leffler
Copyright (c) 1991-1997 Silicon Graphics, Inc.

Permission to use, copy, modify, distribute, and sell this software and 
its documentation for any purpose is hereby granted without fee, provided
that (i) the above copyright notices and this permission notice appear in
all copies of the software and related documentation, and (ii) the names of
Sam Leffler and Silicon Graphics may not be used in any advertising or
publicity relating to the software without the specific, prior written
permission of Sam Leffler and Silicon Graphics.

THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, 
EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY 
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.  

IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR
ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND,
OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF 
LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE 
OF THIS SOFTWARE.