Kevin Backhouse

I noticed that the XMPsdk is on GitHub now: https://github.com/adobe/XMP-Toolkit-SDK So maybe we can include it as a sub-module.

Another option would be to include [XMP-Toolkit-SDK](https://github.com/adobe/XMP-Toolkit-SDK) as a submodule. I wish they were more responsive to feedback though. I sent them a [pull request](https://github.com/adobe/XMP-Toolkit-SDK/pull/49) months ago to fix a...

Sorry, I think you'll have to build from source.You can find prebuilt binaries [here](https://github.com/Exiv2/exiv2/releases/tag/v0.27.5) and [here](https://exiv2.org/download.html) but 32-bit Windows is not on the list.

Thanks @postscript-dev! Good catch on the copyright and bugs address. I have created https://github.com/cjwatson/exiv2/pull/1 to replace those with something more generic.

We updated the copyright and contact details in #1907.

@postscript-dev: I couldn't find a way to update the copyright statement by changing the arguments to `xgettext`, so I just edited the file manually. I don't know about the `.po`...

@postscript-dev: in this situation, I would create a temporary clone of the repo so that I can do potentially destructive things like `git reset`. If something goes wrong then I...

I don't have a strong opinion on this.

My opinion is that we should stop building binaries for MinGW and Cygwin after 0.27.5. We have an [Action](../blob/main/.github/workflows/release.yml) which automatically builds binaries for Linux, MacOS, and Windows. Those are...

My suggestion is to create a few new repositories in the [Exiv2 organization](https://github.com/Exiv2). For example, the svn repository can probably be converted to git and pushed to a new repo...