Date   

Re: NVDA Curiosity

Lenron
 

I wouldn't even want to hit the net with a xp machine.

On 6/4/16, Clare Page <clare.page@...> wrote:
Hi!
NVDA 2016.2 is working fine for me as well: I haven't spotted any issues
since I installed the latest full version.
Bye for now!
From Clare

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Andre
Fisher
Sent: vendredi 3 juin 2016 20:03
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Curiosity

I have no problems with it. I love it!

On 6/3/16, Chris Shook <chris0309@...> wrote:
This goes along with my last post labeled NVDA devils advocate.
Over the last few days, I've noticed a lot of people pointing out
issues with the latest version of NVDA.
For a little perspective, how many people are not having these issues.
So far, everything has worked fine for me.
Is there any one else that is not having any problems with NVDA 2016.2?
Chris








--
Lenron Brown
Cell: 985-271-2832
Skype: ron.brown762


Re: espeak issue fixed

Gene
 

I was saying what I did in case you wanted to experiment with NVDA in future.  I was saying that experimenting with a portable version is safe.  I was addressing the question for the future because there may be times when you would benefit significantly by making changes to NVDA. 
 
Also, my speech dictionary is not large but I have built it up slowly during a number of years.  I have it backed up so I can put a new copy into NVDA if necessary.  It is important to do this to guard against loss of the dictionary. 
 
Gene

----- Original Message -----
Sent: Saturday, June 04, 2016 8:54 AM
Subject: Re: [nvda] espeak issue fixed

Regardless, I'm not messing with that again until there's a more official fix for the problem. That was the most harrowing half hour of my life and I have no desire to relive it.


On 4/06/2016 11:06 PM, Gene wrote:
It isn't a case of experimenting or not experimenting.  Backing up the folder so you could replace it with the original should be done if you are ever going to experiment in this way.  or, you could have the installer create a portable version and experiment with that.  Dictionary files can, and should, be backed up regardless of whether you experiment with NVDA.  They should be backed up just as any files you don't want to lose should be backed up. 
 
Gene

Sent: Saturday, June 04, 2016 7:44 AM
Subject: Re: [nvda] espeak issue fixed

...


I just did this and succeeded in screwing up my copy of NVDA. I copied in the "Espeak Data" folder as was suggested, and suddenly everything NVDA was saying was incomprehensible to me. I tried to undo what I'd done. All I ended up with was silence. Horrible, horrible, unbroken silence. With sighted help, I did a system restore, which accomplished nothing, then had to resort to using a portable copy of NVDA which I hadn't updated since 2015.2, uninstalling NVDA from my computer, reinstalling it from the portable copy and updating it back to 2016.2. I've probably lost a few dictionary entries and I'm right back where I started, but I infinitely prefer speech with a few squished syllables to no NVDA at all. Did I mention after I tried undo NVDA wouldn't even start, probably because it's default synth had been stuffed around with? Oh yeah, it did that.


I am never, ever messing with my screen readers data files again.


On 4/06/2016 7:21 PM, Shaun Everiss wrote:
Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in compiled form I was able to find via sourceforge 2014.4 and this had espeak in it.
I coppied over the espeakdata folder over itself in nvda program folder.
While this will have to be done for just about every coppy it does mean that while espeak will remain the new ng with the voice as it is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2 folders synthdrivers which has the old espeak state from 2014.4 and the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I have yet to see compiled ng binaries for windows sapi, etc so till we see that and as long as sourceforge keeps the depricated espeak project up we will be ok.
To the devs and such trying to solve this especially if you have access to the espeak list which I have no desire to handle and since this may happen on multiple platforms it seems to be the database itself or something in the database causing the trouble currently faced.
I am unsure about what part of the database is naff though, this will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use the latest engine.
I will keep other units the same however as it is not needed that we fiddle with our units like this but at least for my own personal it will work.






Re: espeak issue fixed

Sharni-Lee Ward
 

Regardless, I'm not messing with that again until there's a more official fix for the problem. That was the most harrowing half hour of my life and I have no desire to relive it.


On 4/06/2016 11:06 PM, Gene wrote:
It isn't a case of experimenting or not experimenting.  Backing up the folder so you could replace it with the original should be done if you are ever going to experiment in this way.  or, you could have the installer create a portable version and experiment with that.  Dictionary files can, and should, be backed up regardless of whether you experiment with NVDA.  They should be backed up just as any files you don't want to lose should be backed up. 
 
Gene

Sent: Saturday, June 04, 2016 7:44 AM
Subject: Re: [nvda] espeak issue fixed

...


I just did this and succeeded in screwing up my copy of NVDA. I copied in the "Espeak Data" folder as was suggested, and suddenly everything NVDA was saying was incomprehensible to me. I tried to undo what I'd done. All I ended up with was silence. Horrible, horrible, unbroken silence. With sighted help, I did a system restore, which accomplished nothing, then had to resort to using a portable copy of NVDA which I hadn't updated since 2015.2, uninstalling NVDA from my computer, reinstalling it from the portable copy and updating it back to 2016.2. I've probably lost a few dictionary entries and I'm right back where I started, but I infinitely prefer speech with a few squished syllables to no NVDA at all. Did I mention after I tried undo NVDA wouldn't even start, probably because it's default synth had been stuffed around with? Oh yeah, it did that.


I am never, ever messing with my screen readers data files again.


On 4/06/2016 7:21 PM, Shaun Everiss wrote:
Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in compiled form I was able to find via sourceforge 2014.4 and this had espeak in it.
I coppied over the espeakdata folder over itself in nvda program folder.
While this will have to be done for just about every coppy it does mean that while espeak will remain the new ng with the voice as it is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2 folders synthdrivers which has the old espeak state from 2014.4 and the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I have yet to see compiled ng binaries for windows sapi, etc so till we see that and as long as sourceforge keeps the depricated espeak project up we will be ok.
To the devs and such trying to solve this especially if you have access to the espeak list which I have no desire to handle and since this may happen on multiple platforms it seems to be the database itself or something in the database causing the trouble currently faced.
I am unsure about what part of the database is naff though, this will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use the latest engine.
I will keep other units the same however as it is not needed that we fiddle with our units like this but at least for my own personal it will work.






Re: espeak issue fixed

Gene
 

It isn't a case of experimenting or not experimenting.  Backing up the folder so you could replace it with the original should be done if you are ever going to experiment in this way.  or, you could have the installer create a portable version and experiment with that.  Dictionary files can, and should, be backed up regardless of whether you experiment with NVDA.  They should be backed up just as any files you don't want to lose should be backed up. 
 
Gene

Sent: Saturday, June 04, 2016 7:44 AM
Subject: Re: [nvda] espeak issue fixed

...


I just did this and succeeded in screwing up my copy of NVDA. I copied in the "Espeak Data" folder as was suggested, and suddenly everything NVDA was saying was incomprehensible to me. I tried to undo what I'd done. All I ended up with was silence. Horrible, horrible, unbroken silence. With sighted help, I did a system restore, which accomplished nothing, then had to resort to using a portable copy of NVDA which I hadn't updated since 2015.2, uninstalling NVDA from my computer, reinstalling it from the portable copy and updating it back to 2016.2. I've probably lost a few dictionary entries and I'm right back where I started, but I infinitely prefer speech with a few squished syllables to no NVDA at all. Did I mention after I tried undo NVDA wouldn't even start, probably because it's default synth had been stuffed around with? Oh yeah, it did that.


I am never, ever messing with my screen readers data files again.


On 4/06/2016 7:21 PM, Shaun Everiss wrote:
Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in compiled form I was able to find via sourceforge 2014.4 and this had espeak in it.
I coppied over the espeakdata folder over itself in nvda program folder.
While this will have to be done for just about every coppy it does mean that while espeak will remain the new ng with the voice as it is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2 folders synthdrivers which has the old espeak state from 2014.4 and the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I have yet to see compiled ng binaries for windows sapi, etc so till we see that and as long as sourceforge keeps the depricated espeak project up we will be ok.
To the devs and such trying to solve this especially if you have access to the espeak list which I have no desire to handle and since this may happen on multiple platforms it seems to be the database itself or something in the database causing the trouble currently faced.
I am unsure about what part of the database is naff though, this will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use the latest engine.
I will keep other units the same however as it is not needed that we fiddle with our units like this but at least for my own personal it will work.





Re: espeak issue fixed

Sharni-Lee Ward
 

...


I just did this and succeeded in screwing up my copy of NVDA. I copied in the "Espeak Data" folder as was suggested, and suddenly everything NVDA was saying was incomprehensible to me. I tried to undo what I'd done. All I ended up with was silence. Horrible, horrible, unbroken silence. With sighted help, I did a system restore, which accomplished nothing, then had to resort to using a portable copy of NVDA which I hadn't updated since 2015.2, uninstalling NVDA from my computer, reinstalling it from the portable copy and updating it back to 2016.2. I've probably lost a few dictionary entries and I'm right back where I started, but I infinitely prefer speech with a few squished syllables to no NVDA at all. Did I mention after I tried undo NVDA wouldn't even start, probably because it's default synth had been stuffed around with? Oh yeah, it did that.


I am never, ever messing with my screen readers data files again.


On 4/06/2016 7:21 PM, Shaun Everiss wrote:
Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in compiled form I was able to find via sourceforge 2014.4 and this had espeak in it.
I coppied over the espeakdata folder over itself in nvda program folder.
While this will have to be done for just about every coppy it does mean that while espeak will remain the new ng with the voice as it is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2 folders synthdrivers which has the old espeak state from 2014.4 and the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I have yet to see compiled ng binaries for windows sapi, etc so till we see that and as long as sourceforge keeps the depricated espeak project up we will be ok.
To the devs and such trying to solve this especially if you have access to the espeak list which I have no desire to handle and since this may happen on multiple platforms it seems to be the database itself or something in the database causing the trouble currently faced.
I am unsure about what part of the database is naff though, this will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use the latest engine.
I will keep other units the same however as it is not needed that we fiddle with our units like this but at least for my own personal it will work.





Re: iTunes 12.4.1 update.

Matt Turner
 

For anyone who has subscribed to apple music.
Has any of your music that you bought from the iTunes store been re-tagged?

On 6/4/2016 6:13 AM, Chris wrote:
Many thanks , I can confirm it has improved using nvda


-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Clare
Page
Sent: 04 June 2016 10:00
To: nvda@nvda.groups.io
Subject: Re: [nvda] iTunes 12.4.1 update.

Hi!
In answer to your question, yes, I've updated iTunes to 12.4.1, that's the
correct version number, and it has definitely improved. I haven't tested
everything, but I can report that scrolling up and down lists works like it
used to, with NVDA reading whatever item you land on if you arrow down a
list, use the Page Up and Page Down or Home and End keys, or do first letter
navigation in the list. It also seems to me that iTunes opens and runs
faster than it used to on my Windows 7 laptop, but maybe I'm just lucky with
that.
Glad to see Apple bringing out an improved version so quickly!
Bye for now!
From Clare

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Matt
Turner
Sent: vendredi 3 juin 2016 15:37
To: nvda@nvda.groups.io
Subject: [nvda] iTunes 4.0.1 update.

Anyone tried the updated version of iTunes?

If so, does everything work again?









Re: iTunes 12.4.1 update.

Chris
 

Many thanks , I can confirm it has improved using nvda

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Clare
Page
Sent: 04 June 2016 10:00
To: nvda@nvda.groups.io
Subject: Re: [nvda] iTunes 12.4.1 update.

Hi!
In answer to your question, yes, I've updated iTunes to 12.4.1, that's the
correct version number, and it has definitely improved. I haven't tested
everything, but I can report that scrolling up and down lists works like it
used to, with NVDA reading whatever item you land on if you arrow down a
list, use the Page Up and Page Down or Home and End keys, or do first letter
navigation in the list. It also seems to me that iTunes opens and runs
faster than it used to on my Windows 7 laptop, but maybe I'm just lucky with
that.
Glad to see Apple bringing out an improved version so quickly!
Bye for now!
From Clare

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Matt
Turner
Sent: vendredi 3 juin 2016 15:37
To: nvda@nvda.groups.io
Subject: [nvda] iTunes 4.0.1 update.

Anyone tried the updated version of iTunes?

If so, does everything work again?


NVDA and Chrome 51

 

Hi,

When I tried NVDA (latest version) with Chrome 51, NVDA still doesn't read the character that I've deleted in a number of text boxes, specifically the Facebook status composing box and I think this applies to all textareas.

Is this a NVDA bug or a Chrome bug?


From the moderator: A message about clutter

Gene
 

This is my first message as moderator addressing a subject in depth.  One of my concerns as moderator is reducing clutter.  The following message comments on the current discussion occurring on list and makes more general points on my approach to the subject. 
 
I believe that reducing clutter will make the list more appealing to many members and prospective members and won't detract from the quality of the list.  Will those who wish to comment please do so at the owner's address I provide at the end of this message so as not to have an ongoing lengthy discussion of administrative matters on the list itself.
 
I believe that such matters should be seen in a broader context which I lay out in the following discussion.
 
To start with, I am not stating these things as a matter of list policy.  I am stating them from my perspective of having been on various lists for about seventeen years and my thoughts and impressions from that long experience.
 
My view is that a list should not be too rigid nor too unfocused.  The degree of strictness varies from list to list, depending on its purpose, the number of members, and the kinds of members.
 
Also, at times, a certain amount of off topic traffic is useful in promoting a sense of community and of people getting to know and feeling a personal connection to other members.  I take all such considerations into account.  But on a large list like this, if too much clutter occurs, people may leave the list who might benefit by being here and that is not a desirable occurrence. 
 
The current discussion is a good example.  while some people might believe that feel good messages are desirable, on a list of hundreds of members many may not share that opinion.  This list has members at all skill levels of computer operation and of use of NVDA.  For some members, skipping messages in threads they don't want to read is very fast and easy.  For others, who don't know as much about e-mail use and management, seeing between twenty and forty messages in a thread that do not present any useful information may represent a significant expenditure of their time.  Inexperienced members who don't know how to group messages by conversation, who may not use fast reading speeds and who may be busy with various activities such as school, work, etc. may find it a significant expenditure of time getting through such threads.  Experienced members, on the other hand, may find it very fast and easy to simply skip what they are not interested in.  Please try to take a larger view when considering such things and deciding whether a thread to start or to participate in is useful or productive.  We want the list to be useful to a wide variety of members with a wide variety of skill levels.  We don't want to lose members who become disillusioned with clutter.  Many people won't even join busy lists because they say they have too much mail already. 
 
I am not stating any of this as list policy.  There are no punishments or rules in what I am saying.  I'm simply saying that, as someone who has been asked to be a moderator, I consider it part of what I can do to be useful to try to expand how people view what makes the list attractive to the most number of people who may benefit from it.  also, and the two are closely related, what may discourage people from staying on the list. 
 
My purpose is to attempt to reduce clutter not by pouncing on members or castigating them, but rather through discussion of ways to reduce it.
 
If people have comments on this message, please do not discuss the matter on list.  Please send comments to the below address.  I shall read all comments and I intend to respond to all who comment. 
nvda+owner@nvda.groups.io
 
Gene


espeak issue fixed

 

Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in compiled form I was able to find via sourceforge 2014.4 and this had espeak in it.
I coppied over the espeakdata folder over itself in nvda program folder.
While this will have to be done for just about every coppy it does mean that while espeak will remain the new ng with the voice as it is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2 folders synthdrivers which has the old espeak state from 2014.4 and the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I have yet to see compiled ng binaries for windows sapi, etc so till we see that and as long as sourceforge keeps the depricated espeak project up we will be ok.
To the devs and such trying to solve this especially if you have access to the espeak list which I have no desire to handle and since this may happen on multiple platforms it seems to be the database itself or something in the database causing the trouble currently faced.
I am unsure about what part of the database is naff though, this will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use the latest engine.
I will keep other units the same however as it is not needed that we fiddle with our units like this but at least for my own personal it will work.


Re: NVDA Curiosity

Clare Page <clare.page@...>
 

Hi!
NVDA 2016.2 is working fine for me as well: I haven't spotted any issues since I installed the latest full version.
Bye for now!
From Clare

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Andre Fisher
Sent: vendredi 3 juin 2016 20:03
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Curiosity

I have no problems with it. I love it!

On 6/3/16, Chris Shook <chris0309@...> wrote:
This goes along with my last post labeled NVDA devils advocate.
Over the last few days, I've noticed a lot of people pointing out
issues with the latest version of NVDA.
For a little perspective, how many people are not having these issues.
So far, everything has worked fine for me.
Is there any one else that is not having any problems with NVDA 2016.2?
Chris




Re: iTunes 12.4.1 update.

Clare Page <clare.page@...>
 

Hi!
In answer to your question, yes, I've updated iTunes to 12.4.1, that's the correct version number, and it has definitely improved. I haven't tested everything, but I can report that scrolling up and down lists works like it used to, with NVDA reading whatever item you land on if you arrow down a list, use the Page Up and Page Down or Home and End keys, or do first letter navigation in the list. It also seems to me that iTunes opens and runs faster than it used to on my Windows 7 laptop, but maybe I'm just lucky with that.
Glad to see Apple bringing out an improved version so quickly!
Bye for now!
From Clare

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Matt Turner
Sent: vendredi 3 juin 2016 15:37
To: nvda@nvda.groups.io
Subject: [nvda] iTunes 4.0.1 update.

Anyone tried the updated version of iTunes?

If so, does everything work again?


Re: FW: [Nvda-devel] FW: Browse Mode with NVDA 2016.2 not working

 

hi.
i understand what do you say.
i have this problem for brows mode too.
the best version for me is 2015.3 and i dont have any problem in using it.
sometimes i test the newer versions just for helping others, not for
my daily use.

On 6/3/16, Chris Shook <chris0309@...> wrote:
What problem are you referring to. To the best of my knoledge,
everything is working fine for me.
Chris



--
Those who follow the Messenger-Prophet, the Ummi, whom they find
written down with them in the Taurat and the Injeel [who] enjoins them
good and forbids them evil, and makes lawful to them the good things
and makes unlawful to them impure things, and removes from them their
burden and the shackles which were upon them; so [as for] those who
believe in him and honor him and help him, and follow the light which
has been sent down with him, these it is that are the successful.
holy quran, chapter 7, verse 157.
best website for studying islamic book in different languages
al-islam.org


Re: [nvda\] NVDA Devils advocate

 

Well interestingly tech including printers and routers are a hit and miss thing.
I have had several d-link, tp link and dynalink-sisco units and they all started fine but the later units just have noo accessibility at all.
Right now I have a netcom which works and a netgear universal which after setting it manually, did a firmware update and it worked like a charm
I have had equipment that has been less than helpfull sadly.
Sadly it seems to be a bit of hit and miss weather your favorite bit of kit works or not.

On 4/06/2016 7:38 p.m., Brian's Mail list account wrote:
Yess indeed. I see so many web sites, for examplewhich claim to be
accessible to this r that standard as tested by ( insert program her).
All this means from my experience is that things can be read, not how
overfull and muddled with its links it is, or the issues of stupid music
playing at the slightest provocation or the actual try to do a task test.
Its purely based on does this read, in my experience.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Brian Vogel" <@britechguy>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 5:58 PM
Subject: Re: [nvda] [nvda\] NVDA Devils advocate


Hear, hear!!

Software development is not all that different in that regard than any
other pursuit where repair is involved. Just like a mechanic cannot fix
a car if they're unaware of a problem, or if a reported problem cannot
be replicated by them, neither can a programmer do the same for a bug.

This is one of the reasons I download and install the release
candidates. NVDA is not a major corporation with the resources to hire a
dedicated testing department that can flog the software to death. Having
been a programmer, and one in an entity that can and did do that, you
still will not find all potential bugs. Even with very thorough test
"scripts" the general user public will always find a way to do something
that no one could ever have predicted they'd do, and with results that
are sometimes as unpredictable.

Being a late beta tester on NVDA with the release candidates is a good
idea for all users of the software. And those of you who actually use
NVDA as your primary method of access can be a lot more thorough in
testing just by doing what you always do than anyone creating testing
scenarios could hope to be.


Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

hi bhavya.
could you please report the bug which i mentioned?
i did not see this problems before.
the best version for me is the version 2015.3
i dont use office programs and this versions does the job for me.

On 6/4/16, Brian's Mail list account <bglists@...> wrote:
Well for serious concerns raise a ticket and for queries about techy stuff
use the development mail list.
One of the things I have been doing is running both next and master
branches to see if there were any issues. Very few occour these days though

there are typos that can cause problems. With these more odd effects tat
others cannot duplicate its always harder to fix it until they can.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Lino Morales" <linomorales001@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 4:24 PM
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar

error detection and more to your work, home and everything in between
#NVAccess #Release


Well I'd take this up with with either James Teh or Michael Kerrun. They
put out the updates/releases.


On 6/2/2016 5:55 PM, Brian Vogel wrote:

I disagree that there's no point in announcing it because it would
save quite a few people from doing unnecessary downloads and installs.

However, if it's not announced, is there somewhere that one can look
to determine that for oneself? This was the second option and one I'd
exercise if I knew where I could look on a consistent basis.


--
*/Brian/*

/*I worry a lot. . . I worry that no matter how cynical you **become
it's never enough to keep up.*/

* ~ Trudy, in Jane Wagner's **"Search for Signs of Intelligent
Life in the Universe"*





--
Those who follow the Messenger-Prophet, the Ummi, whom they find
written down with them in the Taurat and the Injeel [who] enjoins them
good and forbids them evil, and makes lawful to them the good things
and makes unlawful to them impure things, and removes from them their
burden and the shackles which were upon them; so [as for] those who
believe in him and honor him and help him, and follow the light which
has been sent down with him, these it is that are the successful.
holy quran, chapter 7, verse 157.
best website for studying islamic book in different languages
al-islam.org


Re: Weird issue

Brian's Mail list account BY <bglists@...>
 

If you turn off the colour announcment what happens then?
Brian

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

----- Original Message -----
From: "Danni" <luv2ride67@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 9:06 PM
Subject: Re: [nvda] Weird issue


No because sometimes I can hear colors or options and sometimes I can't! which tells me something is going on I just don't know what!

----- Original Message -----
From: "Andre Fisher" <andrefisher729@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 8:46 AM
Subject: Re: [nvda] Weird issue


Maybe the site's layout was changed, don't you think?

On 6/3/16, Danni <luv2ride67@...> wrote:
No I can't see it! things are not in the usual place normally on the page it

shows or reads item number then title of item pics and such then price size

color description and so on with of course buttons for adding to cart and
such but it's moving colors before sizing it's too early my brain can't
think of all changes but it's moved around though sometimes it will read the

page the way it normally is!

I don't know how to explain it but will check firefox thanks anyway
----- Original Message -----
From: "Brian's Mail list account" <bglists@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 1:23 AM
Subject: Re: [nvda] Weird issue


When you say moved around, can you see the screen? Often those who can and

also use speech complain that the order is different for the screenreader

to the sighted user. In my mind this implies muddled accessability bolted

on as an afterthought.
If other sites behave as you would expect, its probably the site. Might be

worth trying it in another browser.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Danni" <luv2ride67@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 6:54 AM
Subject: [nvda] Weird issue


I'm not sure if it's NVDA or I?E that is causing the issue but when I go
to qvc.com and read through the page the colors are not being read and I
noticed too that the page is mixed around am not sure how to explain it
exactly but things are out of place and i can't figure out what to check
in order to fix it?













Re: NVDA Curiosity

Brian's Mail list account BY <bglists@...>
 

I don't think the age of the user has much to do with it. Often its the old comfort zone thing and I have to say, though I'm now using 7 and 10 to some extent. I can get stuff done faster in xp.
I think maybe it was said that at some point it will not be able to support xp, but not yet, and in any case as XP is not really going to change the version that is the very laast to work in xp will continue to work so really no problem by then. I like many have the hack on my xp machines so I get updates, but even this will stop sooner ater than later.
At present my main grouse is that many other software companies will no longer support xp. Notable will be Dropbox in august.
This will mean using these machines as anything other than toys will be harder.
Brian

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

----- Original Message -----
From: "Gene" <gsasner@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 8:50 PM
Subject: Re: [nvda] NVDA Curiosity


you don't represent your age group. As a person over 55 myself, I do not accept your representation.

As far as XP is concerned, the developers are still intentionally having NVDA run in Windows Xp. Also, I don't recall messages of people reporting bugs stating that they are using XP. It appears you are making an unsupported assumption.

Gene
----- Original Message -----


From: Carlos
Sent: Friday, June 03, 2016 1:49 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Curiosity


Hello:

The newer the PC/machine; the less problems are encountered with
new software!

At some point some NVDA users will be hit with the reality that
Windows XP has lived a very very long life and wants to retire/be left
alone!

There are a number of charitable organizations/groups that sell
rebuilt PC's at economical prices that at least run Windows 7.

There are a number of software developers that warn customers that
their software no longer will support vintage PC's!

So, if users insist on continued usage of old PC's/machines. Then
don't complain/whine when operating systems/software does not run
correctly on your machines!

Yes! I do sound like an old curmudgeon! And, I'm very proud to
represent my age group! (55 Years and above)



On 6/3/2016 11:29 AM, Roger Stewart wrote:
I'm having no problems with the newest nvda and I use Firefox and
Thunderbird--no issues at all.

Roger








On 6/3/2016 1:01 PM, Chris Shook wrote:
This goes along with my last post labeled NVDA devils advocate.
Over the last few days, I've noticed a lot of people pointing out
issues with the latest version of NVDA.
For a little perspective, how many people are not having these issues.
So far, everything has worked fine for me.
Is there any one else that is not having any problems with NVDA 2016.2?
Chris





--
Carlos Gonzalez - Los Angeles, CA. - gmjc341961@...


Re: [nvda\] NVDA Devils advocate

Brian's Mail list account BY <bglists@...>
 

Yess indeed. I see so many web sites, for examplewhich claim to be accessible to this r that standard as tested by ( insert program her). All this means from my experience is that things can be read, not how overfull and muddled with its links it is, or the issues of stupid music playing at the slightest provocation or the actual try to do a task test.
Its purely based on does this read, in my experience.
Brian

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

----- Original Message -----
From: "Brian Vogel" <@britechguy>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 5:58 PM
Subject: Re: [nvda] [nvda\] NVDA Devils advocate


Hear, hear!!

Software development is not all that different in that regard than any other pursuit where repair is involved. Just like a mechanic cannot fix a car if they're unaware of a problem, or if a reported problem cannot be replicated by them, neither can a programmer do the same for a bug.

This is one of the reasons I download and install the release candidates. NVDA is not a major corporation with the resources to hire a dedicated testing department that can flog the software to death. Having been a programmer, and one in an entity that can and did do that, you still will not find all potential bugs. Even with very thorough test "scripts" the general user public will always find a way to do something that no one could ever have predicted they'd do, and with results that are sometimes as unpredictable.

Being a late beta tester on NVDA with the release candidates is a good idea for all users of the software. And those of you who actually use NVDA as your primary method of access can be a lot more thorough in testing just by doing what you always do than anyone creating testing scenarios could hope to be.
--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.
~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"


Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

Brian's Mail list account BY <bglists@...>
 

Well for serious concerns raise a ticket and for queries about techy stuff use the development mail list.
One of the things I have been doing is running both next and master branches to see if there were any issues. Very few occour these days though there are typos that can cause problems. With these more odd effects tat others cannot duplicate its always harder to fix it until they can.
Brian

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

----- Original Message -----
From: "Lino Morales" <linomorales001@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 4:24 PM
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release


Well I'd take this up with with either James Teh or Michael Kerrun. They
put out the updates/releases.


On 6/2/2016 5:55 PM, Brian Vogel wrote:

I disagree that there's no point in announcing it because it would
save quite a few people from doing unnecessary downloads and installs.

However, if it's not announced, is there somewhere that one can look
to determine that for oneself? This was the second option and one I'd
exercise if I knew where I could look on a consistent basis.


--
*/Brian/*

/*I worry a lot. . . I worry that no matter how cynical you **become
it's never enough to keep up.*/

* ~ Trudy, in Jane Wagner's **"Search for Signs of Intelligent
Life in the Universe"*



Re: NVDA Curiosity

christopher hallsworth <challsworth2@...>
 

Yes it does, but you have to enable it in Sounds in Control Panel.

On 4 Jun 2016, at 06:00, Chris Shook <chris0309@...> wrote:

Arlene,
Windows 10 doesn't have a start up sound.
Chris