2018.02.08 18:45 "[Tiff] TIFFTAG_RICHTIFFIPTC : registered as TIFF_LONG but commonly stored as TIFF_UNDEFINED", by Aaron Boxer

2018.02.08 20:11 "Re: [Tiff] TIFFTAG_RICHTIFFIPTC : registered as TIFF_LONG but commonly stored as TIFF_UNDEFINED", by Aaron Boxer

Some more back story (from an old post):

This is the story of the egg and the many, many chickens.

Originally, there was one manufacturer that got it wrong, used LONG while the data is of mixed datatype, and therefore only makes sense as BYTE or UNDEFINED on the TIFF level. Adobe chose to duplicate that mistake, so as to

remain compatible. LibTiff chose to duplicate Adobe's mistate, so as to

remain compatible. As many chickens were hatched from that very first egg, endianness issues became aparant. Some brew complicated code to correct that, so as to remain compatible... But often that sort of code is either absent, or not working fully correctly. Hence, the attempts to remain compatible, turned out at least partly futile.

includes byteswapping if endianness of file and machine don't match). Next try and interpret the data. If it doesn't make sense as valid IPTC data, byteswap it again, and retry interpreting it.

On Thu, Feb 8, 2018 at 1:45 PM, Aaron Boxer <boxerab@gmail.com> wrote:

I am trying to read the TIFFTAG_RICHTIFFIPTC tag, and I am getting an "incompatible type" warning from libtiff. Is there a way of forcing libtiff to read this tag, even though there is an incompatibility?

Many thanks,