This has been driving me insane for a while, but I've chosen to ignore it up until now.

Any time NVDA hits a case where there is "no next" something, like during object navigation or screen review, it has always said something that's much more akin to "non ext."

I have to believe that this is because, somewhere, the actual two word text phrase, "No Next," is in the bowels of NVDA somewhere, hopefully in settings, entered as a single word, "nonext."

When there is not a next of thing X, I want to hear, "No Next thing X," not, "non ext thing X."
--

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

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill

This has been driving me insane for a while, but I've chosen to ignore it up until now.

Any time NVDA hits a case where there is "no next" something, like during object navigation or screen review, it has always said something that's much more akin to "non ext."

I have to believe that this is because, somewhere, the actual two word text phrase, "No Next," is in the bowels of NVDA somewhere, hopefully in settings, entered as a single word, "nonext."

When there is not a next of thing X, I want to hear, "No Next thing X," not, "non ext thing X."
--

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

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill

Lanie & Sarah,

While I very much appreciate your interest, everything you've both asked/offered has already been covered.

Please read through the entirety of a topic before posting new replies.  The group rules request this of all members, as it avoids repetition, and it gets you up to speed.

It is an issue with the Microsoft David synth, and I have already posted a direct link to the Feedback Hub feedback I left about the issue.
--

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

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill

I dont know if this will work, but you could try removing the voice and adding it again, a long shot but it may work

This has been driving me insane for a while, but I've chosen to ignore it up until now.

Any time NVDA hits a case where there is "no next" something, like during object navigation or screen review, it has always said something that's much more akin to "non ext."

I have to believe that this is because, somewhere, the actual two word text phrase, "No Next," is in the bowels of NVDA somewhere, hopefully in settings, entered as a single word, "nonext."

When there is not a next of thing X, I want to hear, "No Next thing X," not, "non ext thing X."
--

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

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill

On Mon, Jan 3, 2022 at 02:25 PM, Chris Mullins wrote:

OneCore voice seems OK too, could it be anything to do with your dictionary file? 

-
It was.  I had done some work a while back that centered on recognizing the word "no" versus the abbreviation "no." for number.  I screwed up boundary condition after both of these, and in certain combinations it was creating some of that weirdness.

Thanks for bringing this up.  I've corrected it, or at least think I have, time will tell.  Now it will always be in the back of my mind that I need to check the speech dictionary twiddling I've done in the past to see if I made a mistake or didn't take something into account that's now being encountered.

Regular expressions, while absolutely incredible tools, do precisely what you tell them to do.  Screw up your match and you screw up the replacement that relies on it.
 
--

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

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill

On Mon, Jan 3, 2022 at 04:26 PM, Sarah k Alawami wrote:

Can you cancel that feedback then?

-
No, but I already added a comment that it can be safely ignored and explaining what happened.

They don't have a "close ticket" option as these are not really "trouble tickets" but reports.  I don't ever leave someone hanging, though, if a resolution has been found, so I did what I could to make sure the folks who review feedback are aware of that.
 
--

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

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill

This has been driving me insane for a while, but I've chosen to ignore it up until now.

Any time NVDA hits a case where there is "no next" something, like during object navigation or screen review, it has always said something that's much more akin to "non ext."

I have to believe that this is because, somewhere, the actual two word text phrase, "No Next," is in the bowels of NVDA somewhere, hopefully in settings, entered as a single word, "nonext."

When there is not a next of thing X, I want to hear, "No Next thing X," not, "non ext thing X."
--

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

The real art of conversation is not only to say the right thing in the right place but to leave unsaid the wrong thing at the tempting moment.

        ~ Dorothy Nevill