| Summary: | Support xmpMM history | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Alan Pater <alan.pater> |
| Component: | Metadata-Versioning | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 4.12.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Alan Pater
2015-08-22 18:45:39 UTC
This specification is available in Exiv2 since which version exactly ? Registered versionning info into this spec will work only with digiKam. There is not advantage to use this Adobe namespace, as tools settings to use between version are completely different and not compatible. digiKam use already Xmp to store versionning info : Xmp.digiKam.ImageHistory http://dev.exiv2.org/projects/exiv2/repository/entry/tags/0.25/src/properties.cpp#L197 The only think that we can do is to get/put information linking image files to make a sets of images. Gilles (In reply to Gilles Caulier from comment #1) > This specification is available in Exiv2 since which version exactly ? I'm not sure how long xmpMM been there, it predates my involvement with exiv2. The web page listing those properties is dated May 2013. > > Registered versionning info into this spec will work only with digiKam. > There is not advantage to use this Adobe namespace, as tools settings to use > between version are completely different and not compatible. You mean it is impossible to decode the field values written by Adobe products and that other applications would be unable to decode the values written by digikam? I fear yes. Example : I patch and image to fix WB. The settings is specific to digiKam tool. Abode will be completely different. How to join both ? Gilles |