Return-Path: <tiff-bounces@lists.maptools.org>
Delivered-To: info@awaresystems.be
Received: (qmail 1003 invoked from network); 30 Sep 2008 18:10:20 -0000
Received: from floyd.telenet-ops.be ([195.130.136.4])
          (envelope-sender <tiff-bounces@lists.maptools.org>)
          by angelia.telenet-ops.be (qmail-ldap-1.03) with SMTP
          for <info@awaresystems.be>; 30 Sep 2008 18:10:20 -0000
Received: from vijay.telenet-ops.be (vijay.telenet-ops.be [195.130.136.9])
	by floyd.telenet-ops.be (8.13.1/8.13.1) with ESMTP id m8UIAKvB031584
	for <info@awaresystems.be>; Tue, 30 Sep 2008 20:10:20 +0200
Received: from pierre.telenet-ops.be (pierre.telenet-ops.be [195.130.132.34])
	by vijay.telenet-ops.be (Postfix) with ESMTP id 6EEB660004
	for <info@awaresystems.be>; Tue, 30 Sep 2008 20:10:20 +0200 (CEST)
Received: from apate.telenet-ops.be ([195.130.132.43])
	by pierre.telenet-ops.be with bizsmtp
	id M6AK1a00B0wL6ob016AKWM; Tue, 30 Sep 2008 20:10:19 +0200
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153])
	by apate.telenet-ops.be (Postfix) with ESMTP id 7498927EC76
	for <info@awaresystems.be>; Tue, 30 Sep 2008 20:10:18 +0200 (CEST)
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 m8UI421Q013007;
	Tue, 30 Sep 2008 14:08:21 -0400
Received: from mail4.hostpark.net (mail4.hostpark.net [212.243.197.34])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id m8UI3v7l013000
	for <tiff@lists.maptools.org>; Tue, 30 Sep 2008 14:03:57 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail4.hostpark.net (Postfix) with ESMTP id 447393CB59
	for <tiff@lists.maptools.org>; Tue, 30 Sep 2008 20:03:52 +0200 (CEST)
X-Virus-Scanned: by Hostpark/NetZone Mailprotection at hostpark.net
Received: from mail4.hostpark.net ([127.0.0.1])
	by localhost (mail4.hostpark.net [127.0.0.1]) (amavisd-new, port 10124)
	with ESMTP id io3QuzdqVP9r for <tiff@lists.maptools.org>;
	Tue, 30 Sep 2008 20:03:51 +0200 (CEST)
Received: from csqp20 (165.94.202.62.cust.bluewin.ch [62.202.94.165])
	by mail4.hostpark.net (Postfix) with ESMTP id D93183C57F
	for <tiff@lists.maptools.org>; Tue, 30 Sep 2008 20:03:50 +0200 (CEST)
From: "ComSquare Martin Osieka" <martin.osieka@comsquare.ch>
To: <tiff@lists.maptools.org>
References: <006901c920be$a35547c0$1e1fa8c0@csqp20>
	<058BE4B9-7331-4BDE-B65A-6C7741A34674@telegraphics.com.au>
	<000301c92138$9fffdac0$2901a8c0@csqp20>
	<1222604257.3905.95.camel@PCB-Bench-01>
Subject: RE: [Tiff] Compression code 34719 (MDI Tiffs)
Date: Tue, 30 Sep 2008 20:03:49 +0200
Message-ID: <001e01c92326$e4370430$2901a8c0@csqp20>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AckhZDliPNeJY01ZS56SdDVian/+NwBwG5ng
In-Reply-To: <1222604257.3905.95.camel@PCB-Bench-01>
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>
Content-Type: multipart/mixed; boundary="===============1043445731=="
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-SpamCatcher-Score: 2 [X]

This is a multi-part message in MIME format.

--===============1043445731==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001F_01C92337.A7BFD430"

This is a multi-part message in MIME format.

------=_NextPart_000_001F_01C92337.A7BFD430
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Gene,

=20

Sorry for the Greek (we say B=F6hmische D=F6rfer ;-) I know what I =
talked about
may only be of interest for software emgineers. The issue is that our
customers are using these files (I guess this format is somehow popular
because you can easily add annotations. The problem was that our tool =
opened
the files but showed only black content. As I said before I had no idea =
that
libtiff allows the magic =93EP=94 for TIFFs.

=20

For sure first I=92m looking for a solution for our customers but if =
there is
a general solution for all platforms then it may be integrated in to
libtiff.

In the meantime I=92m able to decode these strips (not to difficult if =
you are
looking to a hex dump of the strip).
But the result is that the decoded data is no bitmap, it is an EMF =
(Enhanced
Meta File) data block.

So I=92m able to view these special TIFFs in our product on Windows but =
I can
not offer a general solution because for this you would need a platform
independent EMF to bitmap converter.=20


Martin

>>Since this all read as Greek to me, I decided to try to find out more =
info
on these terms through some google searching. =20
>>
>>>From my investigation, I think you are saying that these image files =
are
in a format used by an old version of MS office (2003), where MDI means
Microsoft >>>Document Image format and MSCD is the Microsoft Secure =
Content
Delivery program.  I think this is saying that Microsoft defined their =
own
codec for image >>>storage in MS Office 2003.  On one google result that =
I
found, it appears that MS has abandoned this image format in later =
versions
of MS Office.
>>
>>Is this what you were saying? =20
>>
>>Also, isn't OLE (Object Linking and Embedding) another MS-only =
standard
that doesn't help anyone using a non-MS platform?
>>
>>Thanks,
>>
>>   Gene Amtower=20


------=_NextPart_000_001F_01C92337.A7BFD430
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<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=3D"http://www.w3.org/TR/REC-html40">

<head>

<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	font-variant:normal !important;
	color:navy;
	text-transform:none;
	text-decoration:none none;
	vertical-align:baseline;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</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=3DSection1>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'>Hi =
Gene,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'>Sorry for the Greek (we say =
B=F6hmische D=F6rfer
;-) I know what I talked about may only be of interest for software =
emgineers.
The issue is that our customers are using these files (I guess this =
format is
somehow popular because you can easily add annotations. The problem was =
that
our tool opened the files but showed only black content. As I said =
before I had
no idea that libtiff allows the magic &#8220;EP&#8221; for =
TIFFs.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'><o:p>&nbsp;</o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy'>For sure first I&#8217;m looking =
for a solution
for our customers but if there is a general solution for all platforms =
then it
may be integrated in to libtiff.<br>
<br>
In the meantime I&#8217;m able to decode these strips (not to difficult =
if you are
looking to a hex dump of the strip).<br>
But the result is that the decoded data is no bitmap, it is an EMF =
(Enhanced
Meta File) data block.<br>
<br>
So I&#8217;m able to view these special TIFFs in our product on Windows =
but I can not
offer a general solution because for this you would need a platform =
independent
EMF to bitmap converter. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
Martin<br>
<br>
<font color=3Dnavy><span =
style=3D'color:navy'>&gt;&gt;</span></font>Since this all
read as Greek to me, I decided to try to find out more info on these =
terms
through some google searching.&nbsp; <br>
<font color=3Dnavy><span style=3D'color:navy'>&gt;&gt;</span></font><br>
<font color=3Dnavy><span =
style=3D'color:navy'>&gt;&gt;</span></font>&gt;From my
investigation, I think you are saying that these image files are in a =
format
used by an old version of MS office (2003), where MDI means Microsoft =
<font
color=3Dnavy><span =
style=3D'color:navy'>&gt;&gt;&gt;</span></font>Document Image
format and MSCD is the Microsoft Secure Content Delivery program.&nbsp; =
I think
this is saying that Microsoft defined their own codec for image <font
color=3Dnavy><span =
style=3D'color:navy'>&gt;&gt;&gt;</span></font>storage in MS
Office 2003.&nbsp; On one google result that I found, it appears that MS =
has
abandoned this image format in later versions of MS Office.<br>
<font color=3Dnavy><span style=3D'color:navy'>&gt;&gt;</span></font><br>
<font color=3Dnavy><span style=3D'color:navy'>&gt;&gt;</span></font>Is =
this what
you were saying?&nbsp; <br>
<font color=3Dnavy><span style=3D'color:navy'>&gt;&gt;</span></font><br>
<font color=3Dnavy><span =
style=3D'color:navy'>&gt;&gt;</span></font>Also, isn't OLE
(Object Linking and Embedding) another MS-only standard that doesn't =
help
anyone using a non-MS platform?<br>
<font color=3Dnavy><span style=3D'color:navy'>&gt;&gt;</span></font><br>
<font color=3Dnavy><span =
style=3D'color:navy'>&gt;&gt;</span></font>Thanks,<br>
<font color=3Dnavy><span style=3D'color:navy'>&gt;&gt;</span></font><br>
<font color=3Dnavy><span =
style=3D'color:navy'>&gt;&gt;</span></font>&nbsp;&nbsp;
Gene Amtower <o:p></o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_001F_01C92337.A7BFD430--


--===============1043445731==
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/
--===============1043445731==--

