CFD: eXIf 2017-06-09a
Glenn Randers-Pehrson <[email protected]> Fri, 9 Jun 2017 07:37:01 -0400
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <CA+PdXctbLqZ1cGg7VPKoat+kUhrXLBqAaBk3F37ds0JzDWNvqw@mail.gmail.com> |
CALL for DISCUSSION eXIf 2017-06-09a ftp://ftp.simplesystems.org/pub/png-group/documents/eXIf/ png-proposed-eXIf-chunk-2017-06-09a.html Glenn Randers-Pehrson <[email protected]> also available at http://www.simplesystems.org/png-group/proposals/eXIf/png-proposed-eXIf-chunk-2017-06-09a.html This simplifies a paragraph that overused "i.e.", wierdly once with a comma and once without, that was the result of some late-night cut-and-paste operations: < There are no ordering constraints upon the position of the eXIf chunk < beyond those imposed by the PNG specification, i.e., if present, the eXIf < chunk may appear anywhere between the IHDR and IEND chunks except between < IDAT chunks. There are no size constraints upon the eXIf chunk size beyond < those imposed by the PNG specification, i.e. maximum 2^31-1 bytes. < Only one eXIf chunk is allowed in a PNG datastream. --- > The eXIf chunk may appear anywhere between the IHDR and IEND chunks except > between IDAT chunks. There are no size constraints upon the eXIf chunk size > beyond the maximum 2^31-1 bytes imposed by the PNG specification. Only one > eXIf chunk is allowed in a PNG datastream. This restarts the 2-week discussion clock again. Glenn ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot