Speech delay in Excel


David Hoff Jr
 

I have experienced a speech delay in Excel spreadsheets when using the
"#" sign.
--
A cell with the text of:
Member ID#: 1234567
will not delay, but speak immediateley.
<>
A cell with the text of:
Member #: 1234567
has a short delay before speaking the cell contents.

As I just cursored over the above I found that the same thing happens in
this email also. When this happens, it is possible to miss some
information that may be important. It seems that preceeding the "#" sign
with a charachor makes the diference.

Is this a bug or is there a reason for this?


Gene
 

What synthesizer are you using?  I have no difference when reading the two examples.  While there is a short pause, I attribute it to the colon.  I have punctuation set to off. 

Gene

On 4/20/2022 1:34 PM, David Hoff Jr wrote:
I have experienced a speech delay in Excel spreadsheets when using the
"#" sign.


David Hoff Jr
 

I am using:
1. Eloquence reed
2. Windows 7
3. Excel 2003
4. latest version of NVDA

I can remove the colon and the delay is still there.
If I remove the "#" sign the delay goes away.

The delay is slight, but long enough that I often cursor over it
accidentaly. If it were not for NVDA saying "cell" on the empty cells I
would not have caught this. I have punctuation set to the default
setting.

--
<>


Gene
 

I don't know why you are having the problem.  I don't know if the Eloquence add-on that you can purchase might cause this problem or if the SAPI 5 Eloquence might have this problem.

I would suggest trying another synthesizer to see if you still have the problem.  E-speak, being very responsive, despite how it sounds, would be a good test and it would be a good test because a lot of people would have that synthesizer available if they want to compare behavior on their machines.

Gene

On 4/21/2022 12:40 PM, David Hoff Jr wrote:
I am using:
1. Eloquence reed
2. Windows 7
3. Excel 2003
4. latest version of NVDA

I can remove the colon and the delay is still there.
If I remove the "#" sign the delay goes away.

The delay is slight, but long enough that I often cursor over it
accidentaly. If it were not for NVDA saying "cell" on the empty cells I
would not have caught this. I have punctuation set to the default
setting.


David Goldfield
 

Not to mention that he's using an unsupported operating system along with an unsupported version of Excel.
David, where did the version of Eloquence come from? Is it a SAPI version or the addon from Code Factory?
Does the delay occur with other synthesizers?
If there is any possibility that your computer can be upgraded to Windows 10 I would definitely recommend doing this along with upgrading your version of Office either to Microsoft 365 or to a supported perpetual license, such as Office 2019, 2021, etc.


David Goldfield,
Blindness Assistive Technology Specialist

NVDA Certified Expert

Subscribe to the Tech-VI announcement list to receive emails regarding news and events in the blindness assistive technology field.
Email: tech-vi+subscribe@groups.io
www.DavidGoldfield.org

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene
Sent: Thursday, April 21, 2022 3:50 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Speech delay in Excel

I don't know why you are having the problem.  I don't know if the Eloquence add-on that you can purchase might cause this problem or if the SAPI 5 Eloquence might have this problem.

I would suggest trying another synthesizer to see if you still have the problem.  E-speak, being very responsive, despite how it sounds, would be a good test and it would be a good test because a lot of people would have that synthesizer available if they want to compare behavior on their machines.

Gene
On 4/21/2022 12:40 PM, David Hoff Jr wrote:
I am using:
1. Eloquence reed
2. Windows 7
3. Excel 2003
4. latest version of NVDA

I can remove the colon and the delay is still there.
If I remove the "#" sign the delay goes away.

The delay is slight, but long enough that I often cursor over it
accidentaly. If it were not for NVDA saying "cell" on the empty cells
I would not have caught this. I have punctuation set to the default
setting.


 

On Thu, Apr 21, 2022 at 10:38 PM, David Goldfield wrote:
Not to mention that he's using an unsupported operating system along with an unsupported version of Excel.
-
Indeed.  And all one needs to do, particularly in regard to Excel, is think about how many patches have been made to Excel and NVDA both as time has marched on and changes have occurred to Excel.  There are fixes that were made for later versions of Excel that very likely rely on patches that occurred to Excel itself, and where something like Excel 2003 would never have received any of those patches.

While I can't (as much as I'd really love to do so) forbid the discussion of Windows 7 here so long as NVDA officially supports running under it, here's a big warning that the very moment that NVDA does a release that no longer runs on Windows 7 that discussions of issues under Windows 7 will stop here.  There seems to be a perception among some that backward compatibility is and should be perpetual - it never has been and it never will be.  There also seems to be a perception that I am being mean or unreasonable for saying (and it's said in the group rules):  "The discussion of software on the NVDA Group is limited to software currently in support.  Depending on the type of software, specific version numbers will change with time.  Users are expected to know what remains in support and what has been dropped, and announcements will be made to this group when new software is released. It should be assumed that, when a new version of software is released, primary discussion will take place on that version, not versions of software which are years old. 

 

Unsupported versions of any software may only be discussed on the Chat Subgroup, not the main NVDA Group. "

But I'm not being unreasonable, it is those that think that any technical support group should be entertaining questions about software that's long out of support and hasn't received a patch in years are.  And very often the issues that are occurring with software that old, in combination with up-to-date screen readers and even Windows cannot ever be solved because they are due to things that will never be fixed.

So, after all of that has been said, if you are someone using Office 2003, then I don't care if you're on the latest version of NVDA or not, the topic belongs in the Chat Subgroup.  Office 2003 has been out of support for over a decade, and all of the programs in it will have issues that are not going to be fixed and that frequently were fixed in subsequent versions.  You are far more likely to fix a range of issues by getting a version of Office that is 2016 or newer, or going to Microsoft 365.  If that's cost prohibitive, although it's not as accessible as Office is overall, there is LibreOffice, which is free, and they have their own accessibility mailing list.

NVDA Chat Subgroup Archive:  https://nvda.groups.io/g/chat/topics

NVDA Chat Subgroup Addresses

To join:  chat+subscribe@nvda.groups.io

To post:  chat@nvda.groups.io

To unsubscribe:  chat+unsubscribe@nvda.groups.io

To receive a message containing the group description, and a list of these commands:  chat+help@nvda.groups.io

To stop receiving messages via email (you may still read messages on the Web):  chat+nomail@nvda.groups.io

This can also be used to put a vacation stop on group messages, then use one of the addresses below to resume delivery in the format of your choice.

To receive each group messages individually:  chat+single@nvda.groups.io

This is the default delivery unless you send a message to one of the addresses that follows.

To receive group messages in an HTML formatted digest:  chat+fulldigest@nvda.groups.io

To receive group messages in a plain text digest:  chat+digest@nvda.groups.io

To receive a daily summary instead of individual messages:  chat+summary@nvda.groups.io

To receive only special messages:  chat+special@nvda.groups.io

To contact the group owner(s):  chat+owner@nvda.groups.io
 
--

Brian - Windows 10, 64-Bit, Version 21H2, Build 19044  

You can't crush ideas by suppressing them. You can only crush them by ignoring them.
     ~ Ursula LeGuin, The Dispossessed


David Hoff Jr
 

Thanks all of you for your help. I was using SAPI 4. When I changed to
SAPI 5 the problem went away. This was not an Excel problem, but a wrong
setting in NVDA.


--
<>