Thread: OCR after scan update
View Single Post
Old 12-03-2021, 12:20 PM   #6
j.p.s
Grand Sorcerer
j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.j.p.s ought to be getting tired of karma fortunes by now.
 
Posts: 5,806
Karma: 103362673
Join Date: Apr 2011
Device: pb360
Quote:
Originally Posted by RbnJrg View Post
Many thanks. Yes, I was aware about that list, that mainly is regarding Tesseact 4.0 GUI. For example, gImageReader works for Tesseract 5.0 but it takes a lot of time to OCR a few pages (when the main advantage for Tesseract 5 over Tesseract 4 is -or should be- the speed).
It looks like gImageReader has a history of slowing down after Tesseact major version changes. Seems to be related to CPU vectorizing support and Tesseact compile options.

https://github.com/manisandro/gImageReader/issues/285

There is a pending pull request that supposedly fixes the above, but it looks like it won't be merged.

https://github.com/manisandro/gImageReader/pull/286

The below links to how to build Tesseract by the gImageReader author, but the links are dead.

https://github.com/manisandro/gImageReader/issues/357

This is all very strange since people having the problem say Tesseact from the command line is not slow and the gImageReader author says it's not a gImageReader problem. This is all T V3 _> T V4.
j.p.s is offline   Reply With Quote