Isn't a browser for interfacing to http?
Show HN: Free, in-browser PDF editor
31–40 of 188 posts
Re: Show HN: Free, in-browser PDF editor
#32Why would you want functionality like this to be in a browser? Isn't a browser for interfacing to http?
Re: Show HN: Free, in-browser PDF editor
#33Nice! Recently I had the need for pdf censoring, aka not adding black rectangles but actually removing the content underneath and I still haven't found a suitable tool. Any recommendation? Or even python library to do it?
Re: Show HN: Free, in-browser PDF editor
#34Nice! Recently I had the need for pdf censoring, aka not adding black rectangles but actually removing the content underneath and I still haven't found a suitable tool. Any recommendation? Or even python library to do it?
Re: Show HN: Free, in-browser PDF editor
#35Nice! Recently I had the need for pdf censoring, aka not adding black rectangles but actually removing the content underneath and I still haven't found a suitable tool. Any recommendation? Or even python library to do it?
Re: Show HN: Free, in-browser PDF editor
#36Nice work. I've been building something lately to manipulate PDFs in the browser for privacy, although it's quite a different use case. I think I see you're using pdf-lib and jspdf - both great libraries, and I'm using both, but: (1) Have you seen the recent WASM compilation of MuPDF? I am also using it for some functions and find it really excellent with accessible APIs and highly functional. Worth an try! (2) We ch…
Since a lot of the basic functionality I've added so far is also covered by more permissible packages like the ones you mentioned, I've started out just using those. But thanks for bringing that up, I'll revisit using MuPDF for redaction and other features
(2) I went with pdf-lib-plus-encrypt because the original pdf-lib doesn't have functionality for password-protecting PDFs, and since pdf-lib-plus-encrypt does, I used it so I could have that feature
Re: Show HN: Free, in-browser PDF editor
#37When downloading the PDF, the text block is not wrapped, so it doesn't match the way it looks in the editor. Tested in Firefox (but it's the same in Chromium).
Nice work on the interface and the offline & local way it works is very welcome!