Re: CFD: eXIF 2017-0207
John Bowler <[email protected]> Sun, 12 Feb 2017 17:52:09 -0800
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <CAP7U39-Td9cG=eDczu9+Jb_dL7GCD-Wb6bw0P9CtT7ccmMHt7w@mail.gmail.com> |
On Sun, Feb 12, 2017 at 10:29 AM, Phil Harvey <phil-CIeU6mJ2MbMd166Dz3SrqbDks+cytr/[email protected]> wrote: > If you gave me a link to the sample I could take a look, but it is not uncommon to >have preview pointers referencing data outside the EXIF segment. That's what I suspected and it does seem that in both the cases I get the warning the entries relate to the preview. Here are the exiv2 warnings: $ pngdumpmeta --exif <Alaska.png >/dev/null Warning: Directory OlympusCs, entry 0x0101: Strip 0 is outside of the data area; ignored. $ pngdumpmeta --exif <BigelowLakes.png >/dev/null Warning: Directory NikonPreview, entry 0x0201: Data area exceeds data buffer, ignoring it. Neither "exif" nor "exiftool" output any messages however I don't think either default to outputting those specific directories, pngdumpmeta just iterates though the whole set of EXIF data. The *original* JPEG images are here: https://drive.google.com/drive/folders/0Bx8MRyhJu3rTaW50eHFVQWRvYXM?usp=sharing In the "CC Atribution-ShareAlike" folder; Alaska.jpg and BigelowLakes.jpg The EXIF (APP1) data was copied verbatim. -- John Bowler <[email protected]> +1 (541) 450-9885 PO BOX 3151 KERBY OR 97531-3151 USA ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot