Status: Read
Received: from [207.176.88.85] by phillip.cerious.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Wed, 19 Jan 2000 09:20:15 -0500
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id IAA12173;
	Wed, 19 Jan 2000 08:54:55 -0500
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Wed, 19 Jan 2000 08:41:38 -0500
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id IAA10107
	for tiff-outgoing; Wed, 19 Jan 2000 08:41:37 -0500
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from inet.yellow.de ([194.121.136.34])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id IAA10097
	for <tiff@olympiakos.com>; Wed, 19 Jan 2000 08:41:31 -0500
Received: from rechner108 ([192.168.3.1]) by inet.yellow.de
          (Post.Office MTA v3.5.1 release 219 ID# 0-55100U100L2S100V35)
          with ESMTP id de for <tiff@olympiakos.com>;
          Wed, 19 Jan 2000 13:26:15 +0100
From: Dirk.Haun@yellow.de (Dirk Haun)
Organization: Yellow Computing Computersysteme GmbH
To: TIFF Mailing List <tiff@olympiakos.com>
Date: Wed, 19 Jan 2000 13:26:19 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Unicode build of libtiff?
X-mailer: Pegasus Mail for Win32 (v3.12b)
Message-ID: <20000119122615352.AAA290@inet.yellow.de@rechner108>
Sender: owner-tiff@olympiakos.com

Hi,

has anyone done a unicode build of libtiff yet? I have just done the 
necessary modifications to the last version of libtiff supplied by 
Sam Leffler, when I found out that libtiff has moved ahead to version 
3.5.4 since then. <doh>

So, obviously, I have to do it all again. I might be willing to send in 
my changes as a diff file so that others can profit but I have no idea 
how non-Windows platforms handle unicode.

Here's how MS does it:
- use type TCHAR instead of char for unicode characters
- each string and char literal has to be enclosed in a _T() macro
- use lstrlen, lstrcpy, etc. instead of strlen, strcpy, ...

Then, if you #define UNICODE, you get a unicode build. Otherwise, 
you get an ASCII/ANSI build just as before.

I guess this can all be handled with a couple of macros to put into 
the tif_<platform>.h files.

What do you think?

regards,


Dirk Haun
Dirk.Haun@yellow.de

Yellow Computing Computersysteme GmbH
Hanns-Martin-Schleyer-Strasse 1
D-74177 Bad Friedrichshall (Germany)
Phone +49-7136-9511-0
Fax +49-7136-9511-11
Web: http://www.yellow.de
