Studio 2015 SR2
Enhanced Termbase Settings UI
To accommodate the possibilities offered by the new Terminology Provider API, the Termbase Settings user interface in the project settings has been refreshed.
The new user interface for adding terminology resources resembles the one for Translation Memory and Automated Translation and is now ready for plugging in third party terminology apps.
The new user controls allow you to add MultiTerm files or server-based termbases as before, but you can now also create new file-based termbases from within Studio. Accessing Termbase Settings > Create > New File-based Termbase opens the MultiTerm Termbase Wizard. This way, you can create new, empty termbases as part of creating the project. For any additional tasks such as importing or exporting terminology from within Studio, we recommend using the Glossary Converter app or the standalone SDL MultiTerm application.
Add to terminology from concordance results
You can now add new terms to your termbase straight from the Concordance Search Window.
To do this, you select a source and a target string from the concordance results, then click on one of the newly added buttons from the Concordance Search Window:
· Add New Term – if you want to add the term and open the Edit Term mode in the Termbase Viewer window – this will allow you to fill all the available termbase fields and review the new term before adding it to the termbase.
· Quick Add New Term – if you want to directly add the term as is.
New Work in Progress (WIP) Report batch task
Leveraging on the new Batch Task API, there is a new WIP Report batch task that gives translators and PMs a more accurate picture of which tasks are required to perform translation or review.
The WIP Report batch task provides a summary of the current contents and status of segments in an SDLXLIFF file without any lookups in TMs. Based on the confirmation level of each segment, the report also shows which tasks are to be performed on each category, such as Post-Editing for machine-translated draft segments or Review for any translated segments.
Enhanced licensing to support multiple editions and add-ins
It is now possible to run multiple product editions on the same network license server.
For example, you can connect Studio to a Professional or Workgroup license from the same network license server if those licenses are activated on that server.
If that is the case, the Product Activation window in Studio displays a new dialog box that allows you to select from multiple product editions.
There is also an optional settings file that gives you control over which editions can be checked out by the user.
Enhancements to the Microsoft Word (2007-2016) file type
The new Microsoft Word (2007-2016) file type has reached maturity and is now the default against the legacy Word (2007-2013) file type. When using the new file type, you can now keep track of your progress with the real-time preview, regardless of your version of Microsoft Office.
These enhancements to the Microsoft Word (2007-2016) file type were made for the SR2 release:
· New real-time preview in separate application window to support Microsoft Office Click-to-Run versions (e.g. Office 365).
· The new embedded HTML-based preview is now fully available.
· The preview types naming has been improved:
· Embedded refers to the legacy realtime preview
· Microsoft Word refers to the new external realtime preview
· HTML refers to the new HTML-based preview.
· The new Microsoft Word (2007-2016) file type has been moved to be listed above the legacy Word (2007-2013) file type in the default order of file types. This helps ensure that the new file type is used for new projects instead of the legacy one. We recommend using the new file type wherever possible.
· The PDF file type also uses the new Word (2007-2016) file type as its output format.
· The default value for the alternative text setting has been changed so that such text is not extracted by default.
Enhanced the project package handling
Some additions to the way project packages are handled were made to customize process.
The Open Package wizard is now more flexible, in the sense that you can now choose whether or not you wish to add the project name to the folder by default. On the Review Package Contents page of the wizard, enable or disable the Append project name to project folder option for this.
On the same wizard page, you can choose whether or not to save packages to the Studio default project location or a custom one with the Use default Studio project location option.
Enforce verification checks before package return
When creating a project package, you now have the option to enforce the assigned user to perform verification checks before they create the returning package.
This is to ensure that less experienced Studio users return an error-free project package. You can find the new User must run verification before returning the package option on the last page of the Create Project Package wizard.
A corresponding flag has also been added to the SDL Project Automation API so that developers of third-party systems can make use of this new feature and flow.
Added option to insert match in merged segments
When merging segments, you now have the option to automatically update the content in target segments, if a better match is found in the TM for the merged segment.
This new option was introduced under File > Options > Editor > Automation.
Added support for QuarkXPress 2015 files
The QuarkXPress file type can now support QuarkXPress 2015 files.
Studio 2015 SR1
Added new option for TM update batch tasks and exposed all options in TM API
Until now, you either had to add all translation units (TUs) as new TUs, thus keeping unwanted duplicates where you fixed spelling mistakes, or overwrite all existing TUs, which lead to deleting duplicates that have been explicitly added by the translator using the Add as New Translation command. With the Merge translation units option, you now have the flexibility to incorporate both options in one single batch task. This also allows you to merge any metadata associated with the TUs during the batch task.
Added support for Microsoft Office 2016 files to all Microsoft file types
All Microsoft file types (Microsoft Word 2007-2013, Microsoft Excel 2007-2013 and Microsoft PowerPoint 2007-2013) as well as the bilingual Workbench file type have been enhanced to support files created in Microsoft Office 2016.
Improved Language Cloud Wizard experience
The SDL Language Cloud Wizard that is displayed on SDL Trados Studio startup has been enhanced to provide easier access to SDL Language Cloud Machine Translation.
Also, the API key for Language Cloud no longer needs to be entered every time after starting Studio.
Production ready Microsoft Word File Type
The new Microsoft Word 2007-20016 file type launched with Studio 2015 as a technical preview alongside the legacy Microsoft Word file type is now production ready. The new file type, designed with robustness and performance in mind, can now be use in production projects. However, it is not the default file type in this release – the legacy file type is still used by default to allow you to finish ongoing projects without disruption.
Due to the changes in handling comments, we recommend you to reset the Word 2007-2016 file type settings to default after you upgrade to Studio Service Release 1. To do this, go to File > Options > Microsoft Word 2007 – 2016 > Common and press Reset to Default.
Translation Quality Assessment for custom quality analysis
Use the new Translation Quality Assessment feature in Studio 2015 to measure the quality of a translation using custom quality criteria.
Choose the quality metrics that matter most to you, weigh their importance and set up a TQA framework. This framework guides the reviewers when evaluating translations and enables Studio to determine the quality of a translation automatically.
Update project files with changes made to a target file during review
With the Retrofit feature, you can import any changes made by an external reviewer to a previously exported native file back into your Studio project. There is a new Update from Reviewed Target File (Retrofit) batch task for this.
After the changes are imported, you can review the updates in the Editor view using tracked changes. Optionally, you can also check and correct the retrofit results in Alignment view before opening them in the Editor.
AutoCorrect spelling or easily insert frequently used text and symbols
Use the AutoCorrect feature to automatically replace misspelled words and typos from a default set of terms. You can modify the list of terms to suit your own needs.
The AutoCorrect settings are applied in the Studio Editor, as you type. Studio uses the replacement list for the project’s target language to make the corrections. You can also set up shortcuts in the replacement list to speed up typing of certain words or phrases or to insert symbols.
To access the settings for autocorrection, select File > Options and find them under Editor > AutoCorrect.
Extend AutoSuggest to every kind of match
You can now extend the AutoSuggest feature in Studio to every kind of match for the current segment, be it a translation memory match, a machine translation match or a concordance match. You can thus refine the way you work with these matches, as you can choose what translation fragments to apply, straight from the Editor. When you activate a segment, Studio looks up the source segment in the translation providers configured with the project. Start typing and matching results are offered to prefixes.
To set up translation providers for AutoSuggest, go to Files > Options > AutoSuggest tree > Translation Memory and Automated Translation.
Choose if machine translation match is inserted in Editor
You now have the option to set the behavior for when a translation memory match is not found. By default, when this happens and a machine translation provider is configured, the MT match appears in the Translation Results window, but is not inserted in the active target segment of the Editor. Instead, when you start typing in the target segment, you get fragments of text from the MT match that you can apply to your translation or not. This gives you a lot more control over the MT and decreases the time it takes for post-editing MT matches.
You can choose whether the MT match is automatically inserted in the Editor using the Apply automated translation when no TM match is found option found in File > Options > Editor > Automation.
Contemporary look and feel for the User Interface
Studio 2015 has a refreshed user interface. The flat-style icon set and window look puts it in line with the current Microsoft operating system and Office suite.
The UI refresh also brings with it minor tweaks in user experience, like a new look of the ribbon display options button. In addition, to enhance usability, the Add as New Translation button was moved from the Advanced tab to the Confirm split button on the Home tab. The Lookup Translations command from the Translation Memory group on the Advanced tab is moved in the Segment Actions group on the Advanced tab.
Personalize the Ribbon interface with your preferred commands
The Ribbon interface is now customizable, allowing you to set up custom tabs and groups and add your preferred commands to those groups. You can add custom groups to default or custom tabs, and populate them with your preferred commands. You cannot add new commands to default groups.
You can now also add custom commands to the Quick Access Toolbar.
The new options are available from the View tab > User Interface group > Ribbon Customization. All changes you make to the ribbon can be reverted to default.
Leverage any TM, regardless of it matching languages with your project
With the new AnyTM provider options, Studio can now add any file- or server-based translation memories to a project, even if the source and target languages of the TMs do not match those of the project’s. You can also work with TMs in reverse language direction. For example, you can translate a German > English project using anEnglish > German TM. To work with TMs that do not match your project’s languages use the AnyTM options from the Translation Memory and Automated Translation page.
AnyTM allows you to translate documents that contain text in more than one different language. For example, translate a document with English, French and Dutch content into German. Studio handles this type of document and automatically leverages and updates the appropriate TM depending on the language of the segment being translated.
For more information, see the Using AnyTM topic in the online Help.
The SDL Automated Translation provider is no longer available in the Add TM list as this engine provider has been retired in favour of more recent options such as SDL Language Cloud.
Create bookmarks and quickly jump to preferred segments
You can add custom bookmarks with notes in any document. Studio can automatically track the segment you were last translating in a document or project. Also, when opening a document, Studio can automatically jump to the last accessed segment.
Quickly insert special characters and symbols in the Editor
Insert special characters and symbols in straight into the translation Editor from the Ribbon UI.
Go to the Advanced tab and click Insert symbol. Choose from the available characters found in the dialog box and click the Insert button.
Robust licensing system
This release extends the licensing system based on third-party technology from SafeNet to all product activation methods. The new licensing mechanism provides an enhanced licensing robustness for a wide range of different network topologies. It also improves your licensing workflow to ensure more flexible deployments in networks and distributed scenarios.
Studio 2015 has discontinued support for the Nalpeiron-based licensing system for both single-user activation and network licenses.
For information on using the new network licensing technology, contact SDL Support.
Exclude locked segments from the Analyze Files batch task
You can now improve analysis speed for files with a lot of PerfectMatches or with locked 100% and context matches by skipping locked segments from the active analysis.
Find this option by navigating to File > Options > Language Pairs > All Language Pairs > Batch Processing > Analyze Files.
Enhanced word count and search logic for words containing hyphens and dashes
Following the improvements to the algorithm used for processing words with hyphens and apostrophes from Studio 2014 SP2, the word count behavior and matching logic has changed.
Word count: Studio 2015 introduces new options to define the word count behavior for words separated by hyphens, dashes or formatting tags. Find these options in the Fields and Settings section when adding or changing settings for a translation memory.
Added a new hyphen character to the list of separating or joining characters: minus sign −.
Matching algorithm: To decide if there is a context match or not when searching in the selected TMs, Studio compares the number of recognized tokens of the surrounding segments from the source and the suggested target. The new logic for counting and matching can therefore affect how a TM recognizes tokens and this may invalidate context matches if you change counting behaviour. Against this background, SDL recommends that you run thorough tests on your translation projects before making changes to the word counting.