Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx009.isp.belgacom.be (inmx009.isp.belgacom.be [195.238.3.146])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id j1SDjS5w024595
        for <joris.at.lebbeke@skynet.be>; Mon, 28 Feb 2005 14:45:28 +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 inmx009.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j1SDjBa5004446
        for <joris.at.lebbeke@skynet.be>; Mon, 28 Feb 2005 14:45:14 +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 E9EF9EA8E8C; Mon, 28 Feb 2005 08:44:50 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from outmx008.isp.belgacom.be (outmx008.isp.belgacom.be
	[195.238.3.235])
	by xserve.flids.com (Postfix) with ESMTP id 7833BEA8E55
	for <tiff@remotesensing.org>; Mon, 28 Feb 2005 08:44:48 -0500 (EST)
Received: from outmx008.isp.belgacom.be (localhost [127.0.0.1])
	by outmx008.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
	ESMTP id j1SDibs7002310
	for <tiff@remotesensing.org>; Mon, 28 Feb 2005 14:44:38 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (160-182.245.81.adsl.skynet.be [81.245.182.160])
	by outmx008.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with SMTP
	id j1SDiYgD002284; Mon, 28 Feb 2005 14:44:34 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <002401c51d9b$b44ae230$a0b6f551@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: =?iso-8859-1?B?Sm9z6SBNYXLtYSBO+vFleiBPcnR18W8=?= <jnunez@indomotika.com>,
        "'Tiff mailing list'" <tiff@remotesensing.org>
References: <20050228131606.B146AEA8AE1@xserve.flids.com>
Subject: Re: [Tiff] Delphi TIFF visualization
Date: Mon, 28 Feb 2005 14:44:59 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
Cc: 
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: cce6033054e1fb44a14af9c1cffb09bb

José,

> Sorry, your other mail was marked by my mail server as Spam. I have
> copy-pasted what you send and tested it. It works fine with some "easy"
> files, but I obtain a blank image with my "preffered" one. Those are my
> tags:
> ...
> Compression (1 Short): JPEG Original TIFF 6.0 spec
> ...
> Do you detect something not compatible with TIFF specifications?

The problem here is the compression mode. You should contact the vendor of the
software that generated the TIFF. The TIFF community has long condemned and
abandonded this original 6.0 jpeg-in-tiff compression scheme, because the
original specification was ambiguous and plainly breaking TIFF. Tom Lane has
written a replacement many many years ago, Technote2,
http://www.remotesensing.org/libtiff/TIFFTechNote2.html, and Adobe have absorbed
that replacement in a specification supplement
http://partners.adobe.com/public/developer/en/tiff/TIFFphotoshop.pdf.
Nevertheless, vendors who prefer monopoly at the cost of portability of data
insist on writing their particular interpretation of original jpeg-in-tiff
compression because we obviously haven't complained enough yet.

LibTiff does try to support reading some vendor's particular interpretations of
original 6.0 jpeg-in-tiff. However, it cannot claim to be perfect and complete,
the original specification was ambiguous. It quite correctly does not support
writing original 6.0 jpeg-in-tiff. LibTiffDelphi 3.7.0.00 does at not support
reading this compression scheme. (The reason is technical, despite my additional
theoretical objections. Avoiding C runtimes and all such additional weight, I
cannot make use of longjumps or exceptions in C. This means that I cannot
directly make use if LibJpeg in LibTiffDelphi. Thus, I have to make a detour,
LibTiffDelphi calls wrappers of LibJpeg functions in pascal instead, where I can
make use of exception handling for trapping and handling LibJpeg errors. This is
a lot of additional hassle. I've put in the work for the good Technote2
jpeg-in-tiff compression scheme, but have not yet done so for abandoned old 6.0
jpeg-in-tiff.)

I am however considering investing the work it takes to include LibTiff's normal
old-style 6.0 jpeg-in-tiff reading support. If I do, I will do so when I upgrade
the package to LibTiff 3.7.1, probably some time soon. I will at that time also
remove the 'beta' status, and start adding proper documentation. If you want to
be kept informed when this happens, I recommend using the appropriate 'drop us a
line' mail-link on the LibTiffDelphi download page
http://www.awaresystems.be/imaging/tiff/delphi.html.

Sorry for the inconvinience.


Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be/
Download your free TIFF tag viewer for windows here:
http://www.awaresystems.be/imaging/tiff/astifftagviewer.html

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