Re: CALL for DISCUSSION: eXIf 20170115
Glenn Randers-Pehrson <[email protected]>
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <CA+PdXcuGt-1V2hr4G4PSy-ysf+gyJ_K8hSAvt9msrZXxS1cwFA@mail.gmail.com> |
I updated the proposal to version 2017-0119, replacing the two paragraphs defining the contents of the data segment with this: The data segment of the eXIf chunk contains an Exif profile in the format specified in "4.7.2 Interoperability Structure of APP1 in Compressed Data" of [CIPA DC-008-2016] except that the JPEG APP1 marker, length, and the "Exif ID code" described in 4.7.2(C), i.e., "Exif", NULL, padding byte, are not included. It begins with either "II" or "MM", depending upon the byte order used. Glenn On Thu, Jan 19, 2017 at 4:03 PM, John Bowler < [email protected]> wrote: > On Thu, Jan 19, 2017 at 10:58 AM, Jason Summers <[email protected]> wrote: > > Sorry if I missed something, but as far as I can tell, the plan is still > to > > put a JPEG app ID string (or "Exif ID code" as they call it in ExifLand) > > ("Exif\0\0") in PNG files. > > > > I think that's a bad idea. The JPEG app ID string is a JPEG-specific > thing > > that doesn't belong in other formats. > > It does make more sense to me to skip it but there may be a good reason > for it. > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ png-mng-misc mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/png-mng-misc