Hi,
On Thu, 2008-03-13 at 18:52 +0100, Sven Neumann wrote:
> Certainly nothing with Exif. My guess is that the Ufraw plug-in claims
> responsibility for this file. Most probably the magic header that the
> ufraw loader registers matches for this file. This may be a bug in the
> Ufraw plug-in. You should contact the author.
Perhaps I should add this hint: If you want to check what exactly the
ufraw and tiff plug-ins are telling GIMP about the files that they can
open, you can do this by looking at your pluginrc (in your ~/.gimp-2.4
folder). There should be something like this for the tiff loader:
(load-proc
(extension "tif,tiff")
(magic "0,string,II*\\0,0,string,MM\\0*")
(mime-type "image/tiff"))
So what does this tell GIMP? It says that any file that starts with the
string "II*\\0" or with the string "MM\\0*" is a TIFF file. This
corresponds to the TIFF spec that says:
A TIFF file begins with an 8-byte image file header, containing the
following information:
Bytes 0-1:
The byte order used within the file. Legal values are:
“II” (4949.H)
“MM” (4D4D.H)
In the “II” format, byte order is always from the least
significant byte to the most significant byte, for both
16-bit and 32-bit integers This is called little-endian byte
order. In the “MM” format, byte order is always from most
significant to least significant, for both 16-bit and 32-bit
integers. This is called big-endian byte order.
Bytes 2-3:
An arbitrary but carefully chosen number (42) that further
identifies the file as a TIFF file.
The byte order depends on the value of Bytes 0-1.
Sven
_______________________________________________
Gimp-user mailing list
[email protected]
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
