Date   

Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

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

I dare not say what is wrong with this synth, I'll have the Eloqence Mafia gunning for me! :-)

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: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 25, 2018 6:50 AM
Subject: Re: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?


Also, what's wrong with Eloquence? Have you tried it And as I recall, you can adjust inflection with it. Don't use the Brittish English voice. It's obviously programmed by Americans amateurishly trying to imitate a Brittish accent. Use the default American English. It pronounces a great many more words correctly compared with e-speak. And I use it very well with the NVDA speech dictionary. Are you familiar with the SAPI 5 demo you can try of Eloquence? Eloquence and Via Voice, the same synthesizer from a sound and performance standpoint, are the most accurate in terms of proper pronounciation of words in my experience.

Gene
----- Original Message -----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sharni-Lee Ward
Sent: Saturday, March 24, 2018 10:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?

I've just caught up on all my emails. If I understood an earlier thread correctly, despite our complaints when 2017.4 came out, the devs did not roll back the version of espeak packaged with NVDA to the version in 2017.3, which means that I will not be updating NVDA, despite the wonderful-sounding new features.


Espeak, and subsequently Espeak NG, has been my default synth since I started using NVDA. There was an issue in 2014 but I was able to get used to that, and then it got fixed, so I was contented. The problems I found in the espeak packaged with 2017.4 were more than I could stand, as someone who primarily uses NVDA to read fanfiction and my own stories. However, Espeak is among the only synths compatible with NVDA's inflection slider, which I have maxed out for optimal performance. I'm not about to sacrifice broad inflection for the drones of MS voices, and I'm currently using a Win 7 computer, but even if I was on a Win 10 one, the 1Core voices don't do it for me either. They're pleasant, but also flat. No inflection. No way to change the inflection. I can't stand human-sounding voices because they're less flexible than synthetic ones in this regard. Also, nearly all non Espeak voices are slow as well as flat, partially due to the length of pauses between clauses of a sentence, and this is about as unbearable as the flatness. And there is one more thing that really clinches my unwillingness to change synths. I cannot get anything else to cooperate with my speech dictionary. As I said, I read a lot of fanfiction, and I have put lots of characters'
names and the names of Pokémon into my dictionary so that they are pronounced properly. The other synths simply do not like these names, no matter what I try to do with them, and some of them even pronounced my name wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their changes to a previous version (surely they have older versions backed up somewhere. I would if I was developing something like this), and for NVDA to likewise roll back the version packaged with it until the devs of the synth work out how to alter one language without screwing up twenty others in the process. I know I can only go so far before I am forced to update to the latest version of NVDA or be left to languish as more and more things become incompatible with the last tolerable version I have.


Please, I am begging you, do something about this.


Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

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

Try what though? Espeak NG is still worse than the old Espeak in UK English, at least to my mind it is.
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: Sunday, March 25, 2018 6:32 AM
Subject: Re: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?


Hi,
May I kindly request that you do something too: please try with 2018.1.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sharni-Lee Ward
Sent: Saturday, March 24, 2018 10:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?

I've just caught up on all my emails. If I understood an earlier thread correctly, despite our complaints when 2017.4 came out, the devs did not roll back the version of espeak packaged with NVDA to the version in 2017.3, which means that I will not be updating NVDA, despite the wonderful-sounding new features.


Espeak, and subsequently Espeak NG, has been my default synth since I started using NVDA. There was an issue in 2014 but I was able to get used to that, and then it got fixed, so I was contented. The problems I found in the espeak packaged with 2017.4 were more than I could stand, as someone who primarily uses NVDA to read fanfiction and my own stories. However, Espeak is among the only synths compatible with NVDA's inflection slider, which I have maxed out for optimal performance. I'm not about to sacrifice broad inflection for the drones of MS voices, and I'm currently using a Win 7 computer, but even if I was on a Win 10 one, the 1Core voices don't do it for me either. They're pleasant, but also flat. No inflection. No way to change the inflection. I can't stand human-sounding voices because they're less flexible than synthetic ones in this regard. Also, nearly all non Espeak voices are slow as well as flat, partially due to the length of pauses between clauses of a sentence, and this is about as unbearable as the flatness. And there is one more thing that really clinches my unwillingness to change synths. I cannot get anything else to cooperate with my speech dictionary. As I said, I read a lot of fanfiction, and I have put lots of characters'
names and the names of Pokémon into my dictionary so that they are pronounced properly. The other synths simply do not like these names, no matter what I try to do with them, and some of them even pronounced my name wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their changes to a previous version (surely they have older versions backed up somewhere. I would if I was developing something like this), and for NVDA to likewise roll back the version packaged with it until the devs of the synth work out how to alter one language without screwing up twenty others in the process. I know I can only go so far before I am forced to update to the latest version of NVDA or be left to languish as more and more things become incompatible with the last tolerable version I have.


Please, I am begging you, do something about this.


Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

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

Well some improvements seem to be there, but I am still using the Speech player in Espeak, but selected for the old voices. At least this is better than the current odd situation where its a mixed bag..
I'm sure others have something to say.I don't know if the sapi version of Espeak is any different, not tried it.
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: "Sharni-Lee Ward" <sharni-lee.ward@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 25, 2018 6:27 AM
Subject: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?


I've just caught up on all my emails. If I understood an earlier thread
correctly, despite our complaints when 2017.4 came out, the devs did not
roll back the version of espeak packaged with NVDA to the version in
2017.3, which means that I will not be updating NVDA, despite the
wonderful-sounding new features.


Espeak, and subsequently Espeak NG, has been my default synth since I
started using NVDA. There was an issue in 2014 but I was able to get
used to that, and then it got fixed, so I was contented. The problems I
found in the espeak packaged with 2017.4 were more than I could stand,
as someone who primarily uses NVDA to read fanfiction and my own
stories. However, Espeak is among the only synths compatible with NVDA's
inflection slider, which I have maxed out for optimal performance. I'm
not about to sacrifice broad inflection for the drones of MS voices, and
I'm currently using a Win 7 computer, but even if I was on a Win 10 one,
the 1Core voices don't do it for me either. They're pleasant, but also
flat. No inflection. No way to change the inflection. I can't stand
human-sounding voices because they're less flexible than synthetic ones
in this regard. Also, nearly all non Espeak voices are slow as well as
flat, partially due to the length of pauses between clauses of a
sentence, and this is about as unbearable as the flatness. And there is
one more thing that really clinches my unwillingness to change synths. I
cannot get anything else to cooperate with my speech dictionary. As I
said, I read a lot of fanfiction, and I have put lots of characters'
names and the names of Pokémon into my dictionary so that they are
pronounced properly. The other synths simply do not like these names, no
matter what I try to do with them, and some of them even pronounced my
name wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their
changes to a previous version (surely they have older versions backed up
somewhere. I would if I was developing something like this), and for
NVDA to likewise roll back the version packaged with it until the devs
of the synth work out how to alter one language without screwing up
twenty others in the process. I know I can only go so far before I am
forced to update to the latest version of NVDA or be left to languish as
more and more things become incompatible with the last tolerable version
I have.


Please, I am begging you, do something about this.




Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

Sharni-Lee Ward
 

The last time I tried something like that I broke Espeak so thoroughly that NVDA couldn't boot up and I had to uninstall and reinstall from a portable copy. And that was to try and fix a much more minor issue than this current one.


Words and phrases that I have found which are slurred include, but are not limited to: our, hour, they're, percent (the only one I've been able to fix so far), and the phrases "for the" and "for a". I'll probably be reminded of more in the future. Did others on the list just learn to put up with this or what?


On 25/03/2018 5:26 PM, Hareth wrote:
You can try to copy the "synthDrivers" folder from your preferred NVDA
version installation directory,
and replace it with the current NVDA release.
I'd assume it would work for you.

On 3/25/18, Sharni-Lee Ward <sharni-lee.ward@...> wrote:
Okay, I installed NVDA 2018.1, after creating a portable copy in case it
became too much to bear.


I don't like Eloquence because it isn't as crisp as Espeak. I have compared
it to A.M radio in the past, and Espeak to FM/CD Quality sound. Also, it has
only eight variants as opposed to Espeak's forty-something (I just realised
my lovingly customised alternate female variants have somehow been broken by
more recent changes which makes me sad, but I usually stick with Linda
anyway).


It's still doing the things that annoyed me in December, but I'm willing to
try and see if I get used to them.


I don't expect a program to be perfect. I don't expect a synth to be
perfect. I would like to hope that people don't break something that was
perfectly all right in a previous version, however.


And as for inflection, I have it set to 100% (GAH, it does the thing with
percent....), which makes Eloquence sound overly chipper, another reason I
don't enjoy that synth as much. By flat, I mean the voice does not use
perceptible inflection in the cases of question marks, commas and
exclamation points. This should not be something a blind user has to put up
with when it comes to synthesised voice. How is one supposed to know if the
statement is yelled or spoken calmly if the voice doesn't give it away? How
emotionally invested can they be in a story if there is no noticeable
inflection for something as basic as exclamations and question marks?



On 25/03/2018 4:54 PM, Gene wrote:
I need to correct one statement.  You can't, as it appears, change
inflection in Eloquence with NVDA.  I don't know what you consider flat.
But if you give Eloquence a chance, you may find that the amount of
inflection it uses is not bothersome to you.  You may want an exaggerated
amount of inflection.  I don't know how you have E-Speak set.  But you may
find that, if you give Eloquence a chance and get used to it, you may find
it generally superior over time.

Gene
----- Original Message -----
From: Gene<mailto:gsasner@...>
Sent: Sunday, March 25, 2018 12:50 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] I take it there have been no improvements to the flawed
espeak ng in 2017.4?

Also, what's wrong with Eloquence?  Have you tried it  And as I recall, you
can adjust inflection with it.  Don't use the Brittish English voice.  It's
obviously programmed by Americans amateurishly trying to imitate a Brittish
accent.  Use the default American English.  It pronounces a great many more
words correctly compared with e-speak.  And I use it very well with the NVDA
speech dictionary.  Are you familiar with the SAPI 5 demo you can try of
Eloquence?  Eloquence and Via Voice, the same synthesizer from a sound and
performance standpoint, are the most accurate in terms of proper
pronounciation of words in my experience.

Gene
----- Original Message -----
From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
<nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>> On Behalf Of Sharni-Lee
Ward
Sent: Saturday, March 24, 2018 10:27 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: [nvda] I take it there have been no improvements to the flawed
espeak ng in 2017.4?

I've just caught up on all my emails. If I understood an earlier thread
correctly, despite our complaints when 2017.4 came out, the devs did not
roll back the version of espeak packaged with NVDA to the version in 2017.3,
which means that I will not be updating NVDA, despite the wonderful-sounding
new features.


Espeak, and subsequently Espeak NG, has been my default synth since I
started using NVDA. There was an issue in 2014 but I was able to get used to
that, and then it got fixed, so I was contented. The problems I found in the
espeak packaged with 2017.4 were more than I could stand, as someone who
primarily uses NVDA to read fanfiction and my own stories. However, Espeak
is among the only synths compatible with NVDA's inflection slider, which I
have maxed out for optimal performance. I'm not about to sacrifice broad
inflection for the drones of MS voices, and I'm currently using a Win 7
computer, but even if I was on a Win 10 one, the 1Core voices don't do it
for me either. They're pleasant, but also flat. No inflection. No way to
change the inflection. I can't stand human-sounding voices because they're
less flexible than synthetic ones in this regard. Also, nearly all non
Espeak voices are slow as well as flat, partially due to the length of
pauses between clauses of a sentence, and this is about as unbearable as the
flatness. And there is one more thing that really clinches my unwillingness
to change synths. I cannot get anything else to cooperate with my speech
dictionary. As I said, I read a lot of fanfiction, and I have put lots of
characters'
names and the names of Pokémon into my dictionary so that they are
pronounced properly. The other synths simply do not like these names, no
matter what I try to do with them, and some of them even pronounced my name
wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their changes to
a previous version (surely they have older versions backed up somewhere. I
would if I was developing something like this), and for NVDA to likewise
roll back the version packaged with it until the devs of the synth work out
how to alter one language without screwing up twenty others in the process.
I know I can only go so far before I am forced to update to the latest
version of NVDA or be left to languish as more and more things become
incompatible with the last tolerable version I have.


Please, I am begging you, do something about this.















Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

Hareth
 

You can try to copy the "synthDrivers" folder from your preferred NVDA
version installation directory,
and replace it with the current NVDA release.
I'd assume it would work for you.

On 3/25/18, Sharni-Lee Ward <sharni-lee.ward@hotmail.com> wrote:
Okay, I installed NVDA 2018.1, after creating a portable copy in case it
became too much to bear.


I don't like Eloquence because it isn't as crisp as Espeak. I have compared
it to A.M radio in the past, and Espeak to FM/CD Quality sound. Also, it has
only eight variants as opposed to Espeak's forty-something (I just realised
my lovingly customised alternate female variants have somehow been broken by
more recent changes which makes me sad, but I usually stick with Linda
anyway).


It's still doing the things that annoyed me in December, but I'm willing to
try and see if I get used to them.


I don't expect a program to be perfect. I don't expect a synth to be
perfect. I would like to hope that people don't break something that was
perfectly all right in a previous version, however.


And as for inflection, I have it set to 100% (GAH, it does the thing with
percent....), which makes Eloquence sound overly chipper, another reason I
don't enjoy that synth as much. By flat, I mean the voice does not use
perceptible inflection in the cases of question marks, commas and
exclamation points. This should not be something a blind user has to put up
with when it comes to synthesised voice. How is one supposed to know if the
statement is yelled or spoken calmly if the voice doesn't give it away? How
emotionally invested can they be in a story if there is no noticeable
inflection for something as basic as exclamations and question marks?



On 25/03/2018 4:54 PM, Gene wrote:
I need to correct one statement. You can't, as it appears, change
inflection in Eloquence with NVDA. I don't know what you consider flat.
But if you give Eloquence a chance, you may find that the amount of
inflection it uses is not bothersome to you. You may want an exaggerated
amount of inflection. I don't know how you have E-Speak set. But you may
find that, if you give Eloquence a chance and get used to it, you may find
it generally superior over time.

Gene
----- Original Message -----
From: Gene<mailto:gsasner@ripco.com>
Sent: Sunday, March 25, 2018 12:50 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] I take it there have been no improvements to the flawed
espeak ng in 2017.4?

Also, what's wrong with Eloquence? Have you tried it And as I recall, you
can adjust inflection with it. Don't use the Brittish English voice. It's
obviously programmed by Americans amateurishly trying to imitate a Brittish
accent. Use the default American English. It pronounces a great many more
words correctly compared with e-speak. And I use it very well with the NVDA
speech dictionary. Are you familiar with the SAPI 5 demo you can try of
Eloquence? Eloquence and Via Voice, the same synthesizer from a sound and
performance standpoint, are the most accurate in terms of proper
pronounciation of words in my experience.

Gene
----- Original Message -----
From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
<nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>> On Behalf Of Sharni-Lee
Ward
Sent: Saturday, March 24, 2018 10:27 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: [nvda] I take it there have been no improvements to the flawed
espeak ng in 2017.4?

I've just caught up on all my emails. If I understood an earlier thread
correctly, despite our complaints when 2017.4 came out, the devs did not
roll back the version of espeak packaged with NVDA to the version in 2017.3,
which means that I will not be updating NVDA, despite the wonderful-sounding
new features.


Espeak, and subsequently Espeak NG, has been my default synth since I
started using NVDA. There was an issue in 2014 but I was able to get used to
that, and then it got fixed, so I was contented. The problems I found in the
espeak packaged with 2017.4 were more than I could stand, as someone who
primarily uses NVDA to read fanfiction and my own stories. However, Espeak
is among the only synths compatible with NVDA's inflection slider, which I
have maxed out for optimal performance. I'm not about to sacrifice broad
inflection for the drones of MS voices, and I'm currently using a Win 7
computer, but even if I was on a Win 10 one, the 1Core voices don't do it
for me either. They're pleasant, but also flat. No inflection. No way to
change the inflection. I can't stand human-sounding voices because they're
less flexible than synthetic ones in this regard. Also, nearly all non
Espeak voices are slow as well as flat, partially due to the length of
pauses between clauses of a sentence, and this is about as unbearable as the
flatness. And there is one more thing that really clinches my unwillingness
to change synths. I cannot get anything else to cooperate with my speech
dictionary. As I said, I read a lot of fanfiction, and I have put lots of
characters'
names and the names of Pokémon into my dictionary so that they are
pronounced properly. The other synths simply do not like these names, no
matter what I try to do with them, and some of them even pronounced my name
wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their changes to
a previous version (surely they have older versions backed up somewhere. I
would if I was developing something like this), and for NVDA to likewise
roll back the version packaged with it until the devs of the synth work out
how to alter one language without screwing up twenty others in the process.
I know I can only go so far before I am forced to update to the latest
version of NVDA or be left to languish as more and more things become
incompatible with the last tolerable version I have.


Please, I am begging you, do something about this.











Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

Sharni-Lee Ward
 

Okay, I installed NVDA 2018.1, after creating a portable copy in case it became too much to bear.


I don't like Eloquence because it isn't as crisp as Espeak. I have compared it to A.M radio in the past, and Espeak to FM/CD Quality sound. Also, it has only eight variants as opposed to Espeak's forty-something (I just realised my lovingly customised alternate female variants have somehow been broken by more recent changes which makes me sad, but I usually stick with Linda anyway).


It's still doing the things that annoyed me in December, but I'm willing to try and see if I get used to them.


I don't expect a program to be perfect. I don't expect a synth to be perfect. I would like to hope that people don't break something that was perfectly all right in a previous version, however.


And as for inflection, I have it set to 100% (GAH, it does the thing with percent....), which makes Eloquence sound overly chipper, another reason I don't enjoy that synth as much. By flat, I mean the voice does not use perceptible inflection in the cases of question marks, commas and exclamation points. This should not be something a blind user has to put up with when it comes to synthesised voice. How is one supposed to know if the statement is yelled or spoken calmly if the voice doesn't give it away? How emotionally invested can they be in a story if there is no noticeable inflection for something as basic as exclamations and question marks?

 


On 25/03/2018 4:54 PM, Gene wrote:
I need to correct one statement.  You can't, as it appears, change inflection in Eloquence with NVDA.  I don't know what you consider flat.  But if you give Eloquence a chance, you may find that the amount of inflection it uses is not bothersome to you.  You may want an exaggerated amount of inflection.  I don't know how you have E-Speak set.  But you may find that, if you give Eloquence a chance and get used to it, you may find it generally superior over time. 
 
Gene
----- Original Message -----
From: Gene
Sent: Sunday, March 25, 2018 12:50 AM
Subject: Re: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?

Also, what's wrong with Eloquence?  Have you tried it  And as I recall, you can adjust inflection with it.  Don't use the Brittish English voice.  It's obviously programmed by Americans amateurishly trying to imitate a Brittish accent.  Use the default American English.  It pronounces a great many more words correctly compared with e-speak.  And I use it very well with the NVDA speech dictionary.  Are you familiar with the SAPI 5 demo you can try of Eloquence?  Eloquence and Via Voice, the same synthesizer from a sound and performance standpoint, are the most accurate in terms of proper pronounciation of words in my experience. 
 
Gene
----- Original Message -----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sharni-Lee Ward
Sent: Saturday, March 24, 2018 10:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?

I've just caught up on all my emails. If I understood an earlier thread correctly, despite our complaints when 2017.4 came out, the devs did not roll back the version of espeak packaged with NVDA to the version in 2017.3, which means that I will not be updating NVDA, despite the wonderful-sounding new features.


Espeak, and subsequently Espeak NG, has been my default synth since I started using NVDA. There was an issue in 2014 but I was able to get used to that, and then it got fixed, so I was contented. The problems I found in the espeak packaged with 2017.4 were more than I could stand, as someone who primarily uses NVDA to read fanfiction and my own stories. However, Espeak is among the only synths compatible with NVDA's inflection slider, which I have maxed out for optimal performance. I'm not about to sacrifice broad inflection for the drones of MS voices, and I'm currently using a Win 7 computer, but even if I was on a Win 10 one, the 1Core voices don't do it for me either. They're pleasant, but also flat. No inflection. No way to change the inflection. I can't stand human-sounding voices because they're less flexible than synthetic ones in this regard. Also, nearly all non Espeak voices are slow as well as flat, partially due to the length of pauses between clauses of a sentence, and this is about as unbearable as the flatness. And there is one more thing that really clinches my unwillingness to change synths. I cannot get anything else to cooperate with my speech dictionary. As I said, I read a lot of fanfiction, and I have put lots of characters'
names and the names of Pokémon into my dictionary so that they are pronounced properly. The other synths simply do not like these names, no matter what I try to do with them, and some of them even pronounced my name wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their changes to a previous version (surely they have older versions backed up somewhere. I would if I was developing something like this), and for NVDA to likewise roll back the version packaged with it until the devs of the synth work out how to alter one language without screwing up twenty others in the process. I know I can only go so far before I am forced to update to the latest version of NVDA or be left to languish as more and more things become incompatible with the last tolerable version I have.


Please, I am begging you, do something about this.










Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

Gene
 

I need to correct one statement.  You can't, as it appears, change inflection in Eloquence with NVDA.  I don't know what you consider flat.  But if you give Eloquence a chance, you may find that the amount of inflection it uses is not bothersome to you.  You may want an exaggerated amount of inflection.  I don't know how you have E-Speak set.  But you may find that, if you give Eloquence a chance and get used to it, you may find it generally superior over time. 
 
Gene

----- Original Message -----
From: Gene
Sent: Sunday, March 25, 2018 12:50 AM
Subject: Re: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?

Also, what's wrong with Eloquence?  Have you tried it  And as I recall, you can adjust inflection with it.  Don't use the Brittish English voice.  It's obviously programmed by Americans amateurishly trying to imitate a Brittish accent.  Use the default American English.  It pronounces a great many more words correctly compared with e-speak.  And I use it very well with the NVDA speech dictionary.  Are you familiar with the SAPI 5 demo you can try of Eloquence?  Eloquence and Via Voice, the same synthesizer from a sound and performance standpoint, are the most accurate in terms of proper pronounciation of words in my experience. 
 
Gene
----- Original Message -----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sharni-Lee Ward
Sent: Saturday, March 24, 2018 10:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?

I've just caught up on all my emails. If I understood an earlier thread correctly, despite our complaints when 2017.4 came out, the devs did not roll back the version of espeak packaged with NVDA to the version in 2017.3, which means that I will not be updating NVDA, despite the wonderful-sounding new features.


Espeak, and subsequently Espeak NG, has been my default synth since I started using NVDA. There was an issue in 2014 but I was able to get used to that, and then it got fixed, so I was contented. The problems I found in the espeak packaged with 2017.4 were more than I could stand, as someone who primarily uses NVDA to read fanfiction and my own stories. However, Espeak is among the only synths compatible with NVDA's inflection slider, which I have maxed out for optimal performance. I'm not about to sacrifice broad inflection for the drones of MS voices, and I'm currently using a Win 7 computer, but even if I was on a Win 10 one, the 1Core voices don't do it for me either. They're pleasant, but also flat. No inflection. No way to change the inflection. I can't stand human-sounding voices because they're less flexible than synthetic ones in this regard. Also, nearly all non Espeak voices are slow as well as flat, partially due to the length of pauses between clauses of a sentence, and this is about as unbearable as the flatness. And there is one more thing that really clinches my unwillingness to change synths. I cannot get anything else to cooperate with my speech dictionary. As I said, I read a lot of fanfiction, and I have put lots of characters'
names and the names of Pokémon into my dictionary so that they are pronounced properly. The other synths simply do not like these names, no matter what I try to do with them, and some of them even pronounced my name wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their changes to a previous version (surely they have older versions backed up somewhere. I would if I was developing something like this), and for NVDA to likewise roll back the version packaged with it until the devs of the synth work out how to alter one language without screwing up twenty others in the process. I know I can only go so far before I am forced to update to the latest version of NVDA or be left to languish as more and more things become incompatible with the last tolerable version I have.


Please, I am begging you, do something about this.









Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

Gene
 

Also, what's wrong with Eloquence?  Have you tried it  And as I recall, you can adjust inflection with it.  Don't use the Brittish English voice.  It's obviously programmed by Americans amateurishly trying to imitate a Brittish accent.  Use the default American English.  It pronounces a great many more words correctly compared with e-speak.  And I use it very well with the NVDA speech dictionary.  Are you familiar with the SAPI 5 demo you can try of Eloquence?  Eloquence and Via Voice, the same synthesizer from a sound and performance standpoint, are the most accurate in terms of proper pronounciation of words in my experience. 
 
Gene

----- Original Message -----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sharni-Lee Ward
Sent: Saturday, March 24, 2018 10:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?

I've just caught up on all my emails. If I understood an earlier thread correctly, despite our complaints when 2017.4 came out, the devs did not roll back the version of espeak packaged with NVDA to the version in 2017.3, which means that I will not be updating NVDA, despite the wonderful-sounding new features.


Espeak, and subsequently Espeak NG, has been my default synth since I started using NVDA. There was an issue in 2014 but I was able to get used to that, and then it got fixed, so I was contented. The problems I found in the espeak packaged with 2017.4 were more than I could stand, as someone who primarily uses NVDA to read fanfiction and my own stories. However, Espeak is among the only synths compatible with NVDA's inflection slider, which I have maxed out for optimal performance. I'm not about to sacrifice broad inflection for the drones of MS voices, and I'm currently using a Win 7 computer, but even if I was on a Win 10 one, the 1Core voices don't do it for me either. They're pleasant, but also flat. No inflection. No way to change the inflection. I can't stand human-sounding voices because they're less flexible than synthetic ones in this regard. Also, nearly all non Espeak voices are slow as well as flat, partially due to the length of pauses between clauses of a sentence, and this is about as unbearable as the flatness. And there is one more thing that really clinches my unwillingness to change synths. I cannot get anything else to cooperate with my speech dictionary. As I said, I read a lot of fanfiction, and I have put lots of characters'
names and the names of Pokémon into my dictionary so that they are pronounced properly. The other synths simply do not like these names, no matter what I try to do with them, and some of them even pronounced my name wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their changes to a previous version (surely they have older versions backed up somewhere. I would if I was developing something like this), and for NVDA to likewise roll back the version packaged with it until the devs of the synth work out how to alter one language without screwing up twenty others in the process. I know I can only go so far before I am forced to update to the latest version of NVDA or be left to languish as more and more things become incompatible with the last tolerable version I have.


Please, I am begging you, do something about this.









Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

Rosemarie Chavarria
 

Hi,

I'm sorry but there's no such thing as a perfect program or synth. Why don't you give NVDA 2018.1 a try. It still has the inflection. You can try changing some word pronunciations but don't expect everything to be perfect. That's not reality. I won't say anything more.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sharni-Lee Ward
Sent: Saturday, March 24, 2018 10:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?

I've just caught up on all my emails. If I understood an earlier thread correctly, despite our complaints when 2017.4 came out, the devs did not roll back the version of espeak packaged with NVDA to the version in 2017.3, which means that I will not be updating NVDA, despite the wonderful-sounding new features.


Espeak, and subsequently Espeak NG, has been my default synth since I started using NVDA. There was an issue in 2014 but I was able to get used to that, and then it got fixed, so I was contented. The problems I found in the espeak packaged with 2017.4 were more than I could stand, as someone who primarily uses NVDA to read fanfiction and my own stories. However, Espeak is among the only synths compatible with NVDA's inflection slider, which I have maxed out for optimal performance. I'm not about to sacrifice broad inflection for the drones of MS voices, and I'm currently using a Win 7 computer, but even if I was on a Win 10 one, the 1Core voices don't do it for me either. They're pleasant, but also flat. No inflection. No way to change the inflection. I can't stand human-sounding voices because they're less flexible than synthetic ones in this regard. Also, nearly all non Espeak voices are slow as well as flat, partially due to the length of pauses between clauses of a sentence, and this is about as unbearable as the flatness. And there is one more thing that really clinches my unwillingness to change synths. I cannot get anything else to cooperate with my speech dictionary. As I said, I read a lot of fanfiction, and I have put lots of characters'
names and the names of Pokémon into my dictionary so that they are pronounced properly. The other synths simply do not like these names, no matter what I try to do with them, and some of them even pronounced my name wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their changes to a previous version (surely they have older versions backed up somewhere. I would if I was developing something like this), and for NVDA to likewise roll back the version packaged with it until the devs of the synth work out how to alter one language without screwing up twenty others in the process. I know I can only go so far before I am forced to update to the latest version of NVDA or be left to languish as more and more things become incompatible with the last tolerable version I have.


Please, I am begging you, do something about this.


Re: I take it there have been no improvements to the flawed espeak ng in 2017.4?

 

Hi,
May I kindly request that you do something too: please try with 2018.1.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sharni-Lee Ward
Sent: Saturday, March 24, 2018 10:27 PM
To: nvda@nvda.groups.io
Subject: [nvda] I take it there have been no improvements to the flawed espeak ng in 2017.4?

I've just caught up on all my emails. If I understood an earlier thread correctly, despite our complaints when 2017.4 came out, the devs did not roll back the version of espeak packaged with NVDA to the version in 2017.3, which means that I will not be updating NVDA, despite the wonderful-sounding new features.


Espeak, and subsequently Espeak NG, has been my default synth since I started using NVDA. There was an issue in 2014 but I was able to get used to that, and then it got fixed, so I was contented. The problems I found in the espeak packaged with 2017.4 were more than I could stand, as someone who primarily uses NVDA to read fanfiction and my own stories. However, Espeak is among the only synths compatible with NVDA's inflection slider, which I have maxed out for optimal performance. I'm not about to sacrifice broad inflection for the drones of MS voices, and I'm currently using a Win 7 computer, but even if I was on a Win 10 one, the 1Core voices don't do it for me either. They're pleasant, but also flat. No inflection. No way to change the inflection. I can't stand human-sounding voices because they're less flexible than synthetic ones in this regard. Also, nearly all non Espeak voices are slow as well as flat, partially due to the length of pauses between clauses of a sentence, and this is about as unbearable as the flatness. And there is one more thing that really clinches my unwillingness to change synths. I cannot get anything else to cooperate with my speech dictionary. As I said, I read a lot of fanfiction, and I have put lots of characters'
names and the names of Pokémon into my dictionary so that they are pronounced properly. The other synths simply do not like these names, no matter what I try to do with them, and some of them even pronounced my name wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their changes to a previous version (surely they have older versions backed up somewhere. I would if I was developing something like this), and for NVDA to likewise roll back the version packaged with it until the devs of the synth work out how to alter one language without screwing up twenty others in the process. I know I can only go so far before I am forced to update to the latest version of NVDA or be left to languish as more and more things become incompatible with the last tolerable version I have.


Please, I am begging you, do something about this.


I take it there have been no improvements to the flawed espeak ng in 2017.4?

Sharni-Lee Ward
 

I've just caught up on all my emails. If I understood an earlier thread
correctly, despite our complaints when 2017.4 came out, the devs did not
roll back the version of espeak packaged with NVDA to the version in
2017.3, which means that I will not be updating NVDA, despite the
wonderful-sounding new features.


Espeak, and subsequently Espeak NG, has been my default synth since I
started using NVDA. There was an issue in 2014 but I was able to get
used to that, and then it got fixed, so I was contented. The problems I
found in the espeak packaged with 2017.4 were more than I could stand,
as someone who primarily uses NVDA to read fanfiction and my own
stories. However, Espeak is among the only synths compatible with NVDA's
inflection slider, which I have maxed out for optimal performance. I'm
not about to sacrifice broad inflection for the drones of MS voices, and
I'm currently using a Win 7 computer, but even if I was on a Win 10 one,
the 1Core voices don't do it for me either. They're pleasant, but also
flat. No inflection. No way to change the inflection. I can't stand
human-sounding voices because they're less flexible than synthetic ones
in this regard. Also, nearly all non Espeak voices are slow as well as
flat, partially due to the length of pauses between clauses of a
sentence, and this is about as unbearable as the flatness. And there is
one more thing that really clinches my unwillingness to change synths. I
cannot get anything else to cooperate with my speech dictionary. As I
said, I read a lot of fanfiction, and I have put lots of characters'
names and the names of Pokémon into my dictionary so that they are
pronounced properly. The other synths simply do not like these names, no
matter what I try to do with them, and some of them even pronounced my
name wrong, so I gave up on them.


This is why I want whoever's developing Espeak to roll back their
changes to a previous version (surely they have older versions backed up
somewhere. I would if I was developing something like this), and for
NVDA to likewise roll back the version packaged with it until the devs
of the synth work out how to alter one language without screwing up
twenty others in the process. I know I can only go so far before I am
forced to update to the latest version of NVDA or be left to languish as
more and more things become incompatible with the last tolerable version
I have.


Please, I am begging you, do something about this.


Re: Issue With Excel 2016

Ron Canazzi
 

Hello:


The warning has existed since I had Excel 2013.  It ix a simple security warning that says:


"Microsoft Excel Security Notice Microsoft Office has identified a potential security concern.
The operation connects to an external data source.
External data sources are used to import data into Excel, but connections to external data sources can be used by queries to access confidential information available to other users, or to perform other harmful actions. If you trust the source of this file, click OK."


Now as I said, I have been getting this warning with both Windows 8.1 and 10 since 2013.  In the past, I simply clicked OK and the file name field appeared, I typed the path to the file name, clicked open and the wizard would launch.


Here is some other information.  I am using the ribbon hotkeys to import data from a text file.  This sequences is as follows:

alt + A for data followed by F for file T for text.  This has worked since 2013 as well.  Now when I followed those steps, rather than the wizard, I get a largely inaccessible dialogue and the first field is a choice of character sets with the default being 1252: Western European (Windows)


Hopefully, this information will give you some idea as to what is happening. It is as if there is no longer a wizard and some preset of some sort is coming up and asking me to verify or edit it.

On 3/24/2018 8:00 PM, Cearbhall O'Meadhra wrote:
Ron,

I don't get any warning message. That implies something different that might relate to the problem you are having. What does the message say?

I have just saved your lines into a text file in notepad. The rows are no longer defined by a carriage return in your message but it is clear that cell 1 contains the word "Multimedia" so I put a carriage return in front of each.
Here is what I experienced:

I opened the browse window with alt>f>o>o and the import wizard came up offering step 1 of 3.
The first step offered that the file data was "Fixed length" so I arrowed up to "Delimited". I ignored the start at and tabbed to Next and step 2 opened.
In Step 2 "Tab" was already selected as the delimiter. I unchecked that and tabbed to the next item which was "Semicolon", so I selected that. I then tabbed to "Next" and Step 3 opened.
In Step 3, I skipped over the format selections and tabbed down to "Finish".
The data was successfully imported into a table within Excel - not the original workbook that I had opened with a new worksheet to take the data. When I tried to save the data, I had no choice but to save it as a new workbook with the name of the original text file.

Every step of the wizard was fully accessible. I am attaching the text file and workbook here for your information.

By the way, I tried a second experiment to see if the data would go into an existing workbook:
I opened "Data" on the menu bar and selected "Get and transform Data". This had a few options and so I tabbed around and selected "From File". The second step opened and I accepted the offered "semicolon" as delimiter. I then tabbed to "Import". This opened a new step where I could set the delimiter and other details which were all visible to NVDA. I then tabbed to "Load" and the whole text file was placed in a new worksheet within the open existing workbook. I did have a worksheet ready but the wizard ignored that and inserted a new "Sheet1" to take the imported data.

I appreciate that all of this is what you describe as being no longer available to you. If it helps, I can confirm that it is still available in Excel 2016.

Perhaps the warning message will give us a clue?

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@blbc.ie


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: Saturday, March 24, 2018 8:41 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Issue With Excel 2016

Hi Rich,


I have been using semi colon [;] for the delimiters for years from Excel
2000 up until Excel2016 just a few weeks ago. I never had this problem before. I save the text file with the standard txt extension. I use Notepad to create the files. The common parameters--which used to appear in the wizard when trying to import the file first ask 'what line of the import file you wish to begin at (the default is line 1) You click next and the second screen asks for the delimiter and I choose semi colon [;]. the next few screens have to do with formulas and other things that i just bypass and then click finish. This wizard like interface no longer occurs when I try the import of the text file. I get the Microsoft security warning which I dismiss and then this odd and new inaccessible interface.


Here are a few lines from the text file I have been trying to import.


Multimedia 363;1950 - The Littlest Angel - Lullaby of Christmas;01 - the littlest angel.mp3 Multimedia 363;1950 - The Littlest Angel - Lullaby of Christmas;02 - lullaby of christmas.mp3 Multimedia 363;baja marimba band - 2001 best of;01 along comes mary.mp3 Multimedia 363;baja marimba band - 2001 best of;02 juarez.mp3 Multimedia 363;baja marimba band - 2001 best of;03 comin' in the back
door.mp3
Multimedia 363;baja marimba band - 2001 best of;04 georgy girl.mp3



On 3/24/2018 8:32 AM, Rick wrote:
Hello Ron:

What file extension are you using for the file you are attempting to import? Excel has a common format (.csv) which stands for Comma Separated Variables, where each field is separated using a comma in the file. Each field in the line of text is then placed in a separate cell in a row. Each new line will begin another row in the worksheet.

Also, can you give us a few sample lines from the file you are attempting to import and the rules you want to apply to the import process?

Thanks, Rick

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron
Canazzi
Sent: Saturday, March 24, 2018 7:45 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Issue With Excel 2016

Hello:


I open the existing Excel Work Book.

I then use open file and type in the path and file name of the delimited text file.


This used to work. I used to get a wizard of sorts that could have a
back, next and finish and step by step, I would be asked which column
I should start the import at, what delimited I should use and other
parameters I should use.


Now I get this odd inaccessible dialogue.



On 3/24/2018 6:50 AM, Cearbhall O'Meadhra wrote:
Hi Ron,

I am using excel 2016 in Windows 10 and a choice of both NVDA and JAWS 17. All are up to the latest versions.

I am curious about your issue as I do a lot of work with excel myself.

I have just created a tab delimited text file and imported it successfully. I tried using the File>Open dialog and the "Get external data" option on the Data Menu. Although the resulting dialog is different in each case, I found every part of the dialog fully accessible with NVDA.

In older versions of Excel, I used to import text files using the File>Open dialog. I was surprised to find that I cannot do this in excel 2016.

You don't say what technique you are using, but if you explain exactly what you have been attempting I would be happy to explore it with you and see what might have changed.


All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e:
cearbhall.omeadhra@blbc.ie


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron
Canazzi
Sent: Saturday, March 24, 2018 1:28 AM
To: nvda@nvda.groups.io
Subject: [nvda] Issue With Excel 2016

Hi Group,


For years, I have been using Microsoft Excel to make a simple spread sheet database for various of my music and movie files. I usually do this by creating a delimited text file using Notepad and then importing the file into Excel via the import data/text file item. For years this has worked. I would click the file and then I would get a Microsoft Security warning and then the file would open and a wizard of sorts would launch and ask me for the parameters: delimiters, beginning column, and so on.


However, now when I load an existing file into Excel, I get some sort of weird interface that doesn't seem to work with NVDA or JAWS and I am unable to complete the importation as I normally did.


I assume that either an update to Office 2016 or some other update to Windows 10 has changed some default setting in Excel that makes things operate differently. I have looked under options in the Excel program but I am unable to find what might be causing this difference. What setting could be changed to get things back to where they used to be for my Excel program?


Thanks for any help.


--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"







--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"





--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Re: Recently updated on accessibilitycentral.net

Gene New Zealand <hurrikennyandopo@...>
 

Hi Adriani


Yep I am looking at doing a page for nvda screen reader related resources  which i will add it into which will be a separate web page. In that page I will break it down into say audio resources, video resources maybe nvda blogs? about using nvda? Not quite sure of other sections if i do and would be more a point to page but not jeffs one.

Even though he had a good site.


I am guessing we do  have links to other nvda resources like on you tube etc but not in the one place.


Gene nz







On 3/5/2018 9:22 PM, Adriani Botez wrote:

Gene,

 

thanks for including that. I wonder if Joseph’s new tutorials set “welcome to NVDA 2018” can be included as well?

 

Best

Adriani

 

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Gene New Zealand
Gesendet: Montag, 5. März 2018 03:21
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Recently updated on accessibilitycentral.net

 

Hi Adriani

 

I was not sure if it worked on XP as when the directions went up i think at that time it had been tested on 7,8 and 10.

 

Would the directions from 10 also work on XP? to get into it as i used to do it the other way that was posted.

 

I have not any XP machines here now to test with.

 

The directions you gave are on the nvda audio tutorials page under trouble shooting.

 

Gene nz

 

 

On 3/4/2018 11:45 AM, Adriani Botez wrote:

Hello,

 

we had this conversation some months ago, here is a gegistry file which activates your sound driver in safe mode. It has been tested with XP as well and it works perfectly. NVDA can be used in safe mode after activating this file:

 

https://www.dropbox.com/s/ebkqst6n393i6jk/Activate_Sound_in_Win10_Safe_Mode.zip?dl=1

 

 

Best

Adriani

 

Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Gene New Zealand
Gesendet: Samstag, 3. März 2018 19:47
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Recently updated on accessibilitycentral.net

 

Hi

 

the old way to get into safe mode in windows 10 can be found here at https://www.lifewire.com/how-to-boot-to-safe-mode-with-command-prompt-2624541

 

You will need a pair of eyes to do this plus you might not even have sound.

 

So am guessing you will need to burrow some eyes and give them directions to fix the problem.

 

Gene nz

 

 

On 3/4/2018 2:58 AM, zahra wrote:

hi gene thanks so much for your great work of you and other members.
how can i access safe mode in windows xp with nvda?
does it have solution for users of xp?
thanks so much every one and God bless you all!
 
On 3/3/18, Gene New Zealand <hurrikennyandopo@...> wrote:
HI guys
 
Recently updated on accessibilitycentral.net
 
RECENTLY UPDATED:
 
 
Added a link to all NVDA related pages for the new NVDA promotional video.
 
Added a link to the addons page for the NVDA Add-on developers guide which
has been updated for 2018.1
 
Added a review of the Samsung UA50MU6100SXNZ television to the podcasts and
product reviews page
http://accessibilitycentral.net/podcasts%20and%20product%20reviews.html
 
NEW:
 
Added a page called Skype Trusted Microsoft Store App (off the NVDA
tutorials for other programs page)
http://accessibilitycentral.net/nvda%20tutorials%20for%20other%20programs.html
as well as a page called Using Windows Media Player with NVDA.
 
Gene NZ
 
On 12/13/2017 12:59 PM, David Moore wrote:
Hi Gene NZ!
Thanks so much for what you do for us!
God bless!
David Moore
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
10
 
From: Gene New Zealand<mailto:hurrikennyandopo@...>
Sent: Tuesday, December 12, 2017 3:01 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: [nvda] Recently updated on accessibilitycentral.net
 
 
Hi guys
 
Pages recently updated
Recently updated: Added links to NVDA Guides on all NVDA related pages
 
New: Added a tutorial How to access safe mode in Windows and exit it with
the NVDA screen reader by Hareth  and co to the NVDA audio tutorials page
under the troubleshooting section
http://accessibilitycentral.net/nvda%20audio%20tutorials.html Added a
tutorial (by Gene Asner) called Navigating ribbons in WordPad (to the NVDA
tutorials learning the basics page)
http://accessibilitycentral.net/nvda%20tutorials%20learning%20the%20basics.html
Added a tutorial called Using the Ribbon interface in Windows via the
keyboard (by Brian Vogel) to the NVDA tutorials for Windows 10 page.
http://accessibilitycentral.net/nvda%20tutorials%20for%20windows%2010.html
 
Gene NZ
--
[Image                NVDA certified expert]
Check out my website for NVDA tutorials and other blindness related material
at http://www.accessibilitycentral.net Regardless of where you are in New
Zealand if you are near one of the APNK sites you can use a copy of the NVDA
screen reader on one of their computers. To find out which locations (or
location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa
People's Network Kaharoa). To find an NVDA certified expert near you, please
visit the following link https://certification.nvaccess.org/. The
certification page contains the official list of NVDA certified individuals
from around the world, who have sat and successfully passed the NVDA expert
exam.
 
 
 
--
[Image NVDA          certified expert]
Check out my website for NVDA tutorials and other blindness related material
at http://www.accessibilitycentral.net Regardless of where you are in New
Zealand if you are near one of the APNK sites you can use a copy of the NVDA
screen reader on one of their computers. To find out which locations (or
location) is near to you please visit
http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa
People's Network Kaharoa). To find an NVDA certified expert near you, please
visit the following link https://certification.nvaccess.org/. The
certification page contains the official list of NVDA certified individuals
from around the world, who have sat and successfully passed the NVDA expert
exam.
 
 
 

 

--

Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.

 

--

Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


--
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


Re: Issue With Excel 2016

Cearbhall O'Meadhra
 

Ron,

I don't get any warning message. That implies something different that might relate to the problem you are having. What does the message say?

I have just saved your lines into a text file in notepad. The rows are no longer defined by a carriage return in your message but it is clear that cell 1 contains the word "Multimedia" so I put a carriage return in front of each.
Here is what I experienced:

I opened the browse window with alt>f>o>o and the import wizard came up offering step 1 of 3.
The first step offered that the file data was "Fixed length" so I arrowed up to "Delimited". I ignored the start at and tabbed to Next and step 2 opened.
In Step 2 "Tab" was already selected as the delimiter. I unchecked that and tabbed to the next item which was "Semicolon", so I selected that. I then tabbed to "Next" and Step 3 opened.
In Step 3, I skipped over the format selections and tabbed down to "Finish".
The data was successfully imported into a table within Excel - not the original workbook that I had opened with a new worksheet to take the data. When I tried to save the data, I had no choice but to save it as a new workbook with the name of the original text file.

Every step of the wizard was fully accessible. I am attaching the text file and workbook here for your information.

By the way, I tried a second experiment to see if the data would go into an existing workbook:
I opened "Data" on the menu bar and selected "Get and transform Data". This had a few options and so I tabbed around and selected "From File". The second step opened and I accepted the offered "semicolon" as delimiter. I then tabbed to "Import". This opened a new step where I could set the delimiter and other details which were all visible to NVDA. I then tabbed to "Load" and the whole text file was placed in a new worksheet within the open existing workbook. I did have a worksheet ready but the wizard ignored that and inserted a new "Sheet1" to take the imported data.

I appreciate that all of this is what you describe as being no longer available to you. If it helps, I can confirm that it is still available in Excel 2016.

Perhaps the warning message will give us a clue?

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@blbc.ie

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: Saturday, March 24, 2018 8:41 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Issue With Excel 2016

Hi Rich,


I have been using semi colon [;] for the delimiters for years from Excel
2000 up until Excel2016 just a few weeks ago. I never had this problem before. I save the text file with the standard txt extension. I use Notepad to create the files. The common parameters--which used to appear in the wizard when trying to import the file first ask 'what line of the import file you wish to begin at (the default is line 1) You click next and the second screen asks for the delimiter and I choose semi colon [;]. the next few screens have to do with formulas and other things that i just bypass and then click finish. This wizard like interface no longer occurs when I try the import of the text file. I get the Microsoft security warning which I dismiss and then this odd and new inaccessible interface.


Here are a few lines from the text file I have been trying to import.


Multimedia 363;1950 - The Littlest Angel - Lullaby of Christmas;01 - the littlest angel.mp3 Multimedia 363;1950 - The Littlest Angel - Lullaby of Christmas;02 - lullaby of christmas.mp3 Multimedia 363;baja marimba band - 2001 best of;01 along comes mary.mp3 Multimedia 363;baja marimba band - 2001 best of;02 juarez.mp3 Multimedia 363;baja marimba band - 2001 best of;03 comin' in the back
door.mp3
Multimedia 363;baja marimba band - 2001 best of;04 georgy girl.mp3



On 3/24/2018 8:32 AM, Rick wrote:
Hello Ron:

What file extension are you using for the file you are attempting to import? Excel has a common format (.csv) which stands for Comma Separated Variables, where each field is separated using a comma in the file. Each field in the line of text is then placed in a separate cell in a row. Each new line will begin another row in the worksheet.

Also, can you give us a few sample lines from the file you are attempting to import and the rules you want to apply to the import process?

Thanks, Rick

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron
Canazzi
Sent: Saturday, March 24, 2018 7:45 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Issue With Excel 2016

Hello:


I open the existing Excel Work Book.

I then use open file and type in the path and file name of the delimited text file.


This used to work. I used to get a wizard of sorts that could have a
back, next and finish and step by step, I would be asked which column
I should start the import at, what delimited I should use and other
parameters I should use.


Now I get this odd inaccessible dialogue.



On 3/24/2018 6:50 AM, Cearbhall O'Meadhra wrote:
Hi Ron,

I am using excel 2016 in Windows 10 and a choice of both NVDA and JAWS 17. All are up to the latest versions.

I am curious about your issue as I do a lot of work with excel myself.

I have just created a tab delimited text file and imported it successfully. I tried using the File>Open dialog and the "Get external data" option on the Data Menu. Although the resulting dialog is different in each case, I found every part of the dialog fully accessible with NVDA.

In older versions of Excel, I used to import text files using the File>Open dialog. I was surprised to find that I cannot do this in excel 2016.

You don't say what technique you are using, but if you explain exactly what you have been attempting I would be happy to explore it with you and see what might have changed.


All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e:
cearbhall.omeadhra@blbc.ie


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron
Canazzi
Sent: Saturday, March 24, 2018 1:28 AM
To: nvda@nvda.groups.io
Subject: [nvda] Issue With Excel 2016

Hi Group,


For years, I have been using Microsoft Excel to make a simple spread sheet database for various of my music and movie files. I usually do this by creating a delimited text file using Notepad and then importing the file into Excel via the import data/text file item. For years this has worked. I would click the file and then I would get a Microsoft Security warning and then the file would open and a wizard of sorts would launch and ask me for the parameters: delimiters, beginning column, and so on.


However, now when I load an existing file into Excel, I get some sort of weird interface that doesn't seem to work with NVDA or JAWS and I am unable to complete the importation as I normally did.


I assume that either an update to Office 2016 or some other update to Windows 10 has changed some default setting in Excel that makes things operate differently. I have looked under options in the Excel program but I am unable to find what might be causing this difference. What setting could be changed to get things back to where they used to be for my Excel program?


Thanks for any help.


--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"







--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Re: Firefox Quantum incompatible with NVDA forever?

Robert Mendoza
 

once you hit the download in the Firefox site it automatically detects and install to your machine.

Robert Mendoza

On 3/25/2018 3:44 AM, Casey wrote:
Hi where can you get the latest version of 59 for Firefox for A 64 bit system running windows seven?




On 3/24/2018 11:38 AM, Antony Stone wrote:
What!?

https://www.mozilla.org/en-US/firefox/59.0.1/system-requirements/ says that the
latest version, Firefox 59.0.1, runs on Windows 7, 8 and 10, all 32bit or
64bit, plus MacOS 10.9 onwards, and various versions of Linux.

Firefox is definitely not 64-bit only.

Antony.

On Saturday 24 March 2018 at 17:30:52, Roger Stewart wrote:

For sure!  Several versions of Firefox back, they went to 64 bit only.
Guess this is what they mean by quantum.

Roger

On 3/24/2018 6:21 AM, Walmir Schultz via Groups.Io wrote:
My system is Windows 7 SP1.

I wonder if the problem is related to the fact that it is 32 bits.

Em 23/03/2018 12:09, Ron Canazzi escreveu:
Hi Walmir,


Using Windows 10 and NVDA 2018.1, I have never had any such issues. I
am on Firefox 59.01--the latest version and everything is great.  I
am wondering if your Windows 7 is the basic 7 or service pack1.  If
you have been following this list at all, you will see that NVDA
2018.1 will no longer support any system earlier than Windows 7
Service Pack 1.

On 3/23/2018 8:01 AM, Walmir Schultz via Groups.Io wrote:
Hi,

Since Firefox Quantum (57, 58, 59, ,,,) NVDA is having
incompatibility problems.

Is it time to forget about Quantum?

The 59 version is unusable because NVDA simply don't recognize the
web page, it is "an unknown" objectt.

I am using Windows 7, NVDA 2018.1 32 bits.

I am still using Firefox 52 ESR, but almost changing to Chrome.

Sadly, even Google recognized in its accessibility documentation
that Firefox was the best browser to be used with NVDA.Very sad.


Re: Firefox Quantum incompatible with NVDA forever?

Casey <cwollner@...>
 

Hi can you send me the link to get the latest version.

I went threw ninite and used that installer and it said that it found the esr version.

I don't want that version I want the newest version so how do I correct this?




On 3/24/2018 3:28 PM, Robert Getting wrote:

I am doing fine with NVDA 2018.1. Have not tried waterfox yet because it is not in the portable apps directory and I am feeling lazy. 59 works fine with a few issues that I've seen already filed in mozillas bug tracker so I'm not worried about it at all. I submitted the context menu bug to them just now as well, where I tried to open the menu on a link to copy the link location and the context menu was the system menu. I didn't hear back though.


-- 

Casey


Re: Issue With Excel 2016

Ron Canazzi
 

Hello:



I did try opening using the file open and drive browse method and I still got the same weird interface.  I finally saw a load button, but when I loaded the file, it came up in a new worksheet and not into the current worksheet that I had open as it did in the past.

On 3/24/2018 10:04 AM, Cearbhall O'Meadhra wrote:
Ron,

I think you may need to find "Browse" and use that file open dialog. It looks to me as if the File Open option favours the "Recent"file management function and this would not be able to access the address of your text file if the address of that file had not been used for a recent Excel workbook.

Could you try these steps:
1. Open an existing workbook
2. Open a blank worksheet for the new data
3. Press alt>f>o>o separately but in sequence, not together, to open the file open dialog in browse mode;

This dialog is pretty well the same as the old one.
Press enter when you have focussed on the text file that you want.

The dialog I have on my screen now is giving me the various options just the same as you describe and NVDA is speaking every field in it.

I think the problem lies in getting the right open dialog. I strongly recommend using alt>f>o>o to open it as, otherwise, you would have to arrow around the screen to get to the browse button at the bottom of the second screen.
I found that I needed to allow a mini-second between each of the keystrokes to allow the screen to update even though I am using a very fast computer.


Let us know if you find this works or not.

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@blbc.ie


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: Saturday, March 24, 2018 11:45 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Issue With Excel 2016

Hello:


I open the existing Excel Work Book.

I then use open file and type in the path and file name of the delimited text file.


This used to work. I used to get a wizard of sorts that could have a
back, next and finish and step by step, I would be asked which column I
should start the import at, what delimited I should use and other
parameters I should use.


Now I get this odd inaccessible dialogue.



On 3/24/2018 6:50 AM, Cearbhall O'Meadhra wrote:
Hi Ron,

I am using excel 2016 in Windows 10 and a choice of both NVDA and JAWS 17. All are up to the latest versions.

I am curious about your issue as I do a lot of work with excel myself.

I have just created a tab delimited text file and imported it successfully. I tried using the File>Open dialog and the "Get external data" option on the Data Menu. Although the resulting dialog is different in each case, I found every part of the dialog fully accessible with NVDA.

In older versions of Excel, I used to import text files using the File>Open dialog. I was surprised to find that I cannot do this in excel 2016.

You don't say what technique you are using, but if you explain exactly what you have been attempting I would be happy to explore it with you and see what might have changed.


All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@blbc.ie


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: Saturday, March 24, 2018 1:28 AM
To: nvda@nvda.groups.io
Subject: [nvda] Issue With Excel 2016

Hi Group,


For years, I have been using Microsoft Excel to make a simple spread sheet database for various of my music and movie files. I usually do this by creating a delimited text file using Notepad and then importing the file into Excel via the import data/text file item. For years this has worked. I would click the file and then I would get a Microsoft Security warning and then the file would open and a wizard of sorts would launch and ask me for the parameters: delimiters, beginning column, and so on.


However, now when I load an existing file into Excel, I get some sort of weird interface that doesn't seem to work with NVDA or JAWS and I am unable to complete the importation as I normally did.


I assume that either an update to Office 2016 or some other update to Windows 10 has changed some default setting in Excel that makes things operate differently. I have looked under options in the Excel program but I am unable to find what might be causing this difference. What setting could be changed to get things back to where they used to be for my Excel program?


Thanks for any help.


--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"







--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Re: Issue With Excel 2016

Ron Canazzi
 

Hi Rich,


I have been using semi colon [;] for the delimiters for years from Excel 2000 up until Excel2016 just a few weeks ago.  I never had this problem before.  I save the text file with the standard txt extension.  I use Notepad to create the files.  The common parameters--which used to appear in the wizard when trying to import the file first ask 'what line of the import file you wish to begin at (the default is line 1)  You click next and the second screen asks for the delimiter and I choose semi colon [;].  the next few screens have to do with formulas and other things that i just bypass and then click finish.  This wizard like interface no longer occurs when I try the import of the text file.  I get the Microsoft security warning which I dismiss and then this odd and new inaccessible interface.


Here are a few lines from the text file I have been trying to import.


Multimedia 363;1950 - The Littlest Angel - Lullaby of Christmas;01 - the littlest angel.mp3
Multimedia 363;1950 - The Littlest Angel - Lullaby of Christmas;02 - lullaby of christmas.mp3
Multimedia 363;baja marimba band - 2001 best of;01 along comes mary.mp3
Multimedia 363;baja marimba band - 2001 best of;02 juarez.mp3
Multimedia 363;baja marimba band - 2001 best of;03 comin' in the back door.mp3
Multimedia 363;baja marimba band - 2001 best of;04 georgy girl.mp3

On 3/24/2018 8:32 AM, Rick wrote:
Hello Ron:

What file extension are you using for the file you are attempting to import? Excel has a common format (.csv) which stands for Comma Separated Variables, where each field is separated using a comma in the file. Each field in the line of text is then placed in a separate cell in a row. Each new line will begin another row in the worksheet.

Also, can you give us a few sample lines from the file you are attempting to import and the rules you want to apply to the import process?

Thanks, Rick

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: Saturday, March 24, 2018 7:45 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Issue With Excel 2016

Hello:


I open the existing Excel Work Book.

I then use open file and type in the path and file name of the delimited text file.


This used to work. I used to get a wizard of sorts that could have a
back, next and finish and step by step, I would be asked which column I
should start the import at, what delimited I should use and other
parameters I should use.


Now I get this odd inaccessible dialogue.



On 3/24/2018 6:50 AM, Cearbhall O'Meadhra wrote:
Hi Ron,

I am using excel 2016 in Windows 10 and a choice of both NVDA and JAWS 17. All are up to the latest versions.

I am curious about your issue as I do a lot of work with excel myself.

I have just created a tab delimited text file and imported it successfully. I tried using the File>Open dialog and the "Get external data" option on the Data Menu. Although the resulting dialog is different in each case, I found every part of the dialog fully accessible with NVDA.

In older versions of Excel, I used to import text files using the File>Open dialog. I was surprised to find that I cannot do this in excel 2016.

You don't say what technique you are using, but if you explain exactly what you have been attempting I would be happy to explore it with you and see what might have changed.


All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@blbc.ie


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: Saturday, March 24, 2018 1:28 AM
To: nvda@nvda.groups.io
Subject: [nvda] Issue With Excel 2016

Hi Group,


For years, I have been using Microsoft Excel to make a simple spread sheet database for various of my music and movie files. I usually do this by creating a delimited text file using Notepad and then importing the file into Excel via the import data/text file item. For years this has worked. I would click the file and then I would get a Microsoft Security warning and then the file would open and a wizard of sorts would launch and ask me for the parameters: delimiters, beginning column, and so on.


However, now when I load an existing file into Excel, I get some sort of weird interface that doesn't seem to work with NVDA or JAWS and I am unable to complete the importation as I normally did.


I assume that either an update to Office 2016 or some other update to Windows 10 has changed some default setting in Excel that makes things operate differently. I have looked under options in the Excel program but I am unable to find what might be causing this difference. What setting could be changed to get things back to where they used to be for my Excel program?


Thanks for any help.


--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"







--
They Ask Me If I'm Happy; I say Yes.
They ask: "How Happy are You?"
I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"


Re: Firefox Quantum incompatible with NVDA forever?

 

I am doing fine with NVDA 2018.1. Have not tried waterfox yet because it is not in the portable apps directory and I am feeling lazy. 59 works fine with a few issues that I've seen already filed in mozillas bug tracker so I'm not worried about it at all. I submitted the context menu bug to them just now as well, where I tried to open the menu on a link to copy the link location and the context menu was the system menu. I didn't hear back though.


Re: Firefox Quantum incompatible with NVDA forever?

Chris
 

They probably just wanted to spend their millions on re-branding

 

Or maybe to differentiate between the old and the new i guess :D

 

From: Gene
Sent: 24 March 2018 20:16
To: nvda@nvda.groups.io
Subject: Re: [nvda] Firefox Quantum incompatible with NVDA forever?

 

I know how the word "quantum" is used in the field of quantum mechanics but I didn't know exactly how to define it.  Here are the two definitions Word Web provides.

1.A discrete amount of something that is analogous to the quantities in
quantum theory
2.(physics) the smallest discrete quantity of some physical property that a
system can possess (according to quantum theory)

 

I suspect a better dictionary would give more comprehensive definitions.  But the expression "quantum leap" means a large change.  It whould mean a small change but, in complete disregard for the meaning of "quantum," it means the opposite. 

 

Who knows why Mozilla decided to name the new series quantum.  In my opinion, one of the most ridiculous aspects of computer culture is the way things are named.  Maybe those who named it had in mind a quantum leap in quality.  Maybe they just liked the sound of the word.  Who knows?  Who's brilliant idea was it to name the bar in firefox that fills different functions depending on how you use it the "awesome bar."  That name tells nothing except that they decided to give it a name that is meaningless as a description of the bar.  It tells how they want you to feel about the bar.  They might just as well call it the awesome browser.  No one would take a car seriously that was named the awesome car.  I don't look for any logic or rationality in how anything is named in computer culture. 

 

Gene

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

Sent: Saturday, March 24, 2018 12:06 PM

Subject: Re: [nvda] Firefox Quantum incompatible with NVDA forever?

 

"Quantum" means the smallest possible amount of something.

Antony.

On Saturday 24 March 2018 at 18:00:41, zahra wrote:

> firefox versions are 64bit only for mac since version 53.
> but for windows, fortunately supports both 32 and 64bit windows.
> i think quantum means very fast.
> in firefox 56 and previous ones, the engine of firefox was gecko.
> but in firefox 57 and later, the engine is changed to photon.
> multiprocess is enabled and firefox recieved many changes to its codes
> and became twice faster.
>
> On 3/24/18, Antony Stone <antony.stone@...> wrote:
> > What!?
> >
> > https://www.mozilla.org/en-US/firefox/59.0.1/system-requirements/ says
> > that the
> > latest version, Firefox 59.0.1, runs on Windows 7, 8 and 10, all 32bit or
> > 64bit, plus MacOS 10.9 onwards, and various versions of Linux.
> >
> > Firefox is definitely not 64-bit only.
> >
> > Antony.
> >
> > On Saturday 24 March 2018 at 17:30:52, Roger Stewart wrote:
> >> For sure!  Several versions of Firefox back, they went to 64 bit only.
> >> Guess this is what they mean by quantum.
> >>
> >> Roger
> >>
> >> On 3/24/2018 6:21 AM, Walmir Schultz via Groups.Io wrote:
> >> > My system is Windows 7 SP1.
> >> >
> >> > I wonder if the problem is related to the fact that it is 32 bits.
> >> >
> >> > Em 23/03/2018 12:09, Ron Canazzi escreveu:
> >> >> Hi Walmir,
> >> >>
> >> >>
> >> >> Using Windows 10 and NVDA 2018.1, I have never had any such issues. I
> >> >> am on Firefox 59.01--the latest version and everything is great.  I
> >> >> am wondering if your Windows 7 is the basic 7 or service pack1.  If
> >> >> you have been following this list at all, you will see that NVDA
> >> >> 2018.1 will no longer support any system earlier than Windows 7
> >> >> Service Pack 1.
> >> >>
> >> >> On 3/23/2018 8:01 AM, Walmir Schultz via Groups.Io wrote:
> >> >>> Hi,
> >> >>>
> >> >>> Since Firefox Quantum (57, 58, 59, ,,,) NVDA is having
> >> >>> incompatibility problems.
> >> >>>
> >> >>> Is it time to forget about Quantum?
> >> >>>
> >> >>> The 59 version is unusable because NVDA simply don't recognize the
> >> >>> web page, it is "an unknown" objectt.
> >> >>>
> >> >>> I am using Windows 7, NVDA 2018.1 32 bits.
> >> >>>
> >> >>> I am still using Firefox 52 ESR, but almost changing to Chrome.
> >> >>>
> >> >>> Sadly, even Google recognized in its accessibility documentation
> >> >>> that Firefox was the best browser to be used with NVDA.Very sad.

--
If you were ploughing a field, which would you rather use - two strong oxen or
1024 chickens?

 - Seymour Cray, pioneer of supercomputing

                                                   Please reply to the list;
                                                         please *don't* CC me.