Bug 456262 - Be able to edit EXIF 2.32 Time Zone fields
Summary: Be able to edit EXIF 2.32 Time Zone fields
Status: RESOLVED DUPLICATE of bug 251357
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-MetadataEdit (other bugs)
Version First Reported In: 7.6.0
Platform: Microsoft Windows Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-02 22:00 UTC by José Oliver-Didier
Modified: 2025-04-11 23:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Edit Metadata - EXIF Date and Time (55.00 KB, image/png)
2022-07-02 22:00 UTC, José Oliver-Didier 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description José Oliver-Didier 2022-07-02 22:00:01 UTC 
Created attachment 150347 [details]
Edit Metadata - EXIF Date and Time

SUMMARY

Add support for editing EXIF 2.32 Time Zone fields in "Edit Metadata"
0x9010 OffsetTime string ExifIFD (time zone for ModifyDate)
0x9011 OffsetTimeOriginal string ExifIFD (time zone for DateTimeOriginal)
0x9012 OffsetTimeDigitized string ExifIFD (time zone for CreateDate)


STEPS TO REPRODUCE
1. Launch Digikam and select an image.
2. From the menu select "Item" -> "Edit Metadata..."
3. In the "Edit Metadata" dialog, select the "Edit EXIF" tab and select the "Date and Time" option.

OBSERVED RESULT
- No options for editing EXIF timezones (in XMP timezones are supported). Ref attached screenshot.

EXPECTED RESULT
- Be able to edit EXIF timezones or clear them.

SOFTWARE/OS VERSIONS
Windows 11 

ADDITIONAL INFORMATION
- Related to bug 251357
Comment 1 Maik Qualmann 2022-07-03 04:40:36 UTC 
It's more or less a duplicate of bug 251357

Maik
Comment 2 José Oliver-Didier 2022-11-02 21:42:30 UTC 
Wow. Did not realize Bug 251357 was opened nearly 12 years ago! I do not believe EXIF standard provided support for time zone, now it does.
Comment 3 caulier.gilles 2025-04-11 23:50:48 UTC 

*** This bug has been marked as a duplicate of bug 251357 ***