Return-Path: <awaresystems.be+caf_=filtered=awaresystems.be@gmail.com>
Delivered-To: filtered@awaresystems.be
Received: from mx7.public.one.com ([10.246.18.27])
	by mail6.local.one.com (Dovecot) with LMTP id Z6S9Hcx5CFlYLQAAsyOMew
	for <filtered@awaresystems.be>; Tue, 02 May 2017 12:58:17 +0000
X-HalOne-ID: 0231887d-2f37-11e7-a464-549f350a6292
Received: from mail-it0-f47.google.com (unknown [209.85.214.47])
	by mx7.public.one.com (Halon) with ESMTPS
	id 0231887d-2f37-11e7-a464-549f350a6292;
	Tue, 02 May 2017 12:58:17 +0000 (UTC)
Received: by mail-it0-f47.google.com with SMTP id e65so10302367ita.1
        for <filtered@awaresystems.be>; Tue, 02 May 2017 05:58:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-original-authentication-results:x-gm-message-state:delivered-to
         :from:to:references:in-reply-to:date:message-id:mime-version
         :thread-index:content-language:subject:precedence:list-id
         :list-unsubscribe:list-archive:list-post:list-help:list-subscribe
         :mime-version:sender:errors-to;
        bh=/lkBq4SuzO5MGcHwJCnKZHokqC82yxKCC7dIc+QfRnM=;
        b=Z2PhwAfWb4/09Cik03gS2BAb+ldr/gxGD/8lb2Jd6rPJ8iXzN3PesecSoYYfZIGKEV
         j8XPrrS50oc1vRGjCSi611+UsVsSro9wmriXU0EZsbLLlQ3Y95yB9dbvL1t6ZVJF2Scc
         k8CZC0rpo9MDoI84NWbqNo8VgM0pXHuZnMAttoVmupVLR2EMsUBiSA8MQ3wa8KvCwCSa
         PADulheo5PAoDVzNKtGRswXE3yP7nOTtq40GWzKp3Xmd6LOQQ7xvsaVlZRwKtfMcC5vE
         3RCXzExQ6DRUGsJ3PGpuJl7cWwRwJZLbPx+HCxsNLyAx6SRJFJCfirgl5RdayBPjQA8P
         E/7w==
X-Original-Authentication-Results: mx.google.com;       spf=neutral (google.com: 94.23.4.142 is neither permitted nor denied by best guess record for domain of tiff-bounces@lists.maptools.org) smtp.mailfrom=tiff-bounces@lists.maptools.org
X-Gm-Message-State: AN3rC/41hMZK0B2iPuaxZZyKelREnsX6jaKIUBLdy+hsE4EZPoWxura5
	DQOW5AcMOZoZgNewBoPI8TidHATxZkHsCEWmCwuEpw==
X-Received: by 10.202.244.149 with SMTP id s143mr10952890oih.116.1493729895983;
        Tue, 02 May 2017 05:58:15 -0700 (PDT)
X-Forwarded-To: filtered@awaresystems.be
X-Forwarded-For: awaresystems.be@gmail.com filtered@awaresystems.be
Delivered-To: awaresystems.be@gmail.com
Received: by 10.202.242.65 with SMTP id q62csp1891537oih;
        Tue, 2 May 2017 05:58:14 -0700 (PDT)
X-Received: by 10.223.151.13 with SMTP id r13mr19313660wrb.6.1493729894728;
        Tue, 02 May 2017 05:58:14 -0700 (PDT)
Return-Path: <tiff-bounces@lists.maptools.org>
Received: from lists.maptools.org (ks365428.kimsufi.com. [94.23.4.142])
        by mx.google.com with ESMTP id 68si20960090wra.23.2017.05.02.05.58.14;
        Tue, 02 May 2017 05:58:14 -0700 (PDT)
Received-SPF: neutral (google.com: 94.23.4.142 is neither permitted nor denied by best guess record for domain of tiff-bounces@lists.maptools.org) client-ip=94.23.4.142;
Authentication-Results: mx.google.com;
       spf=neutral (google.com: 94.23.4.142 is neither permitted nor denied by best guess record for domain of tiff-bounces@lists.maptools.org) smtp.mailfrom=tiff-bounces@lists.maptools.org
Received: from [10.1.0.241] (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id 5438535C041;
	Tue,  2 May 2017 07:57:00 -0500 (EST)
Received: from Mail.MaSSoftware.Com (massoftware.com [74.200.71.197])
	by lists.maptools.org (Postfix) with ESMTPS id 837C135C031
	for <tiff@lists.maptools.org>; Tue,  2 May 2017 07:56:47 -0500 (EST)
Received: from localmail2.massoftware.com
	(CPE005056000101-CM84948c576700.cpe.net.cable.rogers.com
	[99.236.101.199])
	by Mail.MaSSoftware.Com (8.13.1/8.13.1) with ESMTP id v42CujCv028485
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <tiff@lists.maptools.org>; Tue, 2 May 2017 08:56:45 -0400
Received: from MASDEVMAIL ([192.168.127.151]) (authenticated bits=0)
	by localmail2.massoftware.com (8.14.7/8.14.7) with ESMTP id
	v42CuWJ0012105
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <tiff@lists.maptools.org>; Tue, 2 May 2017 08:56:32 -0400
From: "Michael Shiels [ MaS Software Inc ]" <MaSSoft@massoftware.com>
To: <tiff@lists.maptools.org>
References: <fcd301d2c05f$5fd8b730$1f8a2590$@MaSSoftware.Com>
In-Reply-To: <fcd301d2c05f$5fd8b730$1f8a2590$@MaSSoftware.Com>
Date: Tue, 2 May 2017 08:56:42 -0400
Message-ID: <220d01d2c343$8c1c5d60$a4551820$@MaSSoftware.Com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQL1qpqttmVVtvVx4CD8uYxyipWX7J+bMXsg
Content-Language: en-us
Subject: Re: [Tiff] Interesting change/problem in LibTiff 4.0.7 with
	unsupported	compressions
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
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>
Content-Type: multipart/mixed; boundary="===============1588884970=="
Mime-version: 1.0
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

This is a multipart message in MIME format.

--===============1588884970==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_220E_01D2C322.050DCAA0"
Content-Language: en-us

This is a multipart message in MIME format.

------=_NextPart_000_220E_01D2C322.050DCAA0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Just wondering if anyone has thoughts on this problem.  Once I posted it
doesn't' seem to have made it into the archive which means maybe it didn't
get through at all??

 

This is a interesting situation since most people don't expect an error just
from enumerating the directory and reading the tags.  Maybe a warning would
be more appropriate specifically for an inability to detail out the
compression specific tags maybe??

 

Thanks.

Mike

 

From: tiff-bounces@lists.maptools.org
[mailto:tiff-bounces@lists.maptools.org] On Behalf Of Michael | Shiels [ MaS
\ Software \ Inc ]
Sent: Friday, April 28, 2017 4:38 PM
To: tiff@lists.maptools.org
Subject: [Tiff] Interesting change/problem in LibTiff 4.0.7 with unsupported
compressions

 

I found a decent change in the behavior of Libtiff - after I updated from
the 3.5.6/3.5.7 era to the most recent (yes 15 year jump!!)

 

Specifically this piece of code - basically ends up tripping an error if the
compression is not compiled/activated in the code.  So you can't even
peruse/move through a file without tripping an error.

 

               /*

               * An opportunity for compression mode dependent tag fixup

               */

               (*tif->tif_fixuptags)(tif);

 

 

Our engine specifically watches for errors and assumes it's pretty fatal -
when really it's kinda benign - UNLESS I want to extract the image data
itself, right??

 

Surely that should be pretty benign to just enumerate through a TIFF - even
if you don't support the compression of each page??

 

Mike


------=_NextPart_000_220E_01D2C322.050DCAA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Just wondering if anyone has thoughts on this =
problem.&nbsp; Once I posted it doesn&#8217;t&#8217; seem to have made =
it into the archive which means maybe it didn&#8217;t get through at =
all??<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>This is a interesting =
situation since most people don&#8217;t expect an error just from =
enumerating the directory and reading the tags.&nbsp; Maybe a warning =
would be more appropriate specifically for an inability to detail out =
the compression specific tags maybe??<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Mike<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
tiff-bounces@lists.maptools.org [mailto:tiff-bounces@lists.maptools.org] =
<b>On Behalf Of </b>Michael | Shiels [ MaS \ Software \ Inc =
]<br><b>Sent:</b> Friday, April 28, 2017 4:38 PM<br><b>To:</b> =
tiff@lists.maptools.org<br><b>Subject:</b> [Tiff] Interesting =
change/problem in LibTiff 4.0.7 with unsupported =
compressions<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I found a =
decent change in the behavior of Libtiff &#8211; after I updated from =
the 3.5.6/3.5.7 era to the most recent (yes 15 year =
jump!!)<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Specifically this piece of code &#8211; basically ends =
up tripping an error if the compression is not compiled/activated in the =
code.&nbsp; So you can&#8217;t even peruse/move through a file without =
tripping an error.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /*<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * An opportunity for compression mode =
dependent tag fixup<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; */<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(*tif-&gt;tif_fixuptags)(tif);<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Our engine =
specifically watches for errors and assumes it&#8217;s pretty fatal =
&#8211; when really it&#8217;s kinda benign &#8211; UNLESS I want to =
extract the image data itself, right??<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Surely that =
should be pretty benign to just enumerate through a TIFF &#8211; even if =
you don&#8217;t support the compression of each page??<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Mike<o:p></o:p></p></div></body></html>
------=_NextPart_000_220E_01D2C322.050DCAA0--


--===============1588884970==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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