What's New in Studio 2014 SP2?

Below are some of the new features in this release.

Flexible network licensing

This release includes a new network licensing system based on third-party technology from SafeNet. 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 continues to use the legacy Nalpeiron-based licensing system for both single-user activations and network licenses. This is to ensure a smooth transition to the SafeNet licensing scheme.

For more information on migrating from the previous to the new network licensing technology, contact your SDL representative.

Enhanced MultiTerm integration

Java-based technology dependency removed to improve performance and robustness when working with terminology

Starting with this release, Studio uses new technology for the integration with MultiTerm.

This ensures a faster, smoother and more robust experience when adding and editing terminology entries from Studio.

Option to delete termbase entries from within Studio

The Termbase Viewer window in the Editor view now contains an extra button -  Delete this Entry.

This enables you to delete entries from the active termbase without having to open it in MultiTerm and delete the entry from there.

Quick Add New Term option to add a term in one go

In addition to the Add New Term option, Studio 2014 SP2 now includes an extra option for adding and sending a term pair to a termbase in one go – Quick Add New Term.

Quick Add New Term saves terms that you select from the Editor, without requiring you to edit in the Termbase Viewer window. Use Quick Add New Term when you want to populate your termbase quickly, without filling in the available term fields and without manually hitting the Save Entry button. Continue to use  Add New Term if you want to edit term fields such as definition or context before saving the term.

Edit the source segments for all supported file types

Previously, you could only edit the source content for Microsoft Word, Excel and PowerPoint files. Studio 2014 SP2 now allows you to edit the source segments for all document file types (except the legacy SDLX ITD format) so that you can make small changes to the source text in the Editor view.

Source editing is now only restricted for:

• locked segments
• documents that are part of a project package for which source editing has been disabled
• documents containing tracked changes or comments in the source text

Option to sort translation memory (TM) results by date

Studio 2014 SP2 includes a new TM search option, Show most recent translation first.

This enables you to better control how Studio sorts the results of your concordance searches and segment lookups. By default, Studio sorts TM results by match percentage value, then by last edited and last added translation unit.

If you want to return to the old behavior, go to Project Settings/Options > Language Pairs > [your language pair] > Translation Memory and Automated Translation > Search and disable the Show most recent translation first checkbox.

Tag Verifier now available as a global setting

Previous versions of Studio required you to define tag verification settings for each type of file that you open in Studio. Starting with Studio 2014 SP2, the Tag check page is no longer present in the tree of each file type.                       

Instead, to simplify working with tag verification, it is available as a global setting under File > Options > Verification > Tag Verifier. The settings that you define here now control how Studio runs tag verification on any type of document.

Tag verification checks that the tags in the translated document match those in the source format.

Alphanumeric characters added to the list of recognized tokens

Studio now recognizes as tokens (placeables) any strings made up of combinations of:

• uppercase letters (VGN-FW550F)
• numbers (M10X30)
• underscores (NAME_4001C)
• dashes (VGN-FW550F)
• full stops (BV0.mxm.072.531)

Instead of trying to translate such strings, Studio now automatically transfers the alphanumeric string from the source segment into the target segment.

As a result, you can translate faster, especially if you are working with product catalogue and similar document types, where the only changes to segment text are the alphanumeric strings used.

Conditions

To be recognized as alphanumeric strings, the codes:

• must not start or end with underscores, dashes or full stops
• must not contain both dashes and full stops
• must contain at least one number and one letter

Existing TMs

To ensure correct TM leveraging, the new alphanumeric recognition setting remains disabled for existing TMs.

If you enable this new setting under Language Pairs > Translation Memory and Automated Translation > Auto-substitution, re-index your TM so that Studio can fully leverage the existing translation units.

Text replacement penalty also applied to acronyms and alphanumeric strings

The Text Replacement Penalty option now covers not only custom variables but also alphanumeric strings and acronyms in the source text.  

Studio does not try to translate alphanumeric strings (NAME_4001C) or acronyms (EUR). Instead, it automatically inserts these from your source segment because these codes usually do not need to change during translation.  

However, if you want to show that the acronym or alphanumeric string comes from the source text and not from the assigned TM, you can apply a text replacement penalty to the segment that contains the alphanumeric string, acronym or custom variable.

If you want to use the variables, acronyms or alphanumeric strings from the assigned TM instead of transferring them from the source text, disable automatic substitution from Options > Language Pairs > [your language pair] > Translation Memory and Automated Translation > Auto-substitution.

Improved word count and search logic for words containing apostrophes and dashes  

Studio 2014 SP2 uses an improved algorithm for processing words that contain dashes (-) or apostrophes (‘). This improvement translates into:

Lower word count

Studio no longer treats apostrophes and dashes as word separators, but as punctuation marks that link words together. This means that Studio counts elements like “it’s” or “splash-proof”, “NAME_4001C” as one single word.

Apostrophes that do not follow the new logic:

• Apostrophes followed or preceded by space. For example, “the ‘90s” or “girls’ night” both contain two words.
• Right single quotation mark (’)

Dashes that do not follow the new logic:

• Figure dash (‒)
• En dash (–)
• Em dash (—)
• Horizontal bar (―)
• Small Em dash (﹘)

Higher fuzzy matches

When searching for matches in the selected TMs, Studio considers apostrophes and dashes as separate tokens inside the words they link together. This means that when comparing words where the only difference is the type of dash or apostrophe used, Studio only penalizes the difference in punctuation and not the entire word.

Re-index your existing TMs before using them in Studio 2014 SP2. This synchronizes the TMs with the new logic for counting and matching words that contain apostrophes and dashes.  

Option to process newer Adobe InDesign/InCopy CC files

Starting with this release, Studio includes an extra option in the Adobe InDesign and InCopy CC File Type settings - Process unsupported file versions. This enables Studio to open Adobe InDesign CC files even if the file version of Adobe InDesign/InCopy is higher than the version available for Studio SP2.

SDLXLIFF files now always included in the return package

Previously, when running the Finalize or Generate Target Translations batch tasks before creating a return package, Studio only included the target files in the package. Starting with this release, Studio always includes the bilingual *.sdlxliff corresponding to the target files in the return package.

This means that you can continue to update the returned *.sdlxliff file, without running additional tasks like Revert to SDLXLIFF or Export Files.

Enhanced language support

Studio 2014 SP2 now features the same language support on Windows 7 and Windows 8.1.

To achieve this, the installation for Studio SP2 on Windows 7 includes the new languages supported in Windows 8.1. This ensures a smoother supply chain process when using a variety of operating system generations.