Date   

URGENT HELP NEEDED

Christo Vorster
 

Hi Group

 

We ar in need of a Talking Typing Tutor, compatible with Windows 10.

 

Can anybody please assist us with information, or rather, a website where can download such material.

 

Please assist.

 

Christo Vorster (South Africa)

 

Christo Vorster

Dosent: Kaleidoskoop Opleiding

Lecturer: Kaleidoscope Training

 

T: 023 348 7634

C: 079 512 2856

F: 023 348 7633

E: christo@...

W: www.kaleidoscopesa.org

Adderleystraat 20 Adderley Street

Posbus 933 P.O. Box, Worcester, 6849

 

 

 

 

 

 


Re: espeak and pronunciation of some words

Peter Beasley
 

I don't use Espeak, but if words are pronounced wrongly, change the pronunciation in the voice dictionary.

-----Original Message-----
From: Brian's Mail list account via Groups.Io
Sent: Monday, March 12, 2018 9:19 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

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: Question about transferring espeak data between NVDA & Braillenote touch version

Jessica D
 

Hi
I'm not sure.Can you please tell me where to check, for both versions?Thanks,Jessica

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

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





Webbie pdf to text new version with ocr

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

I know not much about it but picked this up on another account and as there have been discussions about such things here, I thought I'd mention it.

If you put webbie into a search you should find the site.
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: Windows10 Mail and NVDA: several bugs reported

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

I'll ask the next question which build of windows 10 is it he is using? I'm sure Joseph will ask otherwise!
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: "Iván Novegil via Groups.Io" <ivan.novegil=nvda.es@groups.io>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 9:59 AM
Subject: [nvda] Windows10 Mail and NVDA: several bugs reported


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@nvda.es <mailto:ivan.novegil@nvda.es>

NVDA.es Logo
Comunidad hispanohablante de NVDA | Proyecto NVDA.es
- www.NVDA.es <https://nvda.es>
- @nvda_es <https://twitter.com/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.***


Registry fixing tool in nvda

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

I know a number of people here have had serious issues with browsers not reading word not working right with nvda and other associated problems.
For some time now this has been known to be due to registry issues due to uninstallers of other software not correctly registering important files. The latest next snapshot has a tool to fix this, rather predictably in its tool menu, so if you are having such issues, it may well be a good idea to try this version of nvda and use the tool.
it should do no harm, but do remember that next snaps are bleeding edge code and will need to be used with caution. Always back up your previous version and set a restore point before doing any work on registry files. Note the account that its used on has to have admin access or it won't work.

Here is what the entry says.

commit 8793a65c7aa65949a9043aafc932627ff158c90a
Author: Michael Curran <mick@nvaccess.org>
Date: Thu 08 Mar 2018 09:41:04 +1000
Installer: re-register some common COM interfaces which commonly get broken by bad uninstallers.
Raw diff
commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 12:06:37 +1000
COMRegistrationFixes tool: add a backslash to the systemDrive. Also deremove some unused functions.
Raw diff
commit 3a5abd72a307fbe02779111dfee3bc5f5371345d
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 12:07:19 +1000
Add the COM Registrations Fixing tool to NVDA's Tools menu.
Raw diff
commit e1d79784de5f0b77343992e61b1fb811a9dc826e
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 15:43:05 +1000
Add a warning dialog to the COM Registration Fixing tool when run manually from the Tools menu.
Raw diff
commit 7c2e945533f7386b4b3142281e23009997f5d801
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@nvaccess.org>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff

------------------------------------------------------------------------------

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.

Gene
 

I don't know if turning up the volume of system sounds would make it louder, nor do I know if the sound can be changed.  But there is a sound.  also, when using the portable version of NVDA, when UAC comes on, you hear the phrase, secure desktop.  I don't know what, if anything, you hear with the installed version.  But it isn't as though, when using the default setting, UAC comes on often.  I don't see a good reason to disable a Windows security feature to eliminate a minimum amount of inconvenience. 
 
Gene

----- Original Message -----
Sent: Monday, March 12, 2018 5:57 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

But its not really a sound that shouts out a different thing. At least not
on windows 7 I have its not, maybe one can change it.
 Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Gene" <gsasner@...>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 10:37 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update
utility.


There already is a UAC sound.

Gene
----- Original Message -----
From: Chris via Groups.Io
Sent: Monday, March 12, 2018 5:01 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update
utility.


A sound can be associated in sounds in control panel



Whether it has a sound by default or not i cannot tell you but there is the
option to do so if one can be bothered that is





From: Brian's Mail list account via Groups.Io
Sent: 12 March 2018 09:35
To: nvda@nvda.groups.io
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update
utility.



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

Sent via blueyonder.

Please address personal E-mail to:-

briang1@..., putting 'Brian Gaff'

in the display name field.

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

From: "Dennis L" <dennisl1982@...>

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

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

But its not really a sound that shouts out a different thing. At least not on windows 7 I have its not, maybe one can change it.
Brian

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

----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Monday, March 12, 2018 10:37 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


There already is a UAC sound.

Gene
----- Original Message -----
From: Chris via Groups.Io
Sent: Monday, March 12, 2018 5:01 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


A sound can be associated in sounds in control panel



Whether it has a sound by default or not i cannot tell you but there is the option to do so if one can be bothered that is





From: Brian's Mail list account via Groups.Io
Sent: 12 March 2018 09:35
To: nvda@nvda.groups.io
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.



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.

Gene
 

There already is a UAC sound. 

Gene

----- Original Message -----
Sent: Monday, March 12, 2018 5:01 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

A sound can be associated in sounds in control panel

 

Whether it has a sound by default or not i cannot tell you but there is the option to do so if one can be bothered that is

 

 

From: Brian's Mail list account via Groups.Io
Sent: 12 March 2018 09:35
To: nvda@nvda.groups.io
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

 

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

Sent via blueyonder.

Please address personal E-mail to:-

briang1@..., putting 'Brian Gaff'

in the display name field.

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

From: "Dennis L" <dennisl1982@...>

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

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

Gene
 

In what version of Windows do you not hear UAC text spoken when the screen comes up?  In Windows 7 the text is spoken, from what I've read, unless you are using the portable version.  If this isn't the case, we should know it and the problem should be corrected.
 
Gene

----- Original Message -----
Sent: Monday, March 12, 2018 4:35 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

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@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Dennis L" <dennisl1982@...>
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@...>
> 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.

Gene
 

It's a minimum amount of inconvenience to respond when the UAC prompt appears.  All you have to do is use the alt y command.  Why are people so casual about disabling a security feature that is minimally inconvenient?  You issue one command.  Compare that very minor inconvenience to what you may have to doo if you are infected because UAC is off.  I realize that malware can circumvent UAC, and, from what I've been told, it isn't difficult.  But still, what if you could have prevented nfection by having it on at a minimum of inconvenience?
 
Gene

----- Original Message -----
From: Dennis L
Sent: Sunday, March 11, 2018 10:52 PM
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@...>
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.

Chris
 

A sound can be associated in sounds in control panel

 

Whether it has a sound by default or not i cannot tell you but there is the option to do so if one can be bothered that is

 

 

From: Brian's Mail list account via Groups.Io
Sent: 12 March 2018 09:35
To: nvda@nvda.groups.io
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

 

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

Sent via blueyonder.

Please address personal E-mail to:-

briang1@..., putting 'Brian Gaff'

in the display name field.

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

From: "Dennis L" <dennisl1982@...>

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

> 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

>

>

 

 

 

 


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