Received: by whizzer.wpd.sgi.com (/911001.SGI)
	 id AA07535; Fri, 11 Feb 94 15:31:30 GMT
Received: from sgi.sgi.com by whizzer.wpd.sgi.com via SMTP (/911001.SGI)
	for /usr/people/sam/majordomo/wrapper resend -l tiff -h sgi.sgi.com -f tiff-owner -s -m "-oi -odq -om" tiff-list id AA07527; Fri, 11 Feb 94 07:31:27 -0800
Received: from ucbvax.Berkeley.EDU by sgi.sgi.com via SMTP (931110.SGI/910110.SGI)
	for tiff-relay@whizzer.wpd.sgi.com id AA18862; Fri, 11 Feb 94 07:31:25 -0800
Received: from daimi.aau.dk by ucbvax.Berkeley.EDU (5.63/1.43)
	id AA29630; Fri, 11 Feb 94 07:31:21 -0800
Received: by daimi.aau.dk id AA29449
  (5.65c8/IDA-1.4.4 for tiff@ucbvax.berkeley.edu); Fri, 11 Feb 1994 16:31:15 +0100
From: S|ren Pingel Dalsgaard <pingel@daimi.aau.dk>
Message-Id: <199402111531.AA29449@daimi.aau.dk>
Subject: LIBTIFFW followup.
To: tiff@ucbvax.Berkeley.EDU (Tiff mailing list)
Date: Fri, 11 Feb 94 16:31:13 GMT
X-Mailer: ELM [version 2.3 PL11]
Sender: tiff-owner@sgi.sgi.com

I have received an amazing amount of mail requesting the library.

1) Where should I put the sources. I could try to ftp-upload it to
wuarchive.wustl.edu, but it is busy most of the time. I am checking if it is
possible to make it available from our server here in Denmark.

2a) How is it compiled? The library will compile if you use Microsoft Visual
C/C++. Whether or not Borland C/C++ version 3.1 or 4.0 will do I don't know. We
have just bought Borland C/C++ 4.0, and I think that I will be able to confirm
that it works within long. There is next to no Windows specific code in the
revised library.

2b) It is currently compiled as a LIBTIFFW.LIB file suitable for linking into a
windows DLL. The reason for this is that we needed a TIFF.DLL that supports
selection of compression method and related flags. In order to compile LIBTIFFW
as a separate DLL requeres changing the compile parameters and creation of a
.DEF file. If someone comes up with this, I'll be glad to know about it for
inclusion in the next revision.

3) It has been pointed out that libtiff is a LIBRARY and therefore the error
and warning functions should not need chaging. My opinion is that the error and
warning routines should provide a sensible default action in the present
environment. fprintf(stderr, ...) is NOT a sensible default action inside
windows and have thus been changed.

4) I have mainly focused on TIFF writing during our tests.

1 revisited) I have made arrangements with our system administrator that the
library can be obtained from our site using anonymous ftp. It is available at
daimi.aau.dk:pub/pc/v33b_win.arj.

You should get sgi.com:graphics/tiff/v3.3beta002.src.tar.Z. This file contains
complete documentation.

Yes it is my hope that (some of) these changes will eventually be included in
the original libtiff library.

***IMPORTANT***

The way I have implemented byte ordering is: The first letter of the mode
string supplied to TIFFOpen is 'r' for read, 'w' for write or 'a' for append.
If opening for writing, the second letter is 'l' to force little endian or 'b'
to force big-endian.  This was done because the tiff header is written during
open which is the first operation applied to a tiff file.

I have probably forgotten to mention something very important, so another
follow-up will most likely be posted soon.

New versions will be put under the same filename. This is because our
administrator doesn't want our site to be filled with software packages that
our university doesn't support. This port of libtiff has nothing to do with the
university. My former boss paid me to do the changes and to get a copy of what
I eventually would come up with.

/Soren
---
Soren Pingel Dalsgaard
pingel@daimi.aau.dk
Department of Computer Science
Aarhus University
Ny Munkegade 116
DK-8000  Aarhus C
DENMARK


