Date   

Nvda 2017

farhan israk
 

Where will I get nvda 2017?


Re: NVDA moving to Python 3

Quentin Christensen
 

Hi Enes,

Not just yet. Potentially in the future, for now we're going to concentrate on getting NVDA itself and all of the add-ons, synthesizers and anything else moved over to Python 3.

Regards

Quentin.

On Tue, Jul 30, 2019 at 2:32 PM enes sarıbaş <enes.saribas@...> wrote:

Hi Quentin,

Will you be considering compiling NVDA in 64 bit in addition to py3?

On 7/29/2019 1:52 AM, Quentin Christensen wrote:
Hi everyone,

There has been a bit of confusion over NVDA's move to "Python 3".  I wanted to share a short message to clarify a couple of issues and concerns people have raised:

First and most importantly; the upcoming NVDA 2019.2 is not affected.  NVDA 2019.2 still uses code based on "Python 2", just like NVDA 2019.1 and earlier.  So, for the most part, anything which works in NVDA 2019.1, should work in 2019.2.

Please do test NVDA 2019.2 beta 3, which is available here: https://www.nvaccess.org/files/nvda/releases/2019.2beta3/nvda_2019.2beta3.exe.  If you do find any issues, particularly things which worked in NVDA 2019.1 which no longer work, please do let us know.  The "Release Candidate" for 2019.2 is due out shortly, and we would encourage all users to test that when it comes out.

So what are we doing?  We're updating NVDA's code from being largely based on Python 2, to Python 3.  Python 3 was first introduced in 2008, and Python 2 will reach end-of-life early next year.   Python's Wikipedia page succinctly explains why Python 3 is important:   Python 3 was "... designed to rectify fundamental design flaws in the language—the changes required could not be implemented while retaining full backwards compatibility with the 2.x series".  https://en.wikipedia.org/wiki/History_of_Python#Version_3

So why are we doing this?   Partly to ensure the ongoing stability and security of NVDA.  We cannot release a product based on a programming language which is no longer supported.  Not only would functionality be increasingly likely to break with updates to Windows and other programs, but it would not be secure.  As well as this, developers learning Python over the past few years have not been taught Python 2, they have been taught Python 3.  Moving to Python 3 ensures that we have access to this growing pool of developers.

NV Access and the community have worked together to ensure the process to transition add-ons is as smooth as possible.  There is a Wiki page with information on the transition at: https://github.com/nvaccess/nvda/wiki/nvdaPy3  Any developers with questions are encouraged to join in the discussion on the NVDA Developers mailing list: https://groups.io/g/nvda-devel  As much as users are concerned about the ongoing viability of add-ons they rely on, we are also keen to maintain stability and continuity of functionality for everyone.

We have just released a first Alpha build of NVDA updated to Python 3.  This is really only aimed at developers at this point.  What we would like end-users to know is that we have been in contact with the major synth and add-on developers.  We knew that would be the first question many people had about this process so we have involved them from early on.

If you are wondering whether "Synthesizer X" or "Add-on Y" will work under Python 3, the manufacturer of that Synthesizer or add-on is the first port of call.  If they have already updated and tested, they will be happy to let you know that.  Remember that we have only just released a first alpha build using Python 3 ourselves, so don't panic if your favourite hasn't been updated yet!

Joseph Lee has helpfully curated a list of add-ons, their known status and the contact details for the developer.  This list is on the official add-ons site:  https://addons.nvda-project.org/addons/nvdapy3.en.html

We will continue to work with add-on and synthesizer developers.  We don't have a choice about making this change, but like you, we don't want to see anyone left with decreased functionality due to an "upgrade".
 
Rest assured we will continue to test these changes to NVDA's codebase prior to pushing them out to users.  If you do still have any questions or concerns, please feel free to ask.

Regards

Quentin

--
Quentin Christensen
Training and Support Manager

NVDA 2019.2beta3 now available!



--
Quentin Christensen
Training and Support Manager

NVDA 2019.2 RC 1 now available!


Re: NVDA moving to Python 3

enes sarıbaş
 

Hi Quentin,

Will you be considering compiling NVDA in 64 bit in addition to py3?

On 7/29/2019 1:52 AM, Quentin Christensen wrote:
Hi everyone,

There has been a bit of confusion over NVDA's move to "Python 3".  I wanted to share a short message to clarify a couple of issues and concerns people have raised:

First and most importantly; the upcoming NVDA 2019.2 is not affected.  NVDA 2019.2 still uses code based on "Python 2", just like NVDA 2019.1 and earlier.  So, for the most part, anything which works in NVDA 2019.1, should work in 2019.2.

Please do test NVDA 2019.2 beta 3, which is available here: https://www.nvaccess.org/files/nvda/releases/2019.2beta3/nvda_2019.2beta3.exe.  If you do find any issues, particularly things which worked in NVDA 2019.1 which no longer work, please do let us know.  The "Release Candidate" for 2019.2 is due out shortly, and we would encourage all users to test that when it comes out.

So what are we doing?  We're updating NVDA's code from being largely based on Python 2, to Python 3.  Python 3 was first introduced in 2008, and Python 2 will reach end-of-life early next year.   Python's Wikipedia page succinctly explains why Python 3 is important:   Python 3 was "... designed to rectify fundamental design flaws in the language—the changes required could not be implemented while retaining full backwards compatibility with the 2.x series".  https://en.wikipedia.org/wiki/History_of_Python#Version_3

So why are we doing this?   Partly to ensure the ongoing stability and security of NVDA.  We cannot release a product based on a programming language which is no longer supported.  Not only would functionality be increasingly likely to break with updates to Windows and other programs, but it would not be secure.  As well as this, developers learning Python over the past few years have not been taught Python 2, they have been taught Python 3.  Moving to Python 3 ensures that we have access to this growing pool of developers.

NV Access and the community have worked together to ensure the process to transition add-ons is as smooth as possible.  There is a Wiki page with information on the transition at: https://github.com/nvaccess/nvda/wiki/nvdaPy3  Any developers with questions are encouraged to join in the discussion on the NVDA Developers mailing list: https://groups.io/g/nvda-devel  As much as users are concerned about the ongoing viability of add-ons they rely on, we are also keen to maintain stability and continuity of functionality for everyone.

We have just released a first Alpha build of NVDA updated to Python 3.  This is really only aimed at developers at this point.  What we would like end-users to know is that we have been in contact with the major synth and add-on developers.  We knew that would be the first question many people had about this process so we have involved them from early on.

If you are wondering whether "Synthesizer X" or "Add-on Y" will work under Python 3, the manufacturer of that Synthesizer or add-on is the first port of call.  If they have already updated and tested, they will be happy to let you know that.  Remember that we have only just released a first alpha build using Python 3 ourselves, so don't panic if your favourite hasn't been updated yet!

Joseph Lee has helpfully curated a list of add-ons, their known status and the contact details for the developer.  This list is on the official add-ons site:  https://addons.nvda-project.org/addons/nvdapy3.en.html

We will continue to work with add-on and synthesizer developers.  We don't have a choice about making this change, but like you, we don't want to see anyone left with decreased functionality due to an "upgrade".
 
Rest assured we will continue to test these changes to NVDA's codebase prior to pushing them out to users.  If you do still have any questions or concerns, please feel free to ask.

Regards

Quentin

--
Quentin Christensen
Training and Support Manager

NVDA 2019.2beta3 now available!


Re: nvda 2019-2 rc1

Quentin Christensen
 

Hi Bobby,

Here's the link to the release announcement where you can download the RC from: https://www.nvaccess.org/post/nvda-2019-2rc1-released/

Kind regards

Quentin.

On Tue, Jul 30, 2019 at 12:33 PM Bobby Vinton <vinton.bobby5277@...> wrote:
Can you please tell me ware to down load nvda 2019.2 rc 1

On 7/29/2019 7:39 PM, Joseph Lee wrote:
> Hi,
> No.
> A helpful way to remember what's going on is thinking about NVDA major releases for 2019:
> * 2019.2: Python 2
> * 2019.3: Python 3
> Cheers,
> Joseph
>
>
> -----Original Message-----
> From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
> Sent: Monday, July 29, 2019 4:24 PM
> To: nvda@nvda.groups.io
> Subject: [nvda] nvda 2019-2 rc1
>
> So does this version use python 3?
>
>
>
>
>
>
>





--
Quentin Christensen
Training and Support Manager

NVDA 2019.2beta1 now available!


Re: nvda 2019-2 rc1

Bobby Vinton <vinton.bobby5277@...>
 

Can you please tell me ware to down load nvda 2019.2 rc 1

On 7/29/2019 7:39 PM, Joseph Lee wrote:
Hi,
No.
A helpful way to remember what's going on is thinking about NVDA major releases for 2019:
* 2019.2: Python 2
* 2019.3: Python 3
Cheers,
Joseph


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Monday, July 29, 2019 4:24 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda 2019-2 rc1

So does this version use python 3?






Re: cells in Excel not reading after a cell is typed in

Quentin Christensen
 

Ok, Follow the suggestions in my last message, and then maybe send me a copy of your log (to info@...).


On Tue, Jul 30, 2019 at 11:33 AM Supanut Leepaisomboon <supanut2000@...> wrote:
For me, the main issue I face is, after editing a cell and press enter, NVDA sometimes won't read the cell coordinate (A1, B5, etc). In other times, it would read, but there would be a delay.



--
Quentin Christensen
Training and Support Manager

NVDA 2019.2beta1 now available!


Re: cells in Excel not reading after a cell is typed in

 

After typing into a cell, we press enter to exit the cell. After we've exited from a cell, it reads cell contents, but no column and row information. It read column and row information before we edited anything. After we have edited a cell, it no longer reads the column and row information, as I'm sure it should.





On 7/29/2019 9:30 PM, Quentin Christensen wrote:
I'm actually not clear on what the issue here is.  Are you saying after editing a cell, when you move around the worksheet NVDA isn't reading cell coordinates (A1, B5, etc)?  If that, is it reading them before editing the cell?  In NVDA's Document settings (NVDA+control+d) there is an option to report "cell coordinates" (alt+o on that page), although that shouldn't have anything to do with editing a cell.

Otherwise, the usual things to check:
1) You said you were running 2019.1.1 so it's unlikely you recently installed that, but since we did release 2019.2 rc2 today, if you update versions, be sure to restart the computer.
2) Are you using any add-ons?  Try pressing NVDA+q, then down arrow to "restart with add-ons disabled" and press ENTER.

If neither of those help, could you provide exact steps to repro, as well as what is happening (and what should happen) and a copy of your NVDA log (perhaps at Debug level, since it sounds like it's just not reading something you're expecting it to read, where it may not be generating an error).  See https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps for info on log files.

Kind regards

Quentin.

On Tue, Jul 30, 2019 at 11:07 AM Supanut Leepaisomboon <supanut2000@...> wrote:
I think I'm experiencing a similar, if not exactly the same, issue as well with the latest version of NVDA and Excel 2016/365.


--
Quentin Christensen
Training and Support Manager

NVDA 2019.2beta1 now available!


Re: cells in Excel not reading after a cell is typed in

 

For me, the main issue I face is, after editing a cell and press enter, NVDA sometimes won't read the cell coordinate (A1, B5, etc). In other times, it would read, but there would be a delay.


Re: cells in Excel not reading after a cell is typed in

Quentin Christensen
 

I'm actually not clear on what the issue here is.  Are you saying after editing a cell, when you move around the worksheet NVDA isn't reading cell coordinates (A1, B5, etc)?  If that, is it reading them before editing the cell?  In NVDA's Document settings (NVDA+control+d) there is an option to report "cell coordinates" (alt+o on that page), although that shouldn't have anything to do with editing a cell.

Otherwise, the usual things to check:
1) You said you were running 2019.1.1 so it's unlikely you recently installed that, but since we did release 2019.2 rc2 today, if you update versions, be sure to restart the computer.
2) Are you using any add-ons?  Try pressing NVDA+q, then down arrow to "restart with add-ons disabled" and press ENTER.

If neither of those help, could you provide exact steps to repro, as well as what is happening (and what should happen) and a copy of your NVDA log (perhaps at Debug level, since it sounds like it's just not reading something you're expecting it to read, where it may not be generating an error).  See https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps for info on log files.

Kind regards

Quentin.

On Tue, Jul 30, 2019 at 11:07 AM Supanut Leepaisomboon <supanut2000@...> wrote:
I think I'm experiencing a similar, if not exactly the same, issue as well with the latest version of NVDA and Excel 2016/365.



--
Quentin Christensen
Training and Support Manager

NVDA 2019.2beta1 now available!


Re: cells in Excel not reading after a cell is typed in

Sarah k Alawami
 

Wasn't ther a fix in excel or nvda, somethingn about reading cell contents etc?

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 29 Jul 2019, at 18:07, Supanut Leepaisomboon wrote:

I think I'm experiencing a similar, if not exactly the same, issue as well with the latest version of NVDA and Excel 2016/365.


Re: cells in Excel not reading after a cell is typed in

 

I think I'm experiencing a similar, if not exactly the same, issue as well with the latest version of NVDA and Excel 2016/365.


cells in Excel not reading after a cell is typed in

 

Hello list. The subject says it pretty well. We are working on a sheet in Excel. We are using the latest version of Excel from Office 365. We can type something into cells and press enter. After we do that, it will read what is in the cells. However, it will not read the row or column information. We alt-tab out of, and back into the sheet, and everything works as it should.  Is there a setting we are forgetting in Excel? We are using NVDA version 2019.1.1. Any help with this annoying issue is very much appreciated. Much thanks in advance.


Windows 10 notifications/toasts: frequently asked questions

 

Hi all,

 

The following was prompted by threads on numerous mailing lists regarding Windows 10 toasts/notifications (they are really the same thing). I hope it can serve as a handy reference in answer all sorts of questions you may have about them (a copy of the below FAQ was sent to a Windows 10 list).

 

Q. What are toasts?

 

Another name for notifications. Basically, when an application (regardless of source; see below) presents a notification, Windows 10 will present a message on the right-hand side of the screen that’ll go away after a short while.

 

Q. Which apps or situations can send notifications?

 

Any app capable of sending notifications will ask Windows to present notifications. These include installed apps, web applications and certain websites, and Windows itself.

 

Q. How do I interact with notifications when they appear?

 

Depending on which Windows 10 release you are using (you can check this by opening About Windows/Winver):

 

  • Version 1803 (April 2018 Update) and earlier: press Windows+V.
  • Version 1809 (October 2018 Update) and later: press Windows+Shift+V.

 

Note: Version 1809 and later reserves Windows+V for clipboard history (a separate topic).

 

Q. What if I miss these notifications?

 

All notifications will eventually end up on Action Center (Windows+A).

 

Q. While using Skype in the background, I get a call. How can I answer calls?

 

Incoming calls are notifications. Therefore you can activate these notifications and press Enter to accept or use options to decline the call.

 

Q. I’m using a recent version of Chrome and somehow I get notifications from nowhere. What should I do?

 

Web applications, or more specifically, apps for websites can send notifications through a web browser. Just like any notification, you can activate the notification and deal with it.

 

Although each web browser differs in terms of stopping these notifications, the general steps involve opening the web browser and asking it to stop sending notifications.

 

Q. How come some notifications have additional controls, not just a button to dismiss it?

 

These are called actionable notifications. If an app wants you to take a follow-up action (such as answering a call on Skype), the notification will feature additional controls such as an edit field to send a reply, answering a call, opening a specific app, or taking additional actions.

 

Q. I don’t want to see notifications from certain apps. How can I configure this?

 

To configure this, open Settings (Windows+I)/System/notifications and Actions. Scroll (press Tab) through this screen, and from “get notifications from these senders” section, go through each app and toggle the notifications on or off.

 

Q. What if I want to tell apps I don’t want to see notifications while I’m busy with something?

 

This is done by setting up focus assist (formerly quiet hours). As of Version 1903 (May 2019 Update), focus assist can be used to silence notifications while you are in a full-screen application or playing games, as well as asking Windows to send notifications from a priority list or alarms.

 

At least the above FAQ should cover majority of cases. Please let us know if other scenarios should be added.

Cheers,

Joseph


Re: NVDA moving to Python 3

Sarah k Alawami
 

You mean the 3 I misspelled lol! Yeah I forgot they would have different languages lol!

Take care and be blessed.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 29 Jul 2019, at 16:49, Joseph Lee wrote:

Hi,

Different languages will have different voices. The three mentioned by Sarah is for American English.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sarah k Alawami
Sent: Monday, July 29, 2019 4:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Windows 1 core Katherine? I only have mark, david and ziera.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 29 Jul 2019, at 16:40, Joseph Lee wrote:

Hi,

Yes. In fact, Windows OneCore was the first speech synthesizer to become compatible with Python 3.
Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of molly the blind tech lover
Sent: Monday, July 29, 2019 4:38 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Will the windows OneCore Microsoft Catherine voice work with python 3?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Monday, July 29, 2019 1:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

I wouldn't bother with anny synth addons to be honest.

If you can afford it I'd use their sapi equivilants.

You are not locked down to one particular program, and they can be used anywhere you want.

While I have vocaliser, its a nice high quality but slow crappy synth for normal use.

Its good for gaming where its needed, and book reading and things like that.

On the other side something like espeak, is low quality, fast responding, high performance, but crappy sounding.

Its good for games without stories, documentation reading, email, brousing the web, doing administration and running virtual machines and things where I don't care what I am hearing or if it sounds good just that I am getting correct information.

I suppose with the powerfull system I have I could run vocaliser constantly but it may not be what I want all day long.

Pluss in a situation where something crashes or goes down or something breaks, I could be stuck with no speech because the net failed, or bit of windows went or something else fails.

The only way for me to get things back would either be a full reformat or killing configurations.

I have found that when I have relied on some stuff like this in the past that when it fails, you have nothing to fall back on.

A reformat fixes it as it always does, however as a result of being bitten to many times, for general purpose and we are talking general purpose, I would prefur crappy low quality but readable information rather than high quality readable but unstable information.

Also until recently any high quality anything is a performance drag.

I know several on xp and lower specked systems that can't afford any upgrades at all.

And even for those that do, they get the cheapest options which may be a few generations lower than current.

I have tried to run high quality on systems for general use and even when it has worked even if the system does not crash, even if it works floorlessly without me having to reformat to get speech back the load time is insane and so is responce time when I press a key.

I know with espeak that I am garanteed speech, crappy that it is.

And I am garanteed information in a readable format.

It may not sound that nice but I can read it.

In my line of work as admin and tester, I don't care if the information is sounding good or not just that I am getting it.

 If I am reading a book or playing an advanced flight game or something like that then of course I do.

I guess if your job is a translater or transcriber, high quality speech would be something you would have to use on a regular basis.

However you would have the hardware and software to support you or at least I do hope so.

I have friends some in the church, some in jobs that have never been able to afford the more expensive tech ever in their lives and get cast offs only.

Some are even used to it.

 

 

On 30/07/2019 4:48 AM, Josh Kennedy wrote:

I am going to buy the eloquence/vocalizer NVDA-addon on Friday. I hope that it will work with python3 when the time comes. Since I get extra social security in the united states now, these voices are easily affordable for me. I want the legal versions of voices because I am hoping that the legal eloquence and legal vocalizer will be updated to python3 whereas unsupported illegal stuff which is unsupported may just plain break and not work. Right now I am using sapi5 eloquence from codeFactory until this Friday when I can register the eloquence/vocalizer codeFactory addon. 


Re: NVDA moving to Python 3

molly the blind tech lover
 

There’s also Hazel ☺ You will have to download and install the language pack.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sarah k Alawami
Sent: Monday, July 29, 2019 7:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Windows 1 core Katherine? I only have mark, david and ziera.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 29 Jul 2019, at 16:40, Joseph Lee wrote:

Hi,

Yes. In fact, Windows OneCore was the first speech synthesizer to become compatible with Python 3.
Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of molly the blind tech lover
Sent: Monday, July 29, 2019 4:38 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Will the windows OneCore Microsoft Catherine voice work with python 3?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Monday, July 29, 2019 1:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

I wouldn't bother with anny synth addons to be honest.

If you can afford it I'd use their sapi equivilants.

You are not locked down to one particular program, and they can be used anywhere you want.

While I have vocaliser, its a nice high quality but slow crappy synth for normal use.

Its good for gaming where its needed, and book reading and things like that.

On the other side something like espeak, is low quality, fast responding, high performance, but crappy sounding.

Its good for games without stories, documentation reading, email, brousing the web, doing administration and running virtual machines and things where I don't care what I am hearing or if it sounds good just that I am getting correct information.

I suppose with the powerfull system I have I could run vocaliser constantly but it may not be what I want all day long.

Pluss in a situation where something crashes or goes down or something breaks, I could be stuck with no speech because the net failed, or bit of windows went or something else fails.

The only way for me to get things back would either be a full reformat or killing configurations.

I have found that when I have relied on some stuff like this in the past that when it fails, you have nothing to fall back on.

A reformat fixes it as it always does, however as a result of being bitten to many times, for general purpose and we are talking general purpose, I would prefur crappy low quality but readable information rather than high quality readable but unstable information.

Also until recently any high quality anything is a performance drag.

I know several on xp and lower specked systems that can't afford any upgrades at all.

And even for those that do, they get the cheapest options which may be a few generations lower than current.

I have tried to run high quality on systems for general use and even when it has worked even if the system does not crash, even if it works floorlessly without me having to reformat to get speech back the load time is insane and so is responce time when I press a key.

I know with espeak that I am garanteed speech, crappy that it is.

And I am garanteed information in a readable format.

It may not sound that nice but I can read it.

In my line of work as admin and tester, I don't care if the information is sounding good or not just that I am getting it.

 If I am reading a book or playing an advanced flight game or something like that then of course I do.

I guess if your job is a translater or transcriber, high quality speech would be something you would have to use on a regular basis.

However you would have the hardware and software to support you or at least I do hope so.

I have friends some in the church, some in jobs that have never been able to afford the more expensive tech ever in their lives and get cast offs only.

Some are even used to it.

 

 

On 30/07/2019 4:48 AM, Josh Kennedy wrote:

I am going to buy the eloquence/vocalizer NVDA-addon on Friday. I hope that it will work with python3 when the time comes. Since I get extra social security in the united states now, these voices are easily affordable for me. I want the legal versions of voices because I am hoping that the legal eloquence and legal vocalizer will be updated to python3 whereas unsupported illegal stuff which is unsupported may just plain break and not work. Right now I am using sapi5 eloquence from codeFactory until this Friday when I can register the eloquence/vocalizer codeFactory addon. 


Re: NVDA moving to Python 3

Quentin Christensen
 

OneCore Catherine is, from memory, one of the English (Australian) voices.  If you install different languages (including variants, eg English (Irish), English (Canadian), etc, and the speech packs, you get additional OneCore voices with those accents.


On Tue, Jul 30, 2019 at 9:49 AM Joseph Lee <joseph.lee22590@...> wrote:

Hi,

Different languages will have different voices. The three mentioned by Sarah is for American English.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sarah k Alawami
Sent: Monday, July 29, 2019 4:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Windows 1 core Katherine? I only have mark, david and ziera.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 29 Jul 2019, at 16:40, Joseph Lee wrote:

Hi,

Yes. In fact, Windows OneCore was the first speech synthesizer to become compatible with Python 3.
Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of molly the blind tech lover
Sent: Monday, July 29, 2019 4:38 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Will the windows OneCore Microsoft Catherine voice work with python 3?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Monday, July 29, 2019 1:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

I wouldn't bother with anny synth addons to be honest.

If you can afford it I'd use their sapi equivilants.

You are not locked down to one particular program, and they can be used anywhere you want.

While I have vocaliser, its a nice high quality but slow crappy synth for normal use.

Its good for gaming where its needed, and book reading and things like that.

On the other side something like espeak, is low quality, fast responding, high performance, but crappy sounding.

Its good for games without stories, documentation reading, email, brousing the web, doing administration and running virtual machines and things where I don't care what I am hearing or if it sounds good just that I am getting correct information.

I suppose with the powerfull system I have I could run vocaliser constantly but it may not be what I want all day long.

Pluss in a situation where something crashes or goes down or something breaks, I could be stuck with no speech because the net failed, or bit of windows went or something else fails.

The only way for me to get things back would either be a full reformat or killing configurations.

I have found that when I have relied on some stuff like this in the past that when it fails, you have nothing to fall back on.

A reformat fixes it as it always does, however as a result of being bitten to many times, for general purpose and we are talking general purpose, I would prefur crappy low quality but readable information rather than high quality readable but unstable information.

Also until recently any high quality anything is a performance drag.

I know several on xp and lower specked systems that can't afford any upgrades at all.

And even for those that do, they get the cheapest options which may be a few generations lower than current.

I have tried to run high quality on systems for general use and even when it has worked even if the system does not crash, even if it works floorlessly without me having to reformat to get speech back the load time is insane and so is responce time when I press a key.

I know with espeak that I am garanteed speech, crappy that it is.

And I am garanteed information in a readable format.

It may not sound that nice but I can read it.

In my line of work as admin and tester, I don't care if the information is sounding good or not just that I am getting it.

 If I am reading a book or playing an advanced flight game or something like that then of course I do.

I guess if your job is a translater or transcriber, high quality speech would be something you would have to use on a regular basis.

However you would have the hardware and software to support you or at least I do hope so.

I have friends some in the church, some in jobs that have never been able to afford the more expensive tech ever in their lives and get cast offs only.

Some are even used to it.

 

 

On 30/07/2019 4:48 AM, Josh Kennedy wrote:

I am going to buy the eloquence/vocalizer NVDA-addon on Friday. I hope that it will work with python3 when the time comes. Since I get extra social security in the united states now, these voices are easily affordable for me. I want the legal versions of voices because I am hoping that the legal eloquence and legal vocalizer will be updated to python3 whereas unsupported illegal stuff which is unsupported may just plain break and not work. Right now I am using sapi5 eloquence from codeFactory until this Friday when I can register the eloquence/vocalizer codeFactory addon. 



--
Quentin Christensen
Training and Support Manager

NVDA 2019.2beta1 now available!


Re: NVDA moving to Python 3

molly the blind tech lover
 

That’s great

The OneCore is my favorite synthesizer. So many different voices to choose from.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Monday, July 29, 2019 7:41 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Hi,

Yes. In fact, Windows OneCore was the first speech synthesizer to become compatible with Python 3.
Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of molly the blind tech lover
Sent: Monday, July 29, 2019 4:38 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Will the windows OneCore Microsoft Catherine voice work with python 3?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Monday, July 29, 2019 1:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

I wouldn't bother with anny synth addons to be honest.

If you can afford it I'd use their sapi equivilants.

You are not locked down to one particular program, and they can be used anywhere you want.

While I have vocaliser, its a nice high quality but slow crappy synth for normal use.

Its good for gaming where its needed, and book reading and things like that.

On the other side something like espeak, is low quality, fast responding, high performance, but crappy sounding.

Its good for games without stories, documentation reading, email, brousing the web, doing administration and running virtual machines and things where I don't care what I am hearing or if it sounds good just that I am getting correct information.

I suppose with the powerfull system I have I could run vocaliser constantly but it may not be what I want all day long.

Pluss in a situation where something crashes or goes down or something breaks, I could be stuck with no speech because the net failed, or bit of windows went or something else fails.

The only way for me to get things back would either be a full reformat or killing configurations.

I have found that when I have relied on some stuff like this in the past that when it fails, you have nothing to fall back on.

A reformat fixes it as it always does, however as a result of being bitten to many times, for general purpose and we are talking general purpose, I would prefur crappy low quality but readable information rather than high quality readable but unstable information.

Also until recently any high quality anything is a performance drag.

I know several on xp and lower specked systems that can't afford any upgrades at all.

And even for those that do, they get the cheapest options which may be a few generations lower than current.

I have tried to run high quality on systems for general use and even when it has worked even if the system does not crash, even if it works floorlessly without me having to reformat to get speech back the load time is insane and so is responce time when I press a key.

I know with espeak that I am garanteed speech, crappy that it is.

And I am garanteed information in a readable format.

It may not sound that nice but I can read it.

In my line of work as admin and tester, I don't care if the information is sounding good or not just that I am getting it.

 If I am reading a book or playing an advanced flight game or something like that then of course I do.

I guess if your job is a translater or transcriber, high quality speech would be something you would have to use on a regular basis.

However you would have the hardware and software to support you or at least I do hope so.

I have friends some in the church, some in jobs that have never been able to afford the more expensive tech ever in their lives and get cast offs only.

Some are even used to it.

 

 

On 30/07/2019 4:48 AM, Josh Kennedy wrote:

I am going to buy the eloquence/vocalizer NVDA-addon on Friday. I hope that it will work with python3 when the time comes. Since I get extra social security in the united states now, these voices are easily affordable for me. I want the legal versions of voices because I am hoping that the legal eloquence and legal vocalizer will be updated to python3 whereas unsupported illegal stuff which is unsupported may just plain break and not work. Right now I am using sapi5 eloquence from codeFactory until this Friday when I can register the eloquence/vocalizer codeFactory addon. 


Re: NVDA moving to Python 3

 

Hi,

Different languages will have different voices. The three mentioned by Sarah is for American English.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sarah k Alawami
Sent: Monday, July 29, 2019 4:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Windows 1 core Katherine? I only have mark, david and ziera.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 29 Jul 2019, at 16:40, Joseph Lee wrote:

Hi,

Yes. In fact, Windows OneCore was the first speech synthesizer to become compatible with Python 3.
Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of molly the blind tech lover
Sent: Monday, July 29, 2019 4:38 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Will the windows OneCore Microsoft Catherine voice work with python 3?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Monday, July 29, 2019 1:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

I wouldn't bother with anny synth addons to be honest.

If you can afford it I'd use their sapi equivilants.

You are not locked down to one particular program, and they can be used anywhere you want.

While I have vocaliser, its a nice high quality but slow crappy synth for normal use.

Its good for gaming where its needed, and book reading and things like that.

On the other side something like espeak, is low quality, fast responding, high performance, but crappy sounding.

Its good for games without stories, documentation reading, email, brousing the web, doing administration and running virtual machines and things where I don't care what I am hearing or if it sounds good just that I am getting correct information.

I suppose with the powerfull system I have I could run vocaliser constantly but it may not be what I want all day long.

Pluss in a situation where something crashes or goes down or something breaks, I could be stuck with no speech because the net failed, or bit of windows went or something else fails.

The only way for me to get things back would either be a full reformat or killing configurations.

I have found that when I have relied on some stuff like this in the past that when it fails, you have nothing to fall back on.

A reformat fixes it as it always does, however as a result of being bitten to many times, for general purpose and we are talking general purpose, I would prefur crappy low quality but readable information rather than high quality readable but unstable information.

Also until recently any high quality anything is a performance drag.

I know several on xp and lower specked systems that can't afford any upgrades at all.

And even for those that do, they get the cheapest options which may be a few generations lower than current.

I have tried to run high quality on systems for general use and even when it has worked even if the system does not crash, even if it works floorlessly without me having to reformat to get speech back the load time is insane and so is responce time when I press a key.

I know with espeak that I am garanteed speech, crappy that it is.

And I am garanteed information in a readable format.

It may not sound that nice but I can read it.

In my line of work as admin and tester, I don't care if the information is sounding good or not just that I am getting it.

 If I am reading a book or playing an advanced flight game or something like that then of course I do.

I guess if your job is a translater or transcriber, high quality speech would be something you would have to use on a regular basis.

However you would have the hardware and software to support you or at least I do hope so.

I have friends some in the church, some in jobs that have never been able to afford the more expensive tech ever in their lives and get cast offs only.

Some are even used to it.

 

 

On 30/07/2019 4:48 AM, Josh Kennedy wrote:

I am going to buy the eloquence/vocalizer NVDA-addon on Friday. I hope that it will work with python3 when the time comes. Since I get extra social security in the united states now, these voices are easily affordable for me. I want the legal versions of voices because I am hoping that the legal eloquence and legal vocalizer will be updated to python3 whereas unsupported illegal stuff which is unsupported may just plain break and not work. Right now I am using sapi5 eloquence from codeFactory until this Friday when I can register the eloquence/vocalizer codeFactory addon. 


Re: NVDA moving to Python 3

Sarah k Alawami
 

Hi,

Yes. In fact, Windows OneCore was the first speech synthesizer to become compatible with Python 3.
Cheers,

Joseph



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of molly the blind tech lover
Sent: Monday, July 29, 2019 4:38 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3



Will the windows OneCore Microsoft Catherine voice work with python 3?



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> > On Behalf Of Shaun Everiss
Sent: Monday, July 29, 2019 1:25 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA moving to Python 3



I wouldn't bother with anny synth addons to be honest.

If you can afford it I'd use their sapi equivilants.

You are not locked down to one particular program, and they can be used anywhere you want.

While I have vocaliser, its a nice high quality but slow crappy synth for normal use.

Its good for gaming where its needed, and book reading and things like that.

On the other side something like espeak, is low quality, fast responding, high performance, but crappy sounding.

Its good for games without stories, documentation reading, email, brousing the web, doing administration and running virtual machines and things where I don't care what I am hearing or if it sounds good just that I am getting correct information.

I suppose with the powerfull system I have I could run vocaliser constantly but it may not be what I want all day long.

Pluss in a situation where something crashes or goes down or something breaks, I could be stuck with no speech because the net failed, or bit of windows went or something else fails.

The only way for me to get things back would either be a full reformat or killing configurations.

I have found that when I have relied on some stuff like this in the past that when it fails, you have nothing to fall back on.

A reformat fixes it as it always does, however as a result of being bitten to many times, for general purpose and we are talking general purpose, I would prefur crappy low quality but readable information rather than high quality readable but unstable information.

Also until recently any high quality anything is a performance drag.

I know several on xp and lower specked systems that can't afford any upgrades at all.

And even for those that do, they get the cheapest options which may be a few generations lower than current.

I have tried to run high quality on systems for general use and even when it has worked even if the system does not crash, even if it works floorlessly without me having to reformat to get speech back the load time is insane and so is responce time when I press a key.

I know with espeak that I am garanteed speech, crappy that it is.

And I am garanteed information in a readable format.

It may not sound that nice but I can read it.

In my line of work as admin and tester, I don't care if the information is sounding good or not just that I am getting it.

If I am reading a book or playing an advanced flight game or something like that then of course I do.

I guess if your job is a translater or transcriber, high quality speech would be something you would have to use on a regular basis.

However you would have the hardware and software to support you or at least I do hope so.

I have friends some in the church, some in jobs that have never been able to afford the more expensive tech ever in their lives and get cast offs only.

Some are even used to it.





On 30/07/2019 4:48 AM, Josh Kennedy wrote:

I am going to buy the eloquence/vocalizer NVDA-addon on Friday. I hope that it will work with python3 when the time comes. Since I get extra social security in the united states now, these voices are easily affordable for me. I want the legal versions of voices because I am hoping that the legal eloquence and legal vocalizer will be updated to python3 whereas unsupported illegal stuff which is unsupported may just plain break and not work. Right now I am using sapi5 eloquence from codeFactory until this Friday when I can register the eloquence/vocalizer codeFactory addon.





Re: NVDA moving to Python 3

Sarah k Alawami
 

Windows 1 core Katherine? I only have mark, david and ziera.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.
For stuff we sell, mac training materials and  tutorials go here.
and for hosting options go here
to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 29 Jul 2019, at 16:40, Joseph Lee wrote:

Hi,

Yes. In fact, Windows OneCore was the first speech synthesizer to become compatible with Python 3.
Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of molly the blind tech lover
Sent: Monday, July 29, 2019 4:38 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

Will the windows OneCore Microsoft Catherine voice work with python 3?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Monday, July 29, 2019 1:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA moving to Python 3

 

I wouldn't bother with anny synth addons to be honest.

If you can afford it I'd use their sapi equivilants.

You are not locked down to one particular program, and they can be used anywhere you want.

While I have vocaliser, its a nice high quality but slow crappy synth for normal use.

Its good for gaming where its needed, and book reading and things like that.

On the other side something like espeak, is low quality, fast responding, high performance, but crappy sounding.

Its good for games without stories, documentation reading, email, brousing the web, doing administration and running virtual machines and things where I don't care what I am hearing or if it sounds good just that I am getting correct information.

I suppose with the powerfull system I have I could run vocaliser constantly but it may not be what I want all day long.

Pluss in a situation where something crashes or goes down or something breaks, I could be stuck with no speech because the net failed, or bit of windows went or something else fails.

The only way for me to get things back would either be a full reformat or killing configurations.

I have found that when I have relied on some stuff like this in the past that when it fails, you have nothing to fall back on.

A reformat fixes it as it always does, however as a result of being bitten to many times, for general purpose and we are talking general purpose, I would prefur crappy low quality but readable information rather than high quality readable but unstable information.

Also until recently any high quality anything is a performance drag.

I know several on xp and lower specked systems that can't afford any upgrades at all.

And even for those that do, they get the cheapest options which may be a few generations lower than current.

I have tried to run high quality on systems for general use and even when it has worked even if the system does not crash, even if it works floorlessly without me having to reformat to get speech back the load time is insane and so is responce time when I press a key.

I know with espeak that I am garanteed speech, crappy that it is.

And I am garanteed information in a readable format.

It may not sound that nice but I can read it.

In my line of work as admin and tester, I don't care if the information is sounding good or not just that I am getting it.

 If I am reading a book or playing an advanced flight game or something like that then of course I do.

I guess if your job is a translater or transcriber, high quality speech would be something you would have to use on a regular basis.

However you would have the hardware and software to support you or at least I do hope so.

I have friends some in the church, some in jobs that have never been able to afford the more expensive tech ever in their lives and get cast offs only.

Some are even used to it.

 

 

On 30/07/2019 4:48 AM, Josh Kennedy wrote:

I am going to buy the eloquence/vocalizer NVDA-addon on Friday. I hope that it will work with python3 when the time comes. Since I get extra social security in the united states now, these voices are easily affordable for me. I want the legal versions of voices because I am hoping that the legal eloquence and legal vocalizer will be updated to python3 whereas unsupported illegal stuff which is unsupported may just plain break and not work. Right now I am using sapi5 eloquence from codeFactory until this Friday when I can register the eloquence/vocalizer codeFactory addon.