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
July 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.07.22 19:32 "Re: Value/Offset field is Value or offset", by Anmol Misra
2005.07.22 22:29 "Re: Value/Offset field is Value or offset", by Joris Van Damme
2005.07.24 01:40 "Re: Value/Offset field is Value or offset", by Anmol Misra
2005.07.25 15:33 "Re: Value/Offset field is Value or offset", by Joris Van Damme

2005.07.25 15:33 "Re: Value/Offset field is Value or offset", by Joris Van Damme

> I am actually trying to join two single page tiff files to multiple tiff
> files. So I need to play around with the offsets of the second files and 
> one of the problems that I am facing was to decide whether 4 bit value is 
> Value or Offset to the value.

If joining tiff pages is your goal, then you've got some additional trouble to
consider.

- Some tags need to be copied in order for your destination file to make sense.
ImageWidth tag is a perfect example.
- Some tags need to do additional very specific processing. TileOffsets and
StripOffsets tags.
- Some tags, you must *not* copy for reasons of their actual meaning. PageNumber
is a perfect example.
- In general, blind copy of unknown tags is downright dangerous. A datatype of
long can mean just that, a 32bit unsigned value, but it is also a not very
recommended way to point to a child IFD. It's very hard to know which of these
two it is used for. This means that you could be copying a pointer to a child
IFD as if it were a long value. Next, an application that actually knows that
particular tag might come along, and might expect that sort of particular child
IFD to be present at that particular offset. But it isn't. It is pointed to
random other data, and depending on whether or not it is very robust, it might
behave in unexpected ways.
- Even though the TIFF spec forbids pointers to locations outside the tag data,
in any tag data block, there are known offenses. This too, leads to trouble.

I recommend you also search the mailing list archive for more information on
this. The archive search is over at:

 http://www.awaresystems.be/imaging/tiff/tml.html.

If I remember correctly, there is a LibTiff tool which does this TIFF concat. It
is very restrictive about the tags it copies. I'm not the expert on LibTiff, but
there's a useful page on LibTiff tools here:

http://www.remotesensing.org/libtiff/tools.html

> About LibTiff, can one use it in the programs ? Are there any license
> restrictions to it?

As far as I know, the license is not restrictive at all. Basically, you can use
it in any applications, including commercial ones.


Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be/
Download your free TIFF tag viewer for windows here:
http://www.awaresystems.be/imaging/tiff/astifftagviewer.html