Re: CFD: eXIf 2017-06-09b
Glenn Randers-Pehrson <[email protected]> Fri, 9 Jun 2017 10:38:03 -0400
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <CA+PdXcvQPVF0mh3FXTttaDyY6aJuXoA6q5reOYow_BzT=Mpuyg@mail.gmail.com> |
On Fri, Jun 9, 2017 at 10:36 AM, Phil Harvey <phil-CIeU6mJ2MbMd166Dz3SrqbDks+cytr/[email protected]> wrote: > >> From: Glenn Randers-Pehrson <[email protected]> >> I removed some of the JPEG-specific details so the recommendation >> now reads, in the 2017-06-09b version, >> >> While the PNG specification allows the chunk size to be as large as >> 2^31-1 bytes, application authors should be aware that, if the Exif profile >> is going to be written to a JPEG datastream, the total length of the eXIf >> chunk data may need to be adjusted to not exceed 2^16-9 bytes, so it can fit >> into a JPEG APP1 marker. > > Great. I apologize for making another suggestion, but calling it a "JPEG APP1 > Exif segment" would be more accurate than a "JPEG APP1 marker" because the 6-byte > Exif00 header is specific to the APP1 Exif segment. Also, a "marker" is > technically the two bytes at the start of a segment (0xff 0xe1 in this case) that > identify the type of segment. OK. BTW I'm always confused about whether we should be saying JPEG, JFIF, or JPEG/JFIF. Glenn ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot