[digikam] [Bug 420195] no support for UTF16 characters under Windows
https://bugs.kde.org/show_bug.cgi?id=420195 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.1.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/c851104 ||f6b65ef0cb463c4769af907534a ||d1283c --- Comment #49 from Maik Qualmann --- Git commit c851104f6b65ef0cb463c4769af907534ad1283c by Maik Qualmann. Committed on 30/08/2020 at 11:17. Pushed by mqualmann into branch 'master'. add the QIODevice writer to save HEIF files FIXED-IN: 7.1.0 M +3-4NEWS M +38 -1core/dplugins/dimg/heif/dimgheifloader_save.cpp https://invent.kde.org/graphics/digikam/commit/c851104f6b65ef0cb463c4769af907534ad1283c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 from caulier.gil...@gmail.com --- Maik, I move this file in HEIF plugin as it still only libheif problem with UTF16 support under Windows to fix. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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, apply and test. Later this patch can be backport officially in libheif with a github PR. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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++ part and we use only the C part? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
https://bugs.kde.org/show_bug.cgi?id=420195 Maik Qualmann changed: What|Removed |Added CC||ngocchibanh+...@gmail.com --- Comment #44 from Maik Qualmann --- *** Bug 421919 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 without any change. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 library are really better since is reported as upstream to have a clean cmake support (aka modern cmake config shared file). This must be also true for libde265, but i don't yet tested. So the rules is really to patch in DK heif plugin, and if it work, make a UPSTREAM PR on github for backport integration. I already do it for IPTC support in heif. The liheif team (which is the same for libde265) is well responding... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 +46 -4core/dplugins/dimg/heif/dimgheifloader_load.cpp https://invent.kde.org/graphics/digikam/commit/c9d0d10f1c38607bc888b4b484106533e13be906 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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.libraw.org/news/libraw-0-20-beta1) Enable Unicode paths support under Windows M +16 -1NEWS M +5-0core/libs/rawengine/CMakeLists.txt M +1-1core/libs/rawengine/libraw/COPYRIGHT M +94 -35 core/libs/rawengine/libraw/Changelog.txt M +1-10 core/libs/rawengine/libraw/README.md M +1-1core/libs/rawengine/libraw/internal/dcraw_common.cpp M +5-1core/libs/rawengine/libraw/internal/dcraw_defs.h M +1-1core/libs/rawengine/libraw/internal/dcraw_fileio.cpp M +1-1core/libs/rawengine/libraw/internal/dcraw_fileio_defs.h M +8-1core/libs/rawengine/libraw/internal/defines.h M +1-1core/libs/rawengine/libraw/internal/dmp_include.h A +300 -0core/libs/rawengine/libraw/internal/libraw_cameraids.h [License: UNKNOWN] * D +0-85 core/libs/rawengine/libraw/internal/libraw_const.h M +24 -4core/libs/rawengine/libraw/internal/libraw_cxx_defs.h M +41 -4core/libs/rawengine/libraw/internal/libraw_internal_funcs.h M +2-1core/libs/rawengine/libraw/internal/var_defines.h M +1-1core/libs/rawengine/libraw/internal/x3f_tools.h M +4-2core/libs/rawengine/libraw/libraw/libraw.h M +1-1core/libs/rawengine/libraw/libraw/libraw_alloc.h M +183 -75 core/libs/rawengine/libraw/libraw/libraw_const.h M +4-4core/libs/rawengine/libraw/libraw/libraw_datastream.h M +4-2core/libs/rawengine/libraw/libraw/libraw_internal.h M +12 -5core/libs/rawengine/libraw/libraw/libraw_types.h M +3-3core/libs/rawengine/libraw/libraw/libraw_version.h M +1-1core/libs/rawengine/libraw/samples/4channels.cpp M +1-1core/libs/rawengine/libraw/samples/dcraw_emu.cpp M +1-1core/libs/rawengine/libraw/samples/dcraw_half.c M +1-1core/libs/rawengine/libraw/samples/half_mt.c M +1-1core/libs/rawengine/libraw/samples/half_mt_win32.c M +1-1core/libs/rawengine/libraw/samples/mem_image_sample.cpp M +1-1core/libs/rawengine/libraw/samples/multirender_test.cpp M +2-2core/libs/rawengine/libraw/samples/openbayer_sample.cpp M +1-1core/libs/rawengine/libraw/samples/postprocessing_benchmark.cpp M +648 -252 core/libs/rawengine/libraw/samples/raw-identify.cpp M +2-2core/libs/rawengine/libraw/samples/rawtextdump.cpp M +1-1core/libs/rawengine/libraw/samples/simple_dcraw.cpp M +3-3core/libs/rawengine/libraw/samples/unprocessed_raw.cpp M +1-1core/libs/rawengine/libraw/src/decoders/canon_600.cpp M +4-1core/libs/rawengine/libraw/src/decoders/crx.cpp M +21 -7core/libs/rawengine/libraw/src/decoders/decoders_dcraw.cpp M +5-1core/libs/rawengine/libraw/src/decoders/decoders_libraw.cpp M +140 -4 core/libs/rawengine/libraw/src/decoders/decoders_libraw_dcrdefs.cpp M +2-2core/libs/rawengine/libraw/src/decoders/dng.cpp M +1-1core/libs/rawengine/libraw/src/decoders/fp_dng.cpp M +1-1core/libs/rawengine/libraw/src/decoders/generic.cpp M +1-1core/libs/rawengine/libraw/src/decoders/kodak_decoders.cpp M +9-9core/libs/rawengine/libraw/src/decoders/load_mfbacks.cpp M +1-1core/libs/rawengine/libraw/src/decoders/smal.cpp M +19 -14 core/libs/rawengine/libraw/src/decoders/unpack.cpp M +9-3core/libs/rawengine/libraw/src/decoders/unpack_thumb.cpp M +1-1core/libs/rawengine/libraw/src/demosaic/ahd_demosaic.cpp M +1-1core/libs/rawengine/libraw/src/demosaic/misc_demosaic.cpp M +1-1core/libs/rawengine/libraw/src/demosaic/xtrans_demosaic.cpp M +154 -43 core/libs/rawengine/libraw/src/integration/dngsdk_glue.cpp M +1-1core/libs/rawengine/libraw/src/integration/rawspeed_glue.cpp M +1-1core/libs/rawengine/libraw/src/libraw_c_api.cpp M +1-1core/libs/rawengine/libraw/src/libraw_cxx.cpp M +112 -44 core/libs/rawengine/libraw/src/libraw_datastream.cpp M +3-7core/libs/rawengine/libraw/src/metadata/adobepano.cpp M +200 -152 core/libs/rawengine/libraw/src/metadata/canon.cpp M +341 -55 core/libs/rawengine/libraw/src/metadata/ciff.cpp M +1-1core/libs/rawengine/libraw/src/metadata/cr3_parser.cpp M +6-6core/libs/rawengine/libraw/src/metadata/epson.cpp M +58 -12 core/libs/rawengine/libraw/src/metadata/exif_gps.cpp M +379 -216 core/libs/rawengine/libraw/src/metadata/fuji.cpp M +5-3core/libs/rawengine/libraw/src/metadata/hasselblad_model.cpp M +2092 -1986 core/libs/rawengine/libraw/src/metadata/identify.cpp M +1-1core/libs/rawengine/libraw/src/metadata/identify_tools.cpp M +17 -17 core/libs/rawengine/libraw/src/metadata/kodak.cpp M +12
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 support Windows UTF16 paths. I think we could add it. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 this new libraw version in digiKam core and enable the flag under Windows. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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/dplugins/dimg/jpeg2000/dimgjpeg2000loader_load.cpp M +12 -5core/dplugins/dimg/jpeg2000/dimgjpeg2000loader_save.cpp https://invent.kde.org/kde/digikam/commit/3b1c95ab04573f3b892d72a95278e2a756f419d7 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 -5core/libs/rawengine/drawdecoder.cpp M +6-1core/libs/rawengine/drawdecoder_p.cpp https://invent.kde.org/kde/digikam/commit/e057a771cecd3f155d5857be507a8dd05ef9a649 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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/dimg/tiff/dimgtiffloader_load.cpp M +10 -2core/dplugins/dimg/tiff/dimgtiffloader_save.cpp https://invent.kde.org/kde/digikam/commit/17124d5f042778c9ac0038a63caf4c822e863b04 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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/metadataengine/engine/metaengine_p.cpp https://invent.kde.org/kde/digikam/commit/df2144e3f3f88ca4be660d80d306d216d3f4fdd2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 if the UNICODE feature is enabled of not, as we do already with XMP support here : https://invent.kde.org/kde/digikam/-/blob/master/core/libs/metadataengine/engine/metaengine_p.h#L84 And just decide which API call to use with Exiv2 under Windows here : https://invent.kde.org/kde/digikam/-/blob/master/core/libs/metadataengine/engine/metaengine_fileio.cpp#L107 ... and at other places. This will work for the bundles and the CI. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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_UNICODE_PATH */ Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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. https://build.kde.org/job/Extragear/job/digikam/job/kf5-qt5%20WindowsMSVCQt5.14/472/ Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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-2core/dplugins/dimg/jpeg/dimgjpegloader_load.cpp M +6-2core/dplugins/dimg/jpeg/dimgjpegloader_save.cpp M +6-1core/dplugins/dimg/jpeg/dimgjpegplugin.cpp M +6-2core/dplugins/dimg/jpeg2000/dimgjpeg2000loader_load.cpp M +6-2core/dplugins/dimg/jpeg2000/dimgjpeg2000loader_save.cpp M +6-1core/dplugins/dimg/jpeg2000/dimgjpeg2000plugin.cpp M +13 -12 core/dplugins/dimg/pgf/dimgpgfloader_load.cpp M +9-12 core/dplugins/dimg/pgf/dimgpgfloader_save.cpp M +6-1core/dplugins/dimg/pgf/dimgpgfplugin.cpp M +5-1core/dplugins/dimg/png/dimgpngloader_load.cpp M +5-1core/dplugins/dimg/png/dimgpngloader_save.cpp M +6-1core/dplugins/dimg/png/dimgpngplugin.cpp M +1-1core/dplugins/dimg/tiff/dimgtiffloader_load.cpp M +6-1core/dplugins/dimg/tiff/dimgtiffplugin.cpp https://invent.kde.org/kde/digikam/commit/183933ce5c6e52bb0e4f307d85a0fa041cb84e7b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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/libs/metadataengine/engine/metaengine_comments.cpp M +6-1core/libs/metadataengine/engine/metaengine_exif.cpp M +12 -2core/libs/metadataengine/engine/metaengine_fileio.cpp M +6-1core/libs/metadataengine/engine/metaengine_iptc.cpp M +12 -2core/libs/metadataengine/engine/metaengine_p.cpp M +6-1core/libs/metadataengine/engine/metaengine_previews.cpp M +6-1core/libs/metadataengine/engine/metaengine_xmp.cpp https://invent.kde.org/kde/digikam/commit/f2f35d19fb56e2e5e9a8f398afcec4e93bb4ca2b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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/metadataengine/engine/metaengine_comments.cpp M +1-6core/libs/metadataengine/engine/metaengine_exif.cpp M +2-12 core/libs/metadataengine/engine/metaengine_fileio.cpp M +1-6core/libs/metadataengine/engine/metaengine_iptc.cpp M +2-12 core/libs/metadataengine/engine/metaengine_p.cpp M +1-6core/libs/metadataengine/engine/metaengine_previews.cpp M +1-6core/libs/metadataengine/engine/metaengine_xmp.cpp https://invent.kde.org/kde/digikam/commit/cf8aa4a0a9475b0e9ea35ebeda421303c6a783f0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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/libs/metadataengine/engine/metaengine_comments.cpp M +5-0core/libs/metadataengine/engine/metaengine_exif.cpp M +9-1core/libs/metadataengine/engine/metaengine_fileio.cpp M +5-0core/libs/metadataengine/engine/metaengine_iptc.cpp M +10 -0core/libs/metadataengine/engine/metaengine_p.cpp M +5-0core/libs/metadataengine/engine/metaengine_previews.cpp M +5-0core/libs/metadataengine/engine/metaengine_xmp.cpp https://invent.kde.org/kde/digikam/commit/a28e8c9512c53a2ee68e60446c9e57ef6f988214 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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-2core/libs/metadataengine/engine/metaengine_comments.cpp M +1-2core/libs/metadataengine/engine/metaengine_exif.cpp M +2-2core/libs/metadataengine/engine/metaengine_fileio.cpp M +1-2core/libs/metadataengine/engine/metaengine_iptc.cpp M +4-4core/libs/metadataengine/engine/metaengine_p.cpp M +1-1core/libs/metadataengine/engine/metaengine_previews.cpp M +1-2core/libs/metadataengine/engine/metaengine_xmp.cpp https://invent.kde.org/kde/digikam/commit/cc61ea9abd278960d8a5caaa1bc66d93d074ba90 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
https://bugs.kde.org/show_bug.cgi?id=420195 Tobias changed: What|Removed |Added CC||shntob...@gmail.com --- Comment #20 from Tobias --- Before I report this as another bug, I wanted to check if this is related: SUMMARY Files of any type (not just HEIF) with a non-latin Unicode character in their file name/path will not show their metadata in the metadata side panel or the metadata editor. The "properties" side panel is not affected and continues to show basic data. REPRODUCE 1. Take existing file, verify that metadata is showing up. 2. Rename file or parent folder to include a Unicode character (e.g. "δΈ‰"). 3. After refresh, verify that metadata panel is blank and metadata editor will be "greyed out". OS: Windows 10 1910 Happens in 6.4.0 up to 7.0.0-beta3 (Win64) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
https://bugs.kde.org/show_bug.cgi?id=420195 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Metadata-Engine -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 -- Building PNG support: YES -- XMP metadata support: YES -- Native language support:YES -- Conversion of Windows XP tags: YES -- Nikon lens database:YES -- Building video support: NO -- Building webready support: NO -- Dynamic runtime override: NO -- Unicode paths (wstring):YES -- Building exiv2 command: NO -- Building samples: NO -- Building PO files: NO -- Building unit tests:NO -- Building doc: NO -- Building with coverage flags: NO -- Using ccache: NO -- -- As you can see Unicode paths feature is enabled... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 older release. compile and install this Exiv2 version at all digiKam update for all bundles M +12 -10 project/bundles/3rdparty/ext_exiv2/CMakeLists.txt M +0-1project/bundles/appimage/01-build-host.sh M +1-0project/bundles/appimage/03-build-digikam.sh M +0-1project/bundles/macports/01-build-macports.sh M +1-0project/bundles/macports/03-build-digikam.sh M +0-1project/bundles/mxe/01-build-mxe.sh M +1-0project/bundles/mxe/03-build-digikam.sh https://invent.kde.org/kde/digikam/commit/e0360b3812396769a0ce2fd58124e9dc4feac555 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 digiKam is compiled (aka Lensfun and QtAv). I see the big changes are operated in master (next 0.28) Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
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 files |characters under Windows Component|Plugin-FilesIO-HEIF |general -- You are receiving this mail because: You are watching all bug changes.
