AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

1994.02.10 19:32 "LibTIFF working on MS-Windows 3.1.", by Soren Pingel Dalsgaard
1994.02.11 09:39 "Re: LibTIFF working on MS-Windows 3.1.", by Bjorn P. Brox
1994.02.11 01:09 "Re: LibTIFF working on MS-Windows 3.1.", by Richard Minner
1994.02.11 14:40 "Re: LibTIFF working on MS-Windows 3.1.", by Jie Yao
1994.02.11 01:16 "Re: LibTIFF working on MS-Windows 3.1.", by Richard Minner
1994.02.11 10:17 "Re: LIBTIFFW working on MS-Windows 3.1.", by Niles Ritter
1994.02.14 11:03 "Error/warning handlers in libtiff", by Erik Corry
1994.02.16 22:38 "Re: Error/warning handlers in libtiff", by Sam Leffler
1994.02.11 18:27 "Re: LibTIFF working on MS-Windows 3.1.", by Francois Gauthier
1994.02.11 21:29 "Re: LibTIFF working on MS-Windows 3.1.", by Sam Leffler

1994.02.11 01:09 "Re: LibTIFF working on MS-Windows 3.1.", by Richard Minner

  • Ability to write both II and MM type tiff images. Yes that's right you can write little and big endian images using the library.

Agree that it could be able to write both types.

The code is able to write both types, but it insist to write the endian type the hardware reports.

However it does not have any practical use since the standard says that a product should be able to read both formats.

If not, they should not be allowed to tell that they support TIFF...

That is a bit legalistic I'm afraid. In reality there are probably hundreds or thousands of little programs that "support TIFF", and many are non-commercial. Many of those will not bother to implement both byte-orders for read, and if you only produce the other order, they will not read your files. Those programs indeed do not "really" support TIFF as specified, but the program owners have broken no law or contract in providing incomplete support!

Thank you for your many fine comments, and code suggestions.

--
Richard Minner rtm@island.com {uunet,sun,well}!island!rtm
Island Graphics Corporation Sacramento, CA (916) 736-1323