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

[lexo]

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

lexo <lexo.lexo at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lexo.lexo at gmail.com

--- Comment #6 from lexo <lexo.lexo at gmail.com> ---
(In reply to comment #0)
> 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).

I've the same issue with Aftershot pro and/or darktable :(
xmp sidecar is overwrite by digikam 2.5.0 if geoloc and/or tag is added :(
merging will be the top :)

-- 
You are receiving this mail because:
You are the assignee for the bug.