AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
August 2006

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2006.08.24 07:29 "IPTC tag", by Joris Van Damme
2006.08.24 17:45 "Re: IPTC tag", by Phil Harvey
2006.08.25 13:30 "Re: IPTC tag", by Joris Van Damme
2006.08.25 17:37 "Re: IPTC tag", by Phil Harvey
2006.08.25 18:30 "Re: IPTC tag", by Chris Cox
2006.08.29 17:39 "Re: IPTC tag", by Joris Van Damme
2006.08.25 18:43 "Re: IPTC tag", by Chris Cox
2006.08.24 21:34 "Re: IPTC tag", by Chris Cox
2006.08.25 11:15 "Re: IPTC tag", by Joris Van Damme
2006.08.25 15:36 "Re: IPTC tag", by Bob Friesenhahn
2006.08.25 15:56 "Re: IPTC tag", by Joris Van Damme
2006.08.25 18:50 "Re: IPTC tag", by Chris Cox
2006.08.29 15:47 "Re: IPTC tag", by Joris Van Damme

2006.08.25 17:37 "Re: IPTC tag", by Phil Harvey

The one thing we should be able to agree on is that regardless of the 
data type, IPTC data should NOT be byte-swapped when written.  If 
writing with the current version of libTIFF, this means that should be 
written as undefined.  I tried this strategy (writing IPTC as 
undefined) with my software and found users who complained of 
incompatibilities, so I changed to writing long as Adobe does.  For me 
it was an easy change, although I agree that it serves to perpetuate a 
historical 'bug' in the way IPTC is written.  I also agree that it 
would be best if this bug could be eventually squashed, but it looks 
like here I am part of the problem, not the solution.

Along the same lines, I also consider it a bug that IFD offsets are 
written as long (value of 4).  They should be written as IFD type 
(value of 13), otherwise unknown IFD's can not be parsed.  If we're 
trying to fix historical bugs, maybe we could fix this as well.  While 
you may never have been stung by this bug, I have repeatedly because of 
the non-standard TIFF-format information that my software has to deal 
with.

- Phil