Newsgroups: sci.image.processing
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!uunet!in1.uu.net!news.sprintlink.net!howland.reston.ans.net!ix.netcom.com!netcom.com!olea
From: olea@netcom.com (Michael Olea)
Subject: Re: THe 'libtiff' library & Intel TIFF support
Message-ID: <oleaD4H5M2.F69@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <sbrogden.30.000C21FB@derwent.co.uk> <331159955wnr@dstrip.demon.co.uk>
Date: Thu, 23 Feb 1995 22:39:38 GMT
Lines: 27
Sender: olea@netcom15.netcom.com

Steve@dstrip.demon.co.uk (Steve Rencontre) writes:

>In article: <sbrogden.30.000C21FB@derwent.co.uk>  sbrogden@derwent.co.uk (Simon Brogden) writes:

>> Does anyone know how to make the excellent  'libtiff' library output purely 
>> Intel format TIFF (0x4949) ? The tools based on the library always write a 
>> TIFF file with the endian of the host machine.

>I don't know the package, but I'd be very surprised if it could be made 
>endian-neutral without a lot of work. I would strongly suggest that you 
>write a post-processor, which is (err, maybe..!) a near-trivial piece of 
>code as you don't have to *understand* any of the TIFF tags, just swap 
>bytes around.
> 

>-----------------------------------------------------------------------
>Steve Rencontre               |  steve@dstrip.demon.co.uk (business) 
>If it works, it's obsolete.   |  steveren@cix.compulink.co.uk (private)
>-----------------------------------------------------------------------

	Swapping bytes in the tags is in general not sufficient.
For example, the "stripOffsets" and "stripByteCounts" tags may point
to data that would also need to be swapped to be consistent - or
they may point to data that should be left alone.  A program cannot
distinguish such cases without *understanding* at least some of the
tags.

