AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2008.10.06 20:45 "Re: [SPAM] Re: [Tiff] Compression code 34719 (MDI Tiffs)", by Brad Hards
2008.10.06 16:09 "Re: [SPAM] Re: [Tiff] Compression code 34719 (MDI Tiffs)", by Edward Lam
2008.10.06 16:31 "Re: [SPAM] Re: [Tiff] Compression code 34719 (MDI Tiffs)", by Bob Friesenhahn
2008.10.07 04:59 "RE: [SPAM] Re: [Tiff] Compression code 34719 (MDI Tiffs)", by ComSquare Martin Osieka
2008.10.08 03:20 "Re: [Tiff] Compression code 34719 (MDI Tiffs)", by Edward Lam
2008.10.08 13:29 "Re: [Tiff] Compression code 34719 (MDI Tiffs)", by Edward Lam
2008.10.08 21:47 "RE: [Tiff] Compression code 34719 (MDI Tiffs)", by ComSquare Martin Osieka

2008.10.07 04:59 "RE: [SPAM] Re: [Tiff] Compression code 34719 (MDI Tiffs)", by ComSquare Martin Osieka

I don't think it should be added to the libtiff library sources. The mechanism to register a codec should be used.

The result maybe an utility converting .mdi to a normal .tif.

Martin

-----Original Message-----

From: tiff-bounces@lists.maptools.org [mailto:tiff-bounces@lists.maptools.org] On Behalf Of Bob Friesenhahn

> LGPL license. Patches / bug reports appreciated.

> Before this gets too far, does the libtiff project accept LGPL code? AFAICT,

libtiff seems to use a BSD-style license.

While it is likely ok for a contributed libtiff utility, it would not be suitable for inclusion in libtiff itself.