nvaccess / nvda-ocr Goto Github PK

For many people using older versions of Windows the OCR add-on is invaluable in day to day work. In some cases the Tesserac engine performs better than the build-in Windows 10 one, so even on Windows 10 add-on has some advantages. What are your plans regarding porting to Python 3? cc @feerrenrut as someone from NV Access and
@jcsteh as an initial author.

The OCR add-on is for many users of Windows versions older than 10 one of the most important plugins for NVDA. It should be updated to provide compatibility with add-on compatibility check introduced in today's snapshot. Furthermore this add-on is developed by NVAcces and they should give an example of conforming to the new requirements.

See NVAccess/NVDA/#2744
Would it be possible to translate NvDA OcR addon for languages other than English?

Use cases:
Set different languages for the add-on, that can be used in different programs or situations.
technical: Manage config from the central system.
Thanks.

Dear NV Access Team,

there are still many users of Windows 7 complaining that the OCR addon does not work anymore, especially when using NVDA 2018.2.

Is there any update in process for this addon?

Comments are appreciated.

I was working with a particularly nasty application that starts with a Team and ends with a Speak, and realized that I can't get past the license agreement page because NVDA is not aware that the bottom part of the screen is part of the same window. There doesn't seem to be a way to OCR the entire screen, just the active window, and particularly when that window consists of a bunch of buttons with no proper parent, it's difficult to define boundaries. I'm probably missing something obvious, but right now I'm stuck, and it occurs to me that this is a problem which could apply to quite a lot of places, so hopefully this is the right place for it.