Re: cOMp chunk [was: EXIF support in PNG]
John Bowler <[email protected]>
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <CAP7U39-xiwOYDdGOYxu2c+S5FG49hfC2VS+Jy0qnmLzzkUkWGg@mail.gmail.com> |
On Sun, Jan 1, 2017 at 10:19 AM, Glenn Randers-Pehrson <[email protected]> wrote: > Of course, consistency would also suggest having a keyword, which I happen > to like. Simple > handles can be useful. > What I'm proposing is a set of chunks which the application never sees; if I ask the encoder will write an sPLT as cOMP/sPLT but I never seer that; I give the encoder an sPLT. When an app reads this using a decoder which supports cOMP the decoder reports an sPLT, not a cOMP. If the compressed chunk had a keyword before compression it has one after compression. Any extra data on the wrapper cOMP chunk is spurious noise. -- John Bowler <[email protected]> +1 (541) 450-9885 PO BOX 3151 KERBY OR 97531-3151 USA ------------------------------------------------------------------------------ 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