| Summary: | Preserve timezone offset Timestamp in metadata. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Chris <chrisc.gigamail> |
| Component: | Metadata-Date | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version: | 8.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Chris
2024-10-28 22:00:02 UTC
First of all, it would be wrong to simply adopt the existing time offset, because this could also be wrong if you have to correct the date. Maik @Maik I suppose you are right. I'm more asking for configuration options, so my scripted prep of date fields (with exiftool) are not overwritten. Especially if I do not touch the date fields. When date fields are touched, it might also be interesting to default the timezone to what was registered originally, but with ability to change it. A further extension could be to use of GPS coordinates as an option to auto suggest timezones (which may require a paid service). /Chris Additional comment. I could solve this by unchecking "Configure Digikam" -> "Metadata" -> "Behavior" -> "Write This Information to the Metadata" -> "Timestamps" However, I had a bug with that, which caused no metadata to be updated at all inside the files. It was consistently and persistently not saving metadata to some files. But when I was writing up a bug report and made a minimum reproduction, I could not find a way to reproduce the error. So I'm still working on that, but even so... I'd still like any timestamp metadata edited in Digikam to be saved in the files, I'd just like to decide which tags to update and which tags should have timezone info and which tags should be stored in UTC time. |