Return-Path: <tiff-bounces@lists.maptools.org>
Received: from mailgate006.isp.belgacom.be (mailgate006.isp.belgacom.be [195.238.5.212])
        by maildelivery011.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id l6G9IoR2012546
        for <joris.at.lebbeke@skynet.be>; Mon, 16 Jul 2007 11:18:50 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from r153.dmsolutions.ca (HELO duke.maptools.org) ([209.217.116.153])
  by in.mx.skynet.be with ESMTP; 16 Jul 2007 11:18:48 +0200
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 l6G8xQZg016088;
	Mon, 16 Jul 2007 05:00:29 -0400
Received: from dns2.namehog.net (dns2.namehog.net [213.52.234.203])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id l6G8xIKS016081
	for <tiff@lists.maptools.org>; Mon, 16 Jul 2007 04:59:19 -0400
Received: from 81-86-57-99.dsl.pipex.com ([81.86.57.99] helo=EKAT)
	by dns2.namehog.net with esmtpa (Exim 4.66)
	(envelope-from <andy.cave@hamillroad.com>)
	id 1IAMQN-000528-PP; Mon, 16 Jul 2007 09:59:24 +0100
Message-ID: <03bf01c7c787$94a06340$da60fea9@EKAT>
From: "Andy Cave" <andy.cave@hamillroad.com>
To: "Lee Howard" <faxguy@howardsilvan.com>
References: <20070714080029.GA20272@ak4719.spb.edu>
	<016901c7c61f$56778df0$da60fea9@EKAT>
	<46990A3E.1020004@howardsilvan.com>
Subject: Re: [Tiff] [ANNOUNCE]: Libtiff 3.9.0beta released
Date: Mon, 16 Jul 2007 09:59:10 +0100
Organization: Hamillroad Software
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-PopBeforeSMTPSenders: acave@hamillroad.com, news@hamillroad.com,
	sales@hamillroad.com, support@hamillroad.com
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - dns2.namehog.net
X-AntiAbuse: Original Domain - lists.maptools.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - hamillroad.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: tiff@lists.maptools.org
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
Reply-To: Andy Cave <andy.cave@hamillroad.com>
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
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>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.0000262a
X-MSP-STORE: Mon, 16 Jul 2007 11:18:53 +0200
Status:   

I hope that this is not the case. If so, I think that's bad, as it's the 
only code in LibTIFF which is not completely unencumbered from patents, 
license fees and GPL. When we had LZW in LibTIFF and it was patented, there 
used to be a 'dummy' file that was compiled in by default and to get real 
LZW you had to explicitly compile it in. I think this should be the case 
with JBIG-KIT given that:
 a) it is covered by patents - even though these can be obtained for free.
 b) you have to license it (from Cambridge University).
 c) it is restricted by GPL.
Otherwise, if someone just happens to have JBIG-KIT on their PC and builds 
LibTIFF they could end up infringing on patents, infringing on copyright 
licensing and violating GPL. I think that if this happens, it could open up 
a whole can of worms - for example rather than have to then publish their 
(commercial) code, a company might end up suing the people who opened up 
this can of worms.

PS I never said you had to *remove* code - just that you had to remove it 
(from what I have read - I've not checked (yet)) - either by removing 
JBUG-KIT (if installed) or using ""--disable-jbig".

Andy.

----- Original Message ----- 
From: "Lee Howard" <faxguy@howardsilvan.com>
To: "Andy Cave" <andy.cave@hamillroad.com>
Cc: "Andrey Kiselev" <dron@ak4719.spb.edu>; <tiff@lists.maptools.org>
Sent: Saturday, July 14, 2007 6:39 PM
Subject: Re: [Tiff] [ANNOUNCE]: Libtiff 3.9.0beta released

> ...
> JBIG support is compiled-in only if the JBIG-KIT library is found during 
> configure *and* if "--disable-jbig" is not used.  If you're building 
> libtiff and you don't want JBIG support compiled-in then you can either 
> ensure that you don't have JBIG-KIT installed (some Linux distros do have 
> it) or simply ensure that you always use "--disable-jbig".  There is no 
> need to *remove* code from libtiff.
> ...


_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
