AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

1999.11.30 22:23 "libtiff 3.5.3 release.", by Michael L. Welles
1999.11.30 22:53 "Re: libtiff 3.5.3 release.", by Izumi Ohzawa
1999.11.30 23:07 "Re: libtiff 3.5.3 release.", by Tom Lane
1999.12.01 00:08 "Re: libtiff 3.5.3 release.", by Michael L. Welles
1999.11.30 23:22 "Re: libtiff 3.5.3 release.", by Daniel McCoy
1999.12.01 13:56 "Re: libtiff 3.5.3 release.", by Bruce Cameron
1999.12.01 18:35 "Re: libtiff 3.5.3 release.", by Daniel McCoy
1999.12.02 07:06 "", by Ruediger
1999.12.01 03:15 "Re: libtiff 3.5.3 release.", by Bob Friesenhahn
1999.12.01 16:04 "Re: libtiff 3.5.3 release.", by Michael L. Welles
1999.12.01 16:43 "Re: libtiff 3.5.3 release.", by Tom Lane
1999.11.30 23:07 "Re: libtiff 3.5.3 release.", by Martin Bailey
1999.12.01 14:08 "Re: libtiff 3.5.3 release.", by Bruce Cameron
1999.12.01 15:02 "Re: libtiff 3.5.3 release.", by Klaus Bartz
1999.12.01 16:17 "RE: libtiff 3.5.3 release.", by Peter Smith
1999.12.01 16:49 "RE: libtiff 3.5.3 release.", by Darrin Cardani
1999.12.01 19:20 "Re: libtiff 3.5.3 release.", by Chris Hanson
1999.12.01 14:33 "Re: libtiff 3.5.3 release.", by Andy
1999.12.01 14:42 "ZIP compression [was: libtiff 3.5.3 release.]", by Tom Kacvinsky
1999.12.01 15:24 "Re: ZIP compression [was: libtiff 3.5.3 release.]", by Leonard Rosenthol
1999.12.01 15:51 "Re: ZIP compression [was: libtiff 3.5.3 release.]", by Tom Kacvinsky
1999.12.01 18:04 "Re: ZIP compression [was: libtiff 3.5.3 release.]", by Bryan H. Maret
1999.12.02 05:16 "Re: ZIP compression [was: libtiff 3.5.3 release.]", by Leonard Rosenthol
1999.12.01 17:39 "Re: ZIP compression [was: libtiff 3.5.3 release.]", by Bryan H. Maret
1999.12.02 11:42 "Re: ZIP compression [was: libtiff 3.5.3 release.]", by Ivo Penzar
1999.12.06 20:42 "Re: ZIP compression [was: libtiff 3.5.3 release.]", by Andy

1999.12.02 07:06 "", by Ruediger

Covers non-commercial use?? What about if you write your own LZW compression [the algorithm is published and well known]. I have done that in more than one executable.

The way I understand it, Unisys is fine with that as long as you don't distribute it in any way. You can write it, but you can't give it away.

I heared from a case, where the distribution of a ready build product wasn't allowed, so they distributed the parts of the product, to be fetched together by the customer. That works in this case.

I am not a expert/lawer, and I don't know if this would work in this case. Also I usually don't discuss a theme I don't know all the facts, but isn't it a idea to distribute a Toolkit to build a LZW compression algorithm?

e.g. what if we have two components which would be on their own no working LZW compression algorithm, but build together, which must be done by everybody on his own, they would work. So you would not publish the algorithm in that way.