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
November 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.11.15 09:38 "libtiff support for Microsoft Office Document Imaging", by Brad Hards
2005.11.15 14:40 "Re: libtiff support for Microsoft Office Document Imaging", by Frank Warmerdam
2005.11.20 04:31 "Re: libtiff support for Microsoft Office Document Imaging", by Brad Hards
2005.11.21 03:29 "Re: libtiff support for Microsoft Office Document Imaging", by Frank Warmerdam

2005.11.20 04:31 "Re: libtiff support for Microsoft Office Document Imaging", by Brad Hards

On Wednesday 16 November 2005 01:40 am, Frank Warmerdam wrote:
> I would suggest adding a potential #define in tiffconf.h
> that is MDI_SUPPORT.  Normally it would not be defined.
> If defined, then .mdi files magic number is supported
> and byte swapping is done accordingly.
>
> Depending on your level of success, the messiness and your
> willingness we might later want to incorporate MDI support
> into the core library (controlled by the MDI_SUPPORT flag).

I've had a go at doing this.  See attached for what it might look like.

I decided to add a configure option instead of doing the #define directly.
The #define has no effect for tiffdump, since tiffdump is already a 
diagnostics tool and can support most of the MDI tags.

I've done a little bit of work on what will happen if the host is bigendian, 
however it is almost certainly incomplete. I will do some more work on this 
before submitting the patch again.

I'd also like to add something to the public API (eg another define or a 
function) that says whether libtiff was compiled with MDI support.

I'm still not sure this is the right approach - doing a more general solution 
(perhaps with some flags) and always having it on would avoid packaging / 
building problems.

Brad