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
March 2005

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

2005.03.17 03:43 "libtiff and EXIF", by <ron@debian.org>
2005.03.17 03:53 "Re: libtiff and EXIF", by Bob Friesenhahn
2005.03.17 05:15 "Re: libtiff and EXIF", by <ron@debian.org>
2005.03.17 06:00 "Re: libtiff and EXIF", by Joris Van Damme
2005.03.17 06:21 "Re: libtiff and EXIF", by Joris Van Damme
2005.03.17 16:43 "Re: libtiff and EXIF", by <ron@debian.org>
2005.03.17 17:21 "Re: libtiff and EXIF", by Joris Van Damme
2005.03.17 18:57 "Re: libtiff and EXIF", by <ron@debian.org>
2005.03.17 16:00 "[PATCH] libtiff and EXIF", by <ron@debian.org>
2005.03.17 16:55 "Re: [PATCH] libtiff and EXIF", by Vadim Sukhomlinov
2005.03.18 11:39 "Re: [PATCH] libtiff and EXIF", by Andrey Kiselev

2005.03.17 03:43 "libtiff and EXIF", by <ron@debian.org>

Hi,

I've been looking at what is required to parse exif data using libtiff,
and it looks like surprisingly little.  It was trivial to bypass enough
sanity checks to easily get it to recognise and read the ExifIFD and
auto register all the tags it found there.  And not that much harder to
get it to recognise a similar tiff'ette extracted from the APP1 section
of a jpeg file with exif data and then fed to libtiff.

So the biggest question is how you all feel about supporting this from
libtiff.  Obviously TIFFFieldInfo for exif tags, if people wanted them,
could be cleanly separated from the main lib, so the main issue would be
how to provide the necessary functions for generic IFD handling.
(generic tags are already handled beautifully)

The easy way is to just provide some alternative functions, that (ab)use
the existing structures as my proof of concept does, without the
operations that are specific to valid .tif, but not found in exif
data.  The harder, but long term more rewarding way, would be to factor
out a generic IFD interface, and reimplement the strictures of TIFF vX.Y
on top of that.  Harder because it probably means breaking the ABI (at
least) to split common parts out of existing structures -- which is a
pretty extreme step to add support for something not strictly tiff but
might be justified in other ways all the same.

I'm not sure that there is much more to that which libtiff would need
to provide for people to get basic access to exif data, either from in
a tiff, or from data extracted out of a jpeg (by an external codec).
Interpreting that data can be done in a layer above libtiff, but parsing
the IFD's and tags out of the file is a job they both share and
libtiff seems to have the best foundation I have seen to build that on.
(or rather, to split it out of).

thoughts?

  Ron