Yes, great news about the Braille too!! I rely on MS Word 2010’s page count to
tell me when there is a page break. If Word tells me it did not go to the next
page, when I have to do a workaround to check. I use find and replace and type
^m in the find what box, and %%% in the replace with. Then those percent signs
show me where there is a page break, or if there is more than one real page
break on what should be just one page. Then of course I have to reverse the
find and replace. It would be lovely not to need to do that, and lately I
haven’t had to do this workaround.
Sue S.
From: Evan Reese
Sent: Tuesday, September 18, 2018 10:45 AM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] Re: double-reporting page breaks in rtf files using
jaws
Thanks Larry, this is good news.
Evan
From: llumpkin@xxxxxxxxxxxxx
Sent: Tuesday, September 18, 2018 11:36 AM
To: bksvol-discuss@xxxxxxxxxxxxx
Subject: [bksvol-discuss] double-reporting page breaks in rtf files using jaws
Hi. You may recall my previous post on the instances where jaws is double
reporting the page break while arrowing down in an rtf document. I just talked
to Eric Damery and I’d like to share his take on the problem which I think is
right on target.
He says that they don’t want to have to tell the users to make a dictionary
rule to do what JAWS should be doing by default. When using NVDA, arrowing down
just reports “page break” when you cross the symbol without doing anything and
that JAWS should do that as well. He verifies that now, arrowing down now just
says “blank”. I think we agreed that turning on the “column, page, and
something else” rule didn’t give us the information we needed. He is writing up
a bug report that says JAWS should be fixed to report “page break” when you
arrow over the symbol and that it should also report this in Braille as well.
Hope this explains it.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
