I wrote a free PDF editor (open a PDF, edit, export a PDF), my users edit around 500,000 PDF files every month.
I have been gradually improving it for the past five years. It is a part of my photo editor https://www.Photopea.com. I know really a lot about PDF, I wish I didn't know that much :D I am glad to see that there are others who try to "make sense" of PDF files instead of just rendering them :)
** fun fact: Often, a PDF contains text as an array of characters, each has its X and Y coordinate and a style (white characters omitted). It is up to you to "cluster" them into words, lines, paragraphs ...
** Often, PDF text is made uneditable (on purpose). You see a text "Hello", but in fact, there is a text "bsiin", and a font, which renders "b" with a shape that looks like a letter "H", "s" as "e", and so on. If you open that PDF in a PDF viewer, select "Hello" and copy-paste it elsewhere, you get "bsiin".
Photopea is fantastic. I don't use Photoshop enough to justify a cloud subscription and adobe has shut down the licensing service for the version I have on disc (CS3).
I haven't accepted it. I sail harder all the time. The Adobe Creative Suite hasn't been a recent priority, but I should look it up on principal. Thank you.
Photopea also helps when you're at a random computer and can help someone do an edit that would otherwise require access to a computer with software installed.
If so, it's hardly noteworthy. If you've written your own PDF to DOCX converter, then you have an interesting technical story (or ten) to tell -- do tell.
yes, it does indeed use pdf2docx under the hood. From a technical point of view, it doesn't do anything new asides from straddling Python and Electron into one App.
However, from an everyday user point of view, it does make it rather simple to convert pdf to word document. An everyday user won't be up for doing that via cli commands. And every alternative user friendly solution requires uploading your documents to servers (which could spark privacy concerns)
> And every alternative user friendly solution requires uploading your documents to servers (which could spark privacy concerns)
If the customer base is less technically adept, wouldn't most of them not care and just upload it to a cloud service? I ask sincerely - recently I've realized I don't have as firm of a grip on the 'average consumer' as I thought.
I just started testing fixpdfs.com, and some of the first feedback I heard when I asked users about pricing was "I'd rather download an app that does this than pay a subscription"
I would only trust my PDFs to Adobe, Microsoft, AWS, etc: the big players, very well-known, that are not going to use the content of the PDFs against me. And of course I'd rather use something that runs completely on my laptop.
Hmm, I haven't used libpdf to know enough, but just from glance through its documentation, it seems libpdf is more suitable for creating and reading PDF files. If this is correct, then it'll be missing the bridge to converting the read content of the PDF file to a Word document
I see a couple of things called libpdf...lib-pdf and libpdf++. One generates pdfs programmatically. The other parses pdfs, but generates only images. Maybe you meant something else?
I believe they are asking if, after extracting all the pieces (it's shipped as a self-extracting archive), does it do the things it needs to do to comply with GPL/AGPL? Like supplying the source code, or how to get the source code.
Installation essentially - the linked website doesn't link to licensing info for third-party dependencies. I was wondering if the licensing info (and source code of this product) were included in the installation bundle or available from the running product - since this is a requirement of the GPL license used in some of the dependencies.
The Windows app is an unsigned executable - not planning on running it myself.
While there hasn't been any actual deep dive into this on my part yet, as the App does all its bit on the user's machine, the code itself also does live on the user machine post-installation. There has been no additional effort made to obfuscate the code that powers the App.
What could possibly be missing at the moment is a written instruction that documents where to locate the code base on the user's machine post-installation
I know right? You can build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem.
Is this sarcasm? this sounds like the dropbox detractors from when they launched. sure you can do all that but a ton of people want packaged up and easy workflows.
What are the chances? I've just started my live beta of https://fixpdfs.com to convert pdfs of scanned documents/books into better "documents" with OCR, normalized margins, etc. (for better reading, searching, and highlighting)
It was my experience that OCRing scanned PDFs, would result in many small errors. For example “Alt” could be interpreted as “A|t”. Did you had those problems? How did you fixed it? What about other languages?
I didn't build my own OCR models, in the beta I'm using tesseract but I'm going to use google or amazon when I start charging. There's no way to compete on OCR quality but I don't see other products automatically fixing doc scans, which is the value add I see my software really giving...
Is there a possibility we will ever get a redesigned PDF format that removes so much unneeded complexity and make conversions/parsing more straightforward? Or are we stuck with this until the end of time?
Hi, thank you for pointing out the room for improvement on the FAQ. What it attempted to communicate is that the App will indeed stop working after the License expires, so it will have to be renewed at that point
I can see how the "Buy Now" text could be misleading. Tbh, that's just the default text that comes with the Paypal button, and it wasn't deliberated crafted that way to mislead buyers. I'll roll out an update to make it more explicit.
> there don't seem to be any substantive further improvements planned
About that, the truth is, it often starts with a use-case as simple as "convert PDF to Word". Improvements usually would come from user feedback, and continuous maintenance. While I deliberately started out to keep the App simple, there's a good chance that features and functionality would expand when user feedback gets in the mix.
Docx is similarly open as PDF. (And full Adobe Acrobat compatibility is similarly difficult as full Microsoft Word compatibility. PDF has an edge here in practice because most use cases are read-only, or only very limited modification.)
I have been gradually improving it for the past five years. It is a part of my photo editor https://www.Photopea.com. I know really a lot about PDF, I wish I didn't know that much :D I am glad to see that there are others who try to "make sense" of PDF files instead of just rendering them :)
** fun fact: Often, a PDF contains text as an array of characters, each has its X and Y coordinate and a style (white characters omitted). It is up to you to "cluster" them into words, lines, paragraphs ...
** Often, PDF text is made uneditable (on purpose). You see a text "Hello", but in fact, there is a text "bsiin", and a font, which renders "b" with a shape that looks like a letter "H", "s" as "e", and so on. If you open that PDF in a PDF viewer, select "Hello" and copy-paste it elsewhere, you get "bsiin".