Date   

Re: Can NVDA 2017.4 run on Windows IOT?

Brian's Mail list account
 

Still think its a dead end myself, at least in third world countries. I hate to have to rely on other systems working for what I do locally.
Brian

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

----- Original Message -----
From: "Pranav Lal" <pranav.lal@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 3:24 AM
Subject: Re: [nvda] Can NVDA 2017.4 run on Windows IOT?


Hi Joseph,
I see what you are getting at. I was confused by the reference to arm processors in the release notes and the different versions of windows. I have read more and see that nvda is being future ready to handle newer devices like always connected pcs that will use arm processors.
Pranav

On 07-Dec-2017, at 6:28 AM, Joseph Lee <joseph.lee22590@...> wrote:

Hi,
Let's try this method: can a car run without an engine? I want folks to find
out the answer on their own this time please.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Pranav
Lal
Sent: Wednesday, December 6, 2017 4:11 PM
To: nvda@nvda.groups.io
Subject: [nvda] Can NVDA 2017.4 run on Windows IOT?

Hi all,

Given that NVDA now supports arm 64 windows, can it run on Windows IOT
running on a raspberry pi 3?

Pranav







Re: Versioned Voice Dictionaries

Brian's Mail list account
 

Yes and percent is said differently in the progress to what it is in a document as well.
Buttong always makes me giggle.
Brian

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

----- Original Message -----
From: "Shaun Everiss" <sm.everiss@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 1:18 AM
Subject: Re: [nvda] Versioned Voice Dictionaries


I know the word for for, is now fur and not 4.

I know the word forbid is not 4 bid but furbid once is unce.

button is now buttung.

I think we should use older but faithfull espeak which doesn't have this issue or simply make something that doesn't rely on it.

Whoever develops this is clearly no longer english and is probably using google translate for everything.




On 7/12/2017 12:06 p.m., Sharni-Lee Ward wrote:
Okay, opened my portable copy of 2017.3 and copied the replacements from
there. Things are mostly back on track, although the Japanese word the
ProTalker synth pronounces wrong in the hiragana couldn't be copy/pasted
into Jarte. It just came up as a line of question marks. But that's not
vitally important to me right now so I'll let that slide for the time being.


On a sort-of related note, though, Why was the pronunciation of the
phrase "for the" and the word "percent" changed in espeakNG? They sound
weird now...
On 7/12/2017 9:45 AM, Sharni-Lee Ward wrote:
So I just updated to the latest NVDA, and I now have some issues thanks
to the changes with the voice dictionaries. I understand why since
languages in espeak have changed names, but I lost several voice
specific entries and don't remember what I did for them. I tried to fix
one instance and although the pronunciation sounded right in the
dictionary file, it didn't when I read the name in question somewhere
else, although it was apparent some change had been made. This behaviour
has never happened before, and the pronunciation of the replacement has
been consistent in all places. I'm concerned that I might never get this
name pronounced the way I want it again, and I've only tested this with
one entry!





Re: Be careful to Mandarin Espeak

 

where we can download speech player for espeak?

On 12/7/17, Brian's Mail list account via Groups.Io
<bglists@...> wrote:
I think one of the problems is as I'm sure you are aware, the biggest user
base for NVDA is the Indian Sub continent. Thus espeak needs to be in there

cos it does support Hindi.


I do agree with you though. I think they have attempted to develop Espeak
when they are still trying to understand the previous developers code.

Have you tried the Speech Player in Espeak add on but set to the old
voices?
I think its the old Espeak so works well.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Shaun Everiss" <sm.everiss@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 1:02 AM
Subject: Re: [nvda] Be careful to Mandarin Espeak


Well espeak ng this version has a lot more issues with things even in
english.

I noticed people having issues with espeak on skype, tyler who is one of
the addon devs simply said to report it to espeakng, which is actually
just dumb since all espeak ng is is a github page, I don't think they have

email I havn't looked, point is do they care exactly.

Its nvaccess that uses espeak ng, and as I said, even though there were
good reasons to upgrade synths, unless it breaks we shouldn't fix it.

Espeak 2015 worked, and in some cases better than ng ever did.

Now ng is a lot better I guess once I got used to the word adjustments but

really not everyone is going to be a total git, not everyone is going to
be that much of a git to report that espeakng is a git and needs fixing.

I still think even if its not default, old espeak whatever version should

be included as an extra synth at least an addon or as part of nvda install

even if espeak is not developed anymore, even if it will remain as it is
for all time, for those that don't like the new datasets, it would fix a
lot of user bitchings.

Thing is, the espeak devs were on here.

I don't know if the ng ones are, but I suspect not since none of them have

posted here and said as much.




On 7/12/2017 10:07 a.m., Marco Oros wrote:
My worries were confirmed about NVDA's New Espeak NG things. Mandarin is

broken down in Espeak. I don't know, where to report It.

Thank You.

Marco Oros



.






--
we have not sent you but as a mercy to the entire creation.
holy quran, chapter 21, verse 107.
in the very authentic narration from prophet Mohammad is:
indeed, imam husayn is the beacon of guidance and the ark of salvation.
best website for studying islamic book in different languages
www.al-islam.org


Re: Be careful to Mandarin Espeak

Brian's Mail list account
 

No because many other languages on other synths are rubbish.
Brian

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

----- Original Message -----
From: "Shaun Everiss" <sm.everiss@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 1:14 AM
Subject: Re: [nvda] Be careful to Mandarin Espeak


Its unlikely espeak itself will actually die as a synth.

Its in android, and linux distros all over the technoverse, its unlikely that espeak itself will die.

However now we have said burger off to xp, and vista, we are also saying screw basically every single core system to.

And with this being done, I question the need for inbuilt synths.

After win7 finally dies, with the good voices out there I question the need especially with the stuff on win10 and faster system of us needing a good synth bar one that is a fallback if something internal fails.

Standard crappy espeak is fine for admin work, it may be crappy but its good if something totally falls over.

There are others, pico which is on android and linux, maybe that could be a default synth I don't know.

But you are right, nvaccess should actually work on its own synth, not based of espeak but its own synth for its own software.

Heck if they want to sell it for sapi at 20 or 30 bucks and maybe other oses I'll buy it but to be honest I do wander.

Espeak will! not! die though, not death as you know it but the devs are clearly not on here.




On 7/12/2017 10:48 a.m., Marco Oros wrote:
There were made some bad misstakes about Mandarin Espeak. I don't know, why, but I think, that some work of Espeak is at the begining.
It'll be maybe good to try create another speech synthesizer, because Espeak will soon be down. This is just my view on It.


.


Re: How does NVDA read text boxes?

Brian's Mail list account
 

Let me tell you a story. I got a diet sheet from Diabetes UK in Word format. Every single bit of text except their contact details and other sundry stuff was in a text box.
This in effect meant it was completely unreadable to me.
At least in the sense of being in the order the eye saw it.

I ended up sending it back to the Doctors practice who sent it and the poor lady had to remove all the boxes and reformat the file. OK you may say that the original creator should really have thought of this, but its my experience they seldom do. its the same people who produce untagged pdfs which do not tag reading order when columns are in use or tend to put the pages in the order that an a5 booklet printed on a4 paper folded in half would need.
I suppose we need more education, but it would be really nice if we had some way to try and get at least some sense out of such documents so we could make a decision what to actually do.
Brian

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

----- Original Message -----
From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 1:06 AM
Subject: Re: [nvda] How does NVDA read text boxes?


When you write text in Word, or add in a table or many other items, they
are placed "in line". That is you can follow the caret through the
document in a linear fashion from the first word through to the end.

Text boxes are placed (by default) outside this regular flow of the
document. The advantage of this (for sighted users) is that you can have a
chunk of text which sits separately from the rest of the page. Sometimes
in a magazine for instance, you might have two columns of text on one page,
but in between them (and taking up part of each) is a box with text in a
different font containing a key quote out of the article. If you were
reading it visually, your eye might jump to that quote before reading the
article and it might form part of your decision about whether to read the
main article. Or, you might read the quote in between paragraphs when you
are next to it in the article itself, or at the end. There is no right
time to read it. If you are reading that page with a screen reader, the
screen reader doesn't see it in the normal flow of text. Now, it's true we
could possibly do more to look for such text boxes, but we would still need
to make some arbitrary decision on when to either read or notify the user
about them.

Word's accessibility checker will notify a document creator about non
in-line text boxes. Currently we will find text boxes which have been set
in line and these are announced as "slash":
https://github.com/nvaccess/nvda/issues/6134

Overall, it's generally best to try to avoid using text boxes where
possible.

Regards

Quentin.

On Thu, Dec 7, 2017 at 3:44 AM, Brian's Mail list account via Groups.Io <
bglists@...> wrote:

I gave up and asked them to take them out, since nobody I knew no matter
what screenreader they used seemed to be able to solve the problem either.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Ann Byrne" <annakb@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 1:27 PM
Subject: [nvda] How does NVDA read text boxes?


I received a word document that appeared to be blank. Turns out it is a
series of 15 text boxes of information. How can I read stinkin' text boxes
with NVDA???

Thanks







--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess


Re: Versioned Voice Dictionaries

Sharni-Lee Ward
 

I know! Isn't it simply horrid?   


On 7/12/2017 9:17 PM, Brian's Mail list account via Groups.Io wrote:

Exactly and the word for can sound like fur sometimes as well. Grrr.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sharni-Lee Ward" <sharni-lee.ward@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 11:06 PM
Subject: Re: [nvda] Versioned Voice Dictionaries


Okay, opened my portable copy of 2017.3 and copied the replacements from
there. Things are mostly back on track, although the Japanese word the
ProTalker synth pronounces wrong in the hiragana couldn't be copy/pasted
into Jarte. It just came up as a line of question marks. But that's not
vitally important to me right now so I'll let that slide for the time being.


On a sort-of related note, though, Why was the pronunciation of the
phrase "for the" and the word "percent" changed in espeakNG? They sound
weird now...
On 7/12/2017 9:45 AM, Sharni-Lee Ward wrote:
So I just updated to the latest NVDA, and I now have some issues thanks
to the changes with the voice dictionaries. I understand why since
languages in espeak have changed names, but I lost several voice
specific entries and don't remember what I did for them. I tried to fix
one instance and although the pronunciation sounded right in the
dictionary file, it didn't when I read the name in question somewhere
else, although it was apparent some change had been made. This behaviour
has never happened before, and the pronunciation of the replacement has
been consistent in all places. I'm concerned that I might never get this
name pronounced the way I want it again, and I've only tested this with
one entry!















Re: NVDA 2017.4 and the version of espeak-ng packaged with it

Sharni-Lee Ward
 

I'm using English Great Britain, as it's called now.

On 7/12/2017 7:02 PM, John Isige wrote:
What variant are you using? I just switched to eSpeak NG from
Eloquence, I'm set to English America, at a rate of 80, and all of
that sounded perfectly fine to me.


On 12/6/2017 22:45, Sharni-Lee Ward wrote:
I updated NVDA this morning and have been periodically jarred out of my
reading by things being pronounced differently, and in my opinion,
unnecessarily so. For example, the phrases "for the" and "for a" are
pronounced with unnecessary emphasis on the first word in them, the "i"
in possible is annunciated more clearly than I feel it should be, the
word "fantasy" has more emphasis on the first syllable than it needs and
sounds slower as a result, words like "latest" sound like they end with
"ist" instead of "est" (I don't understand this one at all, as they were
pronounced just fine before), and words that end with n or an n sound
followed by a word beginning with a hard c or g sound as if they're
being smushed together ("in games" comes out sounding like "ing games").
Also, words like "they're" and "our" are more drawn out than they should
be. It's honestly distracting and I don't think I'll ever get used to
most of them to be perfectly frank.





Re: Be careful to Mandarin Espeak

Brian's Mail list account
 

I think one of the problems is as I'm sure you are aware, the biggest user base for NVDA is the Indian Sub continent. Thus espeak needs to be in there cos it does support Hindi.


I do agree with you though. I think they have attempted to develop Espeak when they are still trying to understand the previous developers code.

Have you tried the Speech Player in Espeak add on but set to the old voices?
I think its the old Espeak so works well.
Brian

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

----- Original Message -----
From: "Shaun Everiss" <sm.everiss@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 1:02 AM
Subject: Re: [nvda] Be careful to Mandarin Espeak


Well espeak ng this version has a lot more issues with things even in english.

I noticed people having issues with espeak on skype, tyler who is one of the addon devs simply said to report it to espeakng, which is actually just dumb since all espeak ng is is a github page, I don't think they have email I havn't looked, point is do they care exactly.

Its nvaccess that uses espeak ng, and as I said, even though there were good reasons to upgrade synths, unless it breaks we shouldn't fix it.

Espeak 2015 worked, and in some cases better than ng ever did.

Now ng is a lot better I guess once I got used to the word adjustments but really not everyone is going to be a total git, not everyone is going to be that much of a git to report that espeakng is a git and needs fixing.

I still think even if its not default, old espeak whatever version should be included as an extra synth at least an addon or as part of nvda install even if espeak is not developed anymore, even if it will remain as it is for all time, for those that don't like the new datasets, it would fix a lot of user bitchings.

Thing is, the espeak devs were on here.

I don't know if the ng ones are, but I suspect not since none of them have posted here and said as much.




On 7/12/2017 10:07 a.m., Marco Oros wrote:
My worries were confirmed about NVDA's New Espeak NG things. Mandarin is broken down in Espeak. I don't know, where to report It.

Thank You.

Marco Oros



.


Re: Can NVDA 2017.4 run on Windows IOT?

Brian's Mail list account
 

Yes but only downhill.
Brian :-)
Brian

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

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 12:58 AM
Subject: Re: [nvda] Can NVDA 2017.4 run on Windows IOT?


Hi,
Let's try this method: can a car run without an engine? I want folks to find
out the answer on their own this time please.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Pranav
Lal
Sent: Wednesday, December 6, 2017 4:11 PM
To: nvda@nvda.groups.io
Subject: [nvda] Can NVDA 2017.4 run on Windows IOT?

Hi all,

Given that NVDA now supports arm 64 windows, can it run on Windows IOT
running on a raspberry pi 3?

Pranav






Re: Navigating Text since NVDA 2017.3

Brian's Mail list account
 

I do agree about Github, though not for the reasons you state. I do feel its trying to be everything to everybody and is thus quite cluttered and opaque to a new user. Also when filling out new issues I'd far prefer separate fields for the questions than the in field suggestions on the current single field, as this is awkward to use for most people.
Brian

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

----- Original Message -----
From: "Damien Sykes" <damien@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 12:30 AM
Subject: [nvda] Navigating Text since NVDA 2017.3


Hi guys,
For anyone like me who has noticed the text lag and wonders why. The following came from Tyler Spivey, who helped me resolve this strange conundrum.
It actually appears that NVDA has always had some reason or other to have to wait a predetermined amount of time for the cursor to move in order to read whatever new information is under the cursor, or to inform of highlighted text, or if no change has occurred, to state the fact that we are at the beginning or end of the field. Until 2017.3, this was 30 milliseconds, a time so short that you would hardly notice it.

An entry in the change log for 2017.3 reads:
• In editable text, when moving the caret (e.g. with the cursor keys or backspace), NVDA's spoken feedback is now more accurate in many cases, particularly in Chrome and terminal applications.

In fact, one of the ways this seems to have been resolved was to increase the cursor wait time from 30 to 100 milliseconds, which may not seem much but is in fact a 230% increase. This means that people who are well tuned in to how NVDA read data previously, and perhaps more importantly rely on speed, will notice this change.
This is all apparently covered on GitHub, which, as far as I’m concerned isn’t really a user-friendly platform (that’s to say it’s meant for developers, and expert ones at that, which means you’re going to see a lot of technical jargon). Some may argue that this issue is a very fine line between a development technicality and usability, and since I seem to have been the only one who cared or even noticed this, I’m inclined to agree. But at least it’s out there now.
So, to summarise:
1. This is actually intended behaviour.
2. You can change it, but you have to know how and where it’s stored. It’s not in the configuration dialogs. Some may not even find it worth the effort – I only did because it ground straight through my sensitive teeth and pounded through my skull.
3. If you change it, be aware that you may not get the improved accuracy stated in the change log entry quoted above.
Cheers.
Damien.


Re: updating to the latest snap, but still waiting for the update to finish

Gene
 

At times, snapshots have features not yet in the release version.  Also, some people run them as a form of beta testing, which is an important reason they are made available.
 
There are snapshots in a different category that incorporate code that hasn't been tested to any extent at all yet and that's more like Alfa testing.
 
Gene

----- Original Message -----
Sent: Thursday, December 07, 2017 12:44 AM
Subject: Re: [nvda] updating to the latest snap, but still waiting for the update to finish

just curious, why would you want to run a snap shot?
i typically tell people to run the stable versions.

-----Original Message-----
From: Sarah k Alawami
Sent: Thursday, December 07, 2017 12:42 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] updating to the latest snap, but still waiting for the
update to finish

Ok, I retarted my computer using the command prompt and all worked. I have
no clue what happened, or why but I hoep what ever happened does not happen
again. Any clue as to what went on? The update worked this time.

Take care

> On Dec 6, 2017, at 9:55 PM, Sarah Alawami <marrie12@...> wrote:
>
> I think I have a very broken nvda update. I followed the directions. The
> update downloaded, however  I still hear the beeps saying it's updating
> etc et etc. I tried to close out but no joy. Narrator is not telling me
> much either. Running nvda latest snap on windows 10 pro..
>
> Take care all.


 




Re: links on single line

Brian's Mail list account
 

Use screen layout. Is this not what you turn off?
Brian

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

----- Original Message -----
From: "Don H" <lmddh50@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 12:25 AM
Subject: [nvda] links on single line


I am running NVDA 2017-4 on a Win 10 64 bit machine. I have a web site where there are multiple links on a single line thus NVDA reads them together. If my memory is right there is a way to get NVDA to read this multi link lines as if each link was separate. Looked everywhere but can't find it.
Thanks a



Re: Can NVDA 2017.4 run on Windows IOT?

Brian's Mail list account
 

Since I've no idea what it is, perhaps you could tell us?
Brian

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

----- Original Message -----
From: "Pranav Lal" <pranav.lal@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, December 07, 2017 12:11 AM
Subject: [nvda] Can NVDA 2017.4 run on Windows IOT?


Hi all,

Given that NVDA now supports arm 64 windows, can it run on Windows IOT
running on a raspberry pi 3?

Pranav



Re: Versioned Voice Dictionaries

Brian's Mail list account
 

Exactly and the word for can sound like fur sometimes as well. Grrr.
Brian

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

----- Original Message -----
From: "Sharni-Lee Ward" <sharni-lee.ward@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 11:06 PM
Subject: Re: [nvda] Versioned Voice Dictionaries


Okay, opened my portable copy of 2017.3 and copied the replacements from
there. Things are mostly back on track, although the Japanese word the
ProTalker synth pronounces wrong in the hiragana couldn't be copy/pasted
into Jarte. It just came up as a line of question marks. But that's not
vitally important to me right now so I'll let that slide for the time being.


On a sort-of related note, though, Why was the pronunciation of the
phrase "for the" and the word "percent" changed in espeakNG? They sound
weird now...
On 7/12/2017 9:45 AM, Sharni-Lee Ward wrote:
So I just updated to the latest NVDA, and I now have some issues thanks
to the changes with the voice dictionaries. I understand why since
languages in espeak have changed names, but I lost several voice
specific entries and don't remember what I did for them. I tried to fix
one instance and although the pronunciation sounded right in the
dictionary file, it didn't when I read the name in question somewhere
else, although it was apparent some change had been made. This behaviour
has never happened before, and the pronunciation of the replacement has
been consistent in all places. I'm concerned that I might never get this
name pronounced the way I want it again, and I've only tested this with
one entry!






Re: Versioned Voice Dictionaries

Brian's Mail list account
 

Have a look in the folder where the dictionaries were you should find your old version in a sub directory. simply rename it to the new name and then copy it over the one you just created and restart nvda.
I think to be certain you need to do this manually in the user folder version then copy to log on afterwards to bring it back into the program folder.
However this really depends on whether you wish to still use Espeak and not the speech player in Espeak add on version of Espeak.
Brian

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

----- Original Message -----
From: "Sharni-Lee Ward" <sharni-lee.ward@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 10:45 PM
Subject: [nvda] Versioned Voice Dictionaries


So I just updated to the latest NVDA, and I now have some issues thanks
to the changes with the voice dictionaries. I understand why since
languages in espeak have changed names, but I lost several voice
specific entries and don't remember what I did for them. I tried to fix
one instance and although the pronunciation sounded right in the
dictionary file, it didn't when I read the name in question somewhere
else, although it was apparent some change had been made. This behaviour
has never happened before, and the pronunciation of the replacement has
been consistent in all places. I'm concerned that I might never get this
name pronounced the way I want it again, and I've only tested this with
one entry!




Re: IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

Gene
 

You are assuming that people are allowing automatic updates. 
 
Gene 

----- Original Message -----
Sent: Thursday, December 07, 2017 3:58 AM
Subject: Re: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7 SP1 or later is absolutely required

Could I ask how people could end up without sp1, as I seem to recall from
friends that this update some years back now was pushed automatically to
existing systems and its not just nvda which relies on it either.

 Also now, how would a user get it and install it, is it relatively simple
on the Microsoft site or would you suggest going the whole way and going to
10 before 31st Dec while a free update is there. I'm assuming that the old
version of 7 will still allow the update.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 6:18 PM
Subject: [nvda] IMPORTANT COMMUNITY DIRECTIVE: to use NVDA 2017.4, Windows 7
SP1 or later is absolutely required


> Dear NVDA community,
>
>
>
> It was brought to developers' attention that some people were having
> issues
> upgrading to NVDA 2017.4, and turns out some were using Windows 7 RTM
> build.
> Thus the following community directive:
>
>
>
> In order to use NVDA 2017.4 or later, Windows 7 Service Pack 1 or later is
> ABSOLUTELY required.
>
>
>
> To find out which Windows release you've got:
>
>
>
> 1. Press Windows key to open Start menu.
> 2. Type "winver" without quotes and press Enter.
> 3. Check the build shown on About Windows dialog.
>
>
>
> If the build number is 7601 or higher, you're all set. If it is lower than
> that:
>
>
>
> * If using Windows 7 RTM (build number is 7600), please use NVDA
> 2017.3, upgrade to Windows 7 SP1 first, then update to NVDA 2017.4.
> * If using versions other than 7 (build number is less than 7600),
> then NVDA 2017.3 is the last supported version for you.
>
>
>
> In the next few weeks, some add-on authors will announce minimum supported
> versions of NVDA and Windows. For example, if you are using
> StationPlaylist
> Studio add-on, starting from version 17.12 stable, Windows 7 SP1 or higher
> is absolutely required.
>
>
>
> Thank you.
>
> Cheers,
>
> Joseph
>
>




Re: Be careful to Mandarin Espeak

Brian's Mail list account
 

Go back to the one that worked. With any project taken over by a new team getting your head around the way its codes is always going to be an issue. This is why I have always been against using it for a while now. its no slight on those making it, its just that its still pretty early days to expect it to be fixed.
Brian

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

----- Original Message -----
From: "Marco Oros" <marco.oros93@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 9:48 PM
Subject: Re: [nvda] Be careful to Mandarin Espeak


There were made some bad misstakes about Mandarin Espeak. I don't know, why, but I think, that some work of Espeak is at the begining.
It'll be maybe good to try create another speech synthesizer, because Espeak will soon be down. This is just my view on It.


Re: NVDA not starting after login under windows 10

Brian's Mail list account
 

Don't you have to enable this somehow? I imagine a none admin user cannot affect changes on the log on screen before one has logged on or it would not be very secure, would it?
Brian

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

----- Original Message -----
From: "George McCoy" <slr1bpz@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 9:41 PM
Subject: [nvda] NVDA not starting after login under windows 10


I'm running windows 10 professional version 1709. I have two local accounts set up; one as administrator and one as standard user.

NVDA works fine on the logon screen and starts when I log into the admin account. When I log into the standard user account, however, NvDA does not start automatically. automatically start NVDA after I log onto windows is checked.

Has anyone else encountered this? Is there a solution?

Thanks very much,
George


Re: A Question about Obtaining NVDA:

Brian's Mail list account
 

Well, I'd first find out if the computer has sound. Most do but it could be muted or disabled so you would need to make sure the sighties around allow this either by simply making it work or letting you work on headphones. Its not rocket science. I'd be more wary of the system admin rights you will have and whether they are prepared to install it on the computer if its part of a network. That really does need to happen as portable copies, particularly on Windows 10, are nowhere near as versatile as an installed copy. Also if you are going online, in my view make sure that if they are using Firefox, that its not a version later than 56. Brian

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

----- Original Message -----
From: "Lawrence Stoler" <lstoler99@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 7:35 PM
Subject: [nvda] A Question about Obtaining NVDA:


Dear NVDA Users Group,


I am one of the many blind people who are unemployed.


There is a place I might be working for on a temporary basis as the
agency here in Connecticut wants to do a work assessment on me since I
have been out of work for a long time.


I have been an Internet user for over 14 years. I have used and enjoyed
NVDA since 2014 when I first became aware of it.


In addition to being able to download the latest version of NVDA, do I
need a sound card as it will be on a computer that has never been used
by a blind person or can I just download it from the website and go from
there?


Lawrence Stoler

?


Re: Windows 10 ADVISORY: you need to use NVDA 2017.4 if you want to install it on Windows 10 on ARM

Brian's Mail list account
 

I have to say, I think always connected on the cloud systems are a bit of a dead end street, seeing as the connection is not guaranteed anywhere and people will not want to lose productivity if they have a laptop and can use it through power outages.
Brian

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

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 6:30 PM
Subject: [nvda] Windows 10 ADVISORY: you need to use NVDA 2017.4 if you want to install it on Windows 10 on ARM


Hi all,



Another advisory/directive, this time a notice concerning a new technology
in Windows 10:



If you come across Windows 10 on ARM (always connected PC's) and wish to use
NVDA on it, you need to install 2017.4 or later. NVDA 2017.4 will recognize
these PC's as running Windows 10 64-bit, though performance won't be as
smooth as Windows 10 on x64 processors for now.



Cheers,

Joseph

69961 - 69980 of 101224