freeswitch

History

Steve Underwood b989f8d3eb The tiff-4.0.2 distribution's configure.ac seems to have two lines missing AC_PROG_LIBTOOL m4_include(m4/acinclude.m4) Adding these and taking out all the Makefile.in files from the tiff-4.0.2 directory seems to sort out the build issues.		2012-09-02 14:38:13 +08:00
..
Makefile.am	Added tiff-4.0.2 as the first step in moving from libtiff 3.8.2 to libtiff 4.0.2	2012-09-01 17:59:43 +08:00
mfs_file.c	Added tiff-4.0.2 as the first step in moving from libtiff 3.8.2 to libtiff 4.0.2	2012-09-01 17:59:43 +08:00
README	Added tiff-4.0.2 as the first step in moving from libtiff 3.8.2 to libtiff 4.0.2	2012-09-01 17:59:43 +08:00

README

Date:    Mon, 23 Jun 1997 13:30:48 +0200
To:      <sam@cthulhu.engr.sgi.com>

From:    "Mike Johnson" <mikehunt@swipnet.se>
Subject: libtiff - Thanks

Return-Path: mikehunt@swipnet.se 
Delivery-Date: Mon, 23 Jun 1997 06:53:39 -0700

Hi Sam,

I noticed in the README from libtiff that you would like to know about
what people have done with libtiff, so I thought I would drop you a
line.

We have used libtiff to create and convert TIFF images of financial
documents which are sent from and to major document processing systems
in Sweden and Denmark.

I would like to express my deep gratitude to yourself and Sillicon
Graphics for making this excellent library available for public use.
There is obviously a lot of work that has gone in to libtiff and the
quality of the code and documentation is an example to others.

One thing that libtiff did not do was work on a memory area rather than
files. In my applications I had already read a TIFF or other format
file in to memory and did not want to waste I/O writing it out again
for libtiff's benefit. I therefore constructed a set of functions to
pass up to TIFFClientOpen to simulate a file in memory. I have attached
my mfs (memory file system) source code for you to use or junk, as you
see fit. :-)

Once again, thanks very much for making my life simpler.

Best Regards,

Mike Johnson.