SDL Trados 2014

Richard Sikes & Angelika Zerfaß
MultiLingual June 2014
Product Reviews

Upon first launch, the user is greeted by a welcome screen containing links to the most important work areas within the software, either from the ribbon or from a navigation panel on the left-hand side. The top of the navigation panel contains an area that displays applications from OpenExchange. The prominent positioning of this display is a not-so-subtle hint at the importance SDL has placed upon OpenExchange as an extension of the core product functionality. Four applications are listed by default, followed by a link to the OpenExchange website.

Although OpenExchange has been available to licenced Trados Studio users since the 2009 version (Service Pack 3), providing users access to a variety of helpful utilities that could run alongside Trados, the 2014 release has made use of a new Integration application programming interface (API) that allows developers to embed their applications directly into the Trados user interface. OpenExchange applications thereby become part of the overall user experience, extending the core product functionality with a palette feature set that is essentially limited only by the time, resources and interest of third-party developers....

From Angelika’s perspective: starting with the installation of SDL Trados Studio and SDL MultiTerm, I was happy to see that the installation and file import into Studio are faster than with previous Studio versions. Also, it seems that the ability of Studio 2014 to export the translated file after translation has been improved. In Studio 2009 and 2011, there were some real issues with exporting InDesign or Word files back to their original format because of structural incompatibilities in the source files. We have historically been confronted with issues such as linked textboxes in InDesign that have a manual line break symbol somewhere between those linked textboxes, or missing paragraph marks in front of section or page breaks in Word files. These previously problematic files behave a lot better in Studio 2014 so that we sometimes use the 2014 version to export files for our support clients who are still using a previous version.

What I liked a lot is that a feature we have been sorely missing since Studio 2009 has come back again — the automatic concordance. As in Trados Workbench, you can now set the option for the concordance window to start a concordance search automatically if no match for the segment itself was found.

Something else I like is the ability to customize the analysis report so that there can be an extra category for locked segments (Figure 4). These had been counted as regular segments in previous versions thus making it difficult to exclude them in any way.

For the most part, working with Studio 2014 is not much different than working with Studio 2011, so switching the versions is mostly a matter of getting used to the new UI. Some new features make working a little faster, especially being able to drag-and-drop files into a project and not having to save files manually after each and every step. There is an auto-save feature now that will do this for you....