Re: CALL for DISCUSSION: cOMp/cOMP/coMp/coMP: compression wrapper chunks
GLENN PEHRSON <[email protected]>
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <[email protected]> |
> > On January 29, 2017 at 8:31 PM John Bowler <[email protected]> wrote: > > On Sun, Jan 29, 2017 at 5:00 PM, Glenn Randers-Pehrson > <[email protected]> wrote: > > > > > > > > > > > > ... A decoder shall discard a cOMp chunk > > > containing an unsafe-to-copy original chunk and a cOMP chunk containing > > > a safe-to-copy original chunk. > > > > > > > > > > Shouldn't that say > > > > ... A PNG editor shall discard a cOMp chunk containing an unsafe-to-copy > > original chunk but it may preserve a cOMP chunk contianing a safe-to-copy > > original chunk, as explained in Chapters 3.3 and 7.1 of the PNG > > specification > > (Clause 14.2 of the ISO PNG Specification). > > > > > > No, it was describing decoder behavior. > D-oh. I missed the whole point of the sentence. How about ... A decoder shall discard a cOMp/cOMP chunk when the copy-safe property bit of the original chunk differs from that of the cOMp/coMP chunk itself. ------------------------------------------------------------------------------ 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