Word problem


Bob Cavanaugh <cavbob1993@...>
 

Hi all,
I'm running Word 2016 and NVDA 2020.4, though this happened with
2020.3 as well. I'm having a weird issue with Word that I was just
able to test thoroughly. When reading a relatively short document,
this isn't an issue, but the longer the document is the bigger of an
issue it becomes. I start NVDA reading the document, and it reads
normally. If I use the control key to stop NVDA before it announces a
new page, I am where I expect to be in the document. However, if NVDA
has announced a page change before I stop reading and then I use
control to stop, I am back where I last stopped instead of where I
stopped reading.
Bob


Quentin Christensen
 

Bob,

Could you please send us a debug log?  I just tried and can't reproduce here with a quick test using OneCore at least.  Which synthesizer are you using?

Also, as a workaround and possibly better solution anyway, if you use SHIFT to pause speech rather than control, you can press SHIFT again to keep reading where it left off.

The other thing I thought was because NVDA grabs blocks of text (eg sentences) if you have a particularly long sentence stretching over a page, could it be that it is at the start of that block and it's just that it's long that you noticed it?

Quentin.

On Wed, Mar 31, 2021 at 2:20 PM Bob Cavanaugh <cavbob1993@...> wrote:
Hi all,
I'm running Word 2016 and NVDA 2020.4, though this happened with
2020.3 as well. I'm having a weird issue with Word that I was just
able to test thoroughly. When reading a relatively short document,
this isn't an issue, but the longer the document is the bigger of an
issue it becomes. I start NVDA reading the document, and it reads
normally. If I use the control key to stop NVDA before it announces a
new page, I am where I expect to be in the document. However, if NVDA
has announced a page change before I stop reading and then I use
control to stop, I am back where I last stopped instead of where I
stopped reading.
Bob







--
Quentin Christensen
Training and Support Manager


 

On Tue, Mar 30, 2021 at 11:31 PM, Quentin Christensen wrote:
Could you please send us a debug log?
-
Just in case it's needed:   Collecting NVDA Debugging Information to Report to NVAccess
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.

       ~ Richard M. Nixon

 


Bob Cavanaugh <cavbob1993@...>
 

I'm using E-Speak. Log will be coming to you privately soon.

On 3/30/21, Quentin Christensen <quentin@nvaccess.org> wrote:
Bob,

Could you please send us a debug log? I just tried and can't reproduce
here with a quick test using OneCore at least. Which synthesizer are you
using?

Also, as a workaround and possibly better solution anyway, if you use SHIFT
to pause speech rather than control, you can press SHIFT again to keep
reading where it left off.

The other thing I thought was because NVDA grabs blocks of text (eg
sentences) if you have a particularly long sentence stretching over a page,
could it be that it is at the start of that block and it's just that it's
long that you noticed it?

Quentin.

On Wed, Mar 31, 2021 at 2:20 PM Bob Cavanaugh <cavbob1993@gmail.com> wrote:

Hi all,
I'm running Word 2016 and NVDA 2020.4, though this happened with
2020.3 as well. I'm having a weird issue with Word that I was just
able to test thoroughly. When reading a relatively short document,
this isn't an issue, but the longer the document is the bigger of an
issue it becomes. I start NVDA reading the document, and it reads
normally. If I use the control key to stop NVDA before it announces a
new page, I am where I expect to be in the document. However, if NVDA
has announced a page change before I stop reading and then I use
control to stop, I am back where I last stopped instead of where I
stopped reading.
Bob





--
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>






Quentin Christensen
 

Got it, thanks Bob, Having a look now.

Quentin.

On Wed, Mar 31, 2021 at 3:28 PM Bob Cavanaugh <cavbob1993@...> wrote:
I'm using E-Speak. Log will be coming to you privately soon.

On 3/30/21, Quentin Christensen <quentin@...> wrote:
> Bob,
>
> Could you please send us a debug log?  I just tried and can't reproduce
> here with a quick test using OneCore at least.  Which synthesizer are you
> using?
>
> Also, as a workaround and possibly better solution anyway, if you use SHIFT
> to pause speech rather than control, you can press SHIFT again to keep
> reading where it left off.
>
> The other thing I thought was because NVDA grabs blocks of text (eg
> sentences) if you have a particularly long sentence stretching over a page,
> could it be that it is at the start of that block and it's just that it's
> long that you noticed it?
>
> Quentin.
>
> On Wed, Mar 31, 2021 at 2:20 PM Bob Cavanaugh <cavbob1993@...> wrote:
>
>> Hi all,
>> I'm running Word 2016 and NVDA 2020.4, though this happened with
>> 2020.3 as well. I'm having a weird issue with Word that I was just
>> able to test thoroughly. When reading a relatively short document,
>> this isn't an issue, but the longer the document is the bigger of an
>> issue it becomes. I start NVDA reading the document, and it reads
>> normally. If I use the control key to stop NVDA before it announces a
>> new page, I am where I expect to be in the document. However, if NVDA
>> has announced a page change before I stop reading and then I use
>> control to stop, I am back where I last stopped instead of where I
>> stopped reading.
>> Bob
>>
>>
>>
>>
>>
>>
>
> --
> Quentin Christensen
> Training and Support Manager
>
> Web: www.nvaccess.org
> Training: https://www.nvaccess.org/shop/
> Certification: https://certification.nvaccess.org/
> User group: https://nvda.groups.io/g/nvda
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess <https://twitter.com/NVAccess>
>
>
>
>
>
>







--
Quentin Christensen
Training and Support Manager


Vinod Benjamin
 

dear team,
I also have problem ,
in my MS office 2019 also NVDA is not reading the text at all.
how to create a debug log.
please help me.
Regards.
Vinod Benjamin

On 3/31/21, Quentin Christensen <quentin@nvaccess.org> wrote:
Got it, thanks Bob, Having a look now.

Quentin.

On Wed, Mar 31, 2021 at 3:28 PM Bob Cavanaugh <cavbob1993@gmail.com> wrote:

I'm using E-Speak. Log will be coming to you privately soon.

On 3/30/21, Quentin Christensen <quentin@nvaccess.org> wrote:
Bob,

Could you please send us a debug log? I just tried and can't reproduce
here with a quick test using OneCore at least. Which synthesizer are
you
using?

Also, as a workaround and possibly better solution anyway, if you use
SHIFT
to pause speech rather than control, you can press SHIFT again to keep
reading where it left off.

The other thing I thought was because NVDA grabs blocks of text (eg
sentences) if you have a particularly long sentence stretching over a
page,
could it be that it is at the start of that block and it's just that
it's
long that you noticed it?

Quentin.

On Wed, Mar 31, 2021 at 2:20 PM Bob Cavanaugh <cavbob1993@gmail.com>
wrote:

Hi all,
I'm running Word 2016 and NVDA 2020.4, though this happened with
2020.3 as well. I'm having a weird issue with Word that I was just
able to test thoroughly. When reading a relatively short document,
this isn't an issue, but the longer the document is the bigger of an
issue it becomes. I start NVDA reading the document, and it reads
normally. If I use the control key to stop NVDA before it announces a
new page, I am where I expect to be in the document. However, if NVDA
has announced a page change before I stop reading and then I use
control to stop, I am back where I last stopped instead of where I
stopped reading.
Bob





--
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>









--
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>






 

On Wed, Mar 31, 2021 at 02:18 PM, Vinod Benjamin wrote:
how to create a debug log.
-
Here's a pasted copy of the file I gave the link to.  I understand, since it's a Word document, and that's where your reading problem currently lies, that you wouldn't be able to read it.

--------

Collecting NVDA Debugging Information to Report to NVAccess.

Whether you are someone who has a GitHub account for NVDA or not, when it comes to reporting detailed information to the developers of NVDA when it’s needed you will be called upon to turn on debug level logging so that they can get a handle on exactly what’s happening.  You will often need to include this (or at least a chunk of the log) along with a description of what you have done (in exact steps, when possible) and what isn't working as it should.

Very often, issues are triggered by an Add-On rather than NVDA itself, so the first thing you should try is restarting NVDA with add-ons disabled, and see if you can recreate your problem, or if it goes away.  If it goes away, then you know that an add-on is triggering it.  You then have to go through add-ons manager, first disabling all add-ons except one, and restarting NVDA as usual, until turning one of them on causes your problem to reappear.  Once you know which add-on is causing the issue, this needs to be reported to the developer of that add-on rather than the NVDA developers.

Your NVDA key is either INSERT (desktop keyboard layout) or CAPS LOCK (laptop keyboard layout), depending on how you have NVDA set up. 

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, try recreate the issue - do whatever causes problems.  If the problem(s) still occur, even with all add-ons disabled, then you’ll want to proceed to changing the NVDA logging level so you have detailed information for reporting purposes.  If the problem(s) are gone, then go through the steps to figure out what add-on is causing them, noted above.


To set your log level:
1) Press NVDA+Control+G to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+Control+C to save settings.

When you restart NVDA, please do so with add-ons disabled, which will give the cleanest log, using the previously noted steps.

Once NVDA is running with add-ons disabled, recreate the issue - do whatever causes problems.  Once the problem(s) have occurred, there will be log information that needs to be sent to the developers.

There are several ways to access the NVDA log  file afterwards:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Press CONTROL+V to paste the copied log where you need to paste it.

Instead of using the log viewer, or if NVDA has stopped and you needed to restart it or the computer:
1) Press WINDOWS+R to open Windows Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letters T E M P and another percent sign).  Windows Explorer should open to the temporary folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log file for the current or most recent NVDA session), nvda-old.log (the log from the previous session) and nvda-crash.dmp (a crash dump with more information created if NVDA itself crashes).
5) Depending on whether you’re filing a GitHub issue or using an email program to send information to
info@..., exactly what you do will be different in regard to attaching files.  That being said, attach as many of those three files to an email to as would contain useful information.  This is generally the nvda.log file where debug level logging was active and the nvda-crash.dmp file if NVDA crashed.  As always, give a detailed description (including steps to reproduce) of has happened as well as a description of what you expected to happen.

 
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.

       ~ Richard M. Nixon

 


Vinod Benjamin
 

dear Brian,

Thanks so very much ,
I will do the same and.
get back to you.

Regards.
Vinod Benjamin

On 3/31/21, Brian Vogel <britechguy@gmail.com> wrote:
On Wed, Mar 31, 2021 at 02:18 PM, Vinod Benjamin wrote:


how to create a debug log.
-
Here's a pasted copy of the file I gave the link to.  I understand, since
it's a Word document, and that's where your reading problem currently lies,
that you wouldn't be able to read it.

--------

*Collecting NVDA Debugging Information to Report to NVAccess.*

Whether you are someone who has a GitHub account for NVDA or not, when it
comes to reporting detailed information to the developers of NVDA when it’s
needed you will be called upon to turn on debug level logging so that they
can get a handle on exactly what’s happening.  You will often need to
include this (or at least a chunk of the log) along with a description of
what you have done (in exact steps, when possible) and what isn't working as
it should.

Very often, issues are triggered by an Add-On rather than NVDA itself, so
the first thing you should try is restarting NVDA with add-ons disabled, and
see if you can recreate your problem, or if it goes away.  If it goes away,
then you know that an add-on is triggering it.  You then have to go through
add-ons manager, first disabling all add-ons except one, and restarting NVDA
as usual, until turning one of them on causes your problem to reappear.
Once you know which add-on is causing the issue, this needs to be reported
to the developer of that add-on rather than the NVDA developers.

Your NVDA key is either INSERT (desktop keyboard layout) or CAPS LOCK
(laptop keyboard layout), depending on how you have NVDA set up.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, try recreate the issue - do whatever causes problems.  If the
problem(s) still occur, even with all add-ons disabled, then you’ll want to
proceed to changing the NVDA logging level so you have detailed information
for reporting purposes.  If the problem(s) are gone, then go through the
steps to figure out what add-on is causing them, noted above.

To set your log level:
1) Press NVDA+Control+G to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+Control+C to save settings.

When you restart NVDA, *please do so with add-ons disabled* , which will
give the cleanest log, using the previously noted steps.

Once NVDA is running with add-ons disabled, recreate the issue - do whatever
causes problems.  Once the problem(s) have occurred, there will be log
information that needs to be sent to the developers.

There are several ways to access the NVDA log  file afterwards:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Press CONTROL+V to paste the copied log where you need to paste it.

Instead of using the log viewer, or if NVDA has stopped and you needed to
restart it or the computer:
1) Press WINDOWS+R to open Windows Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letters T E M P
and another percent sign).  Windows Explorer should open to the temporary
folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log file
for the current or most recent NVDA session), nvda-old.log (the log from the
previous session) and nvda-crash.dmp (a crash dump with more information
created if NVDA itself crashes).
5) Depending on whether you’re filing a GitHub issue or using an email
program to send information to info@nvaccess.org ( info@nvaccess.org ) ,
exactly what you do will be different in regard to attaching files.  That
being said, attach as many of those three files to an email to as would
contain useful information.  This is generally the nvda.log file where debug
level logging was active and the nvda-crash.dmp file if NVDA crashed.  As
always, give a detailed description (including steps to reproduce) of has
happened as well as a description of what you expected to happen.

--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042

Always remember others may hate you but those who hate you don't win unless
you hate them.  And then you destroy yourself.

~ Richard M. Nixon






Vinod Benjamin
 

Dear Brayan,

Wow! i am Able to find the addon doing the issue.
need to write to the developer .

its been a while, i have been facing this issue.
it was your elaborate explanation helped me in finding a resolution.

Regards,

Vinod Benjamin

On 4/1/21, Vinod Benjamin <vinbenji.group@gmail.com> wrote:
dear Brian,

Thanks so very much ,
I will do the same and.
get back to you.

Regards.
Vinod Benjamin

On 3/31/21, Brian Vogel <britechguy@gmail.com> wrote:
On Wed, Mar 31, 2021 at 02:18 PM, Vinod Benjamin wrote:


how to create a debug log.
-
Here's a pasted copy of the file I gave the link to.  I understand, since
it's a Word document, and that's where your reading problem currently
lies,
that you wouldn't be able to read it.

--------

*Collecting NVDA Debugging Information to Report to NVAccess.*

Whether you are someone who has a GitHub account for NVDA or not, when it
comes to reporting detailed information to the developers of NVDA when
it’s
needed you will be called upon to turn on debug level logging so that
they
can get a handle on exactly what’s happening.  You will often need to
include this (or at least a chunk of the log) along with a description of
what you have done (in exact steps, when possible) and what isn't working
as
it should.

Very often, issues are triggered by an Add-On rather than NVDA itself, so
the first thing you should try is restarting NVDA with add-ons disabled,
and
see if you can recreate your problem, or if it goes away.  If it goes
away,
then you know that an add-on is triggering it.  You then have to go
through
add-ons manager, first disabling all add-ons except one, and restarting
NVDA
as usual, until turning one of them on causes your problem to reappear.
Once you know which add-on is causing the issue, this needs to be
reported
to the developer of that add-on rather than the NVDA developers.

Your NVDA key is either INSERT (desktop keyboard layout) or CAPS LOCK
(laptop keyboard layout), depending on how you have NVDA set up.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, try recreate the issue - do whatever causes problems.  If the
problem(s) still occur, even with all add-ons disabled, then you’ll want
to
proceed to changing the NVDA logging level so you have detailed
information
for reporting purposes.  If the problem(s) are gone, then go through the
steps to figure out what add-on is causing them, noted above.

To set your log level:
1) Press NVDA+Control+G to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+Control+C to save settings.

When you restart NVDA, *please do so with add-ons disabled* , which will
give the cleanest log, using the previously noted steps.

Once NVDA is running with add-ons disabled, recreate the issue - do
whatever
causes problems.  Once the problem(s) have occurred, there will be log
information that needs to be sent to the developers.

There are several ways to access the NVDA log  file afterwards:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Press CONTROL+V to paste the copied log where you need to paste it.

Instead of using the log viewer, or if NVDA has stopped and you needed to
restart it or the computer:
1) Press WINDOWS+R to open Windows Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letters T E M
P
and another percent sign).  Windows Explorer should open to the temporary
folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log
file
for the current or most recent NVDA session), nvda-old.log (the log from
the
previous session) and nvda-crash.dmp (a crash dump with more information
created if NVDA itself crashes).
5) Depending on whether you’re filing a GitHub issue or using an email
program to send information to info@nvaccess.org ( info@nvaccess.org ) ,
exactly what you do will be different in regard to attaching files.  That
being said, attach as many of those three files to an email to as would
contain useful information.  This is generally the nvda.log file where
debug
level logging was active and the nvda-crash.dmp file if NVDA crashed.  As
always, give a detailed description (including steps to reproduce) of has
happened as well as a description of what you expected to happen.

--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042

Always remember others may hate you but those who hate you don't win
unless
you hate them.  And then you destroy yourself.

~ Richard M. Nixon






 

On Wed, Mar 31, 2021 at 03:05 PM, Vinod Benjamin wrote:
Wow! i am Able to find the addon doing the issue. Need to write to the developer .
-
Wonderful.   Thank you very much for taking the time to read the tutorial and then following through with all the steps.

I'm not trying to insult add-on developers in any way, but it's generally been the case that add-ons break something rather than the NVDA core.  Part of that is the way the development cycles of the NVDA core and NVDA add-ons diverge.  Many NVDA Add-On developers do this entirely on their own time and as time is available and sometimes changes in NVDA core requires add-on changes, and sometimes not.

Debugging software and determining root causes is a slow process that requires attention to detail.

Again, thanks very much for actually carrying out the necessary process to isolate your issue to its source.
--

Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042  

Always remember others may hate you but those who hate you don't win unless you hate them.  And then you destroy yourself.

       ~ Richard M. Nixon