*** For details on how to be removed from this list visit the ***
*** CCP4 home page http://www.ccp4.ac.uk ***
On Thursday 30 March 2006 10:37 am, Tim Fenn wrote:
> On Wed, Mar 29, 2006 at 11:49:14PM -0800, Ethan A Merritt wrote:
>
> > TIFF is a file format, not an image encoding scheme.
> > Inside that TIFF file may be a raw RGB image, or a RLE
> > (run length-encoded) image, or some proprietary compression format,
> > or indeed a PNG image.
>
> Exactly - which brings up compatibility problems. For example, TIFF
> can use the png compression algorithm (as you mention), but some
> programs won't read your TIFF anymore, including several web browsers,
> since they won't recognize the tags.
You are changing the topic rather dramatically. The original
discussion was about preparing figures for publication; now
you are dragging in web browser capabilities. PNG is indeed
better for web use (for one thing, normal TIFF is not
streamable).
> > The thing that makes it TIFF, and the reason journals tend
> > to request it, is that at the front of the file is a header
> > section that contains envelope information like desired
> > image size, resolution, enddian-ness, comments, and a whole
> > slew of other things.
>
> With no real standard for what can be there, how can it all be
> supported, or how do you know anyone else will be able to read in all
> your image tags?
TIFF standard and related links:
http://www.digitalpreservation.gov/formats/fdd/fdd000022.shtml
> If there is additional information you want to go along with the
> image, use netCDF.
For network use, maybe. But again this has nothing to do with
publication markup or document preparation.
--
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle WA
