https://bugs.kde.org/show_bug.cgi?id=468830
--- Comment #35 from FeikeEU <[email protected]> --- (In reply to caulier.gilles from comment #34) > >Why not to bypass exiv2 when it fails ? (only if user set "delegate to > >Exiftool writing operations"). Of course, I have no idea whether such a fix > >is reasonably feasible, it is just a suggestion. > > Because actually we cannot. <snip> > Thanks for you continued feedback and efforts!! I appreciate the effort it would cost to rebuild digiMam's metadata engine, so I'm more hoping that exiv2 will fix the issue at their end, at some point. Still, until (if 'ever') that happens, it is still unfortunate that people are carefully managing their tags (face tags, in my personal situation), while they don't always get added to the actual image file. In some sense, the work gets lost, without the user realizing it! (That's how I, at some point, came across this issue. In another application (GeoSetter) I did not see some face tags, that I was sure I added to the image. And now I don't know which other tags did not get written, in the tens-of-thousands of images I tagged in the last years....) So I would still (humbly :)) ask for an error message to be shown: "file xyz was not updated", so that I can (try to) fix the issue when it occurs. (E.g. 'clean/fix' the JPG file and try again.) (While the face tags I set are still in the digiKam database, I only 'really rely' on the metadata that is stored in the actual image files, as that is (in my opinion) the only way to be 'future proof', and not be 'forever' dependent on the (continued existence) of the database of one application or the other.) -- You are receiving this mail because: You are watching all bug changes.
