Hi

I'm finding that in some sessions (but not all) my spoken command 'correct that' goes to the last location of 'that' on the page, instead of correcting the phrase I've just spoken - any suggestions?

Don't know if it's connected, but 'question mark' often produces the words rather than a '?'

Nick

Commands that include the word "that" (bold that, capitalize that, compound that) are liable to give unexpected results occasionally, as these commands are ambiguous. Does "that" refer to the word "that" or to the last utterance? It could be either, and there is no way for DNS to determine what you intend. Ditto with question mark: it doesn't happen to me often, but once in a blue moon. My guess is that I might be pausing slightly between the word "question" and "mark."

You might try creating a new profile to see if that's helps.

The best way to prevent the "correct that" problem is to correct phrases rather than individual words. For example, to fix the second last word in the previous paragraph, say "correct if that's helps" instead of "correct that's." Correcting phrases in context will help improve accuracy by fine-tuning the language model.

In addition to Alan's advice you could consider creating your own command for correction that removes "that" from the whole equation, especially as you have the professional version of Dragon NaturallySpeaking. You could create a command, with a name that you can easily remember. Make the command global and for the command type, use advanced scripting. Below the sub main line use:- HeardWord "spell","that".

I personally use "That's a Mistake". The Knowbrainer command set gives you some additional options if you have Knowbrainer, including " Correct" and "Nope". VoicePower uses "Correction" for the same purposes. I have both these programs and find them to be excellent, but found when I was using anything near "Correct" I would occasionally revert back to "Correct That" and strike the problem you are experiencing.

As to your problem with the question mark not being displayed as you wish, it is important that you say "question mark" without any pause between the two words, so that you effectively generate a compound word, i.e. "questionmark". Others on this forum have had the opposite problem in that they typically get the "?" sign when they want "Question Mark" in words. It's all about whether or not there is a pause between the two words as to how Dragon ultimately responds.

Others may be able to offer more elegant solutions to your problems, but the above works for me.

Regards,

Chris

-------------------------

Dual Core T9600 @ 2.80GHz, with 4G Ram, Windows 7, I7 2.67GHz with 8G Ram, Andrea USB, Samson Airline 77, Philips SpeechMike, Speechware 3 in 1, Dragon NaturallySpeaking Medical and 10.1,Knowbrainer 2011

That's great, thanks guys
Nick

What was that options.ini file tweak for changing "correct that" to "oops" - that always worked for me.

You will find what you're looking for when you look for the word “hard” as in How to change/edit NaturallySpeaking's hardcoded commands in the Quick Tips 

-------------------------

Click KB 2012 REV D to Download a 30 Day Evaluation of KnowBrainer 2012