Re: CFD eXIf 2017-05-31 [was DRAFT: eXIF 2017-05-28]

01.06.2017 15:56, Glenn Randers-Pehrson пишет:
>
>   It is beyond the scope of this specification to resolve potential conflicts between
> data in the eXIf chunk and in other PNG chunks. It is recommended that
> unless a decoder has independent knowledge of the validity of the Exif
> data, the data should be considered to be of historical value only.
>
And all these 'maybe' is looks like extra complexity for me, definitely 
not KISS.
As a developer of png software I read "beyond the scope of this 
specification " like "There is no guarantee for EXIF, but someone may 
prefer EXIF over PNG chunks, so try to guess what data is actual". Guess 
is not simple.

Same for
 >there is no expectation that any thumbnails present in the Exif 
profile have (or have not) been updated if the main image was changed.
and
 >encoders should be aware that, if the Exif profile is converted to 
JPEG, the total length of the Exif data (the sum of the lengths of the 
Exif attributes IFD, the GPS IFD, the thumbnail IFD, and the TIFF 
header) must not exceed 64 kbytes, because it must fit into a JPEG APP1 
marker.


-- 
Have a nice DOS.

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