Summary: | Cannot parse date string YYYY-MM-DDTHH:MM:SS.ssss and YYYY:MM:DD HH:MM:SS in EXIF and XMP | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Jens <jens-bugs.kde.org> |
Component: | Metadata-Date | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, metzpinguin |
Priority: | NOR | ||
Version: | 6.1.0 | ||
Target Milestone: | --- | ||
Platform: | Appimage | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.0.0 | |
Sentry Crash Report: | |||
Attachments: | exiftool JSON export of example image |
Description
Jens
2019-03-31 09:03:52 UTC
Can you share your cannon images to test her ? Gilles Caulier With sample images found on the web this IXUS 330 has no abnormalities, images has normal date format and have no XMP section. Maik Created attachment 119202 [details]
exiftool JSON export of example image
Here is an exiftool JSON export which you can reapply to any image. It's the original image exported from Apple iPhoto without modifications (at least the file size and the mtime did not change).
IMHO: Date strings like "YYYY:MM:DD HH:MM:SS" with an optional "+NNNN" or "+NN:00" timezone string appended (without or with space delimited) could be parseable by Digikam without harm even if they are not standard.
Json file applied to an empty JPEG file, only normal EXIF metadata of an IXUS camera can be found. There are no abnormalities with the date format. The "Flash" metadata is a struct field, but that's a different topic. Maik Your problematic date format is the ISO8601 format. After a quick look into the specifications I can not see that the colon is allowed as a date separator, colon is for the time. Valid are: YYYYmmdd YYYY-mm-dd Maik This problem has been solved, digiKam no longer writes the date in XMP with a colon, but with the hyphen. Maik |