Suggestion: Upstream is now in git - mirror that here, rather than hosting a fork

[bjmc]

Upstream has adopted git

IMHO it would be cleaner to have this Github repository mirror the upstream than hosting a separate fork based on a source code release.

git clone http://www.wagner.pp.ru/git/oss/catdoc.git

(P.S. upstream has released 0.94 and 0.95 since this repo was created)

[skierpage]

A vbwagner has a GitHub repository at https://github.com/vbwagner/catdoc which when I checked in 2022 was identical to the wagner.pp.ru git repo at the same "38a2807 Wrote make dist target" commit from 9 years ago. Alas "vbwagner" is as inactive and unresponsive on GitHub as they are in the original wagner.pp.ru.

FYI I have a fork of this that incorporates all of the Debian patches to catdoc, a Fedora build patch, several man page fixes, other updates, adds tests and make check support, and build the project and runs tests in a GitHub action on commits and pull requests. In my humble opinion you should be better off forking from my version. In vbwagner's absence I am working with the Debian packager to make it the new upstream. I welcome other patches and especially test files. I just found your repo; I will investigate its issues and pull request. Cheers!

[skierpage]

A vbwagner has a GitHub repository at https://github.com/vbwagner/catdoc ... Alas "vbwagner" is as inactive and unresponsive on GitHub

@vbwagner came back to life and made a couple of fixes (both incorporated in my fork), but hasn't made a new release.

FYI I have a fork

It now fixes all CVEs, memory access errors, and other Address Sanitizer errors that I can find, and has much better PowerPoint 97 handling.

I just found your repo; I will investigate its issues and pull request.

I did, I think they were all fixed in later releases of catdoc by vbwagner or in the v0.97 release of my fork. (Lots of cats to herd 😉)