https://bugs.kde.org/show_bug.cgi?id=468830
--- Comment #8 from Darek Kay ---
Created attachment 163760
--> https://bugs.kde.org/attachment.cgi?id=163760&action=edit
Example image file
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468830
--- Comment #9 from Darek Kay ---
Created attachment 163761
--> https://bugs.kde.org/attachment.cgi?id=163761&action=edit
Example XMP sidecar file (big)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468830
--- Comment #10 from Darek Kay ---
Created attachment 163762
--> https://bugs.kde.org/attachment.cgi?id=163762&action=edit
Example XMP sidecar file (small)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=468830
--- Comment #11 from Darek Kay ---
I have encountered the same issue (digiKam deletes all metadata) and the core
issue is the same (XMP segment is big), BUT the use case is slightly different
and I feel like this is a problem with digiKam itself. I
https://bugs.kde.org/show_bug.cgi?id=468830
--- Comment #13 from Darek Kay ---
@Maik Thank you for looking into this. I should have been more specific: it is
not the XMP file that is destroyed (here digiKam always works). It's the JPG
file for which the sidecar exists that is destroyed. Th
https://bugs.kde.org/show_bug.cgi?id=468830
Darek Kay changed:
What|Removed |Added
CC||m...@darekkay.com
--
You are receiving this mail
