Date   

Re: your help

Chris Mullins
 

Hi Marisane

You need to download and install the relevant language pack for Windows 10 which I think is “English United Kingdom” if you’re wanting the George voice.

 

1.Open “Settings” using Windows+i, and then select Settings  > Time & Language  > Language.

 

 

2. Under Preferred languages, select “Add a language”.

 

3. Under Choose a language to install, select or type the name of the language that you want to download and install, and then select Next.

 

4. Under Install language features, select the features that you want to use in the language that you selected to download, (this should include associated voices) and then select Install.

 

 

Once installed the additional voices should appear in the list of available voices in NVDA.

 

Cheers

Chris

Sent from Mail for Windows

 

From: Marisane Moruthanyana
Sent: 25 May 2022 12:28
To: nvda
Subject: [nvda] your help

 

Good day guys

 

I am Marisane from SA.

 

I hope you are all well.

 

I am pushing.

 

Your help please.

 

I need to add Windows core voices to the list already found in my PC.

 

How is that done?

 

 

I like George's voice, but my personal laptop does not hav it.

 

I only find it in my PC at work.

 

Please take me through the steps to download and install additional

Win core voices.

 

If you do not mind, direct me to a page with well elaborated tutorial.

 

Thanking you in advance.

 

Marisane

 

 

 

 

 


Re: Code Factory add-on updated!

Sam Bushman
 

It’s working great or me.

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Wednesday, May 25, 2022 4:46 AM
To: nvda@nvda.groups.io
Subject: [nvda] Code Factory add-on updated!

 

Hi everyone,

 

Following on from the confusion around the update to the Code Factory NVDA add-on.  I reached out to them earlier today and they have confirmed that the add-on has been updated and the version on the site now IS the new update.  It is compatible from NVDA 2019.3 through to the current NVDA 2022.1.

 

It's a little confusing as the file name is the same, but it is the new one.  Please do download it from: https://codefactoryglobal.com/app-store/voices-for-nvda/

 

If you have any issues with it, please do reach out to Code Factory.

 

Kind regards

 

Quentin.

 

--

Quentin Christensen
Training and Support Manager

 


your help

Marisane Moruthanyana
 

Good day guys

I am Marisane from SA.

I hope you are all well.

I am pushing.

Your help please.

I need to add Windows core voices to the list already found in my PC.

How is that done?

I like George's voice, but my personal laptop does not hav it.

I only find it in my PC at work.

Please take me through the steps to download and install additional
Win core voices.

If you do not mind, direct me to a page with well elaborated tutorial.

Thanking you in advance.

Marisane


Code Factory add-on updated!

Quentin Christensen
 

Hi everyone,

Following on from the confusion around the update to the Code Factory NVDA add-on.  I reached out to them earlier today and they have confirmed that the add-on has been updated and the version on the site now IS the new update.  It is compatible from NVDA 2019.3 through to the current NVDA 2022.1.

It's a little confusing as the file name is the same, but it is the new one.  Please do download it from: https://codefactoryglobal.com/app-store/voices-for-nvda/

If you have any issues with it, please do reach out to Code Factory.

Kind regards

Quentin.

--
Quentin Christensen
Training and Support Manager


Re: windows builtin ssh client

Luke Davis
 

mattias wrote:

Latest nvda snapshot
Latest windows 11 insider
Someone else with Win 11 will have to confirm. I can only confirm that it isn't a problem on Win 10.

You'll probably have to report an NVDA bug.

Luke


Re: windows builtin ssh client

mattias
 

Latest nvda snapshot

Latest windows 11 insider

 

Skickades från E-post för Windows

 

Från: Luke Davis
Skickat: den 25 maj 2022 11:33
Till: nvda@nvda.groups.io
Kopia: Nvda
Ämne: Re: [nvda] windows builtin ssh client

 

mattias wrote:

 

> Not sure but Seems nvda have issues with windows 11 builtin ssh client

> When deleting characters with backspace nvda dont tell What you delete

 

Not having this problem.

 

What NVDA version and windows version?

 

Luke

 

 

 

 

 

 


Re: Editing an NVDA Add-On Manifest file as a Temporary Workaround #adminnotice

William
 

:p, thanks Luke.


Luke Davis 於 25/5/2022 16:00 寫道:

On May 24, William wrote:

If not is there any instruction on how to change the last tested date of a non-installed .nvda-addon file?
1. Email the add-on author and ask when it's going to be updated.

2. Rename the add-on by changing the .nvda-addon extension to .zip.

3. Unzip it.

4. Change the manifest.

5. Re-zip it.

6. Rename it from .zip to .nvda-addon.

7. Install it.

Bonus instruction: be wise, and stop after step 1.

Luke




Re: creating a portable copy of NVDA 2022.1

Luke Davis
 

mcLeod stinnett wrote:

you have to install it some place, and i want to make sure i get the syntax right. can i put in c:\desktop
Technically, yes.
You probably won't have permission to create a folder called desktop in the root directory of your C drive, at least not automatically, but you can do that.

Lots of files and folders will be created under c:\desktop.

If you were going to do this on your actual user desktop, like c:\Users\mcLeod\Desktop, it would be very messy and you shouldn't.

You should instead use a subdirectory in that case, like c:\Users\mcLeod\Desktop\NVDA_portable

Luke


Re: windows builtin ssh client

Luke Davis
 

mattias wrote:

Not sure but Seems nvda have issues with windows 11 builtin ssh client
When deleting characters with backspace nvda dont tell What you delete
Not having this problem.

What NVDA version and windows version?

Luke


creating a portable copy of NVDA 2022.1

mcLeod stinnett
 

you have to install it some place, and i want to make sure i get the syntax right. can i put in c:\desktop
thanks. Please note the punctuations.
--
from mack


Re: Editing an NVDA Add-On Manifest file as a Temporary Workaround #adminnotice

mattias
 

Dont try this on CodeFactory addon

Yes yes it installs but it dont work

 

Skickades från E-post för Windows

 

Från: Luke Davis
Skickat: den 25 maj 2022 10:00
Till: nvda@nvda.groups.io
Ämne: Re: [nvda] Editing an NVDA Add-On Manifest file as a Temporary Workaround #adminnotice

 

On May 24, William wrote:

 

> If not is there any instruction on how to change the last tested date of a non-installed .nvda-addon file?

 

1. Email the add-on author and ask when it's going to be updated.

 

2. Rename the add-on by changing the .nvda-addon extension to .zip.

 

3. Unzip it.

 

4. Change the manifest.

 

5. Re-zip it.

 

6. Rename it from .zip to .nvda-addon.

 

7. Install it.

 

Bonus instruction: be wise, and stop after step 1.

 

Luke

 

 

 

 

 


windows builtin ssh client

mattias
 

Not sure but Seems nvda have issues with windows 11 builtin ssh client

When deleting characters with backspace nvda dont tell What you delete

 

Skickades från E-post för Windows

 


Re: Editing an NVDA Add-On Manifest file as a Temporary Workaround #adminnotice

Luke Davis
 

On May 24, William wrote:

If not is there any instruction on how to change the last tested date of a non-installed .nvda-addon file?
1. Email the add-on author and ask when it's going to be updated.

2. Rename the add-on by changing the .nvda-addon extension to .zip.

3. Unzip it.

4. Change the manifest.

5. Re-zip it.

6. Rename it from .zip to .nvda-addon.

7. Install it.

Bonus instruction: be wise, and stop after step 1.

Luke


Window title for desktop

Felix G.
 

Hello everyone,
when in the list of desktop icons, pressing NVDA+t sometimes yields
"Explorer" and sometimes "Program Manager." In one word: Why?
Best regards,
Felix Grützmacher


Re: Editing an NVDA Add-On Manifest file as a Temporary Workaround #adminnotice

Héctor Javier Benítez Corredera
 

Hello.

Cricricri is only valid for installed plugins.

I plan to be able to choose one or more of a non-installed add-on and we can modify the manifest without unzipping the add-on and thus save steps.

But at the moment I have a lot of work and for the moment I have not started with it.

I hope that this option will be there when the NVDA 2023 ruckus comes back.

Regards.

El 25/05/2022 a las 5:25, William escribió:

Hello, can your addon work with not installed addon?

If not is there any instruction on how to change the last tested date of a non-installed .nvda-addon file?

Thanks.



Héctor Javier Benítez Corredera 於 24/5/2022 14:58 寫道:

Good morning, last year I created a small add-on to modify the manifests in a simple way.

This add-on has english translation and below I leave the translated manual.

This is the repository:

https://github.com/hxebolax/cricricri-para-NVDA

And from here you can download the latest version:

https://nvda.es/files/get.php?file=cricricri

As colleagues say changing the manifest is something that does not ensure its operation if the add-on requires internal changes in the code but in most cases if it will work to continue using the add-ons.

If I recommend to be attentive to the updates and to update the add-on even if it works with the changed manifest because the updates can bring changes in the code for a better performance.

Next I leave the manual of the add-on that is very simple and we will be able to change in a single blow all the manifests of our installed add-ons that we have chosen and in a simple way.

Manual of cricricri for NVDA
Small add-on that will help us to change the date of the manifests.
Now according to the latest NVDA policy and until further changes, every year in the first version of NVDA programmers will have to change the version to match their manifest to the NVDA version.
There will be programmers who will do it immediately, others who will take some time and others who simply won't do it due to add-on abandonment or any other reason.
In this last case we will have to make the change of the lastTestedNVDAVersion property by hand and if we have many plugins we will have to waste time, besides it is not a task for all users since there are many levels of users.
Also if we want to test the betas and RCs we will have to change this parameter in the manifests otherwise we will not be able to have the add-on installed.
Well cricricri helps us in this task doing the process for us and quickly.
Using cricricri
Cricricri can be launched from the menu Tools / Date changer for manifests or add a shortcut in Preferences / Input gestures and look for the category cricricri.
Once opened the window is simple we will have a list with our plugins and their version in the manifest.
We will be able to choose the ones we want.
If we tab we have two buttons, select all or deselect all, little to say this will act on the list of plugins.
If we tab we will fall in three combo boxes:
-
Select major version: This combo box has to match the date of the version that NVDA is going to have.
-
Select Minor version: Here it is enough to leave it in 1, however I have put the four annual versions in case there are changes (anything can happen).
-
Select a revision: In this combo box leaving it at 0 is enough, however I have put up to 5 also just in case.
If we tab we will fall in the button Apply changes to the manifests which will begin the process of modifying the manifests to those complements that we have selected in the list.
If we tab again we will click on the Close button which will close the window without doing any action.
Shortcut keys
- Alt+L: It takes us quickly to the add-ins list.
- Alt+S: Selects all the add-ons.
- Alt+D: It deselects all the plug-ins that are marked.
- Alt+A: It will start the modification of the manifests of those plug-ins that we have selected.
- Alt+C or Escape: It will close the window without making any action.
Author's comments
Well NVDA is a reader in constant evolution for what many times there are complements that remain in the way for lack of development and for lack of adapting them to the changes that NVDA in its evolution brings.
This means that changing the date in the manifests solves a momentary problem to be able to continue using those add-ons that are not updated or that the developer is slow to update them. But there will be add-ons that not only serves to change the manifest and need internal changes to adapt to new versions, in that case the add-on will break and only remains to contact the author of the add-on.
I advise you to update the plugins that come out with the changes in the manifests even if we have changed the date with cricricri because it is possible that these plugins bring apart from the adaptation of the manifest other modifications that the developer has made.
I am not responsible if something is broken by changing the manifests because there are hundreds of plugins and there may be some exceptions not contemplated by me.
The use of this add-on and its results is solely under the responsibility of the end user.
Translators and contributors:
- French: Rémy Ruiz
- English: Alberto Buffolino
- Turkish: : umut korkmaz
Change log.
Version 0.2.1.
-
Fixed a security bug in secure screens.
-
Fixed a problem with reloading add-ons in NVDA.
-
Added English language.

Regards
Translated with www.DeepL.com/Translator (free version)

El 23/05/2022 a las 22:46, Brian Vogel escribió:

Editing an NVDA Add-On Manifest file as a Temporary Workaround

Moderator's Note:
  This post is about exactly what it says, a temporary workaround.  This is NOT the way to truly fix add-on compatibility issues in many cases, but it will work as a temporary workaround for some in a pinch. You use these instructions completely at your own risk.

Note Well:  This will NOT always work when there is a backward compatibility breaking release of NVDA because, sometimes, add-on code must be changed.  But it sometimes works if nothing more than testing and certification is needed for a given add-on, and that’s a bit behind the actual NVDA release.  Also, the %APPDATA% folder is normally hidden, so if your machine objects to your trying to navigate there, you will have to take the steps to show hidden files and folders on your machine.

Your NVDA Add-Ons are found in the following folder:

%APPDATA%\nvda\addons

and you can type (or cut and paste) the exact path shown above into the Address combo box in File Explorer, and after hitting Enter that’s where you’ll be.  A list of folders corresponding to each of the add-ons you have installed will be in the file list.  Locate the add-on for which you wish to edit the manifest file and open its folder.

In the folder you will find a file with the name manifest.ini.  It is a plain text file, so can be opened for editing with any plain text editor of your choosing.  I use Notepad, but any text editor will do.

Once you have the file open for editing, search for the line that starts with:  lastTestedNVDAVersion =

You will be substituting the current NVDA version number for whatever is currently shown after the equal sign.  It is critical that there be a space after the ‘n’ in “version” as well as after the equal sign itself.  The NVDA version goes after that space after the equal sign.  If you check out the line character by character after the ‘n’ in “version” as you found it, you’ll encounter those spaces.  Just make sure that the equal sign has a space before it, and after it.

This will trick NVDA into believing that the add-on has been tested up to and including the current NVDA version number.

If an add-on crashes or otherwise misbehaves after using this workaround, then work on its code will be required.

If you use this workaround, and become aware that a version of your add-on that has actually been tested with the latest version of NVDA has become available, definitely take the time to install the real version.  Your doctored manifest.ini file will end up being overwritten as part of installing “the real thing.”

--

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

You can't crush ideas by suppressing them. You can only crush them by ignoring them.
     ~ Ursula LeGuin, The Dispossessed


Re: hello, is there anyway I can get the previous version of NVDA, a lot of my addons do not work since updating

hurrikennyandopo ...
 

Hi Joshua



Have a look on the following page from my website jump down a few headings until you hear about obtaining older copies of nvda  it gives examples of what to do.


The link to this page is http://accessibilitycentral.net/nvda%20tutorials.html


Gene nz

On 25/05/2022 3:33 pm, Joshua Hendrickson wrote:
Hello to all. I should have listened to the message yesterday when
updating NVDA which said some of my addons were not compatible with
the new version. I didn't check them and now my IBMTTS, DECTALK,
WINAMP, and clock addons don't work. If I could roll back to the
previous version, that would be greatly appreciated. Thanks for any
help.




Re: hello, is there anyway I can get the previous version of NVDA, a lot of my addons do not work since updating

Socheat
 

Hello,
You can download the previous version from <a href="https://www.nvaccess.org/files/nvda/releases/2021.3.5/nvda_2021.3.5.exe">here.</a>

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joshua Hendrickson
Sent: Wednesday, May 25, 2022 10:34 AM
To: nvda@nvda.groups.io
Subject: [nvda] hello, is there anyway I can get the previous version of NVDA, a lot of my addons do not work since updating

Hello to all. I should have listened to the message yesterday when updating NVDA which said some of my addons were not compatible with the new version. I didn't check them and now my IBMTTS, DECTALK, WINAMP, and clock addons don't work. If I could roll back to the previous version, that would be greatly appreciated. Thanks for any help.


hello, is there anyway I can get the previous version of NVDA, a lot of my addons do not work since updating

Joshua Hendrickson
 

Hello to all. I should have listened to the message yesterday when
updating NVDA which said some of my addons were not compatible with
the new version. I didn't check them and now my IBMTTS, DECTALK,
WINAMP, and clock addons don't work. If I could roll back to the
previous version, that would be greatly appreciated. Thanks for any
help.


Re: Editing an NVDA Add-On Manifest file as a Temporary Workaround #adminnotice

William
 

Hello, can your addon work with not installed addon?

If not is there any instruction on how to change the last tested date of a non-installed .nvda-addon file?

Thanks.



Héctor Javier Benítez Corredera 於 24/5/2022 14:58 寫道:

Good morning, last year I created a small add-on to modify the manifests in a simple way.

This add-on has english translation and below I leave the translated manual.

This is the repository:

https://github.com/hxebolax/cricricri-para-NVDA

And from here you can download the latest version:

https://nvda.es/files/get.php?file=cricricri

As colleagues say changing the manifest is something that does not ensure its operation if the add-on requires internal changes in the code but in most cases if it will work to continue using the add-ons.

If I recommend to be attentive to the updates and to update the add-on even if it works with the changed manifest because the updates can bring changes in the code for a better performance.

Next I leave the manual of the add-on that is very simple and we will be able to change in a single blow all the manifests of our installed add-ons that we have chosen and in a simple way.

Manual of cricricri for NVDA
Small add-on that will help us to change the date of the manifests.
Now according to the latest NVDA policy and until further changes, every year in the first version of NVDA programmers will have to change the version to match their manifest to the NVDA version.
There will be programmers who will do it immediately, others who will take some time and others who simply won't do it due to add-on abandonment or any other reason.
In this last case we will have to make the change of the lastTestedNVDAVersion property by hand and if we have many plugins we will have to waste time, besides it is not a task for all users since there are many levels of users.
Also if we want to test the betas and RCs we will have to change this parameter in the manifests otherwise we will not be able to have the add-on installed.
Well cricricri helps us in this task doing the process for us and quickly.
Using cricricri
Cricricri can be launched from the menu Tools / Date changer for manifests or add a shortcut in Preferences / Input gestures and look for the category cricricri.
Once opened the window is simple we will have a list with our plugins and their version in the manifest.
We will be able to choose the ones we want.
If we tab we have two buttons, select all or deselect all, little to say this will act on the list of plugins.
If we tab we will fall in three combo boxes:
-
Select major version: This combo box has to match the date of the version that NVDA is going to have.
-
Select Minor version: Here it is enough to leave it in 1, however I have put the four annual versions in case there are changes (anything can happen).
-
Select a revision: In this combo box leaving it at 0 is enough, however I have put up to 5 also just in case.
If we tab we will fall in the button Apply changes to the manifests which will begin the process of modifying the manifests to those complements that we have selected in the list.
If we tab again we will click on the Close button which will close the window without doing any action.
Shortcut keys
- Alt+L: It takes us quickly to the add-ins list.
- Alt+S: Selects all the add-ons.
- Alt+D: It deselects all the plug-ins that are marked.
- Alt+A: It will start the modification of the manifests of those plug-ins that we have selected.
- Alt+C or Escape: It will close the window without making any action.
Author's comments
Well NVDA is a reader in constant evolution for what many times there are complements that remain in the way for lack of development and for lack of adapting them to the changes that NVDA in its evolution brings.
This means that changing the date in the manifests solves a momentary problem to be able to continue using those add-ons that are not updated or that the developer is slow to update them. But there will be add-ons that not only serves to change the manifest and need internal changes to adapt to new versions, in that case the add-on will break and only remains to contact the author of the add-on.
I advise you to update the plugins that come out with the changes in the manifests even if we have changed the date with cricricri because it is possible that these plugins bring apart from the adaptation of the manifest other modifications that the developer has made.
I am not responsible if something is broken by changing the manifests because there are hundreds of plugins and there may be some exceptions not contemplated by me.
The use of this add-on and its results is solely under the responsibility of the end user.
Translators and contributors:
- French: Rémy Ruiz
- English: Alberto Buffolino
- Turkish: : umut korkmaz
Change log.
Version 0.2.1.
-
Fixed a security bug in secure screens.
-
Fixed a problem with reloading add-ons in NVDA.
-
Added English language.

Regards
Translated with www.DeepL.com/Translator (free version)

El 23/05/2022 a las 22:46, Brian Vogel escribió:

Editing an NVDA Add-On Manifest file as a Temporary Workaround

Moderator's Note:
  This post is about exactly what it says, a temporary workaround.  This is NOT the way to truly fix add-on compatibility issues in many cases, but it will work as a temporary workaround for some in a pinch. You use these instructions completely at your own risk.

Note Well:  This will NOT always work when there is a backward compatibility breaking release of NVDA because, sometimes, add-on code must be changed.  But it sometimes works if nothing more than testing and certification is needed for a given add-on, and that’s a bit behind the actual NVDA release.  Also, the %APPDATA% folder is normally hidden, so if your machine objects to your trying to navigate there, you will have to take the steps to show hidden files and folders on your machine.

Your NVDA Add-Ons are found in the following folder:

%APPDATA%\nvda\addons

and you can type (or cut and paste) the exact path shown above into the Address combo box in File Explorer, and after hitting Enter that’s where you’ll be.  A list of folders corresponding to each of the add-ons you have installed will be in the file list.  Locate the add-on for which you wish to edit the manifest file and open its folder.

In the folder you will find a file with the name manifest.ini.  It is a plain text file, so can be opened for editing with any plain text editor of your choosing.  I use Notepad, but any text editor will do.

Once you have the file open for editing, search for the line that starts with:  lastTestedNVDAVersion =

You will be substituting the current NVDA version number for whatever is currently shown after the equal sign.  It is critical that there be a space after the ‘n’ in “version” as well as after the equal sign itself.  The NVDA version goes after that space after the equal sign.  If you check out the line character by character after the ‘n’ in “version” as you found it, you’ll encounter those spaces.  Just make sure that the equal sign has a space before it, and after it.

This will trick NVDA into believing that the add-on has been tested up to and including the current NVDA version number.

If an add-on crashes or otherwise misbehaves after using this workaround, then work on its code will be required.

If you use this workaround, and become aware that a version of your add-on that has actually been tested with the latest version of NVDA has become available, definitely take the time to install the real version.  Your doctored manifest.ini file will end up being overwritten as part of installing “the real thing.”

--

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

You can't crush ideas by suppressing them. You can only crush them by ignoring them.
     ~ Ursula LeGuin, The Dispossessed


Re: unable to get to the task bar with nvda Version: 2022.1

Sarah k Alawami
 

Cool cool, as I tell the controllers when I’m flying, yes I’ll restart when able. Loll. Except for them it’t dct (direct) frogz when able. Lol! I really hope that works though as this is frustrating.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Russell James
Sent: Tuesday, May 24, 2022 8:02 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] unable to get to the task bar with nvda Version: 2022.1

 

This happened to me on the latest update as well

Fortunately, when I restarted the computer it was fine again

Russ

 

On Tue, May 24, 2022, 10:30 PM Sarah k Alawami <marrie12@...> wrote:

I sent my debug log just in case.  Yeah when I can I will restart, right now I’m in the middle of something wherein I cannot reboot. This is the first time I have had things brake in I think the 13 years since starting to use nvda. I guess it had to happen to me at some point eh?

 

Take care and thanks.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Tuesday, May 24, 2022 7:27 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] unable to get to the task bar with nvda Version: 2022.1

 

Hi Sarah,

 

I'm using the same build of Windows and can confirm that I can get to the taskbar as expected with Windows+t.  It really sounds like one of those issues you get in between updating NVDA and restarting the PC.  Try that when you can, and do please let us know if it still happens after that.

 

Kind regards

 

Quentin.

 

On Wed, May 25, 2022 at 12:19 PM Sarah k Alawami <marrie12@...> wrote:

Running Windows 10 21H2 (x64) build 19044.1706 and I just updated nvda. I am no longer able to hit windows t, to get to the task bar, nor can I tab to it. I can kind of see it, but all I see is pane when I get to it via the start menu. I cannot restart my computer at this time so can’t test that. I did restart nvda with add ons disabled as I am writing this email and still can reproduce the issue.  I do have the debug log and will look at sending this over to, well, I need to find the address, but it will get sent. Can anyone else reproduce? I know of one other, only because they are on the phone with me.

 

Thanks.


 

--

Quentin Christensen
Training and Support Manager

 

3781 - 3800 of 99459