[1]: https://scantailor.org/ [2]: https://github.com/scantailor/scantailor [3]: https://github.com/4lex4/scantailor-advanced

The desktop app is only 58mb and uses effectively zero CPU, so it's about as far from bloatware as you can get.

Shoot me an email at joe@breezepdf.com — happy to jump on a call and walk you through it before you get it for your company.

Regarding your concern, if a manipulation of the PDF doesn't meet the standard specification, it won't render properly in a PDF viewer as it is in the present day, let alone in 20 years. All PDF viewers/editors worth their salt adhere to the PDF spec. So as long as the PDF specification stays the same, anything that renders correctly now in a PDF viewer will render correctly in the future.

For something like compression, if the file reduces in size and the PDF renders the same (minus expected potential minor quality loss), then you have evidence right there that it worked successfully.

I built BreezePDF with PDF spec adhering libraries, so everything should be up to standards.

Let me know if that answers your question!

Some features took a longggg time to do, such as table extraction, text editing, and (surprisingly) preserving positioning of elements (text, images etc.) when rotating the page in the downloaded file - PDF specification has a different orientation system than the web, so this was very intricate to get correct.

A lot of PDF editors have tools that all work independently, meaning you have to use each tool separately. My decision to add all the features I did while keeping it in one editor was because I felt that was a better user experience, but I means that all features become intertwined, which added a ton of complexity managing that.

In what scenario was undo not working? If you can provide that context, I can dig into it more as to what wasn't undoing properly.

For text editing, I see the issue with that for some of the fonts. Fixing now

Sorry for the trouble!