https://bugs.kde.org/show_bug.cgi?id=395914
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #12 from caulier.gil...@gmail.com ---
Maik,
We needs to take a decision about this file. Removing code is easy but can have
side effects with users workflow. I vote to let's reading XMP sidecar option
available but force to read when writing
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #11 from caulier.gil...@gmail.com ---
Maik,
I think we needs to let the choice to the users at end in all cases, to read or
not the XMP sidecars.
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #10 from caulier.gil...@gmail.com ---
M
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #9 from caulier.gil...@gmail.com ---
Hi Maik,
No, i don't remember a specific case to disable reading from sidecar when
writing to sidecar is enabled.
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #8 from Maik Qualmann ---
I think we should always treat sidecars as a unit with the image. We should
remove the option to read from sidecars and always read from sidecars if they
are available. Gilles, do you see a use case to disable readi
https://bugs.kde.org/show_bug.cgi?id=395914
Maik Qualmann changed:
What|Removed |Added
CC||ja...@lab6.com
--- Comment #7 from Maik Qualman
https://bugs.kde.org/show_bug.cgi?id=395914
aabarkl...@gmail.com changed:
What|Removed |Added
CC||aabarkl...@gmail.com
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=395914
caulier.gil...@gmail.com changed:
What|Removed |Added
Platform|Windows CE |MS Windows
CC|
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #6 from Grzegorz ---
(In reply to Maik Qualmann from comment #5)
> Ok, I think the correct solution is always to mix the sidecar metadata when
> writing.
That's what I'd expect. Always merge, never overwrite.
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #5 from Maik Qualmann ---
Ok, I think the correct solution is always to mix the sidecar metadata when
writing. The digiKam metadata will then have the higher priority when writing.
Maik
--
You are receiving this mail because:
You are watc
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #4 from Grzegorz ---
Created attachment 113594
--> https://bugs.kde.org/attachment.cgi?id=113594&action=edit
digiKam XMP with Read from sidecar files disabled
The darktable XMP after updating from digiKam with the "Read from sidecar
files
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #3 from Grzegorz ---
Created attachment 113593
--> https://bugs.kde.org/attachment.cgi?id=113593&action=edit
digiKam XMP with Read from sidecar files enabled
The darktable XMP after updating from digiKam with the "Read from sidecar
files"
https://bugs.kde.org/show_bug.cgi?id=395914
--- Comment #2 from Grzegorz ---
Created attachment 113592
--> https://bugs.kde.org/attachment.cgi?id=113592&action=edit
darktable XMP
The source XMP coming from darktable containing processing history
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=395914
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
https://bugs.kde.org/show_bug.cgi?id=395914
Grzegorz changed:
What|Removed |Added
Summary|Metadata is wiped out from |Sidecar files are replaced
|the si
16 matches
Mail list logo