Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Studio Ideas
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
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
Hello Daniel. I just checked and confirmed you can use Dragon in the online version of SDL TRADOS 2021. I'm in fact dictating this comment to you using Dragon. If you try for example to use Dragon in chrome…
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.