Version: (using KDE 4.2.0) OS: MS Windows Installed from: MS Windows XMP files do no seem to be generated for raw files. As such a generation does not change the file itself, why not having XMP files being generated for raw files ? Frederic
First. I hate XMP side-car concept. i will never implement something like that. Second, a new option exist to save metadata to RAW files. Currently supported by Exiv2 library are DNG, NEF, and PEF. Others will supported by Exiv2 in the future. So updating Exiv2 later and digiKAm support it automatically. Gilles Caulier
Gilles Thank you for your answer. One thing I do not understand: if you hate XMP side car concept, why is it implemented for JPEG images ? On my side, I am really careful on software that attempts to write inside raw files. Let's wait for the future to see how reliable it will be. Regards. Frederic
>why is it implemented for JPEG images ? digiKam never create XMP side-car files (:=))) ==> a photo = image data + metadata. we never separate both. ==> if file format do not support metadata we use database. Gilles Caulier
And if the database is corrupted you lose meta-data. Bad! Redundency is good. Even if Digikam NEVER used them except to rebuild it's database, it's not unreasonable to support them, especially if there is some standard format for them. This may make it easier for importing and exporting data to other photo programs. E.g. you could have a manual: Export Metadata to XMP files. And a verify XMP. When digikam exported it, it saved a checksum in it's database. If the XMP now has a different checksum, then something besides digikam has played with it. If digikam has never seen it before, it's a potential way to get info into digikam. I would ask that you consider using a small value for 'never' (grin)
*** This bug has been marked as a duplicate of bug 220545 ***
Not reproducible in 6.0.0