Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx011.isp.belgacom.be (inmx011.isp.belgacom.be [195.238.3.50])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id iBCNgIFm006172
        for <joris.at.lebbeke@skynet.be>; Mon, 13 Dec 2004 00:42:18 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx011.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id iBCNg2Qs011738
        for <joris.at.lebbeke@skynet.be>; Mon, 13 Dec 2004 00:42:04 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id 53BE2501D26; Sun, 12 Dec 2004 18:41:45 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from scooby.simplesystems.org (scooby.simplesystems.org
	[65.66.246.67])
	by xserve.flids.com (Postfix) with ESMTP id 4EDCB501D03
	for <tiff@remotesensing.org>; Sun, 12 Dec 2004 18:41:42 -0500 (EST)
Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74])
	by scooby.simplesystems.org (8.12.10+Sun/8.12.10) with ESMTP id
	iBCNffVL015705; Sun, 12 Dec 2004 17:41:41 -0600 (CST)
Date: Sun, 12 Dec 2004 17:41:41 -0600 (CST)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@blade.simplesystems.org
To: =?iso-8859-1?Q?Bruno_Ten=F3rio_=C1vila?= <brunoavila@terra.com.br>
Subject: Re: RES: RES: [Tiff] JPEG2000 and Metadata
In-Reply-To: <20041212232138.57FB23C02A@buvuma.terra.com.br>
Message-ID: <Pine.SOC.4.60.0412121730140.4000@blade.simplesystems.org>
References: <20041212232138.57FB23C02A@buvuma.terra.com.br>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED;
	BOUNDARY="-559023410-1766335976-1102894901=:4000"
Cc: tiff@remotesensing.org
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: 6484a07dcbbcf5c790c22681c00a3da9

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---559023410-1766335976-1102894901=:4000
Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Sun, 12 Dec 2004, Bruno Ten=F3rio =C1vila wrote:

> Anh, ok! Because libtiff is easy to use and it would be easier to use onl=
y
> one API to several image formats, rather then one for libtiff and another
> for jasper lib.

JPEG2000 has a similar number of options as TIFF itself.  Jasper=20
provides a simplified view/set of JPEG2000 capabities yet there are=20
still many options which would not be exposed by the existing set of=20
libtiff options.  For example, Jasper provides a compression ratio=20
option which I don't believe there is a direct correlation to in TIFF.

Since JPEG2000 is itself so complex, I think that while embedding a=20
JPEG2000 file within a TIFF file may make it easier to manage with=20
existing software from a metadata standpoint, you would still need to=20
deal with the JPEG2000 content separately.  It would be a crime to do=20
otherwise.

Bob

> -----Mensagem original-----
> De: Bob Friesenhahn [mailto:bfriesen@simple.dallas.tx.us]
> Enviada em: domingo, 12 de dezembro de 2004 21:17
> Para: Bruno Ten=F3rio =C1vila
> Cc: tiff@remotesensing.org
> Assunto: Re: RES: [Tiff] JPEG2000 and Metadata
>
> On Sun, 12 Dec 2004, Bruno Ten=F3rio =C1vila wrote:
>
>> Because it compress better and support lossless compression for color
>> images.
>
> I am aware of that.  My question is why you would like to embed
> JPEG-2000 in a TIFF wrapper rather than simply using the JPEG-2000
> format directly?
>
> Bob
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Bob Friesenhahn
> bfriesen@simple.dallas.tx.us
> http://www.simplesystems.org/users/bfriesen
>
>
>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen
---559023410-1766335976-1102894901=:4000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff

---559023410-1766335976-1102894901=:4000--
