Date   

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

Brian's Mail list account
 

I already asked this, but of course as the developers of the language do what they like \I'd imagine making something like this would be very hard and might allow people to not use the more modern system.
More to the point though non support of a language does not mean its death. It just means no updates and we are now using it and it has stayed very much the same for a long time, so security wise, will it matter how many people use the older version?
Idealistically of course a rewrite is required for all the stated reasons, but where do you fit the user into the equation. I would suggest myself that a stable latest version be always available in python 2.7 for at least two iterations of the Python 3 version, as finding those annoying little problems is not going to be fast I think. It would also be handy to talk to other projects who have made such a transition and see what their experiences have been. I bet there are still bugs in the new version of the language, so work around are probably known about in the community.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gene" <gsasner@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, August 26, 2018 8:03 PM
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
To: nvda@nvda.groups.io
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

Brian's Mail list account
 

Yes but from what I read at the start, and have not looked of late, the fixes will be done for commonly used Synths, but in the case of externally sourced ones this will have to mean the cooperation of those companies in rewriting their code.
Espeak will, I imagine be fixable. I like Espeak, as its fast and does not have the problems of real voices ie garbled at speed and the terrible lisp of Eloquence for uk English listeners.

Incidentally, I suppose as long as an add on makes no use of the gui for the wx4 versions of nvda, then most things will still work. So add ons with their own set ups etc will be the issue.
Incidentally for all our xp readers, Toolbar Explorer will run on that older nvda version for that system. I tried it last night.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@groups.io>
Sent: Sunday, August 26, 2018 5:06 PM
Subject: [nvda] NVDA 2018.3: wxPython 4 is not the same thing as Python 3


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).



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: Future of speech synth add ons

Chris
 

Kerching kerching kerching :D

 

 

From: Brian's Mail list account via Groups.Io
Sent: 27 August 2018 09:41
To: nvda@nvda.groups.io
Subject: Re: [nvda] Future of speech synth add ons

 

Why, I am pretty sure  the next release of nvda will work as mentioned in

the recent thread on here. I would hope that the developers of synth drivers

will be kept well up to speed before bridges are burned on python 2.7 in

favour of a later version.

It would surely be silly not to do this from a userbase point of view.

Brian

 

bglists@...

Sent via blueyonder.

Please address personal E-mail to:-

briang1@..., putting 'Brian Gaff'

in the display name field.

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

From: "Abbie Taylor" <abbietaylor945@...>

To: <nvda@nvda.groups.io>

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

Subject: Re: [nvda] Future of speech synth add ons

 

 

>I also use Vocalizer from Code Factory, so it looks like I, too, will have

>to find another synthesizer when the new NVDA update comes out. How can I

>get more One-Core voices? The only options I see in the preferences are

>David, Zera, and Mark.

> 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: off topic windows live mail - desperate

Brian's Mail list account
 

Yes the I found for example it was perfectly possible for some word documents when loaded into Jart to print out with some Greek or similar characters for no obvious reason at all.

It might be good to look for print problems in other software and update drivers of find a font that works. If on the other hand the characters are in fact like this on screen then it could be that the version of live mail has some settings wrong, ie set to serilic windows or something daft.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Brian Vogel" <britechguy@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, August 26, 2018 4:29 PM
Subject: Re: [nvda] off topic windows live mail - desperate


I guess the first question is what font is she using?

The defaults under WLM tend to work "out of the box".

I am suspecting this is actually something utterly independent of WLM, as I've encountered instances of printers with a character set mind of their own on a couple of occasions over the decades. My first test is to see if the printer behaves similarly from other programs, such as Notepad or Word.

--

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

Brian's Mail list account
 

Why, I am pretty sure the next release of nvda will work as mentioned in the recent thread on here. I would hope that the developers of synth drivers will be kept well up to speed before bridges are burned on python 2.7 in favour of a later version.
It would surely be silly not to do this from a userbase point of view.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Abbie Taylor" <abbietaylor945@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, August 26, 2018 3:51 PM
Subject: Re: [nvda] Future of speech synth add ons


I also use Vocalizer from Code Factory, so it looks like I, too, will have to find another synthesizer when the new NVDA update comes out. How can I get more One-Core voices? The only options I see in the preferences are David, Zera, and Mark.

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: Words and lines repeat in the Mail app!

Chris
 

Yes, same issue here as well, along with no speech output after using the mail app on some occasions but not all the time

 

 

From: David Moore
Sent: 27 August 2018 01:03
To: nvda@nvda.groups.io
Subject: [nvda] Words and lines repeat in the Mail app!

 

Hi all!

I hope you can help me.

Lately, in the mail app, if I use the arrow keys to read word by word, or line by line, the same word, letter, or line will repeat, even if I am on another line, letter, or word.

When I try to correct my emails, I have to use the text commands to read with the review cursor, and press the command to bring the focus to the review cursor, and make the correction.

My messages read fine with the review cursor, but it is getting almost impossible to read my message with the arrow keys and the focus.

I am using latest alpha build, latest Mail app update, and Windows 1803.

It is the win10 mail app.

I have tried turning off my add-ons except for Windows app essentials, but it does not help.

Let me know if any of you are having this problem with the Win10 mail app with NVDA.

David Moore

 

Sent from Mail for Windows 10

 

 


Re: Free Synthesizers

 

windows 8 used the same voices that windows 10 does but am not sure if the mark voice was added when windows10 came out or if it was present on windows8

I personally didn't use windows8 much so I can not be 100 percent sure.

On 8/26/2018 4:29 PM, Kwork wrote:

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




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


Re: Hi All, This is Michael Munn and I'm also an user of the NVDA Screen Reader. I have been using NVDA for 2 years now. Technology change rapetly now days so I need to master more than one screen reader. I’m also !a JAWS user. I have been using JAW

Gene
 

You put your message in the subject line. 
 
Gene

----- Original Message -----
Sent: Sunday, August 26, 2018 8:59 PM
Subject: [nvda] Hi All, This is Michael Munn and I'm also an user of the NVDA Screen Reader. I have been using NVDA for 2 years now. Technology change rapetly now days so I need to master more than one screen reader. I’m also !a JAWS user. I have been using JAWS for 3 years. I heard about this list from the NVDA Anual conference in June of this year. NVDA is a good Screen Reader Thanks and have a nice evening. Best Regards michael Munn


"If a person must be blind, it is better to be blind in Iowa than anywhere else in the nation or in the world."
Harold Russell, 
Des Moines 
1968
Michael Munn
Member:
Virginia Association of Blind Student
Delegate:  
Virginia Association of Blind Student
Student of:
Hadley Institute for the Blind
Email address:



Hi All, This is Michael Munn and I'm also an user of the NVDA Screen Reader. I have been using NVDA for 2 years now. Technology change rapetly now days so I need to master more than one screen reader. I’m also !a JAWS user. I have been using JAWS for 3 years. I heard about this list from the NVDA Anual conference in June of this year. NVDA is a good Screen Reader Thanks and have a nice evening. Best Regards michael Munn

Michael Munn
 


"If a person must be blind, it is better to be blind in Iowa than anywhere else in the nation or in the world."
Harold Russell, 
Des Moines 
1968
Michael Munn
Member:
Virginia Association of Blind Student
Delegate:  
Virginia Association of Blind Student
Student of:
Hadley Institute for the Blind
Email address:



Re: strange behavior with add on updater

Ian Westerland
 

Thank you Joseph. It is a very handy tool and I wouldn't be without it.

Cheers.


Ian

On 8/27/2018 2:08 PM, Joseph Lee wrote:
Hi,
And the solution has been revealed in the form of Revision A for August 25th snapshot, with the bug caused by a wxPython attribute that isn't available in NVDA 2018.2.1. I'm about to upload August 27th snapshot that not only includes a fix for this (for those who haven't applied revision A), but also will check add-on checkboxes by default so you can update add-ons.
Note that the new build will require manual install for those using August 25th build (not revision A).
Cheers,
Joseph
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ian Westerland
Sent: Sunday, August 26, 2018 8:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] strange behavior with add on updater
Hello Andy. I had the same issue Tony reported and am glad it installed for you. This is the first time I have had any trouble. No doubt all will be revealed.
Ian Westerland
On 8/27/2018 1:49 PM, Andy wrote:
When i launched NVDA yesterday the update dialogue came up and i had
no problem installing the update.

Andy

----- Original Message ----- From: "Ian Westerland"
<iwesterl@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, August 26, 2018 8:44 PM
Subject: Re: [nvda] strange behavior with add on updater


Hi Tony. I was about to write to the list on the same subject. At
first I wondered if there was some kind of bug when the notification
appeared several hours apart but I am convinced it isn't a bug.

Looking forward to the answer and a possible remedy.

Ian Westerland




On 8/27/2018 1:40 PM, Tony Ballou wrote:
Howdy,


The latest version of the add on updater came out yesterday. When I
check the option to install it, the only button that shows up is a
close button. I went through the dialog box, and the only things that
are in there are the checkbox to select the update and the close button.
What's up with that, where's the install button for the darn thing?
Slightly perplexed.


Tony









Re: strange behavior with add on updater

 

Hi,
And the solution has been revealed in the form of Revision A for August 25th snapshot, with the bug caused by a wxPython attribute that isn't available in NVDA 2018.2.1. I'm about to upload August 27th snapshot that not only includes a fix for this (for those who haven't applied revision A), but also will check add-on checkboxes by default so you can update add-ons.
Note that the new build will require manual install for those using August 25th build (not revision A).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ian Westerland
Sent: Sunday, August 26, 2018 8:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] strange behavior with add on updater



Hello Andy. I had the same issue Tony reported and am glad it installed for you. This is the first time I have had any trouble. No doubt all will be revealed.

Ian Westerland





On 8/27/2018 1:49 PM, Andy wrote:
When i launched NVDA yesterday the update dialogue came up and i had
no problem installing the update.

Andy

----- Original Message ----- From: "Ian Westerland"
<iwesterl@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, August 26, 2018 8:44 PM
Subject: Re: [nvda] strange behavior with add on updater


Hi Tony. I was about to write to the list on the same subject. At
first I wondered if there was some kind of bug when the notification
appeared several hours apart but I am convinced it isn't a bug.

Looking forward to the answer and a possible remedy.

Ian Westerland




On 8/27/2018 1:40 PM, Tony Ballou wrote:
Howdy,


The latest version of the add on updater came out yesterday. When I
check the option to install it, the only button that shows up is a
close button. I went through the dialog box, and the only things that
are in there are the checkbox to select the update and the close button.
What's up with that, where's the install button for the darn thing?
Slightly perplexed.


Tony









Re: strange behavior with add on updater

Ian Westerland
 

Hello Andy. I had the same issue Tony reported and am glad it installed for you. This is the first time I have had any trouble. No doubt all will be revealed.

Ian Westerland

On 8/27/2018 1:49 PM, Andy wrote:
When i launched NVDA yesterday the update dialogue came up and i had no problem installing the update.
Andy
----- Original Message ----- From: "Ian Westerland" <iwesterl@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, August 26, 2018 8:44 PM
Subject: Re: [nvda] strange behavior with add on updater
Hi Tony.  I was about to write to the list on the same subject.  At
first I wondered if there was some kind of bug when the notification
appeared several hours apart but I am convinced it isn't a bug.
Looking forward to the answer and a possible remedy.
Ian Westerland
On 8/27/2018 1:40 PM, Tony Ballou wrote:
Howdy,


The latest version of the add on updater came out yesterday. When I
check the option to install it, the only button that shows up is a close
button. I went through the dialog box, and the only things that are in
there are the checkbox to select the update and the close button.
What's up with that, where's the install button for the darn thing?
Slightly perplexed.


Tony




Re: strange behavior with add on updater

Andy
 

When i launched NVDA yesterday the update dialogue came up and i had no problem installing the update.

Andy

----- Original Message -----
From: "Ian Westerland" <iwesterl@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, August 26, 2018 8:44 PM
Subject: Re: [nvda] strange behavior with add on updater


Hi Tony. I was about to write to the list on the same subject. At
first I wondered if there was some kind of bug when the notification
appeared several hours apart but I am convinced it isn't a bug.

Looking forward to the answer and a possible remedy.

Ian Westerland




On 8/27/2018 1:40 PM, Tony Ballou wrote:
Howdy,


The latest version of the add on updater came out yesterday. When I
check the option to install it, the only button that shows up is a close
button. I went through the dialog box, and the only things that are in
there are the checkbox to select the update and the close button.
What's up with that, where's the install button for the darn thing?
Slightly perplexed.


Tony




Re: strange behavior with add on updater

Ian Westerland
 

Hi Tony. I was about to write to the list on the same subject. At first I wondered if there was some kind of bug when the notification appeared several hours apart but I am convinced it isn't a bug.

Looking forward to the answer and a possible remedy.

Ian Westerland

On 8/27/2018 1:40 PM, Tony Ballou wrote:
Howdy,
The latest version of the add on updater came out yesterday. When I
check the option to install it, the only button that shows up is a close
button.   I went through the dialog box, and the only things that are in
there are the checkbox to select the update and the close button.
What's up with that, where's the install button for the darn thing?
Slightly perplexed.
Tony


strange behavior with add on updater

Tony Ballou
 

Howdy,


The latest version of the add on updater came out yesterday. When I
check the option to install it, the only button that shows up is a close
button.   I went through the dialog box, and the only things that are in
there are the checkbox to select the update and the close button. 
What's up with that, where's the install button for the darn thing?
Slightly perplexed.


Tony


Re: thunderbird addon

Tony Ballou
 

Hi,


from the add ons section type in the word navigation.  or the phrase
first letter navigation.  It will probably be the first thing that comes
up.  I can't think of it off the top of my head at the moment. Lack of a
cold beer causes poor thought processing.  Sighs.


Tony

On 8/26/2018 5: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: Free Synthesizers

Kwork
 

Got it. Thank you for the link.

On 8/26/2018 4:56 PM, Brian Vogel wrote:
>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: Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

Chris G <chris@...>
 

QCast is another product that won't work when more and more podcasts start serving their audio over SSL or secure feeds.
I found a workaround for my podcast but it won't work forever. 
Asked the developer to update QCast so it would work with SSL feeds.  I heard crickets. 
It is too bad.


From: Sarah k Alawami
Sent: Sun, Aug 26, 2018 3:02 PM EDT
To: nvda@nvda.groups.io
Subject: [nvda] Advisory... once again (and one last time): NVDA Remote 2.1 (without patch) is incompatible with NVDA 2018.3 and future releases

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


Words and lines repeat in the Mail app!

David Moore
 

Hi all!

I hope you can help me.

Lately, in the mail app, if I use the arrow keys to read word by word, or line by line, the same word, letter, or line will repeat, even if I am on another line, letter, or word.

When I try to correct my emails, I have to use the text commands to read with the review cursor, and press the command to bring the focus to the review cursor, and make the correction.

My messages read fine with the review cursor, but it is getting almost impossible to read my message with the arrow keys and the focus.

I am using latest alpha build, latest Mail app update, and Windows 1803.

It is the win10 mail app.

I have tried turning off my add-ons except for Windows app essentials, but it does not help.

Let me know if any of you are having this problem with the Win10 mail app with NVDA.

David Moore

 

Sent from Mail for Windows 10

 


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