Newsgroups: sci.image.processing
From: Steve@dstrip.demon.co.uk (Steve Rencontre)
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!news2.near.net!news.mathworks.com!udel!gatech!howland.reston.ans.net!pipex!peernews.demon.co.uk!dstrip.demon.co.uk!Steve
Subject: Re: THe 'libtiff' library & Intel TIFF support
References: <sbrogden.30.000C21FB@derwent.co.uk>
Distribution: world
Organization: Datastrip Limited
Reply-To: Steve@dstrip.demon.co.uk
X-Newsreader: Newswin Alpha 0.6
Lines:  19
X-Posting-Host: dstrip.demon.co.uk
Date: Thu, 23 Feb 1995 16:13:29 +0000
Message-ID: <331159955wnr@dstrip.demon.co.uk>
Sender: usenet@demon.co.uk

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)
-----------------------------------------------------------------------

