Live data from Hacker News

How we made our OCR code more accurate

pieces.app

1–10 of 50 posts

Re: How we made our OCR code more accurate

#4
post #3

Neat article, but I feel like I have no idea why they're doing this! Is transcribing code from images really such a big use case?

Maybe they want to compile the Apollo Guidance Computer source code...

https://www.softwareheritage.org/wp-content/uploads/2019/07/...

Re: How we made our OCR code more accurate

#5
post #3

Neat article, but I feel like I have no idea why they're doing this! Is transcribing code from images really such a big use case?

> To best support software engineers when they want to transcribe code from images, we fine-tuned our pre-processing pipeline to screenshots of code in IDEs, terminals, and online resources like YouTube videos and blog posts.

Even with these examples that seems like a very narrow use case.

Re: How we made our OCR code more accurate

#7
post #3

Neat article, but I feel like I have no idea why they're doing this! Is transcribing code from images really such a big use case?

From an accessibility standpoint, yes. To be able to pattern match where you are in I.D.E without using an accessibility api

Re: How we made our OCR code more accurate

#9
post #6

Anything that mentions tesseract is about 10 years out of date at this point.

5.5.0 released November last year. Still a very active project as far as I can tell and runs on CPU. Even compared to best open source GPU option it is still pretty good. VLMs work very differently and don't work as well for everything. Why is it out of date?
Post reply on HN