Dictating #s 11-20 is problematic
Submitted by mvermilion on Fri, 11/06/2009 - 01:17.
I've been using DNS for years, but have not dependent on programming with it for awhile.
I fired up my Codewright editor this week and found that some of my natlink grammers involving operations on line numbers didn't work anymore when I dictated certain numbers.
A large set of them included 11 - 20, but there were other miscellaneous numbers between 1 and 100 sprinkled through that don't work either...
I'm using DNS 10.1, and 3.7 version of the Q's latest packaging. An error message showed up something like "Missing Internal Object." It seemed serious.
I adjusted the formatting to type numbers >= 0 without success. Since I've bullying DNS for years, I'm frustrated at not being able to get this right 
Anyone else seeing this problem?
Thanks.
Yah, it's a very common
Yah, it's a very common problem. With the Pro version I can usually fiddle around to find a workaround in my scripts, and I think Vocola/UniMacro users probably have similar strategies. But if you're just using straight Preferred, I'm not sure what to recommend -- maybe somebody else can help out.
Bruce
can you post the text of the
can you post the text of the error? (usually control C on dialog box will copy it)
I ask because the usual error is for DNS to just stop recognizing certain numbers. However, spelling out the digits usually still works. E.g., if destory ten comma fifteen is failing, try destory one zero comma one five.
To proceed on Marks analysis
To proceed on Marks analysis (if eg twenty three stops being recognised, two three "takes over"), assuming this is the problem in your case:
This is a vocabulary issue. So if you save (in a fresh) speech profile (in which things should work, so twenty three etc) your vocabulary, you can always switch back to this vocabulary when the error slips in. Sometimes after a few hours, often after a few days or a week of work.
Vocabulary optimalisation (adding words from documents etc) has to be followed by a export of your vocabulary (NaturallySpeaking, Manage Vocabularies...).
Before you switch back to your correct vocabulary, you can Export your custom words (if any new were made during correction) and import in the Imported vocabulary.
Quintijn
PS If something else is the case, please give more details.
Thank you! Creating a New Vocabulary Worked
I have been using the same vocabulary since the beginning of v10. Strange that it would've become corrupted like that. I added a new vocabulary, and all is correct. Thank you very much for the help. Thank you Quintijn for your work in keeping Natlink current.
Matt