-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Friday, September 21, 2018 4:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] edge and web shortcuts

What is the default browser set as?

It sounds a bit like a windows issue. I've seen something similar in
windows 7 if a browser is launched with different syntax for the page you
wanted to go to so to speak.

Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Gary Metzler" <gmtravel@comcast.net>
To: "nvda" <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 9:06 PM
Subject: [nvda] edge and web shortcuts

Hi All,



I am using the latest win10 and nvda. Whenever I start my facebook
shortcut
and it loads I get the message invalid entry. But, when I do this within
edge it doesn't happen. It only happens with edge and desktop shortcuts.
Has anyone else noticed this? Can this be fixed? Thanks for any help.



Regards, Gary KN4Ox

Send to: gmtravel@comcast.net

----- Original Message -----
From: "Gary Metzler" <gmtravel@comcast.net>
To: "nvda" <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 9:06 PM
Subject: [nvda] edge and web shortcuts

Hi All,



I am using the latest win10 and nvda. Whenever I start my facebook shortcut
and it loads I get the message invalid entry. But, when I do this within
edge it doesn't happen. It only happens with edge and desktop shortcuts.
Has anyone else noticed this? Can this be fixed? Thanks for any help.



Regards, Gary KN4Ox

Send to: gmtravel@comcast.net

The one thing that Jawes can afford to do is to make significant financial
clout to making a script work for a piece of software where the writers for
whatever reason are not prepared to make it obey conventions. Sadly this
same lack of expertise is now afflicting web sites again where accessibility
seems to men yes things should work but the clutter and complication factor
is far too high when you think about us blind folk not being able to get an
overview and general layout of a site. Helpful comments like the broken
green circle at the top left of the page are not welcome!
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Dave" <dlh007@...>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 1:52 PM
Subject: Re: [nvda] Web Browsers


> Hello Ian,
>
> Yes, I too noticed a Snappier behavior from this latest version of NVDA.
>
> I was using FireFox.
>
> As for the various Browsers being able to read all buttons, or Links, or
> different aspects on a Web Site-  Yes, I too have noticed this.
>
> I have been looking for work lately, and when on www.monster.com, a
> Employment Web Site, Sometimes I can read the Needed Links, and then
> other times, those links are not seen.
>
> Or once I've used them once, even if I return to the Main page of the
> web site, for what ever reason, I cannot find or read these links.  Have
> to shut down my Browser, and then re-visit the same site, and then those
> links will show up, but only sometimes.  Go Figure!
>
> And as far as differences between Screen Readers, Yes there too, I have
> noticed that one will read something better than the others.  I am a
> long time Window eyes user, who moved over to Jaws, and have had NVEA as
> the Screen Reader I call up to bail me out of Trouble when the others
> stop speaking.
>
> Over the last five years or so, I have actually found NVDA to be getting
> stronger and stronger.    In fact, when I needed to switch over to JAWS,
> at that time, I almost just switched to NVDA.  I have one program that
> NVDA will not read the screens, and Jaws does, so have been using Jaws.
>
> But, like I said, NVDA has come a long way, and is actually a very good
> Screen Reader.
>
>
>
> Dave
>
>
>
>
>

---

On 9/21/2018 9:22 AM, Joseph Lee wrote:

Hi,
I think this has to do more with number processing by speech synthesizers.
Cheers,
Joseph
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brice Mijares
Sent: Friday, September 21, 2018 9:16 AM
To: nvda <nvda@nvda.groups.io>
Subject: [nvda] NVDA 2018.3.1
Why is the latest version call March first 2018 when it came out in September. Just curious.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brice Mijares
Sent: Friday, September 21, 2018 9:16 AM
To: nvda <nvda@nvda.groups.io>
Subject: [nvda] NVDA 2018.3.1

Why is the latest version call March first 2018 when it came out in September. Just curious.

On 9/21/2018 9:58 AM, Cohn, Jonathan wrote:

Are you using the programs auto-numbering to number your paragraphs? Also, which version of Word are you using. If you would like to send me a private copy of an example file, I would be glad to figure out the best option.

Take care,

Jonathan Cohn


On 9/21/18, 6:52 AM, "nvda@nvda.groups.io on behalf of kelby carlson" <nvda@nvda.groups.io on behalf of kelbycarlson@gmail.com> wrote:

For some reason when I create a list in Word by numbering each paragraph, NVDA will not read the numbers once I have completed the list. Does anyone know a way to fix this?

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 2:06 PM
Subject: Re: [nvda] FW: [nvda-addons] Project Pylennium: updates, proposing start of Python 3 pre-transition activities

Hi,
Windows 7 SP1 support: this is the reason why Espeak NG readiness is a
priority for some of us so folks on that OS can test it once binary versions
are ready.
Regarding 64-bit NVDA, as stated many times in the past, although it has
advantages, it could reduce appeal of NVDA for those wishing to use it as a
portable copy across bit boundaries.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Friday, September 21, 2018 3:52 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] FW: [nvda-addons] Project Pylennium: updates, proposing
start of Python 3 pre-transition activities

Hi, I'd just like to clarify that no actual release of nvda powered by the
new compiler is going to occur until all code runs on windows 7sp1.
Also what is the attitude these days to a 64 bit version on nvda itself, as
I feel such a move may well impact on some of the current bottlenecks in
processor core usage and other issues.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 1:46 AM
Subject: [nvda] FW: [nvda-addons] Project Pylennium: updates, proposing
start of Python 3 pre-transition activities

Hi everyone,

Although the below post is a bit technical, please keep an eye on it.
You won't feel the impact of what I outline regarding Python 3
transition for a while, but when it does, please listen to notices
from NV Access and add-on authors regarding Python 3. And no, wxPython
4 is not the same thing as Python 3.

Thanks.



From: nvda-addons@nvda-addons.groups.io
<nvda-addons@nvda-addons.groups.io>
On Behalf Of Joseph Lee
Sent: Thursday, September 20, 2018 5:43 PM
To: 'NVDA screen reader development'
<nvda-devel@lists.sourceforge.net>
Subject: [nvda-addons] Project Pylennium: updates, proposing start of
Python
3 pre-transition activities



Dear NVDA development and add-ons communities:



This is Joseph Lee, a student at California State University, Los
Angeles and a long-time NVDA add-on author and code contributor. I'd
like to announce some important updates regarding Project Pylennium.



For a while, some NVDA developers (mostly third-party contributors)
have been working on how to bring Project Pylennium - Python 3
transition - to life. After much discussion, NV Access and other
developers agreed to wait until a stable NVDA version powered by
wxPython 4.0.3 (Phoenix) is released before working on this project.
Now that NVDA 2018.3.x (powered by wxPython
4) has been released, it is time to move forward with this project a
bit, starting with pre-transition activities.



To kick this off, I'm delighted to announce that a prototype archive
of NVDA source code and dependencies powered by Python 3 is now
available. Apart from removal of data generated by SCons, the archive
is ready to run on Python 3.7 with some preparations, and. are you
ready for it: IT RUNS!
Well,
I must add that there are some important features missing or not
working as intended, but I'm sure this will be rectified as the
project moves forward.



Note that the archive is a prototype - please do not test this unless
your intention is to provide contributions to Python 3 transition
workflow once NV Access is ready to accept pull requests.



Archive link:

https://www.josephsl.net/files/pylennium/nvdapy37.zip



Things working:



* Windows OneCore synthesizer
* Python Console
* Sending log output to log file
* Object navigation commands
* Commands to configure options (NVDA+number row 2, for instance)
* Loading app modules



Things to be aware of:



* Requires Windows 10 until Espeak NG is ready.
* NVDA menu won't open due to division operator differences between
Python 2 nad 3
* Add-ons won't load
* Certain synth settings ring commands won't work
* Some braille displays won't work



The idea is to let seasoned developers (preferably third-party
contributors and/or a group of mainstream Python developers) test
ideas and porting issues and report their findings to NV Access. In
turn, when it comes time to actually transition NVDA source code and
add-ons to Python 3, data can be used to guide future work.



Second, a wiki page is being written to help you all move smoothly to
Python
3 and to coordinate this workflow. The document is subject to change based
on progress of pre-transition activities. The page in its current form can
be found at:

https://github.com/nvaccess/nvda/wiki/nvdapy3



As always, the umbrella issue on Python 3 transition can be found on
GitHub
at:

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



Along with other issues having "python 3" label added to them.



Lastly, I'd like to announce that I'm stepping back from Python 3
transition
workflow at this time (and, for that matter, NVDA code contributions for a
while). Besides automatic braille display detection (written by Babbage
B.V.) and various Windows 10 features support (mostly my work), the
biggest
change (and the most controversial one) in NVDA 2018.3.x has been moving
to
wxPython 4 (mostly my work with assistance from many). The results matched
my predictions from earlier this year: some notable add-ons not being
compatible with wxPython 4, hence notices throughout this summer (winter
for
those living in southern hemisphere).



At the moment I have mixed feelings about how we (NvDA community) handled
this change. Yes, wxPython 4 is a necessary stepping stone for moving to
Python 3, and yes, I understand that I was rather forceful in handling
certain parts of this journey. There are good things we did, and lessons
we
have learned so we can make Python 3 transition a smoother experience.
Even
for me, it was an interesting ride for the last three years (wxPython
Phoenix research began in 2015), and I know that I could have done things
better.



Recently, I hinted to some that my time as an active contributor to NVDA
screen reader is slowly coming to a close. As a first step, I'd like to
ask
that the community take an initiative to move forward with Python 3
transition (including other pre-transition activities); I feel that the
best
thing I can do for this work now is to provide the prototype archive and a
vision for its conclusion, along with some pull requests (one of them is
pending review). There is a feature I'd like to present as a token of
appreciation to those who've helped me for the past six years: add-on
update
checks, which will be impacted by Python 3 transition as well. But this
does
not mean I'm leaving the community: I'll still be around to give advice
regarding Project Pylennium.



Thank you.

Cheers,

Joseph

----- Original Message -----
From: "Mark" <mark@tafn.org.uk>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 3:23 PM
Subject: [nvda] still have the windows mail problem


Hi this is a still on going problem when I close windows mail NVDA stops speaking and I have to restart NVDA
Using the latest version of NVDA
Mark.

Tune in to the number one station on the web TAFN radio
http://tafn.org.uk/listen
Or for our catch up service on demand http://www.tafn.org.uk/on-demand
or for our upcoming weekly schedule
http://www.tafn.org.uk/radio
part of the accessible friends network
www.tafn.org.uk
Registered UK Charity: #1108043.
Sent from Windows 10 Mail.

----- Original Message -----
From: "Dave" <dlh007@centurylink.net>
To: <nvda@nvda.groups.io>
Sent: Friday, September 21, 2018 1:52 PM
Subject: Re: [nvda] Web Browsers

Hello Ian,

Yes, I too noticed a Snappier behavior from this latest version of NVDA.

I was using FireFox.

As for the various Browsers being able to read all buttons, or Links, or
different aspects on a Web Site- Yes, I too have noticed this.

I have been looking for work lately, and when on www.monster.com, a
Employment Web Site, Sometimes I can read the Needed Links, and then
other times, those links are not seen.

Or once I've used them once, even if I return to the Main page of the
web site, for what ever reason, I cannot find or read these links. Have
to shut down my Browser, and then re-visit the same site, and then those
links will show up, but only sometimes. Go Figure!

And as far as differences between Screen Readers, Yes there too, I have
noticed that one will read something better than the others. I am a
long time Window eyes user, who moved over to Jaws, and have had NVEA as
the Screen Reader I call up to bail me out of Trouble when the others
stop speaking.

Over the last five years or so, I have actually found NVDA to be getting
stronger and stronger. In fact, when I needed to switch over to JAWS,
at that time, I almost just switched to NVDA. I have one program that
NVDA will not read the screens, and Jaws does, so have been using Jaws.

But, like I said, NVDA has come a long way, and is actually a very good
Screen Reader.



Dave