Peter S

@paolobenve: > I'd expect a "Setting metadata in BMFF images is not supported" error message. You are correct, the error message is wrong. Currently we are throwing a [kerInvalidSettingForImage](https://github.com/Exiv2/exiv2/blob/d2253c91f59be50d58a387b17f37a38c2d2025f7/include/exiv2/error.hpp#L196) which...

@norbertwg: > I noticed, that the lists of keys in easyaccess.cpp seems to be incomplete. > If Exif.PanasonicRaw was intentionally not included, please let me know. If this is not...

@norbertwg: Sorry for the delay replying. > I have now an overview of potentially missing keys, which can be grouped as follows: I like your cautions approach. While reading your...

@kmilos > Thanks, but I think @hassec idea of redirecting this automatically when Exif.CanonCs.LensType is 61182 is the best way to go instead. Haven't thought about how to implement it...

> I really, really, really, don't want to go down the lens recognition rabbit hole further. > This PR was just about bringing the lists up to date wrt exiftool....

@kmilos Can you request a review from me again, as I am having a problem triggering the process.

@norbertwg As far as I know, there are three places where the EasyAccessAPI is written about. 1. [The project API docs on exiv2.org](https://exiv2.org/doc/namespaceExiv2.html#a00abed868b1cd46fdeb8ab331af246cd]. When the website is updated the text...

@bellaperez Thanks for your suggestion. As a native English speaker, I haven't needed to investigate `.po` files. I don't have time to look at this at the moment but will...

@kevinbackhouse > What's the current status on this? I will try and take a look tomorrow and then update you.

@kevinbackhouse > What's the current status on this? The reason for this PR is that the lens in a user's file was incorrectly reported. The problem is that our knowledge...