https://bugs.kde.org/show_bug.cgi?id=470566
--- Comment #38 from maison <bugzi...@kgb.ovh> --- (In reply to Maik Qualmann from comment #26) > So, after various tests on Windows, I can't reproduce the problem. There is > one more thing, since the last versions of Exiv2 (also 0.27.5) the Unicode > support in Windows is broken. If your image path contains characters that > are outside of the current Windows code page, problems may arise. Check this > out, please. > Otherwise we need the image with the problem and a real log (not a log from > a test collection) when updating the metadata of the corresponding image. If > not publicly possible, to my private mail. > > Maik Thanks Maik for trying to reproduce. I’m convinced it’s not a problem with the image files (they are scanned fine if they are new to a new digiKam profile) and it’s not because of Unicode characters (some of them do have Unicode and some don’t, and again, both are scanned fine if digiKam doesn’t know them in advance). The Unicode exiv2 discussion might be a different subject than this bug — to be confirmed. But because you’re asking I’m going to send you the files. BTW, I still use Windows 7 because I’ve never had the time to reinstall all my software on Windows 10. Maybe next winter. -- You are receiving this mail because: You are watching all bug changes.
