Date   

Re: Navigating Text since NVDA 2017.3

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

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@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Damien Sykes" <damien@dcpendleton.plus.com>
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 <bglists@...>
 

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

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

----- Original Message -----
From: "Don H" <lmddh50@adams.net>
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 <bglists@...>
 

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

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

----- Original Message -----
From: "Pranav Lal" <pranav.lal@gmail.com>
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 <bglists@...>
 

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

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email 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: 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 <bglists@...>
 

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@blueyonder.co.uk
Sent via blueyonder.
Please address personal email 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: 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 <bglists@...>
 

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@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Marco Oros" <marco.oros93@gmail.com>
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 <bglists@...>
 

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@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "George McCoy" <slr1bpz@charter.net>
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 <bglists@...>
 

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@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Lawrence Stoler" <lstoler99@optonline.net>
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 <bglists@...>
 

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@blueyonder.co.uk
Sent via blueyonder.
Please address personal email 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: 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


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

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

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@blueyonder.co.uk
Sent via blueyonder.
Please address personal email 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: 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: OT: selecting a new laptop is more difficult than before

Antony Stone
 

A "thumb drive" is *way* slower than a spinning hard disk.

An SSD is way faster.

Antony.

On Thursday 07 December 2017 at 00:23:30, Don H wrote:

Never understood that you can buy a 128 Gig thumb drive for less than 30
bucks yet a 128 Gig SSD cost several hundred bucks.
--
There's a good theatrical performance about puns on in the West End. It's a
play on words.

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


Re: Some misstakes in new rc NVDA version

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

What do you get if you load the speech player in espeak add on and use that instead? Do things go back as they used to mbe then?
You will need to select voice etc, but i'm not sure if this will fix anything but the UK English weirdnesses.
Brian

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

----- Original Message -----
From: "zahra" <nasrinkhaksar3@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 5:23 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


hi quentin,

may i request the problem hear?
iranian people reported problem with espeak ng new version.
they told that espeak voice became more robatic and unpleasant and
also many words which spoked previously correctly, now espeak ng says
them wrong!
we put punctuation level none and nvda speaks some of them!
even we cant select to use farsi with english US or english Uk!
hope that someone help the iranian users of new espeak ng too.
God bless you all!

On 12/6/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
Thanks I've sent off an email to see what occurs.
brain

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Hareth" <hareth4m@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, December 05, 2017 12:41 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Here you go to subscribe:
espeak-ng+subscribe@groups.io

On 12/5/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
What do I do to subscribe by sending an email, by the way?
I don't really want to mess around on the web for this.
brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Hareth" <hareth4m@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, December 05, 2017 7:19 AM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


The developer created a mailing list for that, here is the link:
https://groups.io/g/espeak-ng

On 12/5/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
It would also be good to see a very clear message somewhere permanent
about

somewhere we can interact with the current Espeak team and shall we
say,

not

be sort of ignored as noise.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Quentin Christensen" <quentin@nvaccess.org>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 9:33 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but
for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it.
So,
as Brian guessed, it's likely that the issues here are not specific
to
this
RC as such, but to the change in eSpeak version, since the RCs are a
bit
more widely distributed. It would be good to get confirmation from
Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via
Groups.Io

<
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent
snapshots
since the last two updates of espeak NG, none for the better
particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@nvda.open.source.it>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.

Is this problem something new in the latest RC version and did not
exist
in
earlier (RC or otherwise) versions, or does the same problem also
exist

in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!

At the first, where can I inform about this thing of NVDA
misstakes
of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly
pronounced
in
NVDA in that way, that syllable and some kind of number. Maybe,
this
is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar,
but

I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros
--
"If I've told you once, I've told you a million times - stop
exaggerating!"

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






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












--
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: OT: selecting a new laptop is more difficult than before

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

My ssd claims in hardware to be scssi or something siimilatr to that, but still looks like a normal drive.
Brian

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

----- Original Message -----
From: "Don H" <lmddh50@adams.net>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 06, 2017 11:23 PM
Subject: Re: [nvda] OT: selecting a new laptop is more difficult than before


Never understood that you can buy a 128 Gig thumb drive for less than 30 bucks yet a 128 Gig SSD cost several hundred bucks.



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

John Isige
 

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: Navigating Text since NVDA 2017.3

Lenron
 

wow so I have notice this, please how the hell can I fix it?

On 12/6/17, Quentin Christensen <quentin@nvaccess.org> wrote:
Well, to those who need the answer, that you got the information out there
is as important a part of the process as Tyler in tracking it down. A team
effort :)

On Thu, Dec 7, 2017 at 12:57 PM, Damien Sykes <damien@dcpendleton.plus.com>
wrote:

Hi,
Actually, Tyler did all the tracking down, I simply put it out here for
people to understand what was going on. I still don’t quite understand
the
magnitude of the issue myself. I noticed the issue, Tyler told me what it
was and how to change it, I changed it and verified that it worked, I
“published”, if you will, the results.
Cheers.
Damien.

*From:* Quentin Christensen <quentin@nvaccess.org>
*Sent:* Thursday, December 07, 2017 1:27 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Navigating Text since NVDA 2017.3

Damien,

Well tracked down :)

Quentin.

On Thu, Dec 7, 2017 at 11:30 AM, Damien Sykes
<damien@dcpendleton.plus.com
wrote:
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.



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



--
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
--
Lenron Brown
Cell: 985-271-2832
Skype: ron.brown762


Re: Navigating Text since NVDA 2017.3

 

hi.
can you please explane for me how should i change the behaviour to the
previous state?
God bless you all.

On 12/7/17, Quentin Christensen <quentin@nvaccess.org> wrote:
Well, to those who need the answer, that you got the information out there
is as important a part of the process as Tyler in tracking it down. A team
effort :)

On Thu, Dec 7, 2017 at 12:57 PM, Damien Sykes <damien@dcpendleton.plus.com>
wrote:

Hi,
Actually, Tyler did all the tracking down, I simply put it out here for
people to understand what was going on. I still don’t quite understand
the
magnitude of the issue myself. I noticed the issue, Tyler told me what it
was and how to change it, I changed it and verified that it worked, I
“published”, if you will, the results.
Cheers.
Damien.

*From:* Quentin Christensen <quentin@nvaccess.org>
*Sent:* Thursday, December 07, 2017 1:27 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Navigating Text since NVDA 2017.3

Damien,

Well tracked down :)

Quentin.

On Thu, Dec 7, 2017 at 11:30 AM, Damien Sykes
<damien@dcpendleton.plus.com
wrote:
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.



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



--
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
--
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: updating to the latest snap, but still waiting for the update to finish

Robert Mendoza
 

Hi, Michael

Normally, the version of snapshot often times to be tested for quality if you curious how it works, but again it's up to you to test. Some here were eager to be tester to themselves to help our developers to improves the function wise. Otherwise, go with stable rather. Again, it is advisable to use snapshot to testing machine or have it save to flash drive.

Robert Mendoza

On 12/7/2017 2:44 PM, Michael Capelle wrote:
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@gmail.com> 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: Windows 10 ADVISORY: you need to use NVDA 2017.4 if you want to install it on Windows 10 on ARM

 

Hi,
It'll depend on what apps you're using, if a restart fixed the problem and what not.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Marisane Moruthanyana
Sent: Wednesday, December 6, 2017 10:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 ADVISORY: you need to use NVDA 2017.4 if you want to install it on Windows 10 on ARM

Morning Joseph

This is Marisane from SA.

I posted a concern previously but without any assistance from colleagues.

I hear you that one must move to nvda 2017.4 for effectiveness and efficiency.

I use nvda 2017.3 and it gives me problems.

It freezes easily, goes unresponsive when I run multiple application and when am on internet.

What is the problem with that?

Out of curiosity, what is win10 fall creators?

Your assistance is appreciated in advance.

Kind regards
Marisane

On 12/7/17, tim <z2004a1@gmail.com> wrote:
They mostly use that chip in tablets and some low end laptops.
On Dec 6, 2017, at 2:55 PM, Gene New Zealand
<hurrikennyandopo@outlook.co.nz> wrote:

Hi Joseph



What are these ram thing you are talking about? Is it like the
processor that they used on the RT versions of windows but modified?



Are they the ones found on window phones etc?



Gene nz




On 12/7/2017 7:30 AM, Joseph Lee wrote:
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
--

Check out my website for NVDA tutorials and other blindness related
material at http://www.accessibilitycentral.net
<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
<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/
<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.