Re: CFD: eXIf 2017-05-31
Glenn Randers-Pehrson <[email protected]> Thu, 8 Jun 2017 07:10:45 -0400
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Message-ID | <CA+PdXcsBpMiMGz8V2h1pybL=fguokVg+VUkGy64QzFN_Jr4HhA@mail.gmail.com> |
On Thu, Jun 8, 2017 at 6:41 AM, Glenn Randers-Pehrson <[email protected]> wrote: > On Thu, Jun 8, 2017 at 1:10 AM, Cosmin Truta <[email protected]> wrote: > >> I'm not sweating too much over this. If we can replace this word from >> the CFD to the CFV (without going through another CFD round), great. I >> personally find it useful to have EXIF profiles larger than 64KB, for >> example, to be able to store the preview image (which is different >> than, and larger than the thumbnail image) inside EXIF, rather than >> outside. Storing the preview outside EXIF leaves a dangling pointer >> inside EXIF. Not a problem with TIFF, but a problem with JPEG. By >> imposing this limit in PNG, then PNG would inherit the same problem as >> JPEG. Changing the above two words from "must" to "should" would >> resolve this problem. > > I agree. The phrase should say > > "should not exceed 64 kbytes, so it could fit into a JPEG APP1 marker" Actually, in the context, "must" is correct, because it's subordinate to "if the Exif profile is converted to JPEG..." Glenn ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot