https://bugs.kde.org/show_bug.cgi?id=480345
Maik Qualmann changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/grap
|
https://bugs.kde.org/show_bug.cgi?id=480345
Maik Qualmann changed:
What|Removed |Added
CC||korti...@gmail.com
--- Comment #18 from Maik Qu
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #17 from caulier.gil...@gmail.com ---
Ok,
So it's not urgent to update Exiv2, especially in MXE, as it's a legacy version
of Windows installer.
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #16 from Maik Qualmann ---
In principle, the problem with the file path is not that common, only with file
paths whose characters are outside the current Windows code page. This should
only occur very rarely for most Windows users. We could
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #15 from caulier.gil...@gmail.com ---
well under Windows, we will needs to turn on this option by default... right ?
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #14 from Maik Qualmann ---
The problem would only be when writing metadata if ExifTool is not activated,
as we do not automatically switch to ExifTool when writing.
Maik
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #13 from Maik Qualmann ---
Yes, in case of a file read error due to file path encoding (Exiv2 Error #10),
we automatically read with ExifTool and decode the container with Exiv2 so that
all metadata is present.
Maik
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #12 from caulier.gil...@gmail.com ---
Do you means that i can switch also the Exiv2 version for MXE to 0.28.x now ?
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #11 from Maik Qualmann ---
We also have the problem with the file path encoding with the VCPKG build.
Which I don't understand since this build was supposed to use Windows' Utf8
API.
But it's not a problem because in this case we automatical
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #10 from caulier.gil...@gmail.com ---
Hi Maik,
Exiv2 0.28.2 is out :
https://github.com/Exiv2/exiv2/blob/v0.28.2/doc/ChangeLog
I'm not sure if we must include this version in the bundles. For Windows, VCPKG
still branched to 0.28.1. Under
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #9 from caulier.gil...@gmail.com ---
The digiKam 8.3.0 use also Exiv2 0.21 compiled with MSVC.
The problem with ExifTool is know. Windows do not kill children process when
parent die. What's great operating system. A file already exist in bu
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #8 from nickbishop97+...@gmail.com ---
(In reply to caulier.gilles from comment #6)
> and where come from this other Exiv2 dll ? which version exactly ?
It's the Windows build of 0.28.1 available here:
https://exiv2.org/download.html
https:/
https://bugs.kde.org/show_bug.cgi?id=480345
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #7 from Maik
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #6 from caulier.gil...@gmail.com ---
and where come from this other Exiv2 dll ? which version exactly ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #5 from nickbishop97+...@gmail.com ---
It looks like I had a separate install of Exiv2 v0.28.1 in %PATH%, and that's
where it was getting the DLL from after I removed the one installed with 8.3.0.
Sorry for the confusion.
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #4 from caulier.gil...@gmail.com ---
How digiKam can run with Exiv2.dll ???
Even if you use ExifTool backend, Exiv2 still used internally to parse metadata
contents. ExifTool is only used to acces file contents (read/write). This one
transfr
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #3 from nickbishop97+...@gmail.com ---
The 8.3.0 preview build came with Exiv2.dll v0.28.1, according to Components
Information. If I remove Exiv2.dll from the folder, digiKam switches to using
ExifTool and does not crash.
https://i.imgur.co
https://bugs.kde.org/show_bug.cgi?id=480345
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|8.2.0 |8.3.0
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=480345
--- Comment #2 from nickbishop97+...@gmail.com ---
Just tested with digiKam-8.3.0-20240124T094137-Win64, same crash.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480345
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=480345
Bug Janitor Service changed:
What|Removed |Added
Keywords||qt6
--
You are receiving this mail becau
21 matches
Mail list logo
