https://bugs.kde.org/show_bug.cgi?id=425884
--- Comment #3 from Nicofo <nic...@tuxfamily.org> --- Useful information: (In reply to Nicofo from comment #0) > Note: GPSProcessingMethod and GPSAreaInformation are both encoded in the > same way as EXIF UserComment. (see details > https://github.com/Exiv2/exiv2/issues/1046#issuecomment-599540926 ) I check the UserComment tag: it is correctly handled by Digikam (meaning Digikam removes the "charset=Ascii" before the UserCommment). As far as I understand digikam code, this is realised: - in metaengine_exif.cpp ==> function getExifComment ==> call to convertCommentValue - in metaengine_p.cpp ==> function convertCommentValue ==> reads the charset and consequently decode the UserComment: // libexiv2 will prepend "charset=\"SomeCharset\" " if charset is specified // Before conversion to QString, we must know the charset, so we stay with std::string for a while if (comment.length() > 8 && comment.substr(0, 8) == "charset=") { ... GPSProcessingMethod and GPSAreaInformation are both encoded in the same way as EXIF UserComment. CONCLUSION: you should also use the function convertCommentValue to these Exif tags. -- You are receiving this mail because: You are watching all bug changes.
