Date   
Subject lines, was, Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

Gene
 

Will people please change subject lines when starting a new thread?  This has nothing to do with the old thread.  Also, all the irrelevant old messages were retained.  Please either start a completely new thread or if you use reply, delete everything and then start a completely new message and subject line. 
 
for one thing, people will be less likely to read your message when the subject line has nothing to do with what it is.  For another, it causes the archives not to reflect what is being discussed accurately in a thread.  And third, people who read messages by conversation will not have their mail organized accurately by subject. 
 
I may remind people of this more often.  This isn't something to punish people about but it is my view that one of the functions of a list should be to teach and make people more aware of what are considered good practices on lists.  I almost never see this done and the result is that things don't improve because people aren't reminded and nudged toward improving practices. 
 
Gene
 

Re: FW: [Nvda-devel] FW: Browse Mode with NVDA 2016.2 not working

Bobby <bvinton@...>
 

Hi I am not having that problem at all. Every thing is working very well for me.

On 6/2/2016 7:54 PM, Joseph Lee wrote:
Hi,
Let us know what your thoughts are so one of us can forward this to the
developers (or if you are a member of the nvda-devel list, I'd like to
request help in shuttling emails back and forth). Thanks.
Cheers,
Joseph

-----Original Message-----
From: James Teh [mailto:jamie@...]
Sent: Thursday, June 2, 2016 4:50 PM
To: NVDA screen reader development <nvda-devel@...>
Subject: Re: [Nvda-devel] FW: [nvda] Browse Mode with NVDA 2016.2 not
working

This suggests NVDA is unable to inject itself into the browser. There are a
few possibilities here:
1. NVDA's dll files didn't get updated properly for some reason. This would
also affect a portable copy if that portable copy was generated from the
installed copy. However, if the portable copy was created from a download
directly, that probably isn't the issue.
2. Something is blocking NVDA's dll files on that system; e.g. a virus
scanner.
3. If NVDA is started while a browser is focused, it sometimes cannot
inject. Does the issue persist if the user opens the browser *after* opening
NVDA?

Jamie

On 3/06/2016 8:02 AM, Joseph Lee wrote:
Hi,
I don't follow as to what's going on in the below log. Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Ethan
Sent: Thursday, June 2, 2016 2:58 PM
To: nvda@nvda.groups.io
Subject: [nvda] Browse Mode with NVDA 2016.2 not working

Hello all:

I was not sure where to post this so I apologize if this is off topic.

When I am using NVDA on the web in Firefox or Internet Explorer, it does
not read the page content. I am able to press tab to move through the
elements on the page, but when I press up or down arrow, nothing happens. It
is acting as if it is in browse mode and I am unable to exit out of browse
mode. No audible tones are heard to indicate entering or exit of browse
mode.
Ever since NVDA 2015.4 or NVDA 2016.1, I have been unable to use the
latest version of NVDA on my work computer. Instead, I am using NVDA 2015.3.
This problem appears to happen both on a portable copy and an installed copy
which makes me think it has to do something with dependent software that
needs to be updated on the individual computer. Here is my log viewer on
debug mode at the error point:
WindowsError: [Error 1702] The binding handle is invalid

// Start of log:
INFO - __main__ (16:15:53):
Starting NVDA
INFO - core.main (16:15:53):
Config dir: E:\NVDA 2016.2\userConfig
DEBUG - core.main (16:15:53):
setting language to Windows
INFO - core.main (16:15:53):
NVDA version 2016.2
INFO - core.main (16:15:53):
Using Windows version 6.1.7601 service pack 1 workstation INFO - core.main
(16:15:53):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (16:15:53):
Using comtypes version 0.6.2
DEBUG - core.main (16:15:53):
Initializing addons system.
DEBUG - addonHandler._getAvailableAddonsFromPath (16:15:53):
Listing add-ons from E:\NVDA 2016.2\userConfig\addons DEBUG - core.main
(16:15:54):
Initializing appModule Handler
DEBUG - core.main (16:15:54):
Initializing NVDAHelper
DEBUG - core.main (16:15:54):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary '.\userConfig\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
file '.\userConfig\speechDicts\default.dic' not found.
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
3 loaded records.
DEBUG - core.main (16:15:54):
Initializing speech
INFO - synthDrivers.espeak.SynthDriver.__init__ (16:15:54):
Using eSpeak version 1.48.15 16.Apr.15 DEBUG -
speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary '.\userConfig\speechDicts\espeak-english.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
file '.\userConfig\speechDicts\espeak-english.dic' not found.
INFO - synthDriverHandler.setSynth (16:15:54):
Loaded synthDriver espeak
INFO - core.main (16:15:54):
Using wx version 3.0.2.0 msw (classic) DEBUG - core.main (16:15:54):
Initializing braille
INFO - braille.initialize (16:15:54):
Using liblouis version 2.6.5
INFO - braille.BrailleHandler.setDisplayByName (16:15:54):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (16:15:54):
Initializing braille input
INFO - brailleInput.initialize (16:15:54):
Braille input initialized
DEBUG - core.main (16:15:54):
Initializing displayModel
DEBUG - core.main (16:15:54):
Initializing GUI
DEBUG - core.main (16:15:54):
initializing Java Access Bridge support DEBUG - core.main (16:15:54):
Initializing winConsole support
DEBUG - core.main (16:15:54):
Initializing UIA support
DEBUG - core.main (16:15:54):
Initializing IAccessible support
DEBUG - core.main (16:15:54):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (16:15:54):
No locale gesture map for language en
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (16:15:54):
No user gesture map
DEBUG - core.main (16:15:54):
Initializing keyboard handler
DEBUG - core.main (16:15:54):
initializing mouse handler
DEBUG - core.main (16:15:54):
Initializing touchHandler
DEBUGWARNING - touchHandler.initialize (16:15:54):
Touch only supported on installed copies DEBUG - core.main (16:15:54):
Initializing global plugin handler
DEBUG - core.main (16:15:54):
Initializing core pump
DEBUG - core.main (16:15:54):
Initializing watchdog
DEBUG - core.main (16:15:54):
initializing updateCheck
INFO - core.main (16:15:54):
NVDA initialized
DEBUG - core.main (16:15:54):
entering wx application main loop
IO - speech.speak (16:15:55):
Speaking [LangChangeCommand ('en_GB'), u'Google - Mozilla Firefox icon 2
of 3'] IO - speech.speak (16:15:55):
Speaking [LangChangeCommand ('en_GB'), u'Google - Mozilla Firefox'] DEBUG
- treeInterceptorHandler.update (16:15:55):
Adding new treeInterceptor to runningTable:
<virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x059ACDF0> ERROR -
virtualBuffers.Gecko_ia2._loadBuffer (16:15:55):
Traceback (most recent call last):
File "virtualBuffers\__init__.pyo", line 369, in _loadBuffer
WindowsError: [Error 1702] The binding handle is invalid

Thank you for any information you can provide,

Ethan




----------------------------------------------------------------------
-------- What NetFlow Analyzer can do for you? Monitors network
bandwidth and traffic patterns at an interface-level. Reveals which
users, apps, and protocols are consuming the most bandwidth. Provides
multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make
informed decisions using capacity planning reports.
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie@...


----------------------------------------------------------------------------
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are

consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel



FW: [Nvda-devel] FW: Browse Mode with NVDA 2016.2 not working

 

Hi,
Let us know what your thoughts are so one of us can forward this to the
developers (or if you are a member of the nvda-devel list, I'd like to
request help in shuttling emails back and forth). Thanks.
Cheers,
Joseph

-----Original Message-----
From: James Teh [mailto:jamie@...]
Sent: Thursday, June 2, 2016 4:50 PM
To: NVDA screen reader development <nvda-devel@...>
Subject: Re: [Nvda-devel] FW: [nvda] Browse Mode with NVDA 2016.2 not
working

This suggests NVDA is unable to inject itself into the browser. There are a
few possibilities here:
1. NVDA's dll files didn't get updated properly for some reason. This would
also affect a portable copy if that portable copy was generated from the
installed copy. However, if the portable copy was created from a download
directly, that probably isn't the issue.
2. Something is blocking NVDA's dll files on that system; e.g. a virus
scanner.
3. If NVDA is started while a browser is focused, it sometimes cannot
inject. Does the issue persist if the user opens the browser *after* opening
NVDA?

Jamie

On 3/06/2016 8:02 AM, Joseph Lee wrote:
Hi,
I don't follow as to what's going on in the below log. Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Ethan
Sent: Thursday, June 2, 2016 2:58 PM
To: nvda@nvda.groups.io
Subject: [nvda] Browse Mode with NVDA 2016.2 not working

Hello all:

I was not sure where to post this so I apologize if this is off topic.

When I am using NVDA on the web in Firefox or Internet Explorer, it does
not read the page content. I am able to press tab to move through the
elements on the page, but when I press up or down arrow, nothing happens. It
is acting as if it is in browse mode and I am unable to exit out of browse
mode. No audible tones are heard to indicate entering or exit of browse
mode.
Ever since NVDA 2015.4 or NVDA 2016.1, I have been unable to use the
latest version of NVDA on my work computer. Instead, I am using NVDA 2015.3.
This problem appears to happen both on a portable copy and an installed copy
which makes me think it has to do something with dependent software that
needs to be updated on the individual computer. Here is my log viewer on
debug mode at the error point:
WindowsError: [Error 1702] The binding handle is invalid

// Start of log:
INFO - __main__ (16:15:53):
Starting NVDA
INFO - core.main (16:15:53):
Config dir: E:\NVDA 2016.2\userConfig
DEBUG - core.main (16:15:53):
setting language to Windows
INFO - core.main (16:15:53):
NVDA version 2016.2
INFO - core.main (16:15:53):
Using Windows version 6.1.7601 service pack 1 workstation INFO - core.main
(16:15:53):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (16:15:53):
Using comtypes version 0.6.2
DEBUG - core.main (16:15:53):
Initializing addons system.
DEBUG - addonHandler._getAvailableAddonsFromPath (16:15:53):
Listing add-ons from E:\NVDA 2016.2\userConfig\addons DEBUG - core.main
(16:15:54):
Initializing appModule Handler
DEBUG - core.main (16:15:54):
Initializing NVDAHelper
DEBUG - core.main (16:15:54):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary '.\userConfig\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
file '.\userConfig\speechDicts\default.dic' not found.
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
3 loaded records.
DEBUG - core.main (16:15:54):
Initializing speech
INFO - synthDrivers.espeak.SynthDriver.__init__ (16:15:54):
Using eSpeak version 1.48.15 16.Apr.15 DEBUG -
speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary '.\userConfig\speechDicts\espeak-english.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
file '.\userConfig\speechDicts\espeak-english.dic' not found.
INFO - synthDriverHandler.setSynth (16:15:54):
Loaded synthDriver espeak
INFO - core.main (16:15:54):
Using wx version 3.0.2.0 msw (classic) DEBUG - core.main (16:15:54):
Initializing braille
INFO - braille.initialize (16:15:54):
Using liblouis version 2.6.5
INFO - braille.BrailleHandler.setDisplayByName (16:15:54):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (16:15:54):
Initializing braille input
INFO - brailleInput.initialize (16:15:54):
Braille input initialized
DEBUG - core.main (16:15:54):
Initializing displayModel
DEBUG - core.main (16:15:54):
Initializing GUI
DEBUG - core.main (16:15:54):
initializing Java Access Bridge support DEBUG - core.main (16:15:54):
Initializing winConsole support
DEBUG - core.main (16:15:54):
Initializing UIA support
DEBUG - core.main (16:15:54):
Initializing IAccessible support
DEBUG - core.main (16:15:54):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (16:15:54):
No locale gesture map for language en
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (16:15:54):
No user gesture map
DEBUG - core.main (16:15:54):
Initializing keyboard handler
DEBUG - core.main (16:15:54):
initializing mouse handler
DEBUG - core.main (16:15:54):
Initializing touchHandler
DEBUGWARNING - touchHandler.initialize (16:15:54):
Touch only supported on installed copies DEBUG - core.main (16:15:54):
Initializing global plugin handler
DEBUG - core.main (16:15:54):
Initializing core pump
DEBUG - core.main (16:15:54):
Initializing watchdog
DEBUG - core.main (16:15:54):
initializing updateCheck
INFO - core.main (16:15:54):
NVDA initialized
DEBUG - core.main (16:15:54):
entering wx application main loop
IO - speech.speak (16:15:55):
Speaking [LangChangeCommand ('en_GB'), u'Google - Mozilla Firefox icon 2
of 3'] IO - speech.speak (16:15:55):
Speaking [LangChangeCommand ('en_GB'), u'Google - Mozilla Firefox'] DEBUG
- treeInterceptorHandler.update (16:15:55):
Adding new treeInterceptor to runningTable:
<virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x059ACDF0> ERROR -
virtualBuffers.Gecko_ia2._loadBuffer (16:15:55):
Traceback (most recent call last):
File "virtualBuffers\__init__.pyo", line 369, in _loadBuffer
WindowsError: [Error 1702] The binding handle is invalid

Thank you for any information you can provide,

Ethan




----------------------------------------------------------------------
-------- What NetFlow Analyzer can do for you? Monitors network
bandwidth and traffic patterns at an interface-level. Reveals which
users, apps, and protocols are consuming the most bandwidth. Provides
multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make
informed decisions using capacity planning reports.
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie@...


----------------------------------------------------------------------------
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are

consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel

Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

Hi,

I have reported your findings to LibLouis folks.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ben J. Bloomgren
Sent: Thursday, June 2, 2016 4:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hello all,

I just downloaded 2016.2, and I'm noticing a couple of problems with Braille tables.

I saw that they have implemented Koine (k o i n e) Greek, so I used a virtual keyboard to type the Greek characters. In the table called "Greek", accented letters aren't marked at all, which causes many issues even in modern Greek, which is simpler.

In Koine Greek, which often uses letters with one or two accent marks, the only accent mark shown is the Psili, or the smooth breathing. All the other accent marks, be they single or double, just give those bracket symbols inside of which is the hex value of the Unicode character. Should I post this to the Add-ons list as well?

Ben

On 6/1/2016 22:28, Joseph Lee wrote:
>

> Hi everyone,

>

>

>

> Yes, it is finally here: NVDA 2016.2, introducing spelling error

> beep, grammar error detection and more are now available. More info

> can be found on the nV Access post here:

>

> http://www.nvaccess.org/post/nvda-2016-2-released/

   

    

  





 

 

This email is free from viruses and malware because avast! Antivirus protection is active.

 



Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

Ben J. Bloomgren
 

Hello all,

I just downloaded 2016.2, and I'm noticing a couple of problems with Braille tables.

I saw that they have implemented Koine (k o i n e) Greek, so I used a virtual keyboard to type the Greek characters. In the table called "Greek", accented letters aren't marked at all, which causes many issues even in modern Greek, which is simpler.

In Koine Greek, which often uses letters with one or two accent marks, the only accent mark shown is the Psili, or the smooth breathing. All the other accent marks, be they single or double, just give those bracket symbols inside of which is the hex value of the Unicode character. Should I post this to the Add-ons list as well?

Ben

On 6/1/2016 22:28, Joseph Lee wrote:
> > Hi everyone, > > > > Yes, it is finally here: NVDA 2016.2, introducing spelling error > beep, grammar error detection and more are now available. More info > can be found on the nV Access post here: > > http://www.nvaccess.org/post/nvda-2016-2-released/





This email is free from viruses and malware because avast! Antivirus protection is active.


Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

Hi,

Hmmm, this is getting interesting…

What if you restart NVDA with add-ons disabled (once NVDA starts, press NVDA+Q, then select the third option)?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, June 2, 2016 3:35 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

but it keeps there even if i had restart my computer?

because i can do nothing at all only a reset.

cheers

paul otter

 

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

From: Joseph Lee

Sent: Thursday, June 02, 2016 9:45 PM

Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hi,

I see. Try restarting NVDA (Control+Alt+N), then open your temp folder, then locate nvdaOld.log.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, June 2, 2016 12:36 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

hi,

it is word 2003 with conversion package to open the newer types of files like docx etc.

but when it happens, there is nothing i can do.

all is frozen!

that's the problem.

so it not possible to safe that file.

it is'nt possible to open nvda by pressing nvda key plus n.

that's the case now.

greets

paul otter

 

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

From: Joseph Lee

Sent: Thursday, June 02, 2016 8:02 PM

Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hi,

When this happens again, can you attach the log file so one of us can take a look at it? Also, which Word version is this?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, June 2, 2016 10:00 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

    hello joseph,

i've installed 2016.2 but now i have a problem with my office

when i start word, after a few sentences, word stops because there is a problem in nvda.

when i re-install 2016.1 there is no problem at all.

what can that be?

is there a solution for it?

greets

paul otter

 

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

From: Joseph Lee

Sent: Thursday, June 02, 2016 7:28 AM

Subject: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hi everyone,

 

Yes, it is finally here: NVDA 2016.2, introducing spelling error beep, grammar error detection and more are now available. More info can be found on the nV Access post here:

http://www.nvaccess.org/post/nvda-2016-2-released/

 

Enjoy NVDA 2016.2.

Cheers,

Joseph (now one of the members of this list)

Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

P. Otter
 

but it keeps there even if i had restart my computer?
because i can do nothing at all only a reset.
cheers
paul otter
 

----- Original Message -----
From: Joseph Lee
Sent: Thursday, June 02, 2016 9:45 PM
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

Hi,

I see. Try restarting NVDA (Control+Alt+N), then open your temp folder, then locate nvdaOld.log.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, June 2, 2016 12:36 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

hi,

it is word 2003 with conversion package to open the newer types of files like docx etc.

but when it happens, there is nothing i can do.

all is frozen!

that's the problem.

so it not possible to safe that file.

it is'nt possible to open nvda by pressing nvda key plus n.

that's the case now.

greets

paul otter

 

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

From: Joseph Lee

Sent: Thursday, June 02, 2016 8:02 PM

Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hi,

When this happens again, can you attach the log file so one of us can take a look at it? Also, which Word version is this?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, June 2, 2016 10:00 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

    hello joseph,

i've installed 2016.2 but now i have a problem with my office

when i start word, after a few sentences, word stops because there is a problem in nvda.

when i re-install 2016.1 there is no problem at all.

what can that be?

is there a solution for it?

greets

paul otter

 

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

From: Joseph Lee

Sent: Thursday, June 02, 2016 7:28 AM

Subject: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hi everyone,

 

Yes, it is finally here: NVDA 2016.2, introducing spelling error beep, grammar error detection and more are now available. More info can be found on the nV Access post here:

http://www.nvaccess.org/post/nvda-2016-2-released/

 

Enjoy NVDA 2016.2.

Cheers,

Joseph (now one of the members of this list)

Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

Pascal Lambert
 

Hi,

Please, has anyone seen this message before “about: srcdoc” which appears when surfing with Firefox and causes the page to freeze.  Please any feedback and/or solution is appreciated.

Blessings

Pascal

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Thursday, June 2, 2016 7:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hi,

Ah…

When you notice that latest RC commit date is about a week old than the announcement date, then this means no change between latest RC and master.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Thursday, June 2, 2016 3:04 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Joseph,

             Thanks for that pointer.  That being said the most recent entry in the rc section has main number 13377 and a date-time stamp of May 26th while the most recent entry in the Master section has main number 13348 and a date-time stamp of this afternoon.  I would not ever read this as the current master version having been the most recent release candidate prior to becoming the actual release.
--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    

 

Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

Joseph Lee wrote: "When you notice that latest RC commit date is about a week old than the announcement date, then this means no change between latest RC and master."

Thanks for that clarification.  This is a different system than what I had been accustomed to "back in the day" when doing this sort of thing.  The build number (which is what I consider what comes ahead of the comma (or the whole thing) would not have changed when moved from candidate to master upon release.  

--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    


Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

Hi,

Ah…

When you notice that latest RC commit date is about a week old than the announcement date, then this means no change between latest RC and master.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Thursday, June 2, 2016 3:04 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Joseph,

             Thanks for that pointer.  That being said the most recent entry in the rc section has main number 13377 and a date-time stamp of May 26th while the most recent entry in the Master section has main number 13348 and a date-time stamp of this afternoon.  I would not ever read this as the current master version having been the most recent release candidate prior to becoming the actual release.
--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    

 

Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

That should have been 13337 for the latest RC main number, which is important in this situation as I imagine these increase as time progresses based on the other material on that page.
--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    


Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

Joseph,

             Thanks for that pointer.  That being said the most recent entry in the rc section has main number 13377 and a date-time stamp of May 26th while the most recent entry in the Master section has main number 13348 and a date-time stamp of this afternoon.  I would not ever read this as the current master version having been the most recent release candidate prior to becoming the actual release.
--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    


Re: Browse Mode with NVDA 2016.2 not working

 

Hi,
I don't understand what may hgave caused this - perhaps you are right in that something is happening with a dependent routine. I've forward your email to devs in hopes of getting an answer.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ethan
Sent: Thursday, June 2, 2016 2:58 PM
To: nvda@nvda.groups.io
Subject: [nvda] Browse Mode with NVDA 2016.2 not working

Hello all:

I was not sure where to post this so I apologize if this is off topic.

When I am using NVDA on the web in Firefox or Internet Explorer, it does not read the page content. I am able to press tab to move through the elements on the page, but when I press up or down arrow, nothing happens. It is acting as if it is in browse mode and I am unable to exit out of browse mode. No audible tones are heard to indicate entering or exit of browse mode.
Ever since NVDA 2015.4 or NVDA 2016.1, I have been unable to use the latest version of NVDA on my work computer. Instead, I am using NVDA 2015.3. This problem appears to happen both on a portable copy and an installed copy which makes me think it has to do something with dependent software that needs to be updated on the individual computer. Here is my log viewer on debug mode at the error point:
WindowsError: [Error 1702] The binding handle is invalid

// Start of log:
INFO - __main__ (16:15:53):
Starting NVDA
INFO - core.main (16:15:53):
Config dir: E:\NVDA 2016.2\userConfig
DEBUG - core.main (16:15:53):
setting language to Windows
INFO - core.main (16:15:53):
NVDA version 2016.2
INFO - core.main (16:15:53):
Using Windows version 6.1.7601 service pack 1 workstation INFO - core.main (16:15:53):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (16:15:53):
Using comtypes version 0.6.2
DEBUG - core.main (16:15:53):
Initializing addons system.
DEBUG - addonHandler._getAvailableAddonsFromPath (16:15:53):
Listing add-ons from E:\NVDA 2016.2\userConfig\addons DEBUG - core.main (16:15:54):
Initializing appModule Handler
DEBUG - core.main (16:15:54):
Initializing NVDAHelper
DEBUG - core.main (16:15:54):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary '.\userConfig\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
file '.\userConfig\speechDicts\default.dic' not found.
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
3 loaded records.
DEBUG - core.main (16:15:54):
Initializing speech
INFO - synthDrivers.espeak.SynthDriver.__init__ (16:15:54):
Using eSpeak version 1.48.15 16.Apr.15
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary '.\userConfig\speechDicts\espeak-english.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
file '.\userConfig\speechDicts\espeak-english.dic' not found.
INFO - synthDriverHandler.setSynth (16:15:54):
Loaded synthDriver espeak
INFO - core.main (16:15:54):
Using wx version 3.0.2.0 msw (classic)
DEBUG - core.main (16:15:54):
Initializing braille
INFO - braille.initialize (16:15:54):
Using liblouis version 2.6.5
INFO - braille.BrailleHandler.setDisplayByName (16:15:54):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (16:15:54):
Initializing braille input
INFO - brailleInput.initialize (16:15:54):
Braille input initialized
DEBUG - core.main (16:15:54):
Initializing displayModel
DEBUG - core.main (16:15:54):
Initializing GUI
DEBUG - core.main (16:15:54):
initializing Java Access Bridge support
DEBUG - core.main (16:15:54):
Initializing winConsole support
DEBUG - core.main (16:15:54):
Initializing UIA support
DEBUG - core.main (16:15:54):
Initializing IAccessible support
DEBUG - core.main (16:15:54):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (16:15:54):
No locale gesture map for language en
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (16:15:54):
No user gesture map
DEBUG - core.main (16:15:54):
Initializing keyboard handler
DEBUG - core.main (16:15:54):
initializing mouse handler
DEBUG - core.main (16:15:54):
Initializing touchHandler
DEBUGWARNING - touchHandler.initialize (16:15:54):
Touch only supported on installed copies DEBUG - core.main (16:15:54):
Initializing global plugin handler
DEBUG - core.main (16:15:54):
Initializing core pump
DEBUG - core.main (16:15:54):
Initializing watchdog
DEBUG - core.main (16:15:54):
initializing updateCheck
INFO - core.main (16:15:54):
NVDA initialized
DEBUG - core.main (16:15:54):
entering wx application main loop
IO - speech.speak (16:15:55):
Speaking [LangChangeCommand ('en_GB'), u'Google - Mozilla Firefox icon 2 of 3'] IO - speech.speak (16:15:55):
Speaking [LangChangeCommand ('en_GB'), u'Google - Mozilla Firefox'] DEBUG - treeInterceptorHandler.update (16:15:55):
Adding new treeInterceptor to runningTable:
<virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x059ACDF0> ERROR - virtualBuffers.Gecko_ia2._loadBuffer (16:15:55):
Traceback (most recent call last):
File "virtualBuffers\__init__.pyo", line 369, in _loadBuffer
WindowsError: [Error 1702] The binding handle is invalid

Thank you for any information you can provide,

Ethan

Browse Mode with NVDA 2016.2 not working

Ethan
 

Hello all:

I was not sure where to post this so I apologize if this is off topic.

When I am using NVDA on the web in Firefox or Internet Explorer, it
does not read the page content. I am able to press tab to move through
the elements on the page, but when I press up or down arrow, nothing
happens. It is acting as if it is in browse mode and I am unable to
exit out of browse mode. No audible tones are heard to indicate
entering or exit of browse mode.
Ever since NVDA 2015.4 or NVDA 2016.1, I have been unable to use the
latest version of NVDA on my work computer. Instead, I am using NVDA
2015.3. This problem appears to happen both on a portable copy and an
installed copy which makes me think it has to do something with
dependent software that needs to be updated on the individual
computer. Here is my log viewer on debug mode at the error point:
WindowsError: [Error 1702] The binding handle is invalid

// Start of log:
INFO - __main__ (16:15:53):
Starting NVDA
INFO - core.main (16:15:53):
Config dir: E:\NVDA 2016.2\userConfig
DEBUG - core.main (16:15:53):
setting language to Windows
INFO - core.main (16:15:53):
NVDA version 2016.2
INFO - core.main (16:15:53):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (16:15:53):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (16:15:53):
Using comtypes version 0.6.2
DEBUG - core.main (16:15:53):
Initializing addons system.
DEBUG - addonHandler._getAvailableAddonsFromPath (16:15:53):
Listing add-ons from E:\NVDA 2016.2\userConfig\addons
DEBUG - core.main (16:15:54):
Initializing appModule Handler
DEBUG - core.main (16:15:54):
Initializing NVDAHelper
DEBUG - core.main (16:15:54):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary '.\userConfig\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
file '.\userConfig\speechDicts\default.dic' not found.
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
3 loaded records.
DEBUG - core.main (16:15:54):
Initializing speech
INFO - synthDrivers.espeak.SynthDriver.__init__ (16:15:54):
Using eSpeak version 1.48.15 16.Apr.15
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
Loading speech dictionary '.\userConfig\speechDicts\espeak-english.dic'...
DEBUG - speechDictHandler.SpeechDict.load (16:15:54):
file '.\userConfig\speechDicts\espeak-english.dic' not found.
INFO - synthDriverHandler.setSynth (16:15:54):
Loaded synthDriver espeak
INFO - core.main (16:15:54):
Using wx version 3.0.2.0 msw (classic)
DEBUG - core.main (16:15:54):
Initializing braille
INFO - braille.initialize (16:15:54):
Using liblouis version 2.6.5
INFO - braille.BrailleHandler.setDisplayByName (16:15:54):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (16:15:54):
Initializing braille input
INFO - brailleInput.initialize (16:15:54):
Braille input initialized
DEBUG - core.main (16:15:54):
Initializing displayModel
DEBUG - core.main (16:15:54):
Initializing GUI
DEBUG - core.main (16:15:54):
initializing Java Access Bridge support
DEBUG - core.main (16:15:54):
Initializing winConsole support
DEBUG - core.main (16:15:54):
Initializing UIA support
DEBUG - core.main (16:15:54):
Initializing IAccessible support
DEBUG - core.main (16:15:54):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (16:15:54):
No locale gesture map for language en
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (16:15:54):
No user gesture map
DEBUG - core.main (16:15:54):
Initializing keyboard handler
DEBUG - core.main (16:15:54):
initializing mouse handler
DEBUG - core.main (16:15:54):
Initializing touchHandler
DEBUGWARNING - touchHandler.initialize (16:15:54):
Touch only supported on installed copies
DEBUG - core.main (16:15:54):
Initializing global plugin handler
DEBUG - core.main (16:15:54):
Initializing core pump
DEBUG - core.main (16:15:54):
Initializing watchdog
DEBUG - core.main (16:15:54):
initializing updateCheck
INFO - core.main (16:15:54):
NVDA initialized
DEBUG - core.main (16:15:54):
entering wx application main loop
IO - speech.speak (16:15:55):
Speaking [LangChangeCommand ('en_GB'), u'Google - Mozilla Firefox
icon 2 of 3']
IO - speech.speak (16:15:55):
Speaking [LangChangeCommand ('en_GB'), u'Google - Mozilla Firefox']
DEBUG - treeInterceptorHandler.update (16:15:55):
Adding new treeInterceptor to runningTable:
<virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x059ACDF0>
ERROR - virtualBuffers.Gecko_ia2._loadBuffer (16:15:55):
Traceback (most recent call last):
File "virtualBuffers\__init__.pyo", line 369, in _loadBuffer
WindowsError: [Error 1702] The binding handle is invalid

Thank you for any information you can provide,

Ethan

Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

Hi,

One way is using the source code or looking at the snapshots page:

http://www.nvaccess.org/files/nvda/snapshots/

The branch you might be interested in is “rc”.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Thursday, June 2, 2016 2:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

I disagree that there's no point in announcing it because it would save quite a few people from doing unnecessary downloads and installs.

However, if it's not announced, is there somewhere that one can look to determine that for oneself?  This was the second option and one I'd exercise if I knew where I could look on a consistent basis.


--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    

 

Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

I disagree that there's no point in announcing it because it would save quite a few people from doing unnecessary downloads and installs.

However, if it's not announced, is there somewhere that one can look to determine that for oneself?  This was the second option and one I'd exercise if I knew where I could look on a consistent basis.


--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    


Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

Hi,

In this case, it went directly from RC to stable version, and I think there’s no point in announcing that.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Thursday, June 2, 2016 2:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Joseph,

         Is it possible to include in these announcements whether or not the RC (in this case RC1) went directly to actual release or not, or can you tell me where to find that information on the website?

         I tend to install the RCs and can see no point in installing the actual release in those instances where the candidate went straight to being the release itself without any changes in anything but name.
--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    

 

Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

Joseph,

         Is it possible to include in these announcements whether or not the RC (in this case RC1) went directly to actual release or not, or can you tell me where to find that information on the website?

         I tend to install the RCs and can see no point in installing the actual release in those instances where the candidate went straight to being the release itself without any changes in anything but name.
--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

         ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"

    


Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

 

Hi,

I see. Try restarting NVDA (Control+Alt+N), then open your temp folder, then locate nvdaOld.log.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, June 2, 2016 12:36 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

hi,

it is word 2003 with conversion package to open the newer types of files like docx etc.

but when it happens, there is nothing i can do.

all is frozen!

that's the problem.

so it not possible to safe that file.

it is'nt possible to open nvda by pressing nvda key plus n.

that's the case now.

greets

paul otter

 

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

From: Joseph Lee

Sent: Thursday, June 02, 2016 8:02 PM

Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hi,

When this happens again, can you attach the log file so one of us can take a look at it? Also, which Word version is this?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, June 2, 2016 10:00 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

    hello joseph,

i've installed 2016.2 but now i have a problem with my office

when i start word, after a few sentences, word stops because there is a problem in nvda.

when i re-install 2016.1 there is no problem at all.

what can that be?

is there a solution for it?

greets

paul otter

 

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

From: Joseph Lee

Sent: Thursday, June 02, 2016 7:28 AM

Subject: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hi everyone,

 

Yes, it is finally here: NVDA 2016.2, introducing spelling error beep, grammar error detection and more are now available. More info can be found on the nV Access post here:

http://www.nvaccess.org/post/nvda-2016-2-released/

 

Enjoy NVDA 2016.2.

Cheers,

Joseph (now one of the members of this list)

Re: Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #release

P. Otter
 

hi,
it is word 2003 with conversion package to open the newer types of files like docx etc.
but when it happens, there is nothing i can do.
all is frozen!
that's the problem.
so it not possible to safe that file.
it is'nt possible to open nvda by pressing nvda key plus n.
that's the case now.
greets
paul otter
 

----- Original Message -----
From: Joseph Lee
Sent: Thursday, June 02, 2016 8:02 PM
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

Hi,

When this happens again, can you attach the log file so one of us can take a look at it? Also, which Word version is this?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of P. Otter
Sent: Thursday, June 2, 2016 10:00 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

    hello joseph,

i've installed 2016.2 but now i have a problem with my office

when i start word, after a few sentences, word stops because there is a problem in nvda.

when i re-install 2016.1 there is no problem at all.

what can that be?

is there a solution for it?

greets

paul otter

 

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

From: Joseph Lee

Sent: Thursday, June 02, 2016 7:28 AM

Subject: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release

 

Hi everyone,

 

Yes, it is finally here: NVDA 2016.2, introducing spelling error beep, grammar error detection and more are now available. More info can be found on the nV Access post here:

http://www.nvaccess.org/post/nvda-2016-2-released/

 

Enjoy NVDA 2016.2.

Cheers,

Joseph (now one of the members of this list)