BOLDTHAT does not work.....version DNS 9.5 does not support scripting....what do I do?

 Many thanks, carol

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

DNS 9.5 - Plain version - NOT Preferred and NOT Professional (this was stated in question fill-out form).

Quick Tips does not work - Invalid Pulgin in instruction:  Ox2d830cbc

 Audio Setup Wizard was run two weeks ago - did not assist in solving the issue

 SeaMonkey is my browser with XP Home

Thank you for your suggestions, Carol 

First, let's start with some basics. There is no such version as "Plain version." That is, at least not technically. You either have DNS 9.5 Essentials, Standard, Preferred, Professional, Legal, or Medical. I suspect that when you refer to "Playing version" you are indicating that you are using DNS 9.5 Standard, which is the most common off the shelf retail version next to Preferred. The professional versions are not available for purchase in retail stores or online except from VARs, certified vendors, or directly from Nuance. Assuming that you are referring to DNS 9.5 Standard, will work from there.

Second the reason that quick tips does not work in your browser is either because your browser does not support the Adobe PDF plug-in, or you do not have Adobe Acrobat reader 8.1 installed on your system. Since Adobe Acrobat reader is a free version of Adobe Acrobat, though limited, I would suggest that you go to www.adobe.com and obtain, download, and install a copy of Adobe Acrobat reader. Virtually 99% of all document links on the Internet display their documents using the, now ubiquitous, PDF format. The KnowBrainer "Quick Tips" is an Adobe Acrobat PDF file. If your browser does not support the Adobe Acrobat PDF plug-in, then I would suggest that you use Internet Explorer at least for reviewing such files and ensure that Adobe Acrobat reader is installed on your system.

Sometimes those who post solutions on any of the forums neglect to dig deeper into exactly what the nature of the problem is. Since KnowBrainer's suggestion didn't work for you, I would suggest that the problem originates from where it is exactly that you are trying to use the command "Bold that." Where font bolding is supported, the standard Microsoft hotkey is "Ctrl +b", or more simply, holding down the Ctrl key and pressing the "B" key. In the application in which you are attempting to use the "bold that" command, try using the standard keystrokes (Ctrl +b) by pressing the keys themselves as suggested. If the highlighted text that you want to bold is then bolded, then that command with should work in the application in which you are attempting to use it. If the highlighted text that you want to bold is not bolded when you press and hold down the Ctrl key and then press the "B" key, then the voice command for "bold that" will not work either. All voice commands only work where the standard key press function works, where there is an option under the "Format | Font" in the application menu, or in applications where font characteristics are supported. Bolding a selection of highlighted text using voice commands depends upon those commands being present and supported by MSAA (Microsoft Active Accessibility). If you can get a highlighted selection of text to bold manually by using the keyboard keystrokes, then the voice command should work. If it does not work, go to the Dragon NaturallySpeaking Options dialog and make sure that you have the option for "Enable Natural Language Commands" selected. The only reason that I point this out is that when you are working with in Microsoft Word or WordPerfect, the Natural Language Commands override the global commands. Therefore, using the command to "Bold that" in Microsoft Word or WordPerfect may not work if you have the "Enable Natural Language Commands" unchecked in the DNS Options dialog.

Lastly, make sure that if you're working in Microsoft Word and/or WordPerfect, that you turn off the automatic grammar and spell checking in the options. Having these options enabled in these wordprocessors can sometimes interfere with the correct execution of some voice commands. In addition, in some applications where bolding of text is supported, the command "bold that" may not work because such applications text editors are not fully Select-and-Say compliant. Under these conditions, try using the commands "bold on" and "bold off" to turn bolding on and off. Sometimes saying "bold that" doesn't work properly under these conditions, but you can still turn bolding on and off (i.e., toggle them on and off) using the bold on and bold off commands.

The bottom line is, if the bolding keystrokes don't work my manually engaging them via the keyboard, then they won't work in voice command because all that the voice command does is engage the keystrokes. Under this condition, highlighting and bolding of text is not supported in that particular text editor window.

Chuck Runquist

Former Dragon NaturallySpeaking SDK & Senior Technical Solutions PM for DNS

"We learn by doing." -- Aristotle