2004.08.16 17:29 "[Tiff] ICC profile in tiff file on windows", by Alexander Cohen
-
2004.08.16 17:56 "Re: [Tiff] ICC profile in tiff file on windows", by Chris Cox
-
2004.08.16 18:12 "Re: [Tiff] ICC profile in tiff file on windows", by Alexander Cohen
-
2004.08.16 19:32 "Re: [Tiff] ICC profile in tiff file on windows", by Chris Cox
- 2004.08.16 19:55 "Re: [Tiff] ICC profile in tiff file on windows", by Alexander Cohen
- 2004.08.16 23:07 "Re: [Tiff] ICC profile in tiff file on windows", by Joris Van Damme
-
2004.08.16 19:32 "Re: [Tiff] ICC profile in tiff file on windows", by Chris Cox
-
2004.08.16 18:12 "Re: [Tiff] ICC profile in tiff file on windows", by Alexander Cohen
2004.08.16 23:18 "Re: [Tiff] ICC profile in tiff file on windows", by Chris Cox
The profile itself is always big endian (it's a separate file embedded in a TIFF tag, and doesn't know anything about the TIFF containing it).
The rest of the TIFF file follows the TIFF specifications, of course.
If I may add (and double-check that I got it right):
ICC specification (http://www.color.org/icc32.pdf) says that the ICC profile tag (code 34675) is of datatype undefined (7). Undefined is essentially the same as 'byte' of all encapsulating tiff datajoggling purposes: it means there is no endian issue, and that the stream of bytes should be takes just as is, without any byteswopping on any platform whatsoever.
Right. Right?
Right.
Chris