https://bugs.kde.org/show_bug.cgi?id=499361
Bug ID: 499361
Summary: Possibly add exiftool "-m" parameter to
Classification: Applications
Product: digikam
Version: 8.6.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: minor
Priority: NOR
Component: Metadata-ExifTool
Assignee: digikam-bugs-n...@kde.org
Reporter: josjonke...@gmail.com
Target Milestone: ---
I posted this on KDE discuss as well, as I am not sure if this fits here. If
not; please close.
https://discuss.kde.org/t/digikam-exiftool-wrapper-possibly-add-m-switch-to-ignore-minor-warnings/29083
I noticed that when writing files using Digikam (and Exiftool) – currently
using version 8.5.0 – Not all metadata is written correctly to all files.
I have no logs of the Exiftool output, but I see the progress bar in Digikam go
forward sometimes at the expected speed; sometimes at a very quick rate as if
it skips files.
I have a suspicion that if a minor error or warning from the side of Exiftool
occurs; the file is not written at all.
I see from Digikam that exiftool is invoked like:
```C:\Program Files\digiKam\exiftool.exe" -stay_open true -@ - -common_args
-charset filename=UTF8 -charset iptc=UTF8```
I guess the actual data is put into the ARGS file using Exiv2, and Exiftool is
used to write to the files.
It might be beneficial to add the Exiftool “-m” parameter to the command, to
ensure that files are written, even when minor warnings would otherwise stop
the writing of the file.
It might be added to the invoking command line, or into the ARGS file itself; I
do not know.
SOFTWARE/OS VERSIONS
Digikam 8.5
Windows: 10
--
You are receiving this mail because:
You are watching all bug changes.
