[Digikam-devel] [Bug 264204] New: Existing XMP sidecar file gets overwritten by digiKam

[Milan Knizek]

https://bugs.kde.org/show_bug.cgi?id=264204

           Summary: Existing XMP sidecar file gets overwritten by digiKam
           Product: digikam
           Version: 2.0.0
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Metadata
        AssignedTo: digikam-devel at kde.org
        ReportedBy: knizek at volny.cz


Version:           2.0.0 (using KDE 4.5.5) 
OS:                Linux

If there is already an XMP sidecar created by other application, digiKam
rewrites it with its own content.

Reproducible: Always

Steps to Reproduce:
Use some other application to create a sidecar XMP file for image.cr2 (e.g.
darktable).
Open digiKam, make sure "writing to XMP files is allowed", add some tag to
image.cr2.


Actual Results:  
XMP sidecar image.xmp gets overwritten, information stored by darktable is
lost.

Expected Results:  
digiKam is friendly to existing XMP keys and does not remove them.

darktable creates image.cr2.xmp, while digikam (as of now) creates image.xmp.
For the test above, either rename the sidecar or create a symlink.
BTW, darktable does the same as digiKam (bug).

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.