Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas004.isp.belgacom.be (localhost [127.0.0.1])
        by inav030.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AV-3.00) with ESMTP id k3KKZTUf011589
        for <joris.at.lebbeke@skynet.be>; Thu, 20 Apr 2006 22:35:31 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx011.isp.belgacom.be (inmx011.isp.belgacom.be [195.238.5.50])
        by inas004.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AS-2.03) with ESMTP id k3KKYwju014704
        for <joris.at.lebbeke@skynet.be>; Thu, 20 Apr 2006 22:35:22 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx011.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id k3KKYjm0016176
        for <joris.at.lebbeke@skynet.be>; Thu, 20 Apr 2006 22:34:46 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
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 k3KKRqO1030170;
	Thu, 20 Apr 2006 16:28:50 -0400
Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.182])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id k3KKRlWt030167
	for <tiff@lists.maptools.org>; Thu, 20 Apr 2006 16:27:48 -0400
Received: by pproxy.gmail.com with SMTP id z74so296966pyg
	for <tiff@lists.maptools.org>; Thu, 20 Apr 2006 13:27:46 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=OO8u+YH3uIi7TMO+At3INRIIOhWdtHymd1G1apnP6N1uQ0FHADeLd5CDba4iPlT32eW0wcLgqdaV08tDrCsytDQ9lwDUGnWQVKYYkGKHxD2wN4lgmHqGgLVCH4B50bw5z0QMLPNW5haCf0+FzBLrmp1bSpCcc2S1f+FFDPh6Y9w=
Received: by 10.35.39.2 with SMTP id r2mr372711pyj;
	Thu, 20 Apr 2006 13:27:46 -0700 (PDT)
Received: by 10.35.37.10 with HTTP; Thu, 20 Apr 2006 13:27:46 -0700 (PDT)
Message-ID: <92d3a4950604201327h7bf4f334nccd2934ff02791a4@mail.gmail.com>
Date: Thu, 20 Apr 2006 22:27:46 +0200
From: Antoine <melser.anton@gmail.com>
To: "Gerben Vos" <Gerben@zylab.com>
Subject: Re: [Tiff] TIFF + Group4 will last 10 years?
In-Reply-To: <FC840EC0BF7BFA45A0F94548AF36920DABF21D@zynlms01.ZyLAB.WAN>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <FC840EC0BF7BFA45A0F94548AF36920DABF21D@zynlms01.ZyLAB.WAN>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by duke.maptools.org id
	k3KKRlWt030167
Cc: tiff@lists.maptools.org
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
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.000015f9
X-MSP-STORE: Thu, 20 Apr 2006 22:35:39 +0200
Status:   

On 19/04/06, Gerben Vos <Gerben@zylab.com> wrote:
> Rui Castro wrote:
>
> > My question is, should i keep the compression or not? I'm not
> > sure if in 2013 software that can deal with that compression
> > scheme (Group4) is going to be supported or not; and if i keep
> > the compression, should i use Group4 or another?
>
> Lots of documents are currently being archived every day around the
> world using TIFF and Group 4, both in private business and government.
> The Group 4 standard dates from 1984, and shows no sign of decline
> in its use. The only real competitor at the moment, I think, is
> JBIG, which hasn't really caught on yet. I'd use either Group 4
> or uncompressed; the latter of course has the advantage that you
> have a better chance of recovery if the storage medium becomes
> partially damaged, but you should decide yourself whether that's
> worth the extra storage costs.
>
> I'm sure both TIFF and PDF will still be around too. I'd choose
> TIFF myself, since it's an easier format to decode.

I can second that - we do a lot of work for European aerospace
companies and it is pretty much all (certainly all the b&w stuff) in
either pdf + G4 or tiff + G4. At the end of the day, you can always
store the entire G4 decompression scheme in a tag (OK, I know I am not
worthy but wth!) and it will cost you a couple (OK maybe a few K) of
hundred bytes per image. And that is if you are REALLY paranoid!
Cheers
Antoine

--
This is where I should put some witty comment.

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