1. nvda@nvda.groups.io
  2. Messages
   Date   
Re: Reading WEB Pages

Gene
 

That is not intended for screen-reader users.  It is a way to allow sighted users to have a virtual cursor on the web page.

Gene

On 7/13/2022 1:40 PM, Carlos wrote:

Which browser are you using? Most browsers in their settings will have a check box to toggle using arrow key nav.
Always remember to include name(s) of browsers when asking these types of questions.

On 7/13/2022 11:30 AM, Steven Hicks wrote:

Hi all,

 

new install of Microsoft Windows 10 and NvDA.

When I open a web page, I cannot move around to read it with the arrow keys, it only responds to the tab key, any ideas why please?

 

Many thanks in anticipation,

 
Re: Reading WEB Pages

Ben J. Bloomgren
 

Also make sure that you're in browse mode with NVDA+Spacebar.

Ben

On Jul 13, 2022, at 11:40, Carlos <gmjc341961@...> wrote:

 Which browser are you using? Most browsers in their settings will have a check box to toggle using arrow key nav.
Always remember to include name(s) of browsers when asking these types of questions.

On 7/13/2022 11:30 AM, Steven Hicks wrote:

Hi all,

 

new install of Microsoft Windows 10 and NvDA.

When I open a web page, I cannot move around to read it with the arrow keys, it only responds to the tab key, any ideas why please?

 

Many thanks in anticipation,

 
Re: Reading WEB Pages

Carlos
 

Which browser are you using? Most browsers in their settings will have a check box to toggle using arrow key nav.
Always remember to include name(s) of browsers when asking these types of questions.

On 7/13/2022 11:30 AM, Steven Hicks wrote:

Hi all,

 

new install of Microsoft Windows 10 and NvDA.

When I open a web page, I cannot move around to read it with the arrow keys, it only responds to the tab key, any ideas why please?

 

Many thanks in anticipation,

 
Re: Reading WEB Pages

Gene
 

Try the command NVDA key space.  See if you can move then.  If you can, change a setting in browse mode settings.
Open the browse mode dialog with control NVDA key b.
Tab to enable browse mode on page load or very similar wording.
If it isn't checked, check it with the space bar.
Press enter. 
If that setting is the problem, it should be solved.

Gene

On 7/13/2022 1:30 PM, Steven Hicks wrote:

Hi all,

 

new install of Microsoft Windows 10 and NvDA.

When I open a web page, I cannot move around to read it with the arrow keys, it only responds to the tab key, any ideas why please?

 

Many thanks in anticipation,

 
Reading WEB Pages

Steven Hicks
 

Hi all,

 

new install of Microsoft Windows 10 and NvDA.

When I open a web page, I cannot move around to read it with the arrow keys, it only responds to the tab key, any ideas why please?

 

Many thanks in anticipation,

 
Re: New version of TesseractOCR add-on

Rui Fontes
 

Please, send it directly to me:

rui.fontes@...


Rui Fontes


Às 18:25 de 13/07/2022, farhan israk escreveu:

How can I send a log here?
Re: NVDA 2022.2 RC 1 now available

Rosemarie Chavarria
 

Hi, Quentin,

 

I just downloaded this new release candidate and so-far it’s working great. Thanks so much for all that you and the other NVDA developers do for us.

 

Rosemarie

 

 

 

Sent from Mail for Windows

 

From: Quentin Christensen
Sent: Wednesday, July 13, 2022 1:05 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA 2022.2 RC 1 now available

 

Hi everyone,

 

NVDA 2022.2 RC1 is now available!  As a release candidate build, this is the final step before the stable build.  We encourage ALL users to please download and test this.  If any issues are identified, it is easier to address them now before the stable version comes out.

NVDA 2022.2 includes many bug fixes. Notably, there are significant improvements for Java based applications, braille displays and Windows features.

New table navigation commands have been introduced. Unicode CLDR has been updated. LibLouis has been updated, which includes a new German braille table.

 

Read more and download the RC from https://www.nvaccess.org/post/nvda-2022-2rc1/

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 

 
Re: New version of TesseractOCR add-on

farhan israk
 

How can I send a log here?
Re: New version of TesseractOCR add-on

Rui Fontes
 

Here is the documentation:


TesseractOCR
• Authors: Rui Fontes rui.fontes@... and Angelo Abrantes ampa4374@...
• Updated in 13/07/2022
• Download stable version
• Compatibility: NVDA version 2019.3 and beyond
Informations
This add-on uses the free and open source Tesseract OCR engine, to perform optical character recognition on an image file, PDF, JPG, TIF or other, without the need to open it. It also uses wia-cmd-scanner to be able to access WIA enabled scanners and perform OCR to a paper document. In the NVDA menu, Preferences, a TesseractOCR section is added, where you can configure the languages to be used in recognition and the type of documents to be recognized. With the exception of English and Portuguese, which are already included in add-on, the other languages will be downloaded and installed when you select a language that does not already exist in the add-on. Note that as the number of selected recognition languages increases, the OCR process will take longer. We therefore recommend that you use only the languages you need. Note also that the quality of recognition may vary according to the order of languages. Therefore, if the recognition result is not satisfactory, you may want to try another language ordering.
Shortcut
The default commands are: Windows+Control+r - to recognize the selected document; Windows+Control+w - to scan and recognize a document through the scanner.
Then just wait that ocr.txt opens with the recognized text. If you want to preserve the recognized text, don't forget to save the document under another name and in another location, as all files in the temporary directory are deleted at the start of the next OCR process!
This commands can be modified in the "Input gestures" dialog in the "TesseractOCR" section.
Automatic update
This add-on includes an automatic update feature. The check for a new version will be executed everytime NVDA is loaded. If you want this, go to NVDA, Preferences, Options and in the add-on category check the check box.
Known problems
• In some systems it is possible that add-on do not work due to a comtypes error... In some machines it is enough going to the temp folder, and deleting the comtypes_cache folder.
• When selecting the "Various" option in the "Documents type" combobox, the recognized text probably appear with many blank lines This is a known problem with Tesseract, and, without consumming lots of processing time, I haven't yet found any solution. But, I still haven't given up!
Languages supported
The supported languages in this version are: Afrikans Albanian Amharik Arabic Armenian Assamese Azerbaijani (Latin) Basque Belarusian Bengali Bosnian Breton Bulgarian Burnese Catalan/Valencian Cebuano Cherokee Chinese simplified Chinese traditional Corsican Croatian Czech Dannish Deutch Dhivehi Dutch (Flemish) Dzongkha English Esperanto Estonian Faroese Filipino Finnish French Galician Georgian Greek Gujarati Haitian Hebrew Hindi Hungarian Icelandic Indonesian Inuktitut Irish Italian Javanese Japanese Kannada Kazakh Khmer (Central) Kirghiz Korean Kurdish Kurmanji Lao Latin Lativia Lituanian Luxembourgish Macedonian Malay Malayalam Maltese Maori Marathi Math / equation detection module Mongolian Nepali Norwegian Occitan Oriya Panjabi Pashto Persian Polish Portuguese Quechua Romanian/Moldave Russian Sanskrit Scottish Gaelic Serbian (Latin) Slovak) Slovenian) Sindhi Sinhalese Spanish Sundanese Swahili Swedish Syriac Tajik Tamil Tatar Telugu Thai Tibetan Tigrinya Tonga Turkish Uighur Ukrainian Urdu Uzbek (Latin) Vietnamese Welsh West Frisian Yiddish Yoruba
Image types supported
This add-on supports the following types of files: PDF jpg tif png bmp pnm pbm pgm jp2 gif jfif jpeg tiff spix webp


Best regards,

Rui Fontes
NVDA portuguese team


Às 15:09 de 13/07/2022, Anthony tom escreveu:

How is it used?

Re: Error installing NVDA 2022.2rc1

Joseph Lee
 

Hi,

Sometimes, logging out and back in resolves this, as this error can indicate that NVDA installer could not locate the new NVDA version to start for osme reason.

Cheers,

Joseph
Re: New version of TesseractOCR add-on

Anthony tom
 

How is it used?
Re: Screen Refresh

Gene
 

I was talking about a web page opening, as in downloading a web page.  You are evidently talking about downloading a file.  I haven't seen any information about whether Edge can resume downloads.

Gene

On 7/13/2022 8:48 AM, tim wrote:

Now with edge I have restarted some downloads.

You have to use control + j and arrow down to the download.

Now hit application or shift + f10 and arrow down to resume if it shows. That depends on the sites coding.


On 7/12/2022 11:15 AM, Gene wrote:
If you lose connection with the Internet, no page that has finished downloading to the browser is lost.  When you open a web page, it is downloaded to the browser and it stays there, whether you are online or not, until you close the tab or window containing the page in the browser itself.

If you are downloading something and you lose contact with the Internet briefly or very briefly, I'm not sure if the download stops or resumes, though I think it stops.

This has nothing to do with the speed of the Internet, it depends on what happens when contact with a site or the Internet is interrupted.

Gene

On 7/12/2022 10:06 AM, Dave Grossoehme wrote:

Hi Joseph:  Don

't forget about the speed of the web here.  What's going to happen with all these actions, if the internet skips a beat, and goes out for a part of a second but not long enough for the computer to loose all the pages that are open with a multipage document open as well as other documents. 

Dave


On 7/10/2022 11:41 AM, Joseph Lee wrote:

[Edited Message Follows]

Hi,

Here's why:

Suppose a screen reader went great lengths to obtain content for whatever page you are browsing. Now suppose that, somehow, the screen reader forgets what it was looking at when you switch screens (windows/apps). If the screen reader switches back to the web browser you were using, it doesn't remember what the page "looked" like, so it goes great lengths again to obtain document content.

Now suppose that you are browsing multiple websites, perhaps using tabs to do so. Because the screen reader does not remember content you were looking at whenever screens (or tabs) are changed, the screen reader must figure out where it is, whatever it is looking at, and ask the web browser for browse mode content. Suppose this happens so quickly that you notice the screen reader is slow to respond, and a bug is filed about it.

The task performed by a screen reader to obtain browse mode content is, as a Mozilla engineer put it, "swallowing the document". That is, in order for NVDA to obtain information from a web document and convert it into a suitable representation, it needs to ask the web browser for raw document content. This takes time depending on how responsive the web browser is to requests from other apps (including NVDA) and the length of the document. It goes something like this:

  1. User (to web browser): I want to browse to a particular website.
  2. Browser (to user, after a pause): okay, here is the document you have requested.
  3. NVDA (to web browser): but wait, the user is blind, so I need a way to present the document in a suitable way.
  4. Web browser (to NVDA): what do you want me to do for you?
  5. NVDA (to web browser): I'm going to send a messenger (no joke), and you are supposed to send the raw document (complete with HTML and other code) to them.
  6. Web browser (depending on the browser the user is using): okay, I will wait for you (old browser)/hey, I gave you all the tools you need (accessibility API's for instance), so why are you asking me to give you raw content (new browser)?
  7. NVDA messenger (to web browser): here I am, give me the raw document content please.
  8. Web browser (to NVDA messenger, after gathering the raw document content in a suitable form): here it is.
  9. NVDA messenger (to NVDA): okay, I did what you've asked.
  10. NVDA (to NVDA messenger): well done, I will tell my user about it.
  11. NVDA (to user): Loading document...
  12. NVDA (to user, after the document is formatted): here it is (then starts reading from the top if the user says so).
  13. NVDA (to self): phew, that was a long trip. I don't want to go through this again. Wait, I have a notebook which I can use to jot down document content.

The bottlenecks are the messenger and subsequent document formatting steps.

Technical: the "messenger" in this interaction is a piece of NVDA called Remote Helper, a DLL called upon to inject itself into other processes (programs) for various tasks. An important task this DLL does is ask web browsers for raw document content, which is then passed onto NVDA so it can convert it into a browse mode representation. Newer web browsers are concerned about code injection, so they do their best to provide the web document in a documented way, and one such effort is IAccessible2. In theory, using an API to access web document should eliminate the need for document refreshing (NVDA+F5 in browse mode) whenever content changes, which is different than screen refreshing in JAWS (JAWS key+Escape).

Hope this answers a lot of questions.

Cheers,

Joseph
Error installing NVDA 2022.2rc1

Roberto Perez
 

Hi community. I just updated my installed copy of NVDA 2022.1 with the release candidate of 20222.2. The installation went well, except for the fact that the portable copy that runs while NVDA is installing could not be terminated, therefore the newly installed copy could not start automatically. I got the following error message: “Error  dialog  usage: nvda.exe [-h] [-q] [-k] [-f LOGFILENAME]

                [-l {10,12,15,20,30,40,50,100}] [-c CONFIGPATH]

                [--lang LANGUAGE] [-m] [-s] [--disable-addons]

                [--debug-logging] [--no-logging] [--no-sr-flag]

                [--install | --install-silent | --create-portable | --create-portable-silent]

                [--portable-path PORTABLEPATH] [--launcher]

                [--enable-start-on-logon True|False] [--copy-portable-config]

                [--ease-of-access]

 

error: Couldn't terminate existing NVDA process, abandoning start:

Exception: [WinError 5] Access is denied.”.

Windows specifications: “Edition             Windows 11 Pro

Version 21H2

OS build             22000.739

Experience         Windows Feature Experience Pack 1000.22000.739.0”

Should I open a GitHub issue?

 

Thanks.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of tim
Sent: Wednesday, July 13, 2022 9:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Screen Refresh

 

Now with edge I have restarted some downloads.

You have to use control + j and arrow down to the download.

Now hit application or shift + f10 and arrow down to resume if it shows. That depends on the sites coding.

 

On 7/12/2022 11:15 AM, Gene wrote:

If you lose connection with the Internet, no page that has finished downloading to the browser is lost.  When you open a web page, it is downloaded to the browser and it stays there, whether you are online or not, until you close the tab or window containing the page in the browser itself.

If you are downloading something and you lose contact with the Internet briefly or very briefly, I'm not sure if the download stops or resumes, though I think it stops.

This has nothing to do with the speed of the Internet, it depends on what happens when contact with a site or the Internet is interrupted.

Gene

On 7/12/2022 10:06 AM, Dave Grossoehme wrote:

Hi Joseph:  Don

't forget about the speed of the web here.  What's going to happen with all these actions, if the internet skips a beat, and goes out for a part of a second but not long enough for the computer to loose all the pages that are open with a multipage document open as well as other documents. 

Dave

 

On 7/10/2022 11:41 AM, Joseph Lee wrote:

[Edited Message Follows]

Hi,

Here's why:

Suppose a screen reader went great lengths to obtain content for whatever page you are browsing. Now suppose that, somehow, the screen reader forgets what it was looking at when you switch screens (windows/apps). If the screen reader switches back to the web browser you were using, it doesn't remember what the page "looked" like, so it goes great lengths again to obtain document content.

Now suppose that you are browsing multiple websites, perhaps using tabs to do so. Because the screen reader does not remember content you were looking at whenever screens (or tabs) are changed, the screen reader must figure out where it is, whatever it is looking at, and ask the web browser for browse mode content. Suppose this happens so quickly that you notice the screen reader is slow to respond, and a bug is filed about it.

The task performed by a screen reader to obtain browse mode content is, as a Mozilla engineer put it, "swallowing the document". That is, in order for NVDA to obtain information from a web document and convert it into a suitable representation, it needs to ask the web browser for raw document content. This takes time depending on how responsive the web browser is to requests from other apps (including NVDA) and the length of the document. It goes something like this:

  1. User (to web browser): I want to browse to a particular website.
  2. Browser (to user, after a pause): okay, here is the document you have requested.
  3. NVDA (to web browser): but wait, the user is blind, so I need a way to present the document in a suitable way.
  4. Web browser (to NVDA): what do you want me to do for you?
  5. NVDA (to web browser): I'm going to send a messenger (no joke), and you are supposed to send the raw document (complete with HTML and other code) to them.
  6. Web browser (depending on the browser the user is using): okay, I will wait for you (old browser)/hey, I gave you all the tools you need (accessibility API's for instance), so why are you asking me to give you raw content (new browser)?
  7. NVDA messenger (to web browser): here I am, give me the raw document content please.
  8. Web browser (to NVDA messenger, after gathering the raw document content in a suitable form): here it is.
  9. NVDA messenger (to NVDA): okay, I did what you've asked.
  10. NVDA (to NVDA messenger): well done, I will tell my user about it.
  11. NVDA (to user): Loading document...
  12. NVDA (to user, after the document is formatted): here it is (then starts reading from the top if the user says so).
  13. NVDA (to self): phew, that was a long trip. I don't want to go through this again. Wait, I have a notebook which I can use to jot down document content.

The bottlenecks are the messenger and subsequent document formatting steps.

Technical: the "messenger" in this interaction is a piece of NVDA called Remote Helper, a DLL called upon to inject itself into other processes (programs) for various tasks. An important task this DLL does is ask web browsers for raw document content, which is then passed onto NVDA so it can convert it into a browse mode representation. Newer web browsers are concerned about code injection, so they do their best to provide the web document in a documented way, and one such effort is IAccessible2. In theory, using an API to access web document should eliminate the need for document refreshing (NVDA+F5 in browse mode) whenever content changes, which is different than screen refreshing in JAWS (JAWS key+Escape).

Hope this answers a lot of questions.

Cheers,

Joseph

 
Re: Screen Refresh

tim
 

Now its only with edge not sure if it will effect other browsers.

You can tell the web page to refresh every time you open the page .

You will find that setting in control, internet options.

Just tab down to settings. With it set to every time I don't have any problem with pages in edge.


On 7/12/2022 12:37 PM, Dave Grossoehme wrote:

Hi:  No it isn't just in the one application.  As Joseph explained in his message within the last 24 hours, it's in the communication of the browser and the screen reader and the API that are making the communications between the web site and the browser and the screen reader.  As Bryan said in an earlier message it also depends on the language used for the web page as to whether it will refresh or not. 

Dave


On 7/12/2022 12:32 PM, Gene wrote:
I've seen many times in JAWS when the buffer does not refresh when the screen refreshes and you see old information.  I have to use the screen refresh command in JAWS, JAWS key escape, when that occurs.  At times, such as when filling out a form, if I refreshed the page, I would lose information I entered.  If this ever happens in NVDA, I have seldom, if ever seen it happen but it appears that NVDA key f5 does the same thing as the JAWS command, refreshes the buffer browse mode uses.

This is a proper function of a screen-reader because the problem is in the screen-reader and it is not desirable to refresh the actual page.

Gene

On 7/12/2022 10:46 AM, Brian Vogel wrote:
Dave,

No problem.   I'm still at a bit of a loss to even understand what all the hubbub is about.  This sort of thing does happen, if not constantly, then at least often enough that we all encounter it.

I've never seen an instance where using the browser's own reload current page button doesn't get things right back to where they need to be (whether a screen reader is part of the mix or not).  That's why that function exists in every browser I've ever used.  It's not a screen reader function, per se, nor should it be.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill
Re: Screen Refresh

tim
 

The f5 key is a browser key to refresh the page not a screen reader key they have other keys to refresh the buffer.

The only problem you may get with refreashing is with forms. The page will tell you it needs to resend info and give choices.


On 7/12/2022 12:32 PM, Gene wrote:

I've seen many times in JAWS when the buffer does not refresh when the screen refreshes and you see old information.  I have to use the screen refresh command in JAWS, JAWS key escape, when that occurs.  At times, such as when filling out a form, if I refreshed the page, I would lose information I entered.  If this ever happens in NVDA, I have seldom, if ever seen it happen but it appears that NVDA key f5 does the same thing as the JAWS command, refreshes the buffer browse mode uses.

This is a proper function of a screen-reader because the problem is in the screen-reader and it is not desirable to refresh the actual page.

Gene

On 7/12/2022 10:46 AM, Brian Vogel wrote:
Dave,

No problem.   I'm still at a bit of a loss to even understand what all the hubbub is about.  This sort of thing does happen, if not constantly, then at least often enough that we all encounter it.

I've never seen an instance where using the browser's own reload current page button doesn't get things right back to where they need to be (whether a screen reader is part of the mix or not).  That's why that function exists in every browser I've ever used.  It's not a screen reader function, per se, nor should it be.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill
Re: Screen Refresh

tim
 

That is why I like that f5 key.

I have even went to sleep for days with many web pages open, and when woke up. i just hit f5 and everything is update with changes. I only lost pages from getting to wild with control + w and end up with it all closed


On 7/12/2022 11:46 AM, Brian Vogel wrote:

Dave,

No problem.   I'm still at a bit of a loss to even understand what all the hubbub is about.  This sort of thing does happen, if not constantly, then at least often enough that we all encounter it.

I've never seen an instance where using the browser's own reload current page button doesn't get things right back to where they need to be (whether a screen reader is part of the mix or not).  That's why that function exists in every browser I've ever used.  It's not a screen reader function, per se, nor should it be.
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill
Re: Screen Refresh

tim
 

Now with edge I have restarted some downloads.

You have to use control + j and arrow down to the download.

Now hit application or shift + f10 and arrow down to resume if it shows. That depends on the sites coding.


On 7/12/2022 11:15 AM, Gene wrote:

If you lose connection with the Internet, no page that has finished downloading to the browser is lost.  When you open a web page, it is downloaded to the browser and it stays there, whether you are online or not, until you close the tab or window containing the page in the browser itself.

If you are downloading something and you lose contact with the Internet briefly or very briefly, I'm not sure if the download stops or resumes, though I think it stops.

This has nothing to do with the speed of the Internet, it depends on what happens when contact with a site or the Internet is interrupted.

Gene

On 7/12/2022 10:06 AM, Dave Grossoehme wrote:

Hi Joseph:  Don

't forget about the speed of the web here.  What's going to happen with all these actions, if the internet skips a beat, and goes out for a part of a second but not long enough for the computer to loose all the pages that are open with a multipage document open as well as other documents. 

Dave


On 7/10/2022 11:41 AM, Joseph Lee wrote:

[Edited Message Follows]

Hi,

Here's why:

Suppose a screen reader went great lengths to obtain content for whatever page you are browsing. Now suppose that, somehow, the screen reader forgets what it was looking at when you switch screens (windows/apps). If the screen reader switches back to the web browser you were using, it doesn't remember what the page "looked" like, so it goes great lengths again to obtain document content.

Now suppose that you are browsing multiple websites, perhaps using tabs to do so. Because the screen reader does not remember content you were looking at whenever screens (or tabs) are changed, the screen reader must figure out where it is, whatever it is looking at, and ask the web browser for browse mode content. Suppose this happens so quickly that you notice the screen reader is slow to respond, and a bug is filed about it.

The task performed by a screen reader to obtain browse mode content is, as a Mozilla engineer put it, "swallowing the document". That is, in order for NVDA to obtain information from a web document and convert it into a suitable representation, it needs to ask the web browser for raw document content. This takes time depending on how responsive the web browser is to requests from other apps (including NVDA) and the length of the document. It goes something like this:

  1. User (to web browser): I want to browse to a particular website.
  2. Browser (to user, after a pause): okay, here is the document you have requested.
  3. NVDA (to web browser): but wait, the user is blind, so I need a way to present the document in a suitable way.
  4. Web browser (to NVDA): what do you want me to do for you?
  5. NVDA (to web browser): I'm going to send a messenger (no joke), and you are supposed to send the raw document (complete with HTML and other code) to them.
  6. Web browser (depending on the browser the user is using): okay, I will wait for you (old browser)/hey, I gave you all the tools you need (accessibility API's for instance), so why are you asking me to give you raw content (new browser)?
  7. NVDA messenger (to web browser): here I am, give me the raw document content please.
  8. Web browser (to NVDA messenger, after gathering the raw document content in a suitable form): here it is.
  9. NVDA messenger (to NVDA): okay, I did what you've asked.
  10. NVDA (to NVDA messenger): well done, I will tell my user about it.
  11. NVDA (to user): Loading document...
  12. NVDA (to user, after the document is formatted): here it is (then starts reading from the top if the user says so).
  13. NVDA (to self): phew, that was a long trip. I don't want to go through this again. Wait, I have a notebook which I can use to jot down document content.

The bottlenecks are the messenger and subsequent document formatting steps.

Technical: the "messenger" in this interaction is a piece of NVDA called Remote Helper, a DLL called upon to inject itself into other processes (programs) for various tasks. An important task this DLL does is ask web browsers for raw document content, which is then passed onto NVDA so it can convert it into a browse mode representation. Newer web browsers are concerned about code injection, so they do their best to provide the web document in a documented way, and one such effort is IAccessible2. In theory, using an API to access web document should eliminate the need for document refreshing (NVDA+F5 in browse mode) whenever content changes, which is different than screen refreshing in JAWS (JAWS key+Escape).

Hope this answers a lot of questions.

Cheers,

Joseph
Re: New version of TesseractOCR add-on

Rui Fontes
 

Hello again!


The update process should run in a separate thread...


I am going to test...


Best regards,

Rui Fontes
NVDA portuguese team


Às 03:03 de 13/07/2022, nvdainth@... escreveu:

Hi Rui
I can update your add-on
but I think you must improve some code for update section.
When update this add-on progress the NVDA will not respond and silent.
I think your must add "thread" and "beep" for update progress.
Thanks

Re: New version of TesseractOCR add-on

Rui Fontes
 

Hello!


From 2022.06 to 2022.06.27:

- Updated Tesseract from version 5.0 Alpha (64-bit) to 5.1 (32-bit);
- Added several more recognition languages;
- Introduced the option to select a second language to be used in OCR of documents with multiple languages and a button to forget it;
- Introduced a new document type, "With auto-orientation", that allows the OCR engine to rotate the image as necessary;
- Introduced beeps to signal the add-on is working;
- Corrected code to avoid the non population of the download languages combobox;
- Corrected a problem with controlTypes roles preventing compatibility with NVDA 2020.4;
- Added russian translation.


From 2022.06.27 to 2022.07:

- Allow using any number of recognition languages;
- Complete code re-wrote, including:
    - Split in various modules to make code clear;
    - End using batch files;
    - Allow recognize files on Desktop;
- Added translation to spanish, french, russian and ukranian.


Best regards,

Rui Fontes
NVDA portuguese team


Às 07:12 de 13/07/2022, Brian's Mail list account via groups.io escreveu:

What is the difference between the old and new ones?
Brian
Re: New version of TesseractOCR add-on

Rui Fontes
 

Yah, it is the next thing to do...

The routine was created to very small add-ons and it was not a big problem...

With TesseractOCR it can be a big problem!


Best regards,

Rui Fontes
NVDA portuguese team


Às 03:03 de 13/07/2022, nvdainth@... escreveu:

Hi Rui
I can update your add-on
but I think you must improve some code for update section.
When update this add-on progress the NVDA will not respond and silent.
I think your must add "thread" and "beep" for update progress.
Thanks

5941 - 5960 of 103078