Hello,
On Thu 20 Jun 2019 at 08:34AM +02, Johannes Schauer wrote:
> We have a similar issue but a less severe one because this is only one package
> and not a whole ecosystem of them. Since the required tooling is currently
> missing, I guess any maintainer of PyMuPDF would need to closely follow
Hello,
On Wed 19 Jun 2019 at 11:42PM -07, James R Barlow wrote:
> I should mention that ocrmypdf no longer has an immediate use for PyMuPDF -
> I went the route of creating pikepdf, Python bindings for qpdf, and this is
> library is now in Debian thanks to Sean's work on packaging it. I don't
> t
Hi Sean,
Quoting Sean Whitton (2019-06-20 07:28:12)
> [updating CC to point to the newly-filed RFP]
thank you!
> Thank you again for looking into this.
Incidentally I'm currently writing a tool that needs PyMuPDF so I'll probably
spend a bit more time on this. ;)
> On Sat 08 Jun 2019 at 09:52p
I should mention that ocrmypdf no longer has an immediate use for PyMuPDF -
I went the route of creating pikepdf, Python bindings for qpdf, and this is
library is now in Debian thanks to Sean's work on packaging it. I don't
think I would use PyMuPDF if it were available. pikepdf overlaps the core
o
[updating CC to point to the newly-filed RFP]
Hello Johannes,
Thank you again for looking into this.
On Sat 08 Jun 2019 at 09:52pm +0200, Johannes Schauer wrote:
> after my struggles in #930212 I now figured out how to compile stuff against
> the static library in libmupdf-dev. As a result I ma
5 matches
Mail list logo
