New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NVDA with OCR #1791
Comments
Comment 1 by kevinchao89 on 2011-11-11 10:18 |
Comment 2 by lpintes on 2011-11-11 12:03 Is Tesseract really so bad? Or screen images are of low quality? Or can this be system dependent? However if you have any idea about what to change and test, let me know. I am very interested in this. |
Comment 3 by jteh on 2011-11-11 13:16 It sometimes does produce very good results. Even when it doesn't, the text doesn't have to be entirely readable to make this plugin useful. Sometimes, it's enough to give you the general idea of what's on the screen. Even when it's complete rubbish, the important thing is that there are now characters you can click on, which might help you click something you need with some trial and error. |
Comment 4 by vortex on 2011-11-12 01:05 |
Comment 5 by jteh on 2011-11-12 01:36 |
Comment 6 by vortex on 2011-11-13 00:44 |
Comment 7 by pvagner on 2011-11-15 10:08 |
Comment 8 by jteh on 2011-11-15 10:35 |
Comment 9 by pvagner (in reply to comment 8) on 2011-11-16 14:51
Okay thanks for the tip updating my python installation helped. Replying to vortex:
I've done some initial test with this build you've linked and eventhough cuneiform is reported to be able to handle smaller images for best results it's still good to double the size of an image. Onething I am wondering about and haven't checket whether is doable yet is whether it won't be better to convert to gray scale instead of black. |
Comment 10 by vortex on 2011-11-16 19:30 |
Comment 11 by jteh (in reply to comment 9) on 2011-11-16 20:53
It should already be grayscale unless I'm misinterpreting the docs. I originally used monochrome, but changed it to grayscale later due to what I felt were better results. However, this needs further testing. |
Comment 12 by lpintes on 2011-11-18 18:39
What this error means? |
Comment 13 by barichd on 2011-11-21 19:13 [http://dl.dropbox.com/u/48550043/init.py] |
Comment 14 by jteh (in reply to comment 13) on 2011-11-21 21:04
I really don't follow why this change is necessary. Very strange. It's not just XP, as it works fine on other XP machines. Are you using a language other than English? |
Comment 15 by ateu on 2011-12-03 10:24 Forgive me if it's not a good idea. What do you think microsoft office document scanning? If microsoft already contributed with NV Access, is it not possible they alows NVDA uses its OCR? It's only a suggestion. |
Comment 16 by jteh on 2012-10-15 04:13 |
Reported by KevanGC on 2011-09-15 03:20
This suggestion is fairly simple. I don't think you'll be able to integrate OCR into NVDA soon, I'm not even sure if you've started working on it.
However I think we all would benefit from this. JAWS 13 now has it, and I don't feel it's worth the $1000 to purchase JFW just for OCR.
The text was updated successfully, but these errors were encountered: