Date   

Re: Free Synthesizers

 

From a post I made on the Windows 10 for Screen Reader Users group, quoting a Microsoft technician who sometimes participates there with regard to adding languages, which also adds the voices for same if the language is noted as having text to speech as a feature:

As Shou-Ching Shilling stated earlier:  You can find the steps here: https://support.microsoft.com/en-us/help/22797

Yes, they work very well with NVDA.  As I noted earlier, most are OneCore synth voices, not SAPI 5 voices, so you do have to change your synthesizer in order to have most of them show up in the dropdown for choice of voice.
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    The psychology of adultery has been falsified by conventional morals, which assume, in monogamous countries, that attraction to one person cannot co-exist with a serious affection for another.  Everybody knows that this is untrue. . .

           ~ Bertrand Russell

 

 


Re: thunderbird addon

Don H
 

Thanks I have it now.

On 8/26/2018 6:26 PM, Kwork wrote:
Yes, it's called

Quick Folder Key Navigation

I got it using Thunderbird and it works well.

Travis

On 8/26/2018 2:33 PM, Don H wrote:
There is a Thunderbird addon that allows single letter movement between the folders in Thunderbird. Anyone know the name of the addon?









firefox ?

Danni
 

 
it updated on me yesterday grr had it set not to but apparently it doesn't much matter! anyway since it updated it's not loading pages I just get blank blank blank unless I hit windows escape and arrow over to the page then it will let me read but it's sluggish!
 
I noticed also that if I turn off brouse mode it will let me tab down and it will read though obviously not everything which makes me think it's a brouse mode issue on firefox but I have no clue for sure?
 
it's firefox 61.0.2 I believe
 


Re: Free Synthesizers

Kwork
 

Agreed. Windows 10 actually has better synths than my Windows 7 did, where I only had Microsoft Anna for SAPI 5. Now I have at least three choices, and possibly more, though I haven't figured out how to add them yet. I can't speak for Windows 8 as I never had it.

Travis

On 8/26/2018 11:09 AM, Jackie wrote:
Then Brian V's response was right on the money, wherever the money went lol.

On 8/26/18, kelby carlson <kelbycarlson@...> wrote:
Windows 10 unfortunately.
On Aug 26, 2018, at 1:09 PM, Jackie <abletec@...> wrote:

What version of Windows do you run, Kelby?

On 8/26/18, Brian Vogel <@britechguy> wrote:
MS SAPI 5 and One Core.

--

Brian *-* Windows 10 Home, 64-Bit, Version 1803, Build 17134

The psychology of adultery has been falsified by conventional
morals,
which assume, in monogamous countries, that attraction to one person
cannot
co-exist with a serious affection for another. Everybody knows that this
is
untrue. . .

~ Bertrand Russell



--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com




Re: thunderbird addon

Kwork
 

Yes, it's called

Quick Folder Key Navigation

I got it using Thunderbird and it works well.

Travis

On 8/26/2018 2:33 PM, Don H wrote:
There is a Thunderbird addon that allows single letter movement between the folders in Thunderbird.  Anyone know the name of the addon?






Re: thunderbird addon

 

From part of my "cheat sheet" sections that I give to clients:

IMPORTANT:  For those using Thunderbird with a screen reader I strongly suggest installing the Quick Folder Key Navigation extension.  You will only need to install this extension once for any instance of Thunderbird you might be using.  This allows you to jump from folder in the folder tree using first letter navigation to move between them.  Without it, this does not always work.   You will only need to install this extension once for any instance of Thunderbird you might be using.  If you are using JAWS or NVDA, searching for this add on within Thunderbird is quite simple:

·         Activate the Tools Menu (ALT+T), add-ons option (followed by A) and tab 3 times, at which point you should be on the Extensions Pane.  If you happen to land on any other pane then use Down Arrow (or Up Arrow) until you hear Extensions.

·         Tab 2 times, which lands you in the search all add-ons edit box. 

·         Then type in Quick Folder Key Navigation, hit enter, and wait a few seconds for the search to complete. 

·         Tab 5 times more gain focus on the list of results.  Then hit Down Arrow to start navigating the list.  Quick Folder Key Navigation should be the first result.

·         Tab 2 times to land on the Install button then hit enter.

·         After the install completes you need to exit Thunderbird and start it up again for this extension to become active

 

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

    The psychology of adultery has been falsified by conventional morals, which assume, in monogamous countries, that attraction to one person cannot co-exist with a serious affection for another.  Everybody knows that this is untrue. . .

           ~ Bertrand Russell

 

 


Re: Future of speech synth add ons

Abbie Taylor <abbietaylor945@...>
 

I know what you mean, Brian, about speech synthesizers only for use with one screen reader. I like the IVONA voices that I use occasionally with System Access, but I can't use them with NVDA.

Abbie Johnson Taylor, Author http://abbiescorner.wordpress.com
http://www.abbiejohnsontaylor.com
abbietaylor945@...
Order my new memoir at http://www.abbiejohnsontaylor.com/memoir.htm

--
Abbie Johnson Taylor, Author
http://www.abbiejohnsontaylor.com
http://abbiescorner.wordpress.com
abbietaylor945@...


Re: Free Synthesizers

Larry Silvermintz <silvermintz@...>
 

Hi Kalyb,
Get TruVoice (my favorite, and other classic SAPI 4&5 voices here:
www.bytecool.com/voices.htm

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of kelby
carlson
Sent: Sunday, August 26, 2018 12:44 PM
To: nvda@nvda.groups.io
Subject: [nvda] Free Synthesizers

What are some free synthesizers available for NVDA besides Espeak? I know
that things should be fine for awhile, but I want some alternatives and
can't really afford to pay for anything at the moment unfortunately.

-=-=


thunderbird addon

Don H
 

There is a Thunderbird addon that allows single letter movement between the folders in Thunderbird.  Anyone know the name of the addon?


Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

Marshall handheld Flax
 

One other note: while transitioning to Python 3 isn't optional, there is no limit to how much testing the community can provide before the Python 3 code becomes the production release.  Are there plans to organize the user community to provide additional and more-organized testing?

Thanks!

Marshall

On Sun, Aug 26, 2018 at 3:28 PM Joseph Lee <joseph.lee22590@...> wrote:

Hi Kelby,

I understand the sentiment expressed by you and others. What we saw with one particular add-on discussed throughout yesterday is just a taste of what’s to come in the future. The add-ons community is aware of the fact that Python 3 transition is a big migration, and I’ll remind add-on authors (including myself) to never forget users when we do move to Python 3 (this reminds me: I need to ask add-ons community to start contacting authors of add-ons that will exhibit problems once Python 3 transition takes place; a personal message to Ralph: I’d like to invite you to submit your add-ons for basic add-on review so they can show up on add-ons website for easier discoverability).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of kelby carlson
Sent: Sunday, August 26, 2018 12:15 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Well I definitely can't afford to update by the sound of this. NVDA is my work screen reader and I can't risk anything breaking. I share the frustration of others if this is going to cause such widespread problems.


On Aug 26, 2018, at 3:11 PM, Joseph Lee <joseph.lee22590@...> wrote:

Hi,

In the past, when Python 3 wasn’t under active development or deployed widely, NVDA source code was modified periodically to add features from various Python 2.x releases.

As for emulation: we’re talking about two completely different aspects of computing here: Python is a programming language, not an operating system. Emulation makes sense if Python was an operating system and had necessary infrastructure to run legacy code. However, being a programming language, it may not allow old assumptions to hold true in some cases (Unicode, for example). At least Python 3 interpreter will warn you if you’ve got code that depends on old assumptions, but it won’t correct it for you; in a way, you can get around it by using a compatibility layer (called “shim”), and one such compatibility layer will be included in NVDA 2018.3: the “six” module, and we got this for free as part of moving to wxPython 4.0.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Sunday, August 26, 2018 12:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Does that mean anything for the future?  How often is support stopped for old versions.  If this occurs once every roughly ten years, this could be a serious ongoing problem.  . 

 

Should the new Pytho have some sort of emulator to allow older code to run? 

 

Gene

----- Original Message -----

 

From: Joseph Lee

Sent: Sunday, August 26, 2018 1:51 PM

Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi,
Several important reasons come to my mind:
* Python 2 sunset date is approaching: On January 1, 2020, support for Python 2 will be terminated by Python Software Foundation (PSF), the main entity that defines and coordinates development of Python programming language. Although there might be "night lighting" efforts - longer support by third parties, but for all intents and purposes, as far as CPython is concerned, that is the sunset date.
* Unicode: Python 2 had ability to deal with Unicode and older text encoding mechanisms. Python 3 standardizes this around Unicode. With more characters being added to Unicode standard (the latest edition, version 11.0, adds emoji and characters from additional scripts around the world), coupled with globalization and internationalization of software projects, it became important to standardize around this.
* New possibilities: Python 3 introduces features that could be used by NVDA and its add-ons, including asynchronous I/O, more predictable thread switching mechanism, virtual Python environments (for isolating code from the outside world for testing and other scenarios) and many others.
* Easier source code level debugging: if you run NVDA from source code, you'll find you're using Windows 8 when in fact you might be running 8.1 or 10. Python 3 adds native support for Windows 10, which makes it easier for developers to add new features or test bug fixes for Windows 8.1 and 10 as well as on older Windows versions.

Of course, with change comes responsibilities to make sure old code works as intended (as much as possible), and every change has its upsides and downsides. At the moment some NVDA developers (including I) are researching possible issues people will encounter when we do move to Python 3.
Cheers,
Joseph


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Sunday, August 26, 2018 11:39 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

So I have to ask the question why change to the new python if it has the potential of messing things up?

On 8/26/2018 1:14 PM, Joseph Lee wrote:
> Hi,
>
> When I call espeak_Initialize when initializing Espeak from NVDA, I
> get an exception and Espeak can’t find phonetics table from a specific
> location. I will need to investigate this further, as being able to
> get at least one synthesizer running in Python 3 mode is a crucial
> milestone I hope to achieve soon.
>
> Cheers,
>
> Joseph
>
> *From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Reece
> H. Dunn
> *Sent:* Sunday, August 26, 2018 10:26 AM
> *To:* nvda@nvda.groups.io
> *Subject:* Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as
> Python 3
>
> On Sun, Aug 26, 2018 at 05:06 PM, Joseph Lee wrote:
>
>     Hi all,
>
>     For the last few hours, there has been a thread regarding
>     incompatibility of some add-ons and NVDA 2018.3, with some folks
>     claiming that speech synthesizers are not compatible. This
>     information is mostly false, and this may have been driven by
>     confusion regarding wxPython 4 versus Python 3.
>
>     wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version
>     4.0.3, a necessary milestone for the eventual migration to Python 3.
>     If an add-on uses attributes that are not found in newer wxPython
>     releases, they won’t load. Likewise, an add-on that exclusively uses
>     wxPython 4 material won’t work in older NVDA releases. At least some
>     GUI elements of speech synthesizer drivers are affected, and that’s
>     the reason why there has been an uproar regarding an important
>     add-on. Regarding speech synthesizer drivers and GUI issues, they
>     produce minor warnings, but apart from that, they are usable (but
>     not forever).
>
>     Python 3: Python is a programming language. Therefore, moving from
>     one version of a programming language to the next can be
>     challenging, especially if it introduces incompatible syntax and
>     throws away old internal assumptions. Python 2 to 3 migration will
>     go through both issues and much more, and research suggests that
>     many NVDA features and add-ons will be affected, including some
>     synthesizers the community uses (sorry, Espeak, you’re included in
>     this mix). Specifically, due to prevalence of Unicode, it’ll take
>     some time to come up with routines that will work with text
>     formatted as Unicode and other encodings, and unfortunately, some
>     speech synthesizers will insist on using ANSI format strings when in
>     fact Python 3 wants to read and write Unicode (Espeak is a notable
>     case).
>
> What is the issue/are the issues regarding espeak (I have experience
> converting Python 2 to 3 code)?
>
> Are you referring to espeak wanting UTF-8 (which is like/compatible
> with ANSI/ASCII strings), or issues with the way the NVDA espeak
> binding is written?
>
> NOTE: UTF-8, UTF-16, and UTF-32 are all different Unicode encodings.
> Espeak supports UTF-8 and UTF-16, but not UTF-32.
>
> Kind regards,
> Reece
>
>     In regards to add-ons, any add-on that deals with text processing
>     are affected (speech synthesizers, for example). Also, if they use
>     Python standard library (various Python modules), they need to take
>     note of differences between Python 2 and 3, especially in regards to
>     module and function renames (_winreg versus winreg, the former with
>     an underscore and the latter without).
>
>     A more general overview of what will it take to move NVDA to Python
>     3 can be found at:
>
>     https://github.com/nvaccess/nvda/issues/7105
>
>     Cheers,
>
>     Joseph
>
>








Re: DNS settings using NVDA under Windows 10

Jackie
 

This is actually in control panel under Network & Sharing Center.

On 8/26/18, Jason White via Groups.Io <jason=jasonjgw.net@groups.io> wrote:
https://www.windowscentral.com/how-change-your-pcs-dns-settings-windows-10



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dan Beaver
Sent: Sunday, August 26, 2018 4:05 PM
To: nvda@nvda.groups.io
Subject: [nvda] DNS settings using NVDA under Windows 10



Hi,



It has been recommended to me that I change some DNS settings on my laptop.
The instructions say to right click on the start list. Doing this just
brings me back to the beginning of the start screen where Cortana is.



How do I get to the DNS settings using NVDA on Windows 10?



Thanks.



Dan Beaver






--
Remember! Friends Help Friends Be Cybersafe
Jackie McBride
Helping Cybercrime Victims 1 Person at a Time
https://brighter-vision.com


Re: DNS settings using NVDA under Windows 10

Jason White
 

https://www.windowscentral.com/how-change-your-pcs-dns-settings-windows-10

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dan Beaver
Sent: Sunday, August 26, 2018 4:05 PM
To: nvda@nvda.groups.io
Subject: [nvda] DNS settings using NVDA under Windows 10

 

Hi,

 

It has been recommended to me that I change some DNS settings on my laptop.  The instructions say to right click on the start list.  Doing this just brings me back to the beginning of the start screen where Cortana is.

 

How do I get to the DNS settings using NVDA on Windows 10?

 

Thanks.

 

Dan Beaver


DNS settings using NVDA under Windows 10

Dan Beaver
 

Hi,


It has been recommended to me that I change some DNS settings on my laptop.  The instructions say to right click on the start list.  Doing this just brings me back to the beginning of the start screen where Cortana is.


How do I get to the DNS settings using NVDA on Windows 10?


Thanks.


Dan Beaver


Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi Kelby,

I understand the sentiment expressed by you and others. What we saw with one particular add-on discussed throughout yesterday is just a taste of what’s to come in the future. The add-ons community is aware of the fact that Python 3 transition is a big migration, and I’ll remind add-on authors (including myself) to never forget users when we do move to Python 3 (this reminds me: I need to ask add-ons community to start contacting authors of add-ons that will exhibit problems once Python 3 transition takes place; a personal message to Ralph: I’d like to invite you to submit your add-ons for basic add-on review so they can show up on add-ons website for easier discoverability).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of kelby carlson
Sent: Sunday, August 26, 2018 12:15 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Well I definitely can't afford to update by the sound of this. NVDA is my work screen reader and I can't risk anything breaking. I share the frustration of others if this is going to cause such widespread problems.


On Aug 26, 2018, at 3:11 PM, Joseph Lee <joseph.lee22590@...> wrote:

Hi,

In the past, when Python 3 wasn’t under active development or deployed widely, NVDA source code was modified periodically to add features from various Python 2.x releases.

As for emulation: we’re talking about two completely different aspects of computing here: Python is a programming language, not an operating system. Emulation makes sense if Python was an operating system and had necessary infrastructure to run legacy code. However, being a programming language, it may not allow old assumptions to hold true in some cases (Unicode, for example). At least Python 3 interpreter will warn you if you’ve got code that depends on old assumptions, but it won’t correct it for you; in a way, you can get around it by using a compatibility layer (called “shim”), and one such compatibility layer will be included in NVDA 2018.3: the “six” module, and we got this for free as part of moving to wxPython 4.0.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Sunday, August 26, 2018 12:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Does that mean anything for the future?  How often is support stopped for old versions.  If this occurs once every roughly ten years, this could be a serious ongoing problem.  . 

 

Should the new Pytho have some sort of emulator to allow older code to run? 

 

Gene

----- Original Message -----

 

From: Joseph Lee

Sent: Sunday, August 26, 2018 1:51 PM

Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi,
Several important reasons come to my mind:
* Python 2 sunset date is approaching: On January 1, 2020, support for Python 2 will be terminated by Python Software Foundation (PSF), the main entity that defines and coordinates development of Python programming language. Although there might be "night lighting" efforts - longer support by third parties, but for all intents and purposes, as far as CPython is concerned, that is the sunset date.
* Unicode: Python 2 had ability to deal with Unicode and older text encoding mechanisms. Python 3 standardizes this around Unicode. With more characters being added to Unicode standard (the latest edition, version 11.0, adds emoji and characters from additional scripts around the world), coupled with globalization and internationalization of software projects, it became important to standardize around this.
* New possibilities: Python 3 introduces features that could be used by NVDA and its add-ons, including asynchronous I/O, more predictable thread switching mechanism, virtual Python environments (for isolating code from the outside world for testing and other scenarios) and many others.
* Easier source code level debugging: if you run NVDA from source code, you'll find you're using Windows 8 when in fact you might be running 8.1 or 10. Python 3 adds native support for Windows 10, which makes it easier for developers to add new features or test bug fixes for Windows 8.1 and 10 as well as on older Windows versions.

Of course, with change comes responsibilities to make sure old code works as intended (as much as possible), and every change has its upsides and downsides. At the moment some NVDA developers (including I) are researching possible issues people will encounter when we do move to Python 3.
Cheers,
Joseph


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Sunday, August 26, 2018 11:39 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

So I have to ask the question why change to the new python if it has the potential of messing things up?

On 8/26/2018 1:14 PM, Joseph Lee wrote:
> Hi,
>
> When I call espeak_Initialize when initializing Espeak from NVDA, I
> get an exception and Espeak can’t find phonetics table from a specific
> location. I will need to investigate this further, as being able to
> get at least one synthesizer running in Python 3 mode is a crucial
> milestone I hope to achieve soon.
>
> Cheers,
>
> Joseph
>
> *From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Reece
> H. Dunn
> *Sent:* Sunday, August 26, 2018 10:26 AM
> *To:* nvda@nvda.groups.io
> *Subject:* Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as
> Python 3
>
> On Sun, Aug 26, 2018 at 05:06 PM, Joseph Lee wrote:
>
>     Hi all,
>
>     For the last few hours, there has been a thread regarding
>     incompatibility of some add-ons and NVDA 2018.3, with some folks
>     claiming that speech synthesizers are not compatible. This
>     information is mostly false, and this may have been driven by
>     confusion regarding wxPython 4 versus Python 3.
>
>     wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version
>     4.0.3, a necessary milestone for the eventual migration to Python 3.
>     If an add-on uses attributes that are not found in newer wxPython
>     releases, they won’t load. Likewise, an add-on that exclusively uses
>     wxPython 4 material won’t work in older NVDA releases. At least some
>     GUI elements of speech synthesizer drivers are affected, and that’s
>     the reason why there has been an uproar regarding an important
>     add-on. Regarding speech synthesizer drivers and GUI issues, they
>     produce minor warnings, but apart from that, they are usable (but
>     not forever).
>
>     Python 3: Python is a programming language. Therefore, moving from
>     one version of a programming language to the next can be
>     challenging, especially if it introduces incompatible syntax and
>     throws away old internal assumptions. Python 2 to 3 migration will
>     go through both issues and much more, and research suggests that
>     many NVDA features and add-ons will be affected, including some
>     synthesizers the community uses (sorry, Espeak, you’re included in
>     this mix). Specifically, due to prevalence of Unicode, it’ll take
>     some time to come up with routines that will work with text
>     formatted as Unicode and other encodings, and unfortunately, some
>     speech synthesizers will insist on using ANSI format strings when in
>     fact Python 3 wants to read and write Unicode (Espeak is a notable
>     case).
>
> What is the issue/are the issues regarding espeak (I have experience
> converting Python 2 to 3 code)?
>
> Are you referring to espeak wanting UTF-8 (which is like/compatible
> with ANSI/ASCII strings), or issues with the way the NVDA espeak
> binding is written?
>
> NOTE: UTF-8, UTF-16, and UTF-32 are all different Unicode encodings.
> Espeak supports UTF-8 and UTF-16, but not UTF-32.
>
> Kind regards,
> Reece
>
>     In regards to add-ons, any add-on that deals with text processing
>     are affected (speech synthesizers, for example). Also, if they use
>     Python standard library (various Python modules), they need to take
>     note of differences between Python 2 and 3, especially in regards to
>     module and function renames (_winreg versus winreg, the former with
>     an underscore and the latter without).
>
>     A more general overview of what will it take to move NVDA to Python
>     3 can be found at:
>
>     https://github.com/nvaccess/nvda/issues/7105
>
>     Cheers,
>
>     Joseph
>
>








Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

kelby carlson
 

Well I definitely can't afford to update by the sound of this. NVDA is my work screen reader and I can't risk anything breaking. I share the frustration of others if this is going to cause such widespread problems.


On Aug 26, 2018, at 3:11 PM, Joseph Lee <joseph.lee22590@...> wrote:

Hi,

In the past, when Python 3 wasn’t under active development or deployed widely, NVDA source code was modified periodically to add features from various Python 2.x releases.

As for emulation: we’re talking about two completely different aspects of computing here: Python is a programming language, not an operating system. Emulation makes sense if Python was an operating system and had necessary infrastructure to run legacy code. However, being a programming language, it may not allow old assumptions to hold true in some cases (Unicode, for example). At least Python 3 interpreter will warn you if you’ve got code that depends on old assumptions, but it won’t correct it for you; in a way, you can get around it by using a compatibility layer (called “shim”), and one such compatibility layer will be included in NVDA 2018.3: the “six” module, and we got this for free as part of moving to wxPython 4.0.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Sunday, August 26, 2018 12:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Does that mean anything for the future?  How often is support stopped for old versions.  If this occurs once every roughly ten years, this could be a serious ongoing problem.  . 

 

Should the new Pytho have some sort of emulator to allow older code to run? 

 

Gene

----- Original Message -----

 

From: Joseph Lee

Sent: Sunday, August 26, 2018 1:51 PM

Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi,
Several important reasons come to my mind:
* Python 2 sunset date is approaching: On January 1, 2020, support for Python 2 will be terminated by Python Software Foundation (PSF), the main entity that defines and coordinates development of Python programming language. Although there might be "night lighting" efforts - longer support by third parties, but for all intents and purposes, as far as CPython is concerned, that is the sunset date.
* Unicode: Python 2 had ability to deal with Unicode and older text encoding mechanisms. Python 3 standardizes this around Unicode. With more characters being added to Unicode standard (the latest edition, version 11.0, adds emoji and characters from additional scripts around the world), coupled with globalization and internationalization of software projects, it became important to standardize around this.
* New possibilities: Python 3 introduces features that could be used by NVDA and its add-ons, including asynchronous I/O, more predictable thread switching mechanism, virtual Python environments (for isolating code from the outside world for testing and other scenarios) and many others.
* Easier source code level debugging: if you run NVDA from source code, you'll find you're using Windows 8 when in fact you might be running 8.1 or 10. Python 3 adds native support for Windows 10, which makes it easier for developers to add new features or test bug fixes for Windows 8.1 and 10 as well as on older Windows versions.

Of course, with change comes responsibilities to make sure old code works as intended (as much as possible), and every change has its upsides and downsides. At the moment some NVDA developers (including I) are researching possible issues people will encounter when we do move to Python 3.
Cheers,
Joseph


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Sunday, August 26, 2018 11:39 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

So I have to ask the question why change to the new python if it has the potential of messing things up?

On 8/26/2018 1:14 PM, Joseph Lee wrote:
> Hi,
>
> When I call espeak_Initialize when initializing Espeak from NVDA, I
> get an exception and Espeak can’t find phonetics table from a specific
> location. I will need to investigate this further, as being able to
> get at least one synthesizer running in Python 3 mode is a crucial
> milestone I hope to achieve soon.
>
> Cheers,
>
> Joseph
>
> *From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Reece
> H. Dunn
> *Sent:* Sunday, August 26, 2018 10:26 AM
> *To:* nvda@nvda.groups.io
> *Subject:* Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as
> Python 3
>
> On Sun, Aug 26, 2018 at 05:06 PM, Joseph Lee wrote:
>
>     Hi all,
>
>     For the last few hours, there has been a thread regarding
>     incompatibility of some add-ons and NVDA 2018.3, with some folks
>     claiming that speech synthesizers are not compatible. This
>     information is mostly false, and this may have been driven by
>     confusion regarding wxPython 4 versus Python 3.
>
>     wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version
>     4.0.3, a necessary milestone for the eventual migration to Python 3.
>     If an add-on uses attributes that are not found in newer wxPython
>     releases, they won’t load. Likewise, an add-on that exclusively uses
>     wxPython 4 material won’t work in older NVDA releases. At least some
>     GUI elements of speech synthesizer drivers are affected, and that’s
>     the reason why there has been an uproar regarding an important
>     add-on. Regarding speech synthesizer drivers and GUI issues, they
>     produce minor warnings, but apart from that, they are usable (but
>     not forever).
>
>     Python 3: Python is a programming language. Therefore, moving from
>     one version of a programming language to the next can be
>     challenging, especially if it introduces incompatible syntax and
>     throws away old internal assumptions. Python 2 to 3 migration will
>     go through both issues and much more, and research suggests that
>     many NVDA features and add-ons will be affected, including some
>     synthesizers the community uses (sorry, Espeak, you’re included in
>     this mix). Specifically, due to prevalence of Unicode, it’ll take
>     some time to come up with routines that will work with text
>     formatted as Unicode and other encodings, and unfortunately, some
>     speech synthesizers will insist on using ANSI format strings when in
>     fact Python 3 wants to read and write Unicode (Espeak is a notable
>     case).
>
> What is the issue/are the issues regarding espeak (I have experience
> converting Python 2 to 3 code)?
>
> Are you referring to espeak wanting UTF-8 (which is like/compatible
> with ANSI/ASCII strings), or issues with the way the NVDA espeak
> binding is written?
>
> NOTE: UTF-8, UTF-16, and UTF-32 are all different Unicode encodings.
> Espeak supports UTF-8 and UTF-16, but not UTF-32.
>
> Kind regards,
> Reece
>
>     In regards to add-ons, any add-on that deals with text processing
>     are affected (speech synthesizers, for example). Also, if they use
>     Python standard library (various Python modules), they need to take
>     note of differences between Python 2 and 3, especially in regards to
>     module and function renames (_winreg versus winreg, the former with
>     an underscore and the latter without).
>
>     A more general overview of what will it take to move NVDA to Python
>     3 can be found at:
>
>     https://github.com/nvaccess/nvda/issues/7105
>
>     Cheers,
>
>     Joseph
>
>







Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi,

In the past, when Python 3 wasn’t under active development or deployed widely, NVDA source code was modified periodically to add features from various Python 2.x releases.

As for emulation: we’re talking about two completely different aspects of computing here: Python is a programming language, not an operating system. Emulation makes sense if Python was an operating system and had necessary infrastructure to run legacy code. However, being a programming language, it may not allow old assumptions to hold true in some cases (Unicode, for example). At least Python 3 interpreter will warn you if you’ve got code that depends on old assumptions, but it won’t correct it for you; in a way, you can get around it by using a compatibility layer (called “shim”), and one such compatibility layer will be included in NVDA 2018.3: the “six” module, and we got this for free as part of moving to wxPython 4.0.3.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Sunday, August 26, 2018 12:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Does that mean anything for the future?  How often is support stopped for old versions.  If this occurs once every roughly ten years, this could be a serious ongoing problem.  . 

 

Should the new Pytho have some sort of emulator to allow older code to run? 

 

Gene

----- Original Message -----

 

From: Joseph Lee

Sent: Sunday, August 26, 2018 1:51 PM

Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi,
Several important reasons come to my mind:
* Python 2 sunset date is approaching: On January 1, 2020, support for Python 2 will be terminated by Python Software Foundation (PSF), the main entity that defines and coordinates development of Python programming language. Although there might be "night lighting" efforts - longer support by third parties, but for all intents and purposes, as far as CPython is concerned, that is the sunset date.
* Unicode: Python 2 had ability to deal with Unicode and older text encoding mechanisms. Python 3 standardizes this around Unicode. With more characters being added to Unicode standard (the latest edition, version 11.0, adds emoji and characters from additional scripts around the world), coupled with globalization and internationalization of software projects, it became important to standardize around this.
* New possibilities: Python 3 introduces features that could be used by NVDA and its add-ons, including asynchronous I/O, more predictable thread switching mechanism, virtual Python environments (for isolating code from the outside world for testing and other scenarios) and many others.
* Easier source code level debugging: if you run NVDA from source code, you'll find you're using Windows 8 when in fact you might be running 8.1 or 10. Python 3 adds native support for Windows 10, which makes it easier for developers to add new features or test bug fixes for Windows 8.1 and 10 as well as on older Windows versions.

Of course, with change comes responsibilities to make sure old code works as intended (as much as possible), and every change has its upsides and downsides. At the moment some NVDA developers (including I) are researching possible issues people will encounter when we do move to Python 3.
Cheers,
Joseph


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Sunday, August 26, 2018 11:39 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

So I have to ask the question why change to the new python if it has the potential of messing things up?

On 8/26/2018 1:14 PM, Joseph Lee wrote:
> Hi,
>
> When I call espeak_Initialize when initializing Espeak from NVDA, I
> get an exception and Espeak can’t find phonetics table from a specific
> location. I will need to investigate this further, as being able to
> get at least one synthesizer running in Python 3 mode is a crucial
> milestone I hope to achieve soon.
>
> Cheers,
>
> Joseph
>
> *From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Reece
> H. Dunn
> *Sent:* Sunday, August 26, 2018 10:26 AM
> *To:* nvda@nvda.groups.io
> *Subject:* Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as
> Python 3
>
> On Sun, Aug 26, 2018 at 05:06 PM, Joseph Lee wrote:
>
>     Hi all,
>
>     For the last few hours, there has been a thread regarding
>     incompatibility of some add-ons and NVDA 2018.3, with some folks
>     claiming that speech synthesizers are not compatible. This
>     information is mostly false, and this may have been driven by
>     confusion regarding wxPython 4 versus Python 3.
>
>     wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version
>     4.0.3, a necessary milestone for the eventual migration to Python 3.
>     If an add-on uses attributes that are not found in newer wxPython
>     releases, they won’t load. Likewise, an add-on that exclusively uses
>     wxPython 4 material won’t work in older NVDA releases. At least some
>     GUI elements of speech synthesizer drivers are affected, and that’s
>     the reason why there has been an uproar regarding an important
>     add-on. Regarding speech synthesizer drivers and GUI issues, they
>     produce minor warnings, but apart from that, they are usable (but
>     not forever).
>
>     Python 3: Python is a programming language. Therefore, moving from
>     one version of a programming language to the next can be
>     challenging, especially if it introduces incompatible syntax and
>     throws away old internal assumptions. Python 2 to 3 migration will
>     go through both issues and much more, and research suggests that
>     many NVDA features and add-ons will be affected, including some
>     synthesizers the community uses (sorry, Espeak, you’re included in
>     this mix). Specifically, due to prevalence of Unicode, it’ll take
>     some time to come up with routines that will work with text
>     formatted as Unicode and other encodings, and unfortunately, some
>     speech synthesizers will insist on using ANSI format strings when in
>     fact Python 3 wants to read and write Unicode (Espeak is a notable
>     case).
>
> What is the issue/are the issues regarding espeak (I have experience
> converting Python 2 to 3 code)?
>
> Are you referring to espeak wanting UTF-8 (which is like/compatible
> with ANSI/ASCII strings), or issues with the way the NVDA espeak
> binding is written?
>
> NOTE: UTF-8, UTF-16, and UTF-32 are all different Unicode encodings.
> Espeak supports UTF-8 and UTF-16, but not UTF-32.
>
> Kind regards,
> Reece
>
>     In regards to add-ons, any add-on that deals with text processing
>     are affected (speech synthesizers, for example). Also, if they use
>     Python standard library (various Python modules), they need to take
>     note of differences between Python 2 and 3, especially in regards to
>     module and function renames (_winreg versus winreg, the former with
>     an underscore and the latter without).
>
>     A more general overview of what will it take to move NVDA to Python
>     3 can be found at:
>
>     https://github.com/nvaccess/nvda/issues/7105
>
>     Cheers,
>
>     Joseph
>
>







Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

Gene
 

Does that mean anything for the future?  How often is support stopped for old versions.  If this occurs once every roughly ten years, this could be a serious ongoing problem.  . 
 
Should the new Pytho have some sort of emulator to allow older code to run? 
 
Gene
----- Original Message -----

From: Joseph Lee
Sent: Sunday, August 26, 2018 1:51 PM
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

Hi,
Several important reasons come to my mind:
* Python 2 sunset date is approaching: On January 1, 2020, support for Python 2 will be terminated by Python Software Foundation (PSF), the main entity that defines and coordinates development of Python programming language. Although there might be "night lighting" efforts - longer support by third parties, but for all intents and purposes, as far as CPython is concerned, that is the sunset date.
* Unicode: Python 2 had ability to deal with Unicode and older text encoding mechanisms. Python 3 standardizes this around Unicode. With more characters being added to Unicode standard (the latest edition, version 11.0, adds emoji and characters from additional scripts around the world), coupled with globalization and internationalization of software projects, it became important to standardize around this.
* New possibilities: Python 3 introduces features that could be used by NVDA and its add-ons, including asynchronous I/O, more predictable thread switching mechanism, virtual Python environments (for isolating code from the outside world for testing and other scenarios) and many others.
* Easier source code level debugging: if you run NVDA from source code, you'll find you're using Windows 8 when in fact you might be running 8.1 or 10. Python 3 adds native support for Windows 10, which makes it easier for developers to add new features or test bug fixes for Windows 8.1 and 10 as well as on older Windows versions.

Of course, with change comes responsibilities to make sure old code works as intended (as much as possible), and every change has its upsides and downsides. At the moment some NVDA developers (including I) are researching possible issues people will encounter when we do move to Python 3.
Cheers,
Joseph


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Sunday, August 26, 2018 11:39 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

So I have to ask the question why change to the new python if it has the potential of messing things up?

On 8/26/2018 1:14 PM, Joseph Lee wrote:
> Hi,
>
> When I call espeak_Initialize when initializing Espeak from NVDA, I
> get an exception and Espeak can’t find phonetics table from a specific
> location. I will need to investigate this further, as being able to
> get at least one synthesizer running in Python 3 mode is a crucial
> milestone I hope to achieve soon.
>
> Cheers,
>
> Joseph
>
> *From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Reece
> H. Dunn
> *Sent:* Sunday, August 26, 2018 10:26 AM
> *To:* nvda@nvda.groups.io
> *Subject:* Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as
> Python 3
>
> On Sun, Aug 26, 2018 at 05:06 PM, Joseph Lee wrote:
>
>     Hi all,
>
>     For the last few hours, there has been a thread regarding
>     incompatibility of some add-ons and NVDA 2018.3, with some folks
>     claiming that speech synthesizers are not compatible. This
>     information is mostly false, and this may have been driven by
>     confusion regarding wxPython 4 versus Python 3.
>
>     wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version
>     4.0.3, a necessary milestone for the eventual migration to Python 3.
>     If an add-on uses attributes that are not found in newer wxPython
>     releases, they won’t load. Likewise, an add-on that exclusively uses
>     wxPython 4 material won’t work in older NVDA releases. At least some
>     GUI elements of speech synthesizer drivers are affected, and that’s
>     the reason why there has been an uproar regarding an important
>     add-on. Regarding speech synthesizer drivers and GUI issues, they
>     produce minor warnings, but apart from that, they are usable (but
>     not forever).
>
>     Python 3: Python is a programming language. Therefore, moving from
>     one version of a programming language to the next can be
>     challenging, especially if it introduces incompatible syntax and
>     throws away old internal assumptions. Python 2 to 3 migration will
>     go through both issues and much more, and research suggests that
>     many NVDA features and add-ons will be affected, including some
>     synthesizers the community uses (sorry, Espeak, you’re included in
>     this mix). Specifically, due to prevalence of Unicode, it’ll take
>     some time to come up with routines that will work with text
>     formatted as Unicode and other encodings, and unfortunately, some
>     speech synthesizers will insist on using ANSI format strings when in
>     fact Python 3 wants to read and write Unicode (Espeak is a notable
>     case).
>
> What is the issue/are the issues regarding espeak (I have experience
> converting Python 2 to 3 code)?
>
> Are you referring to espeak wanting UTF-8 (which is like/compatible
> with ANSI/ASCII strings), or issues with the way the NVDA espeak
> binding is written?
>
> NOTE: UTF-8, UTF-16, and UTF-32 are all different Unicode encodings.
> Espeak supports UTF-8 and UTF-16, but not UTF-32.
>
> Kind regards,
> Reece
>
>     In regards to add-ons, any add-on that deals with text processing
>     are affected (speech synthesizers, for example). Also, if they use
>     Python standard library (various Python modules), they need to take
>     note of differences between Python 2 and 3, especially in regards to
>     module and function renames (_winreg versus winreg, the former with
>     an underscore and the latter without).
>
>     A more general overview of what will it take to move NVDA to Python
>     3 can be found at:
>
>     https://github.com/nvaccess/nvda/issues/7105
>
>     Cheers,
>
>     Joseph
>
>








Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

Sarah k Alawami
 

Yep that’s normal behavior for this person. I got reported and called a doosh bag for calling him out publicly on twitter, but he is showing the same behavior again.

Take care all

On 26 Aug 2018, at 11:47, The Wolf wrote:

he never responds to emails either

On 8/26/2018 9:58 AM, Sarah k Alawami wrote:

I have to agree. I’ve seen this behavior with one of the devs wiht a lot of his programs, the qube anybody, and the thing he did for pandora for windows? Yeah. So frankly I’m not surprised


I do agree this should be a part of nvda’s core and if we don’t use it, we don’t have to. And eah this dev has broken other things with gpl with his apps as well, so again, not surprised. Good apps but horable bedside manners?

Take care

On 26 Aug 2018, at 4:48, Noah Carver via Groups.Io wrote:

This is not the official server. Someone studied the connection between remote and the official server and developed an unofficial server so that others could host NVDA remote.  I’ve written to the creators of this addon via email regarding the violations of GPL, however it appears that the creators of this addon don’t care. Therefore, I feel it would be in the interest of both NVAccess and the community at large for NVAccess to take possession of all code associated with the remote addon and incorporate it into NVDA core.

On Aug 26, 2018, at 05:45, dingpengyu <dingpengyu06@...> wrote:

-- 
check out my song on youtube
https://youtu.be/YeWgx2LRu7Y


Re: NVDA 2018.3: wxPython 4 is not the same thing as Python 3

 

Hi,
Several important reasons come to my mind:
* Python 2 sunset date is approaching: On January 1, 2020, support for Python 2 will be terminated by Python Software Foundation (PSF), the main entity that defines and coordinates development of Python programming language. Although there might be "night lighting" efforts - longer support by third parties, but for all intents and purposes, as far as CPython is concerned, that is the sunset date.
* Unicode: Python 2 had ability to deal with Unicode and older text encoding mechanisms. Python 3 standardizes this around Unicode. With more characters being added to Unicode standard (the latest edition, version 11.0, adds emoji and characters from additional scripts around the world), coupled with globalization and internationalization of software projects, it became important to standardize around this.
* New possibilities: Python 3 introduces features that could be used by NVDA and its add-ons, including asynchronous I/O, more predictable thread switching mechanism, virtual Python environments (for isolating code from the outside world for testing and other scenarios) and many others.
* Easier source code level debugging: if you run NVDA from source code, you'll find you're using Windows 8 when in fact you might be running 8.1 or 10. Python 3 adds native support for Windows 10, which makes it easier for developers to add new features or test bug fixes for Windows 8.1 and 10 as well as on older Windows versions.

Of course, with change comes responsibilities to make sure old code works as intended (as much as possible), and every change has its upsides and downsides. At the moment some NVDA developers (including I) are researching possible issues people will encounter when we do move to Python 3.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Sunday, August 26, 2018 11:39 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3

So I have to ask the question why change to the new python if it has the potential of messing things up?

On 8/26/2018 1:14 PM, Joseph Lee wrote:
Hi,

When I call espeak_Initialize when initializing Espeak from NVDA, I
get an exception and Espeak can’t find phonetics table from a specific
location. I will need to investigate this further, as being able to
get at least one synthesizer running in Python 3 mode is a crucial
milestone I hope to achieve soon.

Cheers,

Joseph

*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Reece
H. Dunn
*Sent:* Sunday, August 26, 2018 10:26 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as
Python 3

On Sun, Aug 26, 2018 at 05:06 PM, Joseph Lee wrote:

Hi all,

For the last few hours, there has been a thread regarding
incompatibility of some add-ons and NVDA 2018.3, with some folks
claiming that speech synthesizers are not compatible. This
information is mostly false, and this may have been driven by
confusion regarding wxPython 4 versus Python 3.

wxPython: NVDA 2018.3 will upgrade wxPython GUI toolkit to version
4.0.3, a necessary milestone for the eventual migration to Python 3.
If an add-on uses attributes that are not found in newer wxPython
releases, they won’t load. Likewise, an add-on that exclusively uses
wxPython 4 material won’t work in older NVDA releases. At least some
GUI elements of speech synthesizer drivers are affected, and that’s
the reason why there has been an uproar regarding an important
add-on. Regarding speech synthesizer drivers and GUI issues, they
produce minor warnings, but apart from that, they are usable (but
not forever).

Python 3: Python is a programming language. Therefore, moving from
one version of a programming language to the next can be
challenging, especially if it introduces incompatible syntax and
throws away old internal assumptions. Python 2 to 3 migration will
go through both issues and much more, and research suggests that
many NVDA features and add-ons will be affected, including some
synthesizers the community uses (sorry, Espeak, you’re included in
this mix). Specifically, due to prevalence of Unicode, it’ll take
some time to come up with routines that will work with text
formatted as Unicode and other encodings, and unfortunately, some
speech synthesizers will insist on using ANSI format strings when in
fact Python 3 wants to read and write Unicode (Espeak is a notable
case).

What is the issue/are the issues regarding espeak (I have experience
converting Python 2 to 3 code)?

Are you referring to espeak wanting UTF-8 (which is like/compatible
with ANSI/ASCII strings), or issues with the way the NVDA espeak
binding is written?

NOTE: UTF-8, UTF-16, and UTF-32 are all different Unicode encodings.
Espeak supports UTF-8 and UTF-16, but not UTF-32.

Kind regards,
Reece

In regards to add-ons, any add-on that deals with text processing
are affected (speech synthesizers, for example). Also, if they use
Python standard library (various Python modules), they need to take
note of differences between Python 2 and 3, especially in regards to
module and function renames (_winreg versus winreg, the former with
an underscore and the latter without).

A more general overview of what will it take to move NVDA to Python
3 can be found at:

https://github.com/nvaccess/nvda/issues/7105

Cheers,

Joseph


Re: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

 

he never responds to emails either

On 8/26/2018 9:58 AM, Sarah k Alawami wrote:

I have to agree. I’ve seen this behavior with one of the devs wiht a lot of his programs, the qube anybody, and the thing he did for pandora for windows? Yeah. So frankly I’m not surprised


I do agree this should be a part of nvda’s core and if we don’t use it, we don’t have to. And eah this dev has broken other things with gpl with his apps as well, so again, not surprised. Good apps but horable bedside manners?

Take care

On 26 Aug 2018, at 4:48, Noah Carver via Groups.Io wrote:

This is not the official server. Someone studied the connection between remote and the official server and developed an unofficial server so that others could host NVDA remote.  I’ve written to the creators of this addon via email regarding the violations of GPL, however it appears that the creators of this addon don’t care. Therefore, I feel it would be in the interest of both NVAccess and the community at large for NVAccess to take possession of all code associated with the remote addon and incorporate it into NVDA core.

On Aug 26, 2018, at 05:45, dingpengyu <dingpengyu06@...> wrote:

-- 
check out my song on youtube
https://youtu.be/YeWgx2LRu7Y