not all fields are always written to XMP, sometimes just IPTC
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DigiWf |
Won't Fix
|
Low
|
Stefaan Vanderheyden |
Bug Description
it's strange: when I use digiWF (version 0.3.3 from launchpad PPA) to edit metadata, sometimes a field (maybe city, for example) will write to both IPTC and XMP formats, but other fields are only stored in the older IPTC format.
Isn't the IPTC standard becoming abandoned in favor of XMP? in which standard is digiWF intended to record metadata like photo origin sublocation, city, etc.; and...why is it being inconsistent?
I think the best option is that it records the information to the appropriate fields in BOTH IPTC and XMP standards at same time. but if only one can be done, isn't XMP better? Dublin core of XMP is open source, isn't it? I don't know if it includes all the needed fields. But even if we have to use proprietary adobe XMP fields, it is better to stay up with the changing standards, than using one that will be abandoned...
(note: I am checking the data storage format using the metadata viewers in both digiKam (Ubuntu) and Photoshop (OSX))
Hi Poikloid,
I use Phil Harvey's exiftool to store the metadata.
I guess you have raised a bug that concerns his software rather than the DigiWf GUI.
I won't be making any changes to the code regarding this issue.
Thanks for using DigiWf and taking time to provide me with your feedback.
BR,
Stefaan