Hello Like gThumb 2, gThumb 3 stores comment data both in an XML comment file and in IPTC tags. In gThumb 2, the IPTC date was treated as authoritative: if the comment file was missing or the date differed, the comment file date would be replaced with the IPTC one. This seems to have changed in gThumb 3. If the comment file is missing, the date is re-created from the EXIF date, rather than the IPTC date. Further, the default behaviour in the comment/metadata dialog is to replace the date with the EXIF date, even if an IPTC date and comment date are already set. This new behaviour is a problem for me. I keep my camera clock in UTC so that I don't need to worry about changing the camera clock when I travel. However, I want the display date on my photos to reflect the local time zone where they were taken, so I change the time in the comment. With the gThumb 3 behaviour, I need to manually correct the time every time I edit a photo's comment, rather than just editing it the first time and trusting gThumb to leave it as I left it. Is there any particular reason for the new behaviour? If not, any chance that it could be reverted to the old gThumb behaviour? Thanks, Rennie
Attachment:
signature.asc
Description: OpenPGP digital signature