Dan Cline wrote:
> On Fri, 27 Jun 2008 16:13:34 +0200, Ofnuts wrote:
>
>>> How did you do it?
>> My mom agrees with you.
>
> Give up. There is no exif editing tool that will read in a text file.
>
> If there were, someone would say so.
There is at least one...
> The reason no tool will read in an edited exif text file is because the
> tool developers don't want to risk the inevitable crashes that would occur.
Changing the Exifs in a file is no more complicated that rewriting them
together with a modified version of the picture (PS, PSP, GIMP...)
> All exif editing tools will only edit their own proprietary binary files
> and then read in only their own binary exif information.
Something which is ignored by the author of the software I just used. Of
course he is not using binary files to export the exifs, he uses XML.
And as a software developer myself, I can tell you that playing with
exifs is ridiculously easy compared to writing a working JPEG
encoder/decoder from scratch, for instance.
> It would be nice if there were an exif standard but there isn't.
There is a standard for the core stuff (
http://www.exif.org/, and in
particular
http://www.exif.org/Exif2-2.PDF). This format defines 1) how
data items are stored, so anyone can come up with tags for his own
purpose, and 2) a common set of core tags (standard enough for the
Windows explorer to use it (check the columns you can use in a "details"
view)). Of course camera makers have added their own extensions and they
may even use different extensions depending on model.
Reading/writing this data isn't difficult, even if the software doesn't
know what the purpose of a given tag would be (and so could not display
a human-friendly name). In fact anyone familiar with binary editors can
patch up the data quite easily since most of it is fixed-length.
--
Bertrand