https://bugs.kde.org/show_bug.cgi?id=420195
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||7.1.0
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=420195
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Metadata-Engine |Plugin-FilesIO-HEIF
--- Comment #48 f
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #47 from caulier.gil...@gmail.com ---
yes we use C API, even if C++ compiler is used even if all libheif
implementation use .cc everywhere.
I think it's better to patch C API. As libheif is currently included in DK
core, it's easy do to, app
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #46 from Maik Qualmann ---
Hi Gilles,
Saving HEIF images does not currently support UTF-16. There is a patch for
KImageFormats, a function of the libheif is overloaded and saved using
QIODevice. If I see it correctly, libheif also has a C++
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #45 from caulier.gil...@gmail.com ---
Maik,
It still a patch to apply to libheif to close this file ?
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420195
Maik Qualmann changed:
What|Removed |Added
CC||ngocchibanh+...@gmail.com
--- Comment #44 from
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #43 from caulier.gil...@gmail.com ---
ffmpeg rock (:=)))...
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #42 from Maik Qualmann ---
I like the solution in FFmpeg. FFmpeg uses char* as UTF8 file name. Under
Windows, a UTF8ToUTF16WChar() function is used to convert and the corresponding
Windows wchar* functions are called. Therefore FFmpeg works
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #41 from caulier.gil...@gmail.com ---
This is the advantage to use libheif internally until the library has all main
bug fixed.
Typically, we can already use it as external dependency, since the cmake
compilation and install rules from the l
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #40 from Maik Qualmann ---
Ok, loading HEIF images from Unicode paths now works. It remains to save HEIF
images. I think we have to patch the libheif.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #39 from Maik Qualmann ---
Git commit c9d0d10f1c38607bc888b4b484106533e13be906 by Maik Qualmann.
Committed on 19/05/2020 at 19:35.
Pushed by mqualmann into branch 'master'.
load HEIF file into memory if loading from Unicode path detected
M
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #38 from caulier.gil...@gmail.com ---
Git commit 65fd05a84cb463edc976e2120ac66e09c9cb87ea by Gilles Caulier.
Committed on 12/05/2020 at 11:10.
Pushed by cgilles into branch 'master'.
Update internal libraw to last 0.20.0-beta1
(https://www.l
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #37 from Maik Qualmann ---
Ok, fine. Libraw already works in digiKam with UTF16 paths.
https://invent.kde.org/kde/digikam/-/commit/e057a771cecd3f155d5857be507a8dd05ef9a649
We still have the problem with the HEIF Loader. This does not suppo
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #36 from caulier.gil...@gmail.com ---
Maik,
Look well on the libraw 0.20.-beat1 announcement. We have now a compilation
flag to enable to support UTF16 paths under Windows.
https://www.libraw.org/news/libraw-0-20-beta1
So i will backport t
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #35 from Maik Qualmann ---
Git commit 3b1c95ab04573f3b892d72a95278e2a756f419d7 by Maik Qualmann.
Committed on 09/05/2020 at 06:45.
Pushed by mqualmann into branch 'master'.
add unicode support for the JPEG2000 loader
M +16 -10 core/dp
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #34 from Maik Qualmann ---
Git commit e057a771cecd3f155d5857be507a8dd05ef9a649 by Maik Qualmann.
Committed on 08/05/2020 at 05:32.
Pushed by mqualmann into branch 'master'.
try to use unicode under Windows for the RAW decoder
M +29 -5
https://bugs.kde.org/show_bug.cgi?id=420195
Tobias changed:
What|Removed |Added
CC|shntob...@gmail.com |
--
You are receiving this mail because:
You are watc
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #33 from Maik Qualmann ---
to Comment 30: Ok, I'll do it tonight.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #32 from Maik Qualmann ---
Git commit 17124d5f042778c9ac0038a63caf4c822e863b04 by Maik Qualmann.
Committed on 07/05/2020 at 05:51.
Pushed by mqualmann into branch 'master'.
libtiff has a wchar open function
M +9-1core/dplugins/dim
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #31 from Maik Qualmann ---
Git commit df2144e3f3f88ca4be660d80d306d216d3f4fdd2 by Maik Qualmann.
Committed on 07/05/2020 at 05:39.
Pushed by mqualmann into branch 'master'.
first try to support unicode with utime()
M +20 -4core/libs
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #30 from caulier.gil...@gmail.com ---
Maik,
MetaEngine private container has the Exiv2 configuration header included :
https://invent.kde.org/kde/digikam/-/blob/master/core/libs/metadataengine/engine/metaengine_p.h#L69
You can just check
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #29 from Maik Qualmann ---
I just see the build is done, Exiv2 is without unicode support.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #28 from Maik Qualmann ---
The MSVC may be more precise and also requires the std::wstring instead of
wchar_t*. Let's see, you can not see from the error message whether the
function is available.
Maik
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #27 from caulier.gil...@gmail.com ---
Maik,
To know which Exiv2 features are enabled, an exported header must be available
:
exv_conf.h
... with this kind of definition:
// Define to enable the Windows unicode path support.
/* #undef EXV_U
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #26 from caulier.gil...@gmail.com ---
Maik,
Windows CI build do not pass because It do not use last stable release or last
code from git 0.27 maintenance branch. I suspect that the Exiv2 API to support
Windows Unicode path is not too old.
h
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #25 from Maik Qualmann ---
Git commit 183933ce5c6e52bb0e4f307d85a0fa041cb84e7b by Maik Qualmann.
Committed on 06/05/2020 at 20:16.
Pushed by mqualmann into branch 'master'.
first DImg loaders support unicode under Windows
M +6-2co
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #24 from Maik Qualmann ---
Git commit f2f35d19fb56e2e5e9a8f398afcec4e93bb4ca2b by Maik Qualmann.
Committed on 06/05/2020 at 18:30.
Pushed by mqualmann into branch 'master'.
now Exiv2 can read unicode paths under Windows
M +6-1core
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #23 from Maik Qualmann ---
Git commit cf8aa4a0a9475b0e9ea35ebeda421303c6a783f0 by Maik Qualmann.
Committed on 06/05/2020 at 05:50.
Pushed by mqualmann into branch 'master'.
revert all unicode changes at Exiv2
M +1-6core/libs/metad
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #22 from Maik Qualmann ---
Git commit a28e8c9512c53a2ee68e60446c9e57ef6f988214 by Maik Qualmann.
Committed on 05/05/2020 at 20:58.
Pushed by mqualmann into branch 'master'.
try to give Exiv2 under Windows a UTF16 string
M +5-0core
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #21 from Maik Qualmann ---
Git commit cc61ea9abd278960d8a5caaa1bc66d93d074ba90 by Maik Qualmann.
Committed on 04/05/2020 at 20:16.
Pushed by mqualmann into branch 'master'.
first attempt to use unicode file names with Exiv2
M +1-2
https://bugs.kde.org/show_bug.cgi?id=420195
Tobias changed:
What|Removed |Added
CC||shntob...@gmail.com
--- Comment #20 from Tobias ---
B
https://bugs.kde.org/show_bug.cgi?id=420195
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|general |Metadata-Engine
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #19 from Maik Qualmann ---
I will patch the days and pass Exiv2 UTF8 strings to see if it is used
correctly in Windows.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #18 from caulier.gil...@gmail.com ---
MAik,
See the configuration of Exiv2 from 0.27-maintenance branch under Windows :
-- --
-- Building shared library:YES
-- Buil
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #17 from caulier.gil...@gmail.com ---
Git commit e0360b3812396769a0ce2fd58124e9dc4feac555 by Gilles Caulier.
Committed on 28/04/2020 at 11:21.
Pushed by cgilles into branch 'master'.
Switch to Exiv2 0.27-maintenance branch instead 0.27.2 old
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #16 from caulier.gil...@gmail.com ---
Note : bugfixes list from Exiv2 0.27.3 RC1 :
https://github.com/Exiv2/exiv2/issues/1018#issuecomment-604539346
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #15 from caulier.gil...@gmail.com ---
Ok, well i will switch all bundles from Exiv2 0.27.2 to 0.27-maintance git
branch. Like this we will use next 0.27.3 and future small improvement
automatically. I will recompile automatically Exiv2 when d
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #14 from Maik Qualmann ---
For me that's fine to use the Exiv2-RC.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420195
--- Comment #13 from caulier.gil...@gmail.com ---
Maik,
Next Exiv2 0.27.3 is near to release :
https://github.com/Exiv2/exiv2/issues/1186
What do you think to include this RC in all bundles ?
Gilles
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=420195
Maik Qualmann changed:
What|Removed |Added
Summary|no thumbnails and previews |no support for UTF16
|of heic
40 matches
Mail list logo
