Summary: | SCHEMA : add time zone support as properties of items | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Matthieu Pupat <kde> |
Component: | Database-Schema | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | adam.siembida, caulier.gilles, debruyck, iwannaberich, jose_oliver, julien.t43+kde |
Priority: | NOR | ||
Version: | 2.8.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Matthieu Pupat
2010-09-15 19:11:40 UTC
This is a job for digiKam DB properties, to dispatch later to plugin... Gilles Caulier still valid in 2.8.0. got a mixup of chronological order when traveling timezone. Now that time zone is supported in the new EXIF standard it would be nice to revisit this bug. EXIF 2.32 Time Zone fields: 0x9010 OffsetTime string ExifIFD (time zone for ModifyDate) 0x9011 OffsetTimeOriginal string ExifIFD (time zone for DateTimeOriginal) 0x9012 OffsetTimeDigitized string ExifIFD (time zone for CreateDate) Also, timezone are supported in XMP dates. Ref email sent to the Digikam Mailing list: http://digikam.1695700.n4.nabble.com/digiKam-users-Determining-Time-Zone-based-on-date-location-and-supporting-new-EXIF-time-zone-offset-s-td4714273.html *** Bug 443098 has been marked as a duplicate of this bug. *** Adding comment from Bug 377857 The MWG 2.0 spec (the group seems to have disbanded, but the spec is still referenced) has some thoughts on timezones on page 33. https://s3.amazonaws.com/software.tagthatphoto.com/docs/mwg_guidance.pdf Also, something which I stumbled upon some time ago: "TimeZoneOffset is a non-standard tag that was made before the EXIF standard actually added time zone tags. There are three time zone tags, EXIF:OffsetTimeOriginal, EXIF:OffsetTime, and EXIF:OffsetTimeDigitized, which correspond to EXIF:DateTimeOriginal, EXIF:ModifyDate, and EXIF:CreateDate respectively." https://exiftool.org/forum/index.php?topic=13170.0 *** Bug 474834 has been marked as a duplicate of this bug. *** |