Re: CFD: eXIf 2017-05-31

GLENN PEHRSON <[email protected]> Thu, 8 Jun 2017 14:48:57 -0400 (EDT)
Newsgroups gmane.comp.graphics.png.general
Message-ID <[email protected]>
> 
>     On June 8, 2017 at 12:30 PM Phil Harvey <phil-CIeU6mJ2MbMd166Dz3SrqbDks+cytr/[email protected]> wrote:
> 
>         > > 
> >         On Jun 8, 2017, at 12:26 PM, Phil Harvey <phil-CIeU6mJ2MbMd166Dz3SrqbDks+cytr/[email protected]> wrote:
> >         The encoder should know where the information is coming from (eg. JPEG or TIFF image), but it may not know the ultimate destination, so I see why it should be its responsibility for limiting the data size.
> > 
> >     > 
>     Sorry. Typo. Should read: "I don't see why it should be [the encoder's] responsibility for limiting the data size."
> 

Agreed.  It's not the PNG encoder's responsibility; it's the responsibility of a PNG decoder that plans to write a JPEG.

See the 2017-06-08a CFD.


Glenn

------------------------------------------------------------------------------
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