]>
Commit | Line | Data |
---|---|---|
8414a40c VZ |
1 | Date: Mon, 23 Jun 1997 13:30:48 +0200 |
2 | To: <sam@cthulhu.engr.sgi.com> | |
3 | ||
4 | From: "Mike Johnson" <mikehunt@swipnet.se> | |
5 | Subject: libtiff - Thanks | |
6 | ||
7 | Return-Path: mikehunt@swipnet.se | |
8 | Delivery-Date: Mon, 23 Jun 1997 06:53:39 -0700 | |
9 | ||
10 | Hi Sam, | |
11 | ||
12 | I noticed in the README from libtiff that you would like to know about | |
13 | what people have done with libtiff, so I thought I would drop you a | |
14 | line. | |
15 | ||
16 | We have used libtiff to create and convert TIFF images of financial | |
17 | documents which are sent from and to major document processing systems | |
18 | in Sweden and Denmark. | |
19 | ||
20 | I would like to express my deep gratitude to yourself and Sillicon | |
21 | Graphics for making this excellent library available for public use. | |
22 | There is obviously a lot of work that has gone in to libtiff and the | |
23 | quality of the code and documentation is an example to others. | |
24 | ||
25 | One thing that libtiff did not do was work on a memory area rather than | |
26 | files. In my applications I had already read a TIFF or other format | |
27 | file in to memory and did not want to waste I/O writing it out again | |
28 | for libtiff's benefit. I therefore constructed a set of functions to | |
29 | pass up to TIFFClientOpen to simulate a file in memory. I have attached | |
30 | my mfs (memory file system) source code for you to use or junk, as you | |
31 | see fit. :-) | |
32 | ||
33 | Once again, thanks very much for making my life simpler. | |
34 | ||
35 | Best Regards, | |
36 | ||
37 | Mike Johnson. |