Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-g.b-one.net (mx-g.one.com [91.198.169.54])
	by mail9.b-one.net (Postfix) with ESMTP id B4BA8400125
	for <info@awaresystems.be>; Fri, 27 Feb 2009 04:38:23 +0100 (CET)
X-Virus-Scanned: by one.com
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=0 required=6
	tests=[HTML_MESSAGE=0.001]
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144])
	by mx-g.b-one.net (Postfix) with ESMTP id 4E44C1400158
	for <info@awaresystems.be>; Fri, 27 Feb 2009 04:38:21 +0100 (CET)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id 0BF9D1D203EAF;
	Thu, 26 Feb 2009 22:37:39 -0500 (EST)
Received: from exprod6og107.obsmtp.com (exprod6og107.obsmtp.com [64.18.1.208])
	by lists.maptools.org (Postfix) with ESMTPS id 32AF21D203E8B
	for <tiff@lists.maptools.org>; Thu, 26 Feb 2009 22:07:46 -0500 (EST)
Received: from source ([192.150.8.22]) by exprod6ob107.postini.com
	([64.18.5.12]) with SMTP
	ID DSNKSadY/0rBlYcEuQkIAHDKrx55fcZ0zurI@postini.com;
	Thu, 26 Feb 2009 19:08:18 PST
Received: from inner-relay-3.eur.adobe.com (inner-relay-3b [10.128.4.236])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	n1R37eE0000196; Thu, 26 Feb 2009 19:07:41 -0800 (PST)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98])
	by inner-relay-3.eur.adobe.com (8.12.10/8.12.9) with ESMTP id
	n1R37cY2021515; Thu, 26 Feb 2009 19:07:39 -0800 (PST)
Received: from excas03.corp.adobe.com (10.8.189.123) by nahub02.corp.adobe.com
	(10.8.189.98) with Microsoft SMTP Server (TLS) id 8.1.336.0;
	Thu, 26 Feb 2009 19:07:37 -0800
Received: from nambx03.corp.adobe.com ([10.8.189.93]) by
	excas03.corp.adobe.com ([10.8.189.123]) with mapi;
	Thu, 26 Feb 2009 19:07:37 -0800
From: Chris Cox <ccox@adobe.com>
To: "zhangweiwu@realss.com" <zhangweiwu@realss.com>, "stephen@scarlsen.com"
	<stephen@scarlsen.com>
Date: Thu, 26 Feb 2009 19:07:35 -0800
Thread-Topic: [Tiff] OT: Text layer possible in tiff format?
Thread-Index: AcmYghQfGuyMsd20Tmi8UP61Mn2q8wABnWUv
Message-ID: <C5CC98F7.7D325%ccox@adobe.com>
In-Reply-To: <49A74791.3050100@realss.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "Joris Van Damme \(AWare Systems\)" <info@awaresystems.be>,
	TIFF <tiff@lists.maptools.org>
Subject: Re: [Tiff] OT: Text layer possible in tiff format?
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="===============1103380834=="
Mime-version: 1.0
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

--===============1103380834==
Content-Language: en
Content-Type: multipart/alternative;
	boundary="_000_C5CC98F77D325ccoxadobecom_"

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

Yes, Kodak stuffed a lot of non-standard, undocumented stuff into their fil=
es.

For Photoshop, the text has to be pixel accurate - what one user sees, all =
users should see. That requires the same exact layout and rasterization eng=
ine everywhere.  So, Photoshop's text layers are not a good candidate for s=
haring with other apps.

If you just want comments, that could be standardized - since the exact ras=
terization doesn't matter.  Of course, comments could just be added to stan=
dard XMP metadata and optionally rendered.

Chris


On 2/26/09 5:53 PM, "zhangweiwu@realss.com" <zhangweiwu@realss.com> wrote:

S Carlsen schrieb:
> Joris, Zhang, and all,
>
> Yes, it would certainly be possible to add constructs such as image
> layers, text layers, masks, and so on to TIFF. (There was actually a
> brief discussion of this topic at least as far back as May of 2004.)
> It would of course take a fair amount of commitment to make it happen.
> But if it did happen, if it were reasonably elegant and not too
> difficult to implement, and if it gained some momentum and popularity,
> I suspect that Photoshop would eventually support it.
>
Hi thanks for the comment.

If there could be effort on this, where should this effort be put? On
Gimp TIFF save plugin? or could libtiff do something? I guess first
thing that should be done should be in GIMP.

I remember some 10 years ago I used a software pre-installed on MS
Windows, made by Kodak, called "Image". The software allows me to put
comment text on TIFF images and save it in the tiff images. The other
person who opens the tiff image can see and edit my comment. "Comment"
is simply text above image layers. Does anyone know if Kodak stuffed a
lot of non-standard information as comment into TIFF or it extended tiff
in the "legal" way? If so they already have an implementation that
contain text layers, only thing need to do is to work on gimp to make it
compatible with that format.

I think Kodak's "Image" did not implement all the text attributes like
hinting, anti-alias and so like. But in GIMP not all text decoration are
implemented neither (e.g. not possible to set text underlined).
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/


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

<HTML>
<HEAD>
<TITLE>Re: [Tiff] OT: Text layer possible in tiff format?</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Myriad Pro"><SPAN STYLE=3D'font-size:10pt'>Yes, Kodak stuffed=
 a lot of non-standard, undocumented stuff into their files.<BR>
<BR>
For Photoshop, the text has to be pixel accurate &#8212; what one user sees=
, all users should see. That requires the same exact layout and rasterizati=
on engine everywhere. &nbsp;So, Photoshop&#8217;s text layers are not a goo=
d candidate for sharing with other apps.<BR>
<BR>
If you just want comments, that could be standardized &#8211; since the exa=
ct rasterization doesn&#8217;t matter. &nbsp;Of course, comments could just=
 be added to standard XMP metadata and optionally rendered.<BR>
<BR>
Chris<BR>
<BR>
<BR>
On 2/26/09 5:53 PM, &quot;<a href=3D"zhangweiwu@realss.com">zhangweiwu@real=
ss.com</a>&quot; &lt;<a href=3D"zhangweiwu@realss.com">zhangweiwu@realss.co=
m</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Myriad Pro"><SPAN STYLE=3D'font-siz=
e:10pt'>S Carlsen schrieb:<BR>
&gt; Joris, Zhang, and all,<BR>
&gt;<BR>
&gt; Yes, it would certainly be possible to add constructs such as image<BR=
>
&gt; layers, text layers, masks, and so on to TIFF. (There was actually a<B=
R>
&gt; brief discussion of this topic at least as far back as May of 2004.)<B=
R>
&gt; It would of course take a fair amount of commitment to make it happen.=
<BR>
&gt; But if it did happen, if it were reasonably elegant and not too<BR>
&gt; difficult to implement, and if it gained some momentum and popularity,=
<BR>
&gt; I suspect that Photoshop would eventually support it.<BR>
&gt;<BR>
Hi thanks for the comment.<BR>
<BR>
If there could be effort on this, where should this effort be put? On<BR>
Gimp TIFF save plugin? or could libtiff do something? I guess first<BR>
thing that should be done should be in GIMP.<BR>
<BR>
I remember some 10 years ago I used a software pre-installed on MS<BR>
Windows, made by Kodak, called &quot;Image&quot;. The software allows me to=
 put<BR>
comment text on TIFF images and save it in the tiff images. The other<BR>
person who opens the tiff image can see and edit my comment. &quot;Comment&=
quot;<BR>
is simply text above image layers. Does anyone know if Kodak stuffed a<BR>
lot of non-standard information as comment into TIFF or it extended tiff<BR=
>
in the &quot;legal&quot; way? If so they already have an implementation tha=
t<BR>
contain text layers, only thing need to do is to work on gimp to make it<BR=
>
compatible with that format.<BR>
<BR>
I think Kodak's &quot;Image&quot; did not implement all the text attributes=
 like<BR>
hinting, anti-alias and so like. But in GIMP not all text decoration are<BR=
>
implemented neither (e.g. not possible to set text underlined).<BR>
_______________________________________________<BR>
Tiff mailing list: <a href=3D"Tiff@lists.maptools.org">Tiff@lists.maptools.=
org</a><BR>
<a href=3D"http://lists.maptools.org/mailman/listinfo/tiff">http://lists.ma=
ptools.org/mailman/listinfo/tiff</a><BR>
<a href=3D"http://www.remotesensing.org/libtiff/">http://www.remotesensing.=
org/libtiff/</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C5CC98F77D325ccoxadobecom_--

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