Detecting language please wait for.......
Looking at previous threads, I am encouraged to see that SDL are looking at improving compatibility with DNS and other programs that are designed to enhance accessibility.
I see that there is a new version of Studio coming out soon, so it seems like a good time to ask again whether SDL is going to be implementing full compatibility of the editor with Dragon NaturallySpeaking. As others have pointed out, MemoQ and DejaVu have been fully compatible for some time and it is a little odd that Studio hasn't followed suit yet.
Does anyone know whether Trados Studio 2017 will offer full text control?
A description of full text control can be found here: www.nuance.com/.../about_full_text_control.htm
Rob Edwards said:I agree that other software companies may have lucked into compatibility with DNS, but I can't help but wonder whether that is perhaps because they made the effort to make their products accessible from the design stage
I really doubt this. I do think we could have made it easier if we'd made consistent design choices 8-yrs or so ago as the studio Editor was built using C++ as oppose to .NET which is what most of the rest of the application uses. This would have given us what DNS looks for. So I don't think others specifically tried to make things work with Dragon that early on, but because they used a technology that DNS looks for today things just work out of the box.
The problem now is that this is a significant piece of work to correct and whilst work is ongoing to make this possible as part of a wider ranging change it won't be something we'll see in the Studio 2017 release.
Rob Edwards said:Also, do you think it may be possible for someone to develop a plug-in to allow Trados to work with DNS
Believe me when I tell you we have looked at this many times... I would like nothing more than to be able to achieve this. The problem also affects other speech technologies such as JAWS. A tech partner for Freedom Scientific has found a way to do this with a plugin specifically for JAWS but the development effort is very high which means that without a significant opportunity for them, or us, to recoup the costs through additional sales this is unlikely to move forward. I get the occasional request for this but once costs are mentioned it all goes very quiet!
A plugin for DNS would have exactly the same problem. The solution for us here is really different technology in the Studio Editor.
Rob Edwards said:Thanks for your reply Paul. ...or I disable the dictation box in DNS for Trados and then I have difficulties with spacing and capitalisation, I cannot use Dragon to correct the text that I have dictated and not being able to correct in Dragon means that I lose the ability to use my corrections to improve Dragon's accuracy.
Can I ask what version of Dragon you're using? Spacing used to be an issue for me with DNS 12 and 13, but in DPI14 it has disappeared altogether. Capitalization (assuming you're thinking of capitalizing the first letter of a segment) has also been a non-issue for me since Studio 2015, thanks to the AutoCorrect options. Regarding accuracy, or the perceived accuracy improvements that Dragon can achieve by using the correction menu, I have recently learned that we're not really missing out on that much, as speech recognition experts have explained to me that Dragon's accuracy is better fine-tuned and improved by doing other things, such as having Dragon recognize custom documents or adding words to the vocabulary. Apparently, correcting misrecognitions doesn't play that big a role. Plus, the improved accuracy since DPI14 (or DPI15 if you dictate into one of the first supported languages) means that the out-of-the-box accuracy is so high, even with a new profile, that this is no longer a big issue in unsupported applications.