| AWARE [SYSTEMS] | Imaging expertise for the Delphi developer | |||||||
![]() |
TIFF and LibTiff Mailing List Archive | |||||||
LibTiff Mailing List
TIFF and LibTiff Mailing List Archive Contact
The TIFF Mailing List Homepage |
Thread2008.02.06 11:05 "Re: Why is TIFF/zip not a default option?", by Anders Sewerin JohansenHi, Well, the reason for my question is that as far as I have so far been able to determine the deflate option was not enabled by default, which I took to mean that the majority of the libtiff equiped systems in use weould as default not be able to handle tiff/deflate. If it turns out I was mistaken, well that's just great! The reason for the question is that several parameters are relevant for picking a format for our purposes. Some are obvious to outsiders (size of final file, CPU requirements for rendering...), while others may not be (openness of format, availability of several open source renderes, patent issues). In particular the tiff/lzw format, while suitable on most counts (stable, well-known...) is discounted due to the patent issues past, present and future of the lzw compression algorithm/implementation. The tiff/zip format would not be discounted on the patent issue as far as I know, but might be discounted with regards to cross-platform usability, if the default Linux/UNIX system configuration did not allow for reading and writing it. Can I conclude that most recent libtiff equiped systems (e.g. systems deployed or updated during the last five years) will support tiff/zip? A Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from Exchange-1.kb.dk ([130.226.220.151]) by Exchange-2.kb.dk with Microsoft SMTPSVC(6.0.3790.3959); Wed, 6 Feb 2008 11:58:22 +0100 MIME-Version: 1.0 Received: from hans.kb.dk ([130.226.229.20]) by Exchange-1.kb.dk with Microsoft SMTPSVC(6.0.3790.3959); Wed, 6 Feb 2008 11:58:22 +0100 Received: by hans.kb.dk (Postfix) id CC4EE1A04B6; Wed, 6 Feb 2008 11:58:21 +0100 (CET) Received: from hans.kb.dk (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A03821A02C4 for <asjo@kb.dk>; Wed, 6 Feb 2008 11:58:21 +0100 (CET) Received: from duke.maptools.org (unknown [209.217.116.153]) by hans.kb.dk (Postfix) with ESMTP id 892D61A04BD for <asjo@kb.dk>; Wed, 6 Feb 2008 11:58:20 +0100 (CET) Received: from duke.maptools.org (duke.maptools.org [127.0.0.1]) by duke.maptools.org (8.12.11/8.12.10) with ESMTP id m16Aodck022775; Wed, 6 Feb 2008 05:51:03 -0500 Received: from cgp2.pu.ru (cgp2.pu.ru [195.70.197.22]) by duke.maptools.org (8.12.11/8.12.10) with ESMTP id m16AoUto022772 for <tiff@lists.maptools.org>; Wed, 6 Feb 2008 05:50:30 -0500 Received: from [195.70.196.218] (HELO wg.pu.ru) by cgp2.pu.ru (CommuniGate Pro SMTP 5.2.0) with ESMTP id 993836 for tiff@lists.maptools.org; Wed, 06 Feb 2008 13:50:27 +0300 Received: (from uucp@localhost) by wg.pu.ru (8.9.1a/8.9.1) with UUCP id KAA25490 for tiff@lists.maptools.org; Wed, 6 Feb 2008 10:50:27 GMT Received: from ak4719.spb.edu (localhost.localdomain [127.0.0.1]) by ak4719.spb.edu (8.13.8/8.13.8/Debian-3) with ESMTP id m16AYA9Q013309 for <tiff@lists.maptools.org>; Wed, 6 Feb 2008 13:34:10 +0300 Received: (from dron@localhost) by ak4719.spb.edu (8.13.8/8.13.8/Submit) id m16AYAuh013308 for tiff@lists.maptools.org; Wed, 6 Feb 2008 13:34:10 +0300 Content-class: urn:content-classes:message Subject: Re: [Tiff] Why is TIFF/zip not a default option? Date: Wed, 6 Feb 2008 11:34:10 +0100 Message-ID: <20080206103410.GB13261@ak4719.spb.edu> In-Reply-To: <476DC57E7DF07E4B9C7426231A216EA472855F@exchange-2.kb.dk> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Tiff] Why is TIFF/zip not a default option? Thread-Index: AchorzCP7Bo3B0sWTFybR/IkaHE6hA== References: <476DC57E7DF07E4B9C7426231A216EA472855F@exchange-2.kb.dk> List-Help: <mailto:tiff-request@lists.maptools.org?subject=help> List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>, <mailto:tiff-request@lists.maptools.org?subject=subscribe> List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>, <mailto:tiff-request@lists.maptools.org?subject=unsubscribe> From: "Andrey Kiselev" <dron@ak4719.spb.edu> Sender: <tiff-bounces@lists.maptools.org> To: <tiff@lists.maptools.org> Content-Type: text/plain; charset="iso-8859-1" Anders, On Wed, Feb 06, 2008 at 11:01:59AM +0100, Anders Sewerin Johansen wrote: > Can anybody at the mailing list elaborate on why zip/deflate > compression of image data is not enabled as a default in libtiff? Is > it e.g. because it's still considered experimental, or is there some > other reason (technical, legal, "inertia",...)? Deflate is enabled by default if development package of zlib is installed (deflate depends on that 3rd party software separate from libtiff). That's how it is configured on POSIX system where we have automatically configuring shell script. If you are using MSVC compiler environment then you should enable zlib support manually and point where it is installed on your system, because we can't automatically configure with MSVC. So I really can't understand your question, libtiff is being distributed with deflate option enabled by many vendors and there no reason to disable it. Best regards, Andrey --=20 Andrey V. Kiselev ICQ# 26871517 |
|||||||