Re: CFD: eXIf 2017-05-31
Glenn Randers-Pehrson <[email protected]> Thu, 8 Jun 2017 12:35:13 -0400
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <CA+PdXcvkSQnws5SqhyyLhzpxyEuKDVYgyV4Ugfvr7pYRCbe_6g@mail.gmail.com> |
On Thu, Jun 8, 2017 at 12:26 PM, Phil Harvey <phil-CIeU6mJ2MbMd166Dz3SrqbDks+cytr/[email protected]> wrote: >> From: Cosmin Truta <[email protected]> >> >> Should this not be under Recommendations for Encoders? It's the >> encoder who controls whether the 64KB limit is to be exceeded or not >> (having consideration for subsequent conversion to JPEG or not). > > I disagree. > > In general, the encoder knows nothing about what the EXIF will be used for. It is the decoder that knows this. The encoder should know where the information is coming from (eg. JPEG or TIFF image), but it may not know the ultimate destination, so I see why it should be its responsibility for limiting the data size. > Strictly speaking (which we always do here), it's about image editors that decode a PNG and write a JPEG. The PNG decoder is free to read an eXIf chunk that's over 64k, but the editor then must decide what to do about it (e.g., removing the thumbnail). Glenn ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot