Date   

Windows10 Mail and NVDA: several bugs reported

Iván Novegil
 

Hello all.


A Spanish user asked us about the following two bugs he has with Windows10's mail app.

-When opening a mail to read it, NVDA reports "page 1".

-When writing a message with word echo enabled and pressing space after typing a word with accented letters or "ñ" on it NVDA doesn't report it.


Can someone try to reproduce these bugs to open an issue if needed? The two ones happened after updating to 2018.1 and using either Eloquence or eSpeakNG and with WinTenApps and without it.


Thanks in advance.

Regards.

--

Iván Novegil Cancelas
Editor
ivan.novegil@...


Comunidad hispanohablante de NVDA | Proyecto NVDA.es
- www.NVDA.es
- @nvda_es

Usuario do NVDA en galego

***Note que a anterior mensaxe e/ou os seus adxuntos pode conter información privada ou confidencial. O emprego da información desta mensaxe e/ou dos seus adxuntos está reservado ao ámbito privado do destinatario agás autorización do remitente. Se recibiu esta mensaxe por erro comuníqueo por esta mesma vía e destrúa a mensaxe.***


Espeak email list

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

Now I had hope there was a subscribe entry in the header, but noo, but its not hard to figure it out I suspect!

List-Unsubscribe: <https://groups.io/g/espeak-ng/unsub>
Sender: espeak-ng@groups.io
List-Id: <espeak-ng.groups.io>
Mailing-List: list espeak-ng@groups.io; contact espeak-ng+owner@groups.io
Delivered-To: mailing list espeak-ng@groups.io
Reply-To: espeak-ng@groups.io


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


Re: Error while updating to NVDA 2018.1 via the NVDA update utility.

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

Bah humbug, as somebody once said.

The new windows every few months irks me.
I'll stick to 7 till this nonsense is done away with.
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 New Zealand" <hurrikennyandopo@outlook.co.nz>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 5:19 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


Hi


Do the following


Press the windows key and in the search box type uac it should come with a result like change user account

settings.

Press the enter key on that result.


Tab down until you get to the slider and then use the down arrow key to make it go to nought


Then either tab down to if i remember either apply if it is there if so apply it then tab to ok then press the enter key on it.


After you press the enter key the UAC screen will come up just tab to yes then press the enter key on it and it should be done.


Hopefully after that it will not come up again until the next big windows update.


Gene nz



On 3/12/2018 5:56 PM, richard kurlander wrote:
how do you turn off user account control?At 11:52 PM 3/11/2018, you wrote:
this is why I turn off user account control.
----- Original Message ----- From: "Joseph Lee" <joseph.lee22590@gmail.com><mailto:joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io><mailto:nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 9:45 PM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


Hi,
Yes, but this time, say "yes" when UAC (User Account Control) screen appears.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io><mailto:nvda@nvda.groups.io> On Behalf Of Arianna Sepulveda
Sent: Sunday, March 11, 2018 6:44 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

Hello, All,


I just tried installing the NVDA 2018.1 update via the NVDA update utility, and got the following error. I'm not sure what is relevant, so I just coppied the entire output of the log viewer.

INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation INFO - core.main (18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.

Should I try updating again?


Thanks,
Ari













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


Re: Error while updating to NVDA 2018.1 via the NVDA update utility.

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

Yes because for some reason only known to Microsoft this screen does not have any text that can be spoken by a screenreader. It would be nice if it made a sound so you knew it was there. If you are the only user, then having uac on seems completely pointless.
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: "Dennis L" <dennisl1982@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 3:52 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


this is why I turn off user account control.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 9:45 PM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


Hi,
Yes, but this time, say "yes" when UAC (User Account Control) screen appears.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Arianna Sepulveda
Sent: Sunday, March 11, 2018 6:44 PM
To: nvda@nvda.groups.io
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

Hello, All,


I just tried installing the NVDA 2018.1 update via the NVDA update utility, and got the following error. I'm not sure what is relevant, so I just coppied the entire output of the log viewer.

INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation INFO - core.main (18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.

Should I try updating again?


Thanks,
Ari








Re: Error while updating to NVDA 2018.1 via the NVDA update utility.

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

It says it was cancelled by the user. I have not seen this before unless I cancelled it from the keyboard while it was loading in.
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: "Arianna Sepulveda" <englishrider91@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 1:43 AM
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


Hello, All,


I just tried installing the NVDA 2018.1 update via the NVDA update
utility, and got the following error. I'm not sure what is relevant,
so I just coppied the entire output of the log viewer.

INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation
INFO - core.main (18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.

Should I try updating again?


Thanks,
Ari


Re: Question about transferring espeak data between NVDA & Braillenote touch version

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

Is this a sapi 5 version? I'd have thought the settings could be moved between them if you could figure out the storage places for both versions parameters.
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: "Jessica D" <jldail13@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 12:52 AM
Subject: [nvda] Question about transferring espeak data between NVDA & Braillenote touch version


Hi,
Yesterday, I bought eSpeak for my Braillenote touch.
I’m really enjoying it, and its totally boosted my productivity.
I’m now using eSpeak with NVDA, and was wondering if it was possible to transfer my settings and other data between the 2 versions?

Thanks,
Jessica


Sent from Mail for Windows 10


Re: Typing Echo Change with 2018.1

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

No me neither, but as Joseph said, the other setting allows one to use one and does cause a lag.

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: "Rosemarie Chavarria" <knitqueen2007@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 12:42 AM
Subject: Re: [nvda] Typing Echo Change with 2018.1


I don't have a braille display. Can't afford one.



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's Mail list account via Groups.Io
Sent: Sunday, March 11, 2018 1:31 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

Do all of you have Braille displays?
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Gary" <ironmangary@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 6:08 AM
Subject: Re: [nvda] Typing Echo Change with 2018.1


Ok, that's really odd. All of them were slow on the typing echo, including
2017.4, which is what I was running previously without issue. I'm confused
to how that could be possible. :/


Re: espeak and pronunciation of some words

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

Those using 7 cannot do this.
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: "Rosemarie Chavarria" <knitqueen2007@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 12:28 AM
Subject: Re: [nvda] espeak and pronunciation of some words


I've used the one-core voices and they're really great.



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Devin Prater
Sent: Sunday, March 11, 2018 5:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

I agree, eSpeak needs lots of work, still. But the worst part of Open Source is that we all talk about it, but nothing gets done, we all wish, but never act, and there is only one person working on eSpeak. I know, we can't all program. But, with Windows 10, there are the OneCore voices, created by Microsoft which we can use, so we are no longer limited to eSpeak.

On 3/11/18, 7:05 PM, "nvda@nvda.groups.io on behalf of Rosemarie Chavarria" <nvda@nvda.groups.io on behalf of knitqueen2007@gmail.com> wrote:

I've noticed that about e-speak too. The word "for" when with other words soundlike "fer".



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Dejan Ristic
Sent: Sunday, March 11, 2018 12:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07:54, Governor staten wrote:
> I'll try to describe this as best I can. Take the word "content". The
> stress in this word is wrong, or, very much off. This is the case with
> other words too. Nazarene should sound like Nazareen. I'm sure there
> are other words like this I, and others, could think of.
>
>
> Any word with the letter "o" is likely to have the stress wrong.
> Monster is another example. This could just be me. Does anyone else
> hear what I'm hearing?
>
>
>
>
> .
>


Re: espeak and pronunciation of some words

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

Not sure about that, I'm on their email list and there are several people on there doing pull requests and updates.

I think at the moment they are trying to tidy up the code so all of the changes can be seen easeir and possible make it easier to tweak later on.
its not bad, but I think wheras previously uk english was the main language, now people are attempting to make the us English work and some of the changes sound odd in uk english. The slurring that is normal for us is not pleasent in the uk

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: "Devin Prater" <r.d.t.prater@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 12:13 AM
Subject: Re: [nvda] espeak and pronunciation of some words


I agree, eSpeak needs lots of work, still. But the worst part of Open Source is that we all talk about it, but nothing gets done, we all wish, but never act, and there is only one person working on eSpeak. I know, we can't all program. But, with Windows 10, there are the OneCore voices, created by Microsoft which we can use, so we are no longer limited to eSpeak.

On 3/11/18, 7:05 PM, "nvda@nvda.groups.io on behalf of Rosemarie Chavarria" <nvda@nvda.groups.io on behalf of knitqueen2007@gmail.com> wrote:

I've noticed that about e-speak too. The word "for" when with other words soundlike "fer".



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Dejan Ristic
Sent: Sunday, March 11, 2018 12:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07:54, Governor staten wrote:
> I'll try to describe this as best I can. Take the word "content". The
> stress in this word is wrong, or, very much off. This is the case
with
> other words too. Nazarene should sound like Nazareen. I'm sure there
> are other words like this I, and others, could think of.
>
>
> Any word with the letter "o" is likely to have the stress wrong.
> Monster is another example. This could just be me. Does anyone else
> hear what I'm hearing?
>
>
>
>
> .
>













Re: espeak and pronunciation of some words

Ian Blackburn
 

Certainly has deteriorated in its pronunciation

On 12 Mar 2018, at 5:22 pm, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:

Actually the original Espeak did a fine job. Too much tweaking recently has broken things that were good compromises before.
I certainly cannot stand Eloquence, I'd rather listen to a voice based on George W Bush than that!
However, as I say synths are intensely personal things.
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: "Adriani Botez" <adriani.botez@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 7:15 PM
Subject: Re: [nvda] espeak and pronunciation of some words


Dear all,


I think eSpeak has to be adjusted from scratch. It is very hard to get to a point where every word is being pronounced correctly. This is a matter of accent and phonemes which are very limited in eSpeak development.

If we begin to assess every word in eSpeak, we will find thousants and thousants of words which are mispronounced. Don't forget eSpeak supports more than 50 languages. So, developing this synthesizer word by word is not a long term solution.

So, in my view, if another speech synthesizer becomes free (i.e. eloquence or vocalizer), every user will change to it unless eSpeak is being vastly improved from scratch.


Best
Adriani


-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Dejan
Ristic
Gesendet: Sonntag, 11. März 2018 20:01
An: nvda@nvda.groups.io
Betreff: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems
to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07:54, Governor staten wrote:
I'll try to describe this as best I can. Take the word "content". The
stress in this word is wrong, or, very much off. This is the case with
other words too. Nazarene should sound like Nazareen. I'm sure there
are other words like this I, and others, could think of.


Any word with the letter "o" is likely to have the stress wrong.
Monster is another example. This could just be me. Does anyone else
hear what I'm hearing?




.



Re: espeak and pronunciation of some words

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

Actually the original Espeak did a fine job. Too much tweaking recently has broken things that were good compromises before.
I certainly cannot stand Eloquence, I'd rather listen to a voice based on George W Bush than that!
However, as I say synths are intensely personal things.
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: "Adriani Botez" <adriani.botez@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 7:15 PM
Subject: Re: [nvda] espeak and pronunciation of some words


Dear all,


I think eSpeak has to be adjusted from scratch. It is very hard to get to a point where every word is being pronounced correctly. This is a matter of accent and phonemes which are very limited in eSpeak development.

If we begin to assess every word in eSpeak, we will find thousants and thousants of words which are mispronounced. Don't forget eSpeak supports more than 50 languages. So, developing this synthesizer word by word is not a long term solution.

So, in my view, if another speech synthesizer becomes free (i.e. eloquence or vocalizer), every user will change to it unless eSpeak is being vastly improved from scratch.


Best
Adriani


-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Dejan
Ristic
Gesendet: Sonntag, 11. März 2018 20:01
An: nvda@nvda.groups.io
Betreff: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems
to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07:54, Governor staten wrote:
I'll try to describe this as best I can. Take the word "content". The
stress in this word is wrong, or, very much off. This is the case with
other words too. Nazarene should sound like Nazareen. I'm sure there
are other words like this I, and others, could think of.


Any word with the letter "o" is likely to have the stress wrong.
Monster is another example. This could just be me. Does anyone else
hear what I'm hearing?




.



Re: espeak and pronunciation of some words

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

Yes I really think for the record often should have an audible T as well as for still being 'FOR'

Brian!
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: "Dejan Ristic" <r.dejan83@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 7:01 PM
Subject: Re: [nvda] espeak and pronunciation of some words


Let me remind you of the word for, which, if followed by another word, seems to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07:54, Governor staten wrote:
I'll try to describe this as best I can. Take the word "content". The stress in this word is wrong, or, very much off. This is the case with other words too. Nazarene should sound like Nazareen. I'm sure there are other words like this I, and others, could think of.


Any word with the letter "o" is likely to have the stress wrong. Monster is another example. This could just be me. Does anyone else hear what I'm hearing?



.



Re: Typing Echo Change with 2018.1

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

This sounds like its not reading the checked stat for everyone unless its changed and changed back then. That is very odd as its, as far as I can tell the same code which is running now as it always was at start up.
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: "Lino Morales" <linomorales001@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 5:46 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


I just unchecked min and oh yeah buddy there is a lag. When I checked again. No more lag.

Lino Morales

From: Chris via Groups.Io<mailto:chrismedley=btinternet.com@groups.io>
Sent: Sunday, March 11, 2018 1:45 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Mines checked, unchecked it lags


From: Lino Morales<mailto:linomorales001@gmail.com>
Sent: 11 March 2018 17:41
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Gary was it on or off. Also for the rest of the list is it on by default? I think mine is on currently.

Lino Morales

From: Gary<mailto:ironmangary@gmail.com>
Sent: Sunday, March 11, 2018 11:20 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

The typing interrupt toggle under keyboard settings fixed it!?

I have never touched that setting...ever. Is there a chance 2018.1 changed this setting somehow? Sorry for the trouble.


Re: Typing Echo Change with 2018.1

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

Its always on as fare as I can see from the old xp machines. If something has turned it off that is a little odd.
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: "Lino Morales" <linomorales001@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 5:40 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


Gary was it on or off. Also for the rest of the list is it on by default? I think mine is on currently.

Lino Morales

From: Gary<mailto:ironmangary@gmail.com>
Sent: Sunday, March 11, 2018 11:20 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

The typing interrupt toggle under keyboard settings fixed it!?

I have never touched that setting...ever. Is there a chance 2018.1 changed this setting somehow? Sorry for the trouble.


Re: Typing Echo Change with 2018.1

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

Hmm, I still don't like the new Firefox.
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: "Lino Morales" <linomorales001@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 5:37 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


Hi Brian. I’m using Firefox 58.2, but I have been using 59 betas for the past month. FF 59.0 is coming soon.

Lino Morales

From: Brian Moore<mailto:bmoore@screenreview.org>
Sent: Sunday, March 11, 2018 9:41 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1


What browser are people using who have this problem. Just tried with 2018.1 and both ff 58 and chrome and can't reproduce it. this is on windows 10 1709

I could try with ie although I never use it. Just trying to pin it down.



Contact me on skype: brian.moore

follow me on twitter:

http://www.twitter.com/bmoore123
On 2018-03-11 12:28 AM, Joseph Lee wrote:
Hi,
I see. Can you try the following for me:
1. Download several beta builds (listed below).
2. Run each one as an installer (do not install them, just run them) with NVDA set to speak typed characters.
3. Tell me which beta build seems slower when announcing typed characters.

Beta build candidates to try:
1. NVDA 2017.4.
2. Build 14729 (December 14, 2017): https://ci.appveyor.com/api/buildjobs/ui46m9d93xvsn7rw/artifacts/output/nvda_snapshot_master-14729,3152eacc.exe
3. Build 14767 (January 3, 2018): https://ci.appveyor.com/api/buildjobs/w1e53fm8wj1vwqvv/artifacts/output/nvda_snapshot_master-14767,f7853f34.exe
4. Build 14825 (February 1, 2018): https://ci.appveyor.com/api/buildjobs/54881ddsb9906a9l/artifacts/output/nvda_snapshot_master-14825,2017d1f5.exe
5. Build 14868 (February 19, 2018): https://ci.appveyor.com/api/buildjobs/tmfpypkc4fwuoqlw/artifacts/output/nvda_snapshot_master-14868,48743675.exe
6. NVDA 2018.1.

Thanks.
Cheers,
Joseph

From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io><mailto:nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 9:17 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

I had tried restarting the PC earlier. I just now tried two different syntehsizers, but no difference.


Re: Typing Echo Change with 2018.1

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

Its set as it always is, on here.
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: "Hareth" <hareth4m@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 4:40 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


Hi Joseph.
Confirmed,
Just disabled "Speech interrupt for typed characters"
The typing lag is noticeable with all tts engines I have.
After re enabling "Speech interrupt for typed characters", the lag is gone.
Good catch.



On 3/11/18, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,

Huh? That’s new for me. So you’re saying turning this off fixed this for
you? Can others test this theory?

Cheers,

Joseph



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Sunday, March 11, 2018 8:21 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1



The typing interrupt toggle under keyboard settings fixed it!?

I have never touched that setting...ever. Is there a chance 2018.1 changed
this setting somehow? Sorry for the trouble.




Re: Typing Echo Change with 2018.1

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

For the alexa app its windows 7 pro, and firefox 52esr.
its not the screenreader as other enttry fields do not show the issue.
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: "Brian Moore" <bmoore@screenreview.org>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 1:41 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


What browser are people using who have this problem. Just tried with
2018.1 and both ff 58 and chrome and can't reproduce it. this is on
windows 10 1709

I could try with ie although I never use it. Just trying to pin it down.


Contact me on skype: brian.moore
follow me on twitter:
http://www.twitter.com/bmoore123

On 2018-03-11 12:28 AM, Joseph Lee wrote:

Hi,

I see. Can you try the following for me:

1. Download several beta builds (listed below).
2. Run each one as an installer (do not install them, just run them)
with NVDA set to speak typed characters.
3. Tell me which beta build seems slower when announcing typed
characters.

Beta build candidates to try:

1. NVDA 2017.4.
2. Build 14729 (December 14, 2017):
https://ci.appveyor.com/api/buildjobs/ui46m9d93xvsn7rw/artifacts/output/nvda_snapshot_master-14729,3152eacc.exe
3. Build 14767 (January 3, 2018):
https://ci.appveyor.com/api/buildjobs/w1e53fm8wj1vwqvv/artifacts/output/nvda_snapshot_master-14767,f7853f34.exe
4. Build 14825 (February 1, 2018):
https://ci.appveyor.com/api/buildjobs/54881ddsb9906a9l/artifacts/output/nvda_snapshot_master-14825,2017d1f5.exe
5. Build 14868 (February 19, 2018):
https://ci.appveyor.com/api/buildjobs/tmfpypkc4fwuoqlw/artifacts/output/nvda_snapshot_master-14868,48743675.exe
6. NVDA 2018.1.

Thanks.

Cheers,

Joseph

*From:* nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Gary
*Sent:* Saturday, March 10, 2018 9:17 PM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] Typing Echo Change with 2018.1

I had tried restarting the PC earlier. I just now tried two different
syntehsizers, but no difference.


Re: NVDA randumly crashing?

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

Its very hard without a log set to debug of the crashing session. IE when it reboots grab the old log not the current one, but before any crashes set logging level to debug as that shows most detail.
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: "Matt Turner" <meturner2214@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 12:33 PM
Subject: Re: [nvda] NVDA randumly crashing?


Hi.

I mostly use e-speak.

As for the crashing, sometimes nvda will restart on its own, and other times I have to manually restart it.


On 3/11/2018 5:25 AM, Brian's Mail list account via Groups.Io wrote:
I do not see this in Windows 7, but the other person has windows 8.1.
I'd expect all sorts of issues with 10, due to its numerous builds over its lifetime thus far.
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: "Don H" <lmddh50@adams.net>
To: <nvda@nvda.groups.io>
Sent: Saturday, March 10, 2018 11:23 PM
Subject: Re: [nvda] NVDA randumly crashing?


I am running NVDA on a Win 10 64 bit laptop and with the last two or three versions of NVDA including 2018-1 I get NVDA crashing randomly when I hit the windows key to open the start menu. I simply restart NVDA and everything seems fine again until the next random crash.






Re: Typing Echo Change with 2018.1

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

That is probably because to stop delays in one core voices it has to be altered in windows, not nvda.
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: "Lino Morales" <linomorales001@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 12:27 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


Well I used ESpeak with FB cause I commented on some posts. This problem doesn’t happen with ESpeak only One Core voices. I use MSS David with NVDA.

Lino Morales

From: Gene<mailto:gsasner@ripco.com>
Sent: Sunday, March 11, 2018 8:22 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

It can be tried and it's unlikely CCleaner would cause problems. But I am very skeptical that it will accomplish anything. If the problem started with a new version of NVDA, why would the registry suddenly and coincidentally become corrupted at that time? And one or two other people have said they have the same problem when the new version is used. It's strains credulity that coincidentally, two or three people had the same problem when trying a new version and that the problem is caused by the registry suddenly becoming corrupted on three computers in exactly the same way when a new version is being tried.

If someone wants to try registry cleaning with CCleaner, it is unlikely to cause problems and they may want to. But I'm very skeptical.

Gene
----- Original Message -----
From: Adriani Botez<mailto:adriani.botez@gmail.com>
Sent: Sunday, March 11, 2018 7:15 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

I had the problem with a portable version of NVDA, where the speech did not follow the cursor movement in an application. Registry clean solved this problem. So why not trying it? I don’t see any big issues in cleaning registry with CCleaner. I didn’t hear of any issue raising after cleaning registry with that program.


Best
Adriani


Von: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io> Im Auftrag von Gene
Gesendet: Sonntag, 11. März 2018 13:13
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Typing Echo Change with 2018.1

I see no reason to do anything with the registry. Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory. The problem started with a new release of NVDA. Other people have reported this problem. Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk. I don't believe in taking even small risks for no benefit. is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?

Gene
----- Original Message -----
From: Adriani Botez<mailto:adriani.botez@gmail.com>
Sent: Sunday, March 11, 2018 2:32 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Garry,

Do the letters appear on the screen as fast as you type? Or are they delayed?

Please run a CCleaner and clean your registry. Does the issue still occur?

Best
Adriani

Von meinem iPhone gesendet

Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@gmail.com<mailto:joseph.lee22590@gmail.com>>:
Hi,
Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.
Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).
Cheers,
Joseph

From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Ok, that's really odd. All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue. I'm confused to how that could be possible. :/


Re: Typing Echo Change with 2018.1

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

Remember Espeak being horrid is just your opinion, many people like myself like it a lot aas 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: "Lino Morales" <linomorales001@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 12:19 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


Actually I’ve noticed this problem myself in NVDA 2017.4 and 2017.3. I’m using horrid Espeak right now cause I’ll be checking my Facebook before church.

Lino Morales

From: Gene<mailto:gsasner@ripco.com>
Sent: Sunday, March 11, 2018 8:12 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

I see no reason to do anything with the registry. Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory. The problem started with a new release of NVDA. Other people have reported this problem. Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk. I don't believe in taking even small risks for no benefit. is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?

Gene
----- Original Message -----
From: Adriani Botez<mailto:adriani.botez@gmail.com>
Sent: Sunday, March 11, 2018 2:32 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Garry,

Do the letters appear on the screen as fast as you type? Or are they delayed?

Please run a CCleaner and clean your registry. Does the issue still occur?

Best
Adriani

Von meinem iPhone gesendet

Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@gmail.com<mailto:joseph.lee22590@gmail.com>>:
Hi,
Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.
Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).
Cheers,
Joseph

From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Ok, that's really odd. All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue. I'm confused to how that could be possible. :/