Re: Endless gamma in eXIf 2017-0119
Pavel Zlatovratskii <[email protected]>
| Newsgroups | gmane.comp.graphics.png.general |
|---|---|
| Organization | TB.Budget |
| Message-ID | <[email protected]> |
Well, in my scenario everyone know what they application doing. The just don't know how others application doing. And proposal allow both way. If I'll try to write PNG2JPG how I must handle case 'gamma in EXIF, no gAMA chunk'? Proposal have words 'data shall be assumed to be correct unless it can be determined to be incorrect'. You may choose 'no gAMA - no conflict, no incorrectness', I may choose 'no gAMA is for 1.0 gamma, if EXIF data content other it's incorrect'. How we should determine which of us are right? That's what specification writing for(via proposals). If someone keep iCCP intact after applying gAMA you may point to specification(14.2). For gamma in eXIf you have nothing except your understanding. That is bad thing in proposal. Other (like compression 'salt' we discuss before) does not motivate me to vote NO. 07.02.2017 5:44, Willem van Schaik пишет: > We're still relying on both developers and users to act responsibly. > Which is for me the right thing to do. They know what their applications > are doing. > > Protection against hackers, I'm all for it, but protecting dumb users, I > don't know why we should. :) > > Willem > -- Pavel Zlatovratskii [email protected]; [email protected] ------------------------------------------------------------------------------ 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