Detecting language please wait for.......
I've been using Dragon with SDL for several years now, and although I'm not completely unhappy with the results, I feel frustrated that I can't use the 'Correct that' command so as to teach Dragon to become more accurate. Just being able to use that command would make a huge difference over time. If MemoQ has managed to offer full compatibility with Dragon, why has SDL not addressed this matter? Thanks in advance for your answers!
It's not a question of whether we have considered this or not, nor is it a question of memoQ or anyone else doing this. It is very likely that memoQ didn't have to do anything to achieve this capability of "full" compatibility with Dragon. If the technology in the editor of any application is based on something that Dragon can support then it works out of the box. Unfortunately the Studio editor is not based on a technology that Dragon will support in this way.
We have spent quite a bit of time looking at this, and not just for Dragon, but also for applications such as JAWS which need to be able to access more of the commands and features than Dragon needs and we are making progress. So a company retailing JAWS for example is working on a solution using the Studio API and some libraries we prepared to support this. I hope this will be available soon.
The compatibility with Dragon could probably be enhanced by Dragon developers if they chose to do this, but our own solution is unlikely to achieve native support until we change the Studio editor, and this is also something we are looking at.
In the meatime there are many users making good use of Dragon now, so perhaps there are some useful things you could do to improve things using some of the little tools such as "Knowbrainer" (I think that's what it's called). A very good person to ask about this is Nora Díaz as she has taken the use of Dragon to a new level for me!
Bruce Campbell said: The KnowBrainer scripts are faster, easier and more flexible than native Dragon scripts. As far as I know, it would not be possible to write a script like this as a native Dragon script.
The professional versions of Dragon also allow you to create custom scripts, so in essence anything you create in KnowBrainer can be created in Dragon Professional. Having said that, KnowBrainer is superior to Dragon in ease of use and flexibility, so I find it essential, even alongside Dragon Professional.
I have created a collection of text control commands to be used in Studio that I'm very happy with, so this really opens a lot of new possibilities, especially for someone with advanced scripting knowledge like yourself, I think as you play more with it you'll find that you can get Studio (and other applications unsupported by Dragon) to do practically anything you want.
Regarding your workflow where you dictate into Word and then transfer the text to Studio, wouldn't it be better to use Dragon's dictation box? I personally dictate directly into Studio and have disabled this option, but it can be activated in Dragon - Options - Miscellaneous - Use the dictation box for unsupported applications.
From Nuance: nuance.custhelp.com/.../limitations-of-dragon-13-in-unsupported-applications
Claudia Franco said:Thanks a lot for your detailed reply, Paul, this is exactly what I needed to know. I'm planning to do some research on how to improve my use of Dragon within Studio, but I didn't want to spend my time on that only to find that you were on your way to providing additional compatibility soon. Thanks!
We've already been in touch via my blog, but I think it would be a good idea to clarify for others who come upon this thread that the most recent version of Dragon, called Dragon Professional Individual 14 is a great improvement and offers lots of command customization possibilities that can be used in Studio, including custom text control.