The tessdata files I tested, has the following information .:
- swe.traineddata 13.308kB
- eng.traineddata 4.017kB
- Runtime (one row) .: 3.531000 sek.
- Total Runtime (fifteen rows) .: 51.218000 sek.
- swe.traineddata 13.990kB
- Runtime (one row) .: 3.609000 sek.
- Total Runtime (fifteen rows) .: 48.016000 sek.
Not much difference in speed ("best" was a bit faster overall)
You were right, suddenly the first lines started working without problems. (y=749 Instead y=750 - 150dpi)
That I chose the right language (swe) was not a disadvantage either (ÅÄÖ began to be interpreted correctly)
Have also tested using several traineddata, like this .: OCR(imgFile, "swe+eng", [x, y, w, h]) (did not get worse)
Right now I am trying to get the AHK-program to interpret rows 5,6,7 correctly - but fail (the rows after become correct again)
Thought it would be better with an image of 600 dpi, and to some extent it turned out so. But not on these signs.
F. becomes E and 8 becomes 3 and...
These characters are in the middle of the line - everything is correct before and at the end of the line (but not these two...)
Is there any way to see what is in the selected area (x, y, w, h) ?
The document is written with the font Courier (Courier is monospaced ABC KLM ÅÄÖ - Does not appear correctly here)
How is this font selected in the OCR interpretation? (Is it possible?)