3 ms·
Why use Tesseract for this? Windows' built-in OCR is so much better in my experience.
by criddell 1y ago
Why use Tesseract for this? Windows' built-in OCR is so much better in my experience.
- Oras 1y agoYeah, tesseract has lots of issues especially identifying tables
- skeeter2020 1y agoI suspect because of the vintage of this project. This is built on .net Framework 4.x, hence windows only. edit: and goes deep into COM for device interfaces. Wow! blast from the past.
- wolfi1 1y ago.Net Framework is mostly a wrapper for COM
- PeterStuer 1y agoThat's a bit of a streach. Yes, .Net was MS's next gen of component tech following (D)COM, but it grew way past that from the start.
- jeroenhd 1y agoMicrosoft's OCR engine supports Windows 10.0.10240.0 and up. This project intends to support Windows 7 and up. In theory you could maintain code paths for both, offering a slimmer package for Windows 10+, but that'd also cost more time and effort to maintain. Also, not many people know Windows comes with an OCR API. It's extremely underused in my opinion.
- atmanactive 1y agoWindows OCR is used by PowerToys. https://github.com/microsoft/PowerToys https://github.com/microsoft/PowerToys