https://bugs.kde.org/show_bug.cgi?id=420715
--- Comment #15 from caulier.gil...@gmail.com --- Hi all, Voilà, now digiKam use libheif to parse HEIF file metadata instead Exiv2. It work like a charm here and image are not decoded to acheive this job. this will populate the database as expected with Exif, Iptc, and Xmp. Of course, HEIF metadata are available as read only for the moment. libheif is not yet able to write metadata without to re-encode whole image file. There is a report about this topic in libheif project. Please ping the developers to look about this feature: https://github.com/strukturag/libheif/issues/127 Other solution is to wait than Exiv2 project support officialy HEIF format. But to be honest, lead coordinator become completely crazy about this topic. I proposed more than time some patches about this feature, all have been banned (closed), and no real code review have been done... This is not how open source collaboration can be done safety for the future. I already write large code for Exiv2 in the pass, i code since more than 35 years now, and i'm an active open-source developer with digiKam since 18 years now : so i know the rules about open source world... To close this topic with Exiv2, i hate to read an amount of troll messages about "possible" patents to parse HEIF data. I said to parse, not to decode/encode X265 streams. Metadata are separated well from compressed data, so it's a safe operation. And in all cases, if a possible patent exist about HEIF parsing, well if we made the HEIF support as optional at configuration time, this will fix definitively the problem at packaging time. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
