Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-f.b-one.net (mx-f.one.com [91.198.169.53])
	by mail9.b-one.net (Postfix) with ESMTP id 920E8400125
	for <info@awaresystems.be>; Fri, 27 Feb 2009 20:42:33 +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-f.b-one.net (Postfix) with ESMTP id C9955280024B
	for <info@awaresystems.be>; Fri, 27 Feb 2009 20:42:32 +0100 (CET)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id 631341D201D72;
	Fri, 27 Feb 2009 14:41:50 -0500 (EST)
Received: from toronto2.smartgames.ca (toronto2.smartgames.ca [204.15.192.18])
	by lists.maptools.org (Postfix) with ESMTP id C880C1D18FA89
	for <tiff@lists.maptools.org>; Fri, 27 Feb 2009 14:09:49 -0500 (EST)
Received: from [10.143.176.101] (unknown [10.143.176.101])
	by toronto2.smartgames.ca (Postfix) with ESMTP id 7C3161887;
	Fri, 27 Feb 2009 14:10:09 -0500 (EST)
In-Reply-To: <a768e9280902271030q46fdd434t80b9c1542c764eaa@mail.gmail.com>
References: <C5CC98F7.7D325%ccox@adobe.com>
	<C1D0D145-19B8-47BF-AD2D-9193E388B9B2@telegraphics.com.au>
	<Pine.SOC.4.64.0902270949230.1127@freddy.simplesystems.org>
	<59A9C69A-D1C8-4327-A773-EFA6E2A786C4@telegraphics.com.au>
	<a768e9280902271030q46fdd434t80b9c1542c764eaa@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <4D462AA3-8B73-4578-8C9E-F37C8CBD4E25@telegraphics.com.au>
From: Toby Thain <toby@telegraphics.com.au>
Date: Fri, 27 Feb 2009 14:09:41 -0500
To: stephen@scarlsen.com
X-Mailer: Apple Mail (2.753.1)
Cc: 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="===============0832061270=="
Mime-version: 1.0
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org


--===============0832061270==
Content-Type: multipart/alternative; boundary=Apple-Mail-147--243455883


--Apple-Mail-147--243455883
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On 27-Feb-09, at 1:30 PM, S Carlsen wrote:

> I would say "both." Start from a clean, well-thought-out, TIFF-ish  
> architecture -- one that is powerful enough to represent the  
> graphics and text constructs that are found in a PSD/PSB file.

If only we knew exactly how they are represented and rendered, that  
might be possible. But we don't.

Interoperability. See also: Samba.

--Toby

> (And more.)
>
> On Fri, Feb 27, 2009 at 8:54 AM, Toby Thain  
> <toby@telegraphics.com.au> wrote:
> So, for those who want to design equivalent add-ons to TIFF, do they
> start with a clean slate, or do they try to align their efforts with
> a mangled, incomplete 79-page codex?
>
>


--Apple-Mail-147--243455883
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=US-ASCII

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<br><div><div>On 27-Feb-09, at 1:30 PM, S Carlsen wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">I would =
say "both." Start from a clean, well-thought-out, TIFF-ish architecture =
-- one that is powerful enough to represent the graphics and text =
constructs that are found in a PSD/PSB file. =
</blockquote><div><br></div><div>If only we knew exactly how they are =
represented and rendered, that might be possible. But we =
don't.</div><div><br></div><div>Interoperability. See also: =
Samba.</div><div><br></div><div>--Toby</div><br><blockquote =
type=3D"cite">(And more.)<br><br><div class=3D"gmail_quote"> On Fri, Feb =
27, 2009 at 8:54 AM, Toby Thain <span dir=3D"ltr">&lt;<a =
href=3D"mailto:toby@telegraphics.com.au">toby@telegraphics.com.au</a>></sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"border-left: =
1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: =
1ex;"> So, for those who want to design equivalent add-ons to TIFF, do =
they<br> start with a clean slate, or do they try to align their efforts =
with<br> a mangled, incomplete 79-page codex?<br> =
<br></blockquote></div><br></blockquote></div><br></body></html>=

--Apple-Mail-147--243455883--

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