Date   

NVDA 2020.4 Beta 2 is now available

Quentin Christensen
 

Hi everyone,

NVDA 2020.4 Beta2 is now available for download & testing. Since Beta1 we added Afrikaans Grade 2 braille, fixed reporting incorrect information when copying fails, QWERTY input with Papenmeier braille displays & an error affecting some add-ons. More at: https://www.nvaccess.org/post/nvda-2020-4beta2/

--
Quentin Christensen
Training and Support Manager


Re: Looking for newest vocalizer driver

Rui Fontes
 

Hello!


To start debugging, two questions:

1 - In what apps are you trying the automatic language switching with SayAll?


2 - Have you any NVDA profil to sayAll?

If so, check if automatic language switching is on.


Best regards,


Customer support

Tiflotecnia, Lda.


Às 13:52 de 23/12/2020, darkmad88@... escreveu:

Hello, Rui! This driver works almost fine in my case, but there is one issue: automatic language switching doesn't work in "Say all" mode. I tried different russian+english voice combinations andsettings for automatic lang switching. It works fine in all modes except "Say all". Is there a chance to fix this?
Best regards and thank you for your work!


Re: Looking for newest vocalizer driver

darkmad88@...
 

Hello, Rui! This driver works almost fine in my case, but there is one issue: automatic language switching doesn't work in "Say all" mode. I tried different russian+english voice combinations andsettings for automatic lang switching. It works fine in all modes except "Say all". Is there a chance to fix this?
Best regards and thank you for your work!


Re: NVDA 2020.4 Beta 1 now available

 

Hi,

This is one of the reasons for using betas as portable copies. Although you won’t be able to test everything, it should give you a feel as to what’s new and changed (and a few months from now, add-ons that must be updated).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dan Miner via groups.io
Sent: Tuesday, December 22, 2020 9:52 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2020.4 Beta 1 now available

 

I’m on the side of parallel install for the beta line.  I’ve done it both ways over my career as software a developer and yes there is a bit more complexity with the release management side of it… but it is safer for users and potentially easier to switch back and forth if provisioned for in the project.  Saying that, I see the complexity of that with the logon screen support and roaming settings stuff.

 

I've not participated in trying a beta as I thought this was the case and I just don't want to crater my box.  *grin*

 

    Dan

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen

Sent: Tuesday, December 22, 2020 2:45 PM

To: nvda@nvda.groups.io

Subject: Re: [nvda] NVDA 2020.4 Beta 1 now available

 

Jim,

 

Interesting point.  The way it works currently is that:

- We regularly release Alpha snapshots every few days or sometimes several times a day, regardless of where else we are in the release cycle

- Three or four weeks before a release, we release a beta version.  If any bugs are found, we release a second (or third etc) beta.  This time around, the beta will have a little longer so we didn't either rush things to push a release before Christmas, or leave it entirely until next year.

- A week or so before the release, we put out a "Release Candidate" (RC) build.  Again, if any issues are found, we go to RC2, RC3 etc.

- Once all the big bugs have been ironed out (or pulled), we put out the final version.

 

The Beta and RC versions are set by default to prompt to update as new beta or RC builds, or the final stable version comes out.  If we were to have the beta install in a separate place, then it would make that sequence more complex.  And it would also be one more thing to change at some point (when we move to the RC?  Or only when we move to the stable version?) - and of course, any change is an opportunity to break something.

 

That's my thoughts off the top of my head, but it's an idea I'm happy to take more thoughts on.

 

Quentin.

 

On Tue, Dec 22, 2020 at 10:20 AM Jim Pipczak <jim.pipczak@...> wrote:

Hi all,

 

I believe that the beta should be installed into its own directory and not overwrite the existing full version. Your thoughts would be appreciated.

 

Thanks,

Jim

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen

Sent: Thursday, 17 December 2020 9:14 AM

To: nvda@nvda.groups.io

Subject: [nvda] NVDA 2020.4 Beta 1 now available

 

Hi everyone,

 

Lazily copying my tweet - so you get everything in one sentence: NVDA 2020.4Beta1 is now available for testing, including  new Chinese Input methods, an update to Liblouis, the elements list now works in focus mode, context sensitive help pressing F1 in NVDA dialogs & heaps more!

 

Read more and download from: https://www.nvaccess.org/post/nvda-2020-4beta1/

 

As usual, please do report any issues on GitHub.

 

Kind regards

 

Quentin.

 

 

--

Quentin Christensen

Training and Support Manager

 

Web: www.nvaccess.org

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

Facebook: http://www.facebook.com/NVAccess

Twitter: @NVAccess

 

Jim Pipczak

Access Technology Service Development Lead

Client Services

Vision Australia

14 & 17 Barrett Street Kensington VIC 3031

 

M: +614 3375 7598 T: +613 8378 1243 (I: 344243)

E: Jim.Pipczak@...

www.visionaustralia.org

 

Vision Australia is committed to supporting the blind and low vision community through COVID-19. Find out about our response and free support resources online at www.visionaustralia.org/COVID19.

 

  

 

 

Vision Australia acknowledges Aboriginal and Torres Strait Islander people as the traditional custodians of the land on which we operate. We have an inclusive culture and value diversity and all abilities.

 

 

 

 

 

--

Quentin Christensen

Training and Support Manager

 

Web: www.nvaccess.org

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

Facebook: http://www.facebook.com/NVAccess

Twitter: @NVAccess

 


Re: NVDA 2020.4 Beta 1 now available

Dan Miner
 

I’m on the side of parallel install for the beta line.  I’ve done it both ways over my career as software a developer and yes there is a bit more complexity with the release management side of it… but it is safer for users and potentially easier to switch back and forth if provisioned for in the project.  Saying that, I see the complexity of that with the logon screen support and roaming settings stuff.

 

I've not participated in trying a beta as I thought this was the case and I just don't want to crater my box.  *grin*

 

    Dan

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen

Sent: Tuesday, December 22, 2020 2:45 PM

To: nvda@nvda.groups.io

Subject: Re: [nvda] NVDA 2020.4 Beta 1 now available

 

Jim,

 

Interesting point.  The way it works currently is that:

- We regularly release Alpha snapshots every few days or sometimes several times a day, regardless of where else we are in the release cycle

- Three or four weeks before a release, we release a beta version.  If any bugs are found, we release a second (or third etc) beta.  This time around, the beta will have a little longer so we didn't either rush things to push a release before Christmas, or leave it entirely until next year.

- A week or so before the release, we put out a "Release Candidate" (RC) build.  Again, if any issues are found, we go to RC2, RC3 etc.

- Once all the big bugs have been ironed out (or pulled), we put out the final version.

 

The Beta and RC versions are set by default to prompt to update as new beta or RC builds, or the final stable version comes out.  If we were to have the beta install in a separate place, then it would make that sequence more complex.  And it would also be one more thing to change at some point (when we move to the RC?  Or only when we move to the stable version?) - and of course, any change is an opportunity to break something.

 

That's my thoughts off the top of my head, but it's an idea I'm happy to take more thoughts on.

 

Quentin.

 

On Tue, Dec 22, 2020 at 10:20 AM Jim Pipczak <jim.pipczak@...> wrote:

Hi all,

I believe that the beta should be installed into its own directory and not overwrite the existing full version. Your thoughts would be appreciated.

Thanks,

Jim

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen

Sent: Thursday, 17 December 2020 9:14 AM

To: nvda@nvda.groups.io

Subject: [nvda] NVDA 2020.4 Beta 1 now available

Hi everyone,

Lazily copying my tweet - so you get everything in one sentence: NVDA 2020.4Beta1 is now available for testing, including  new Chinese Input methods, an update to Liblouis, the elements list now works in focus mode, context sensitive help pressing F1 in NVDA dialogs & heaps more!

Read more and download from: https://www.nvaccess.org/post/nvda-2020-4beta1/

As usual, please do report any issues on GitHub.

Kind regards

Quentin.

 

--

Quentin Christensen

Training and Support Manager

Web: www.nvaccess.org

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

Facebook: http://www.facebook.com/NVAccess

Twitter: @NVAccess

 

Jim Pipczak

Access Technology Service Development Lead

Client Services

Vision Australia

14 & 17 Barrett Street Kensington VIC 3031

 

M: +614 3375 7598 T: +613 8378 1243 (I: 344243)

E: Jim.Pipczak@...

www.visionaustralia.org

 

Vision Australia is committed to supporting the blind and low vision community through COVID-19. Find out about our response and free support resources online at www.visionaustralia.org/COVID19.

  

 

 

Vision Australia acknowledges Aboriginal and Torres Strait Islander people as the traditional custodians of the land on which we operate. We have an inclusive culture and value diversity and all abilities.

 

 

 

 

 

--

Quentin Christensen

Training and Support Manager

 

Web: www.nvaccess.org

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

User group: https://nvda.groups.io/g/nvda

Facebook: http://www.facebook.com/NVAccess

Twitter: @NVAccess

 


Re: NVDA 2020.4 Beta 1 now available

Quentin Christensen
 

Jim,

Interesting point.  The way it works currently is that:
- We regularly release Alpha snapshots every few days or sometimes several times a day, regardless of where else we are in the release cycle
- Three or four weeks before a release, we release a beta version.  If any bugs are found, we release a second (or third etc) beta.  This time around, the beta will have a little longer so we didn't either rush things to push a release before Christmas, or leave it entirely until next year.
- A week or so before the release, we put out a "Release Candidate" (RC) build.  Again, if any issues are found, we go to RC2, RC3 etc.
- Once all the big bugs have been ironed out (or pulled), we put out the final version.

The Beta and RC versions are set by default to prompt to update as new beta or RC builds, or the final stable version comes out.  If we were to have the beta install in a separate place, then it would make that sequence more complex.  And it would also be one more thing to change at some point (when we move to the RC?  Or only when we move to the stable version?) - and of course, any change is an opportunity to break something.

That's my thoughts off the top of my head, but it's an idea I'm happy to take more thoughts on.

Quentin.

On Tue, Dec 22, 2020 at 10:20 AM Jim Pipczak <jim.pipczak@...> wrote:

Hi all,

 

I believe that the beta should be installed into its own directory and not overwrite the existing full version. Your thoughts would be appreciated.

 

Thanks,

Jim

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Thursday, 17 December 2020 9:14 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA 2020.4 Beta 1 now available

 

Hi everyone,

 

Lazily copying my tweet - so you get everything in one sentence: NVDA 2020.4Beta1 is now available for testing, including  new Chinese Input methods, an update to Liblouis, the elements list now works in focus mode, context sensitive help pressing F1 in NVDA dialogs & heaps more!

 

 

As usual, please do report any issues on GitHub.

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 


Jim Pipczak
Access Technology Service Development Lead
Client Services
Vision Australia
14 & 17 Barrett Street Kensington VIC 3031

M: +614 3375 7598 T: +613 8378 1243 (I: 344243)
E: Jim.Pipczak@...
www.visionaustralia.org


Vision Australia is committed to supporting the blind and low vision community through COVID-19. Find out about our response and free support resources online at www.visionaustralia.org/COVID19.




--
Quentin Christensen
Training and Support Manager


Re: Nvda beta still not keeping the setting to run at startup.

Kevin Cussick
 

I should have said that it will run at startup, I think I did but can not remember. anyway it was running at startup and then installing it changed the setting. this has been a problem for some years now maybe 2 years and I hope at some point maybe this year this might be fixed.

On 22/12/2020 02:42, Vickie Andrada wrote:
Hmmmm, I've never had a problem getting NVDA to run at start up.
Vicki
On 12/21/2020 5:30 PM, Kevin Cussick via groups.io wrote:
Hi all, OK not really much of a problem but this has being going on now for years and it would be nice to see a fix for this nvda did not keep[ my setting to run at startup. but anyway got it fixed I installed the beta last week but my computer was not shut down. until last night and when I booted up to night nvda was not running fixed for now. just thought I would report.





Re: Dell issues - information request

William
 

are you sure it is cpu not ram?


Rowen Cary 於 22/12/2020 20:44 寫道:

I used to use latitude7410 and I was really troubled by the Realtek driver.
After using it for a period of time, the CPU occupancy rate will rise to 100, but I don't use this machine now, I can be sure that this is a problem with the Realtek driver, and the specific version has been forgotten.





Skim reading suggestions

William
 

Hi all,

Not sure if this is appropiate to post here, or else do let me know where should I put these content.


I am testing latest beta 20.4 of nvda.

I found that the function Skim reading is very useful and interesting.

With regard to this, can I suggest that nvda adding a function for user to configure which key will not stop say all.

For instance, the find next for notepad++ is f3 and shift f3, the find next in word is shift f4, I want to configure these keys to be included in that function.

Thanks,

William


Re: Dell issues - information request

Rowen Cary
 

I used to use latitude7410 and I was really troubled by the Realtek driver.
After using it for a period of time, the CPU occupancy rate will rise to 100, but I don't use this machine now, I can be sure that this is a problem with the Realtek driver, and the specific version has been forgotten.


Please your help with one program in Nvda

Jarek.Krcmar
 

Hello everyone
I am a believer and that is why I am from a web address
www.jw.org
downloaded and installed JWLibrary. But I found that Nvda doesn't read any text to me in this program.
Could you please advise me what to do with it?
Thank you in advance for your help.

--
Jarek


Re: Odd arrow keys and speak current character behavior with MinTTY under Windows Subsystem for Linux

Dan Miner
 

The shift modifier did the trick so now I can jump to the top or bottom quickly.  Now just need “Go to line” kind of feature and targeted navigation will have decent support.   Like pressing shift+keypad 5, then it could prompt for input and I enter 6 and it moves the review cursor to line 6 of the object, and for extra credit: 6,15 to move to line 6 and position 15.  The next one of less use is “where am I?” to report the believed line and position of the cursor in the object.  And the one I am surprised to not find is text search via review cursor in a terminal like display.. even dialog boxes would benefit.

 

As for “What is prompt tracking”, I see I wasn’t clear.  It’s the little bit of text throw out by shells before waiting on user input.  Any modest command-line user is aware of them but they can be a bother to find easily.  There was a screen reader that did a surprisingly good job noting these natural “stopping points” in the user’s interactions and kind of treated them like a bookmark or annotation to be used like a latter to climb up and down the terminal session.  Great for referencing and linking ideas together.

 

As for emacs, I think much of the barebones support is there since bash is quite emacs-like.  It is the control key combos which do movement and modifications which is missing.  Most they just need to read character or word, etc the current position.  This is how I would approach vim support too initially.  It is the navigation by non-arrow key means which causes problems and it is common in vim.  Vim (and vi based editors) use a neat compositional  approach to its command structure which will help support the basics.

 

Then line numbered displays with monitored (quiet or live) regions and we have a decent text area canvas to paint our wonderous creations upon.  The gotcha is knowing the app within the terminal to use an app switching approach like regular Windows apps.

 

Ah well… I can dream…

 

    Dan

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 21, 2020 5:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Odd arrow keys and speak current character behavior with MinTTY under Windows Subsystem for Linux

 

Yeah, clip.exe is great if you are in MSYS or WSL.
> review: go to top of screen
Try Shift+Numpad 7?
Finding things in review mode can be a nice feature.
What is prompt tracking ? NVDA seems to be pretty responsive in command prompt, and you can even navigate control+Left/right, nVDA would track all the words correctly. It probably won't work as well in bash, since the definition of the word is different. That's why I want to write command line editor add-on for NVDA....

As for VIM support or emacs support, people have been talking for a long time, but it seems to me that not enough people are actually using either vim or emacs, so nobody has actually spent time on this. Most NVDA users either use specialized IDEs for coding, or something like Notepad++. And also it is not quite clear how to improve accessibility of emacs/vim - that is there is no way for screenreader to identify what's running inside the command prompt application, especially given the fact that emacs/vim can run from within SSH session.

 

On 12/21/2020 10:30 AM, Dan Miner via groups.io wrote:

I’ll take a closer look at your add-on.

 

For my usage of “cut & paste”, I am usually only pasting into a terminal.  And I do like that review mark & copy mechanism  For the larger copy needs, I was just redirecting to a file and yanking it open in something like notepad.  But I recently ran across a Windows CLI utility  called clip.exe which can remove all of that or shorten up the steps.  Works withinMSYS2, Cygwin, and WSL (must be clip.exe or aliased somehow to drop the .exe).

 

My wish list is a bit different, I want faster navigation tools for the terminal like there was back in the late 80s and early 90s.  A DOS screen reader back then was a terminal navigation ninja.  At a minimum, I need “review: go to top of screen” and “review: Find first occurrence” plus “review: Find Next”  A real nice to have would be prompt tracking and using a key combo to go backward and forward along the “prompt blocks”.  Then there is good vim within the terminal support… *sigh*

 

                Dan

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 21, 2020 9:59 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Odd arrow keys and speak current character behavior with MinTTY under Windows Subsystem for Linux

 

So for pasting things, I implemented a function that pastes into command prompt window even when context menu is not available. You can get it in my Tony's enhancements add-on - you'd need to enable it in the options, it is disabled by default.

For copying things out of command prompt I would still try to use review cursor. Or for copying large amounts of data, like large output of some command, I have some scripts where on Linux side I save it to a shared folder, and on Windows I periodically check that shared folder and copy things to clipboard as they appear.

But yeah, I wish there was a single good terminal solution, that works for NVDA. I think too few blind people work in terminals, so things are what they are. Sometimes I am thinking, someone should just implmement a simple terminal from within NVDA - something that would be accessible to begin with - in the end there is no rocket science in terminals....

--Tony

On 12/20/2020 10:23 PM, Dan Miner via groups.io wrote:

Well, I’ll take a peek and see if I can make any sense of it.

 

As for why, I find myself in WSL, mSYS2 and Cygwin depending on the task I am trying to do or testing.  It would be helpful to have a consistent terminal for them all and MinTTY is the closest I know of.  Regarding using Cmd console, it doesn’t work in ways needed for anything that prompts for a password in the Cygwin-style.  So, ssh, svn and “native git” will fail horribly and hair loss is soon to follow.

 

I’m actually a Linux guy trying to adapt to developing on Windows and for Windows.  Thus, I keep running back to UNIX-like land when my blood pressure gets too high.  *smiley*

 

The WSL standard terminal (basically Cmd but not quite) has an accessibility bug and will not respond to ALT+spacebar to open the system menu.  I couldn’t turn on cut and paste until recently  because my object navigation skills in NVDA reached a level I could find the system menu in the terminal UI object structure and get the mouse over there and simulate a left lick on it.

 

Now if I could figure out why the terminal audible bell doesn’t work for any minty (WSL, MSYS2 or Cygwin)…

    Dan

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tony Malykh
Sent: Sunday, December 20, 2020 10:40 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Odd arrow keys and speak current character behavior with MinTTY under Windows Subsystem for Linux

 

If you would like to debug this yourself, you can probably start with class Terminal - defined in NVDAObjects/behaviors.py.

But also, just curious, why can't you use normal command prompt if things are working fine there? If I remember correctly MSYS can run in command prompt.

On a side note, I have been suffering from poor editing experience in command line too, mostly over ssh connections, soI have been thinking about an add-on that would provide a better way to edit command in command line - it will try to identify current text in command line and open it up in a fully accessible edit box, then after editing it will update it back in the command line. So whenever I have some free time, I'll work on this.

HTH

--Tony

On 12/9/2020 9:59 AM, Dan Miner via groups.io wrote:

Just wanted to check to see if I am doing something wrong but I am having troubles editing shell commands with minty in any environment that uses it so far (Git for Windows, msys2 and WSLTTY).

 

I just installed the latest versions of Git for Windows, msys2 and WSLTTY in the last week And ran across a “consistent” problem.  I am using bash in its default configuration from these packages (Ubuntu 20.04.1 for WSL2).

 

 

The initial set up to reproduce problem (keeping it simple):

 

Type: echo hi

 

Without hitting return and intending to edit that line, changing hi (all lowercase) to Hi (with a capital H).

 

Press left arrow and “space” is spoken” and if you continue hitting the left or right arrows, you will always get “space” said.  So, it is easy to get lost as none of the under lying characters are spoken.  Thus, I hit the speak current character (Keypad 2) and I get an inconsistent spoken output of “space” or the character under the cursor.  Typical instances it will alternate between the two states and one time I got repeating twice.  To clarify, it would say “space”, “space” “h”, “h”, and cycle back to “space”.  But in this simple example and movement, it will likely just alternate back and forth between “space” and the letter (“I” in this case).

 

A partial workaround I have found is using bash’s readline advanced editing keys.  If I use control+left arrow and move by word, NVDA will speak the words as expected.  However, I still have to deal with arrow key problem and speak character issues within the word of interest.

 

Is anyone seeing this behavior?  It has been going on for many versions of NVDA (easily a year).

 

As sanity check, the standard cmd console behaves as expected with these features.

 

    Dan


Re: Dell issues - information request

William
 

Quentin

Thanks for your email.

First of all, my desktop is

Dell Vostro_3881


The sound drivers are

Realtek-High-Definition-Audio-Driver_V9NFW_WIN_6.0.8928.1_A00.EXE

Waves-MaxxAudio-Pro-Application_M96FF_WIN64_3.0.30.0_A02_01.EXE


Windows version

20h1


nvda version

2020.2


Besides, if you have further info, can you let me pass to my Dell support?

Thanks,

William


Quentin Christensen 於 18/12/2020 12:01 寫道:

Hi everyone,

I'd like to collate a bit more information just from those having issues
with Dell PCs and NVDA at the moment please. If that's you, could you
please reply and let me know:

1) What model laptop you have?
1a) If you know what Driver / driver version you have that would be great
too please.
2) Which version of Windows are you using?
3) Which version of NVDA you are using?

If anyone is using alpha versions, if you use the stable 2020.3 does it
make a difference?

My feeling is this is a Dell / Realtek driver issue, but I'd like to double
check and also collate that information for chasing it up with Dell and
Realtek.

Kind regards

Quentin.


Welcome to the NVDA Community Add-ons website - Quick Dictionary #nvdaaddonsfeed

nvda@nvda.groups.io Integration <nvda@...>
 

Quick Dictionary

Welcome to NVDA Quick Dictionary addon, which will allow you to quickly get a dictionary article with the translation of a word or phrase into your chosen language by pressing a key combination. There are few basic keyboard shortcuts and they are all intuitive and convenient so you will remember them quickly.
Dictionary articles contain detailed information about a word, such as part of speech, gender, plural or singular, translation options, list of meanings, synonyms and detailed examples. Such information will be useful for people who are learning foreign languages, or seek to use in communication all the richness and diversity of their own language.
The add-on supports several online dictionary services. You can select the desired remote dictionary in the appropriate dialog box or by using keyboard shortcuts. Each available service has its own settings panel.
There are also advanced opportunities for working with profiles of the voice synthesizers. You can associate a voice synthesizer profile with a specific language, after that translations into this language will be automatically voiced by the selected synthesizer.
Below are all the features of the add-on and keyboard shortcuts to control them. By default all functions are called using two-layer commands. But for any of these methods you can always assign convenient for you keyboard shortcuts. You can do it in the NVDA "Preferences" -> "Input gestures..." dialog.

Receiving a dictionary article

In order to get an article from the dictionary, you must first select the word you are interested in or copy it to the clipboard. Then just press NVDA+Y twice. There is also another way to get a dictionary entry: pressing NVDA+Y once switches the keyboard to add-on control mode, then just use the D key.

Add-on control mode

To access all the features of the add-on, you need to switch to add-on control mode, you can do this by pressing NVDA+Y once. You will hear a short low beep and will be able to use the other commands described below. When you press a key that is not used in the add-on, you will hear another signal notifying you of an erroneous command and the add-on control mode will be automatically turned off.

Add-on commands list

Basic dictionary commands: * D - announce a dictionary entry for a selected word or phrase (same as NVDA+Y); * W - show dictionary entry in a separate browseable window; * S - swap languages and get Quick Dictionary translation; * A - announce the current source and target languages; * C - copy last dictionary entry to the clipboard; * E - edit text before sending; * U - download from online dictionary and save the current list of available languages; * function keys - select online dictionary service; * Q - statistics on the using the online service; * F - choose online service.

Voice synthesizers profiles management: * from 1 to 9 - selection of the voice synthesizer profile; * G - announce the selected profile of voice synthesizers; * B - back to previous voice synthesizer; * R - restore default voice synthesizer; * Del - delete the selected voice synthesizer profile; * V - save configured voice synthesizer profile; * P - display a list of all customized voice synthesizers profiles.

Press O to open add-on settings dialog.

Help on add-on commands

You can see a list of all the commands used in the add-on as follows: * Via the NVDA menu - by pressing NVDA+N, go to the submenu "Tools", then - "Quick Dictionary" and activate the menu item "Help on add-on commands". * Press the H key in add-on control mode (NVDA+Y).

Add-on help

To open the add-on help - press NVDA+N, go to the "Tools" submenu, then - "Quick Dictionary" and activate the menu item "Help".

Contributions

We are very grateful to everyone who made the effort to develop, translate and maintain this add-on: * Cagri Dogan - Turkish translation; * Wafiqtaher - Arabic translation.

Several good solutions from other developments were used in the Quick Dictionary add-on. Thanks to the authors of the following add-ons: * Instant Translate - Alexy Sadovoy, Beqa Gozalishvili, Mesar Hameed, Alberto Buffolino and other NVDA contributors. * To work with voice synthesizers profiles were used ideas from the Switch Synth add-on (thanks to Tyler Spivey).

Change log

Version 2.1

  • added a dialog to edit the text before sending to remote service;
  • separated add-on help page from ReadMe;
  • Turkish translation added (thanks to Cagri Dogan).

Version 2.0

  • added the ability to connect other online dictionary services;
  • added Lexicala service and its settings panel;
  • added a dialog for choosing an online service from the list of available ones;
  • added a command to get information about the selected service;
  • added a dialog for working with profiles of voice synthesizers;
  • implemented the procedure for switching to the previous voice synthesizer;
  • implemented a parallel thread to monitor the state of the synthesizer;
  • due to an increase in the number of functions in the add-on - help for commands is now displayed in a separate window;
  • updated procedure for caching requests to online services;
  • added add-on submenu to NVDA menu;
  • updated ReadMe.

Version 1.2

  • added the ability to automatically switch voice synthesizers for selected languages;
  • added the ability to download the current list of languages available in the online-dictionary;
  • Turkish translation added thanks to Cagri Dogan.

Version 1.1

  • changed some keyboard shortcuts which conflicted with other add-ons;
  • changed the description of the main add-on features;
  • updated help and translation of the add-on;
  • removed some keyboard shortcuts and gave to user opportunity to setup them yourself;
  • fixed error in Ukrainian translation (thanks to Volodymyr Perig);
  • added russian translation.

Version 1.0: features of implementation

  • execution of requests to the remote server in a separate thread to avoid blocking the operation of NVDA;
  • signals while waiting for a response from the server;
  • caching of the last 100 requests to reduce the load on the remote dictionary service;
  • switching to add-on control mode;
  • possibility to use an alternative server;
  • add-on settings dialog.


Re: Nvda beta still not keeping the setting to run at startup.

hurrikennyandopo ...
 

Hi


I usually have the beta in its own directory then run a shortcut to it to play around with.


I just installed the beta over the 2020.3 release  shut down the computer then started it up.

This was installing the beta over the installed copy of nvda.


It started as normal as I have nvda start when windows does and it started up correctly. I will monitor over the next day or so but do not think  it will not start up when windows does.


This is also running the latest version of Windows 10 something a rather h2?


So am guessing it will start up as normal. Which way are you applying the settings? through the menus then apply and ok it or doing it through the shortcut way?


Have you set nvda back to factory defaults just in case the nvda.ini file has got a little corrupt then set it up again this usually fixes problems that may come up.


Gene nz

On 22/12/2020 3:42 pm, Vickie Andrada wrote:
Hmmmm, I've never had a problem getting NVDA to run at start up.

Vicki

On 12/21/2020 5:30 PM, Kevin Cussick via groups.io wrote:
Hi all, OK not really much of a problem but this has being going on now for years and it would be nice to see a fix for this nvda did not keep[ my setting to run at startup. but anyway got it fixed I installed the beta last week but my computer was not shut down. until last night and when I booted up to night nvda was not running fixed for now. just thought I would report.







Re: Nvda beta still not keeping the setting to run at startup.

Vickie Andrada
 

Hmmmm, I've never had a problem getting NVDA to run at start up.

Vicki

On 12/21/2020 5:30 PM, Kevin Cussick via groups.io wrote:
Hi all, OK not really much of a problem but this has being going on now for years and it would be nice to see a fix for this nvda did not keep[ my setting to run at startup. but anyway got it fixed I installed the beta last week but my computer was not shut down. until last night and when I booted up to night nvda was not running fixed for now. just thought I would report.




Re: Odd arrow keys and speak current character behavior with MinTTY under Windows Subsystem for Linux

Tony Malykh
 

Yeah, clip.exe is great if you are in MSYS or WSL.
> review: go to top of screen
Try Shift+Numpad 7?
Finding things in review mode can be a nice feature.
What is prompt tracking ? NVDA seems to be pretty responsive in command prompt, and you can even navigate control+Left/right, nVDA would track all the words correctly. It probably won't work as well in bash, since the definition of the word is different. That's why I want to write command line editor add-on for NVDA....

As for VIM support or emacs support, people have been talking for a long time, but it seems to me that not enough people are actually using either vim or emacs, so nobody has actually spent time on this. Most NVDA users either use specialized IDEs for coding, or something like Notepad++. And also it is not quite clear how to improve accessibility of emacs/vim - that is there is no way for screenreader to identify what's running inside the command prompt application, especially given the fact that emacs/vim can run from within SSH session.


On 12/21/2020 10:30 AM, Dan Miner via groups.io wrote:

I’ll take a closer look at your add-on.

 

For my usage of “cut & paste”, I am usually only pasting into a terminal.  And I do like that review mark & copy mechanism  For the larger copy needs, I was just redirecting to a file and yanking it open in something like notepad.  But I recently ran across a Windows CLI utility  called clip.exe which can remove all of that or shorten up the steps.  Works withinMSYS2, Cygwin, and WSL (must be clip.exe or aliased somehow to drop the .exe).

 

My wish list is a bit different, I want faster navigation tools for the terminal like there was back in the late 80s and early 90s.  A DOS screen reader back then was a terminal navigation ninja.  At a minimum, I need “review: go to top of screen” and “review: Find first occurrence” plus “review: Find Next”  A real nice to have would be prompt tracking and using a key combo to go backward and forward along the “prompt blocks”.  Then there is good vim within the terminal support… *sigh*

 

                Dan

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tony Malykh
Sent: Monday, December 21, 2020 9:59 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Odd arrow keys and speak current character behavior with MinTTY under Windows Subsystem for Linux

 

So for pasting things, I implemented a function that pastes into command prompt window even when context menu is not available. You can get it in my Tony's enhancements add-on - you'd need to enable it in the options, it is disabled by default.

For copying things out of command prompt I would still try to use review cursor. Or for copying large amounts of data, like large output of some command, I have some scripts where on Linux side I save it to a shared folder, and on Windows I periodically check that shared folder and copy things to clipboard as they appear.

But yeah, I wish there was a single good terminal solution, that works for NVDA. I think too few blind people work in terminals, so things are what they are. Sometimes I am thinking, someone should just implmement a simple terminal from within NVDA - something that would be accessible to begin with - in the end there is no rocket science in terminals....

--Tony

On 12/20/2020 10:23 PM, Dan Miner via groups.io wrote:

Well, I’ll take a peek and see if I can make any sense of it.

 

As for why, I find myself in WSL, mSYS2 and Cygwin depending on the task I am trying to do or testing.  It would be helpful to have a consistent terminal for them all and MinTTY is the closest I know of.  Regarding using Cmd console, it doesn’t work in ways needed for anything that prompts for a password in the Cygwin-style.  So, ssh, svn and “native git” will fail horribly and hair loss is soon to follow.

 

I’m actually a Linux guy trying to adapt to developing on Windows and for Windows.  Thus, I keep running back to UNIX-like land when my blood pressure gets too high.  *smiley*

 

The WSL standard terminal (basically Cmd but not quite) has an accessibility bug and will not respond to ALT+spacebar to open the system menu.  I couldn’t turn on cut and paste until recently  because my object navigation skills in NVDA reached a level I could find the system menu in the terminal UI object structure and get the mouse over there and simulate a left lick on it.

 

Now if I could figure out why the terminal audible bell doesn’t work for any minty (WSL, MSYS2 or Cygwin)…

    Dan

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Tony Malykh
Sent: Sunday, December 20, 2020 10:40 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Odd arrow keys and speak current character behavior with MinTTY under Windows Subsystem for Linux

 

If you would like to debug this yourself, you can probably start with class Terminal - defined in NVDAObjects/behaviors.py.

But also, just curious, why can't you use normal command prompt if things are working fine there? If I remember correctly MSYS can run in command prompt.

On a side note, I have been suffering from poor editing experience in command line too, mostly over ssh connections, soI have been thinking about an add-on that would provide a better way to edit command in command line - it will try to identify current text in command line and open it up in a fully accessible edit box, then after editing it will update it back in the command line. So whenever I have some free time, I'll work on this.

HTH

--Tony

On 12/9/2020 9:59 AM, Dan Miner via groups.io wrote:

Just wanted to check to see if I am doing something wrong but I am having troubles editing shell commands with minty in any environment that uses it so far (Git for Windows, msys2 and WSLTTY).

 

I just installed the latest versions of Git for Windows, msys2 and WSLTTY in the last week And ran across a “consistent” problem.  I am using bash in its default configuration from these packages (Ubuntu 20.04.1 for WSL2).

 

 

The initial set up to reproduce problem (keeping it simple):

 

Type: echo hi

 

Without hitting return and intending to edit that line, changing hi (all lowercase) to Hi (with a capital H).

 

Press left arrow and “space” is spoken” and if you continue hitting the left or right arrows, you will always get “space” said.  So, it is easy to get lost as none of the under lying characters are spoken.  Thus, I hit the speak current character (Keypad 2) and I get an inconsistent spoken output of “space” or the character under the cursor.  Typical instances it will alternate between the two states and one time I got repeating twice.  To clarify, it would say “space”, “space” “h”, “h”, and cycle back to “space”.  But in this simple example and movement, it will likely just alternate back and forth between “space” and the letter (“I” in this case).

 

A partial workaround I have found is using bash’s readline advanced editing keys.  If I use control+left arrow and move by word, NVDA will speak the words as expected.  However, I still have to deal with arrow key problem and speak character issues within the word of interest.

 

Is anyone seeing this behavior?  It has been going on for many versions of NVDA (easily a year).

 

As sanity check, the standard cmd console behaves as expected with these features.

 

    Dan


Re: NVDA 2020.4 Beta 1 now available

Jim Pipczak
 

Hi all,

 

I believe that the beta should be installed into its own directory and not overwrite the existing full version. Your thoughts would be appreciated.

 

Thanks,

Jim

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Thursday, 17 December 2020 9:14 AM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA 2020.4 Beta 1 now available

 

Hi everyone,

 

Lazily copying my tweet - so you get everything in one sentence: NVDA 2020.4Beta1 is now available for testing, including  new Chinese Input methods, an update to Liblouis, the elements list now works in focus mode, context sensitive help pressing F1 in NVDA dialogs & heaps more!

 

 

As usual, please do report any issues on GitHub.

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 


Jim Pipczak
Access Technology Service Development Lead
Client Services
Vision Australia
14 & 17 Barrett Street Kensington VIC 3031

M: +614 3375 7598 T: +613 8378 1243 (I: 344243)
E: Jim.Pipczak@...
www.visionaustralia.org


Vision Australia is committed to supporting the blind and low vision community through COVID-19. Find out about our response and free support resources online at www.visionaustralia.org/COVID19.



Re: Nvda beta still not keeping the setting to run at startup.

 

This happens here as well. For no reason I can track down, It will not start up on reboot.




On 12/21/2020 5:30 PM, Kevin Cussick via groups.io wrote:
Hi all, OK not really much of a problem but this has being going on now for years and it would be nice to see a fix for this nvda did not keep[ my setting to run at startup. but anyway got it fixed I installed the beta last week but my computer was not shut down.   until last night and when I booted up to night nvda was not running fixed for now. just thought I would report.






Nvda beta still not keeping the setting to run at startup.

Kevin Cussick
 

Hi all, OK not really much of a problem but this has being going on now for years and it would be nice to see a fix for this nvda did not keep[ my setting to run at startup. but anyway got it fixed I installed the beta last week but my computer was not shut down. until last night and when I booted up to night nvda was not running fixed for now. just thought I would report.

6621 - 6640 of 86483