2004.04.15 00:26 "[Tiff] Large TIFF files", by Lynn Quam

2004.04.22 19:52 "Re: [Tiff] Large TIFF files", by Phillip Crews

Of course, that brings up the question: do we still need to support two byte orders?

In my experiments, reading from the disk always swamped the time needed to swap byte order - so there is no noticable impact from using a fixed byte order and forcing conversion on one platform the other.

I suggest that network byte order (big endian) be used. Especially if any Big TIFF variant will go before the IETF for RFC approval.

If the choice is made to go with one byte order, then I second the choice of big endian since it allows portable sample-parsing code to be more efficient and easier to implement.

Probably someone will complain about that because their application only uses one sample size and they only use Intel x86.

Or maybe VAX!

I work mostly on x86/Windows, and I say let 'em whine. It should be one byte order; less confusion in the future, and network byte order is the appropriate choice.

PS. Sorry for the direct e-mail, Bob. I forget again to change the recipient to the list.