On 06/01/2015 05:11 AM, Paolo Benvenuto wrote:
2015-04-18 15:39 GMT+02:00 Paolo Bacchilega <paolo bacchilega libero it>:Il 17/04/2015 14:18, Paolo Benvenuto ha scritto:- change date command: the user hasn't the possibility to change exif date. I consider it an important feature, which the user would appreciate in the case the camera had wrong date settings. I think it's a rather trivial problem to code it, in the shell I use jhead command. Did you decide to negate the user this possibility or will it appear in a near future?If you change the comment date the exif date will be updated as well.No, It doesn't change: I tried all the ways without success.
On the other hand, I *prefer* that EXIF:DateTimeOriginal doesn't get automatically changed when I change the comment date. I don't want to need to remember to change the camera clock every time I travel to a different time zone or go through a DST switch and there's no time zone or UTC offset in EXIF:DateTimeOriginal that I can check to verify that I had set the time zone correctly, so I always keep my camera clock in UTC. Then when commenting the photo, I localize the display time. Since there's no time zone or UTC offset in EXIF:DateTimeOriginal (and since there's no unambiguous way to convert a localized time back to UTC), I leave EXIF:DateTimeOriginal alone. This ensures that I can always correct a mistake without needing to try to undo a localization first. Since the version of gthumb that I'm using can't change the display time without overwriting EXIF:DateTimeOriginal, I use a script to perform the localization, storing the result in XMP:DateTimeOriginal (which *does* have a UTC offset). Rennie
Attachment:
signature.asc
Description: OpenPGP digital signature