SDL Trados Studio 2014 Advanced

SDL Trados Studio 2014
Advanced
Training Course
Table of Contents
T A B L E O F CO NTENTS
Chapter 1: Introduction
Scope of this Training Course ... 1-2
Chapter 2: Translation Memory Maintenance

About Maintaining Translation Memories ... 2-2
Viewing the TM ... 2-2
Opening the TM ... 2-2
Browsing the TM ... 2-3
Viewing the TU Count ... 2-4
Editing TM Content ... 2-4
Editing TUs ... 2-5
Editing Segment Content ... 2-5
Editing TM Fields ... 2-5
Deleting TUs ... 2-6
Committing Pending Changes ... 2-6
Global Find and Replace ... 2-7
Filtering for TUs that Contain a Particular Term ... 2-9
Defining a Filter ... 2-9
Performing Batch Operations ... 2-11
Batch Editing Specific TUs ... 2-11
Batch Deleting Specific TUs ... 2-13
Example 1: Deleting very Short TUs ... 2-13
Defining the Filter ... 2-13
Running the Batch Delete Operation ... 2-15
Example 2: Deleting all TUs that Contain only a Hyperlink or an E-Mail Address ... 2-16
Defining the Filter ... 2-16
Running the Batch Delete Operation ... 2-18
Searching for Potential Duplicates ... 2-18
Exporting and Importing TM Content ... 2-20
Exporting a Subset of a TM ... 2-20
Importing a TMX File into a TM ... 2-22
Creating a New TM ... 2-22
Importing the TMX File ... 2-23
Summary ... 2-25
Chapter 3: Language Resources

What are Language Resources? ... 3-2
Editing the Language Resources of a TM ... 3-2
Viewing the Language Resources ... 3-2
Adding a Custom Abbreviation ... 3-3
Defining a Variable List ... 3-4
Using Variables during Translation ... 3-5
Summary ... 3-6
SDL TRADOS STUDIO 2014 ADVANCED

SDL plc Confidential. Copyright
2013 SDL plc.
Table of Contents
Chapter 4: Translation Memory Fields

What are TM Fields? ... 4-2
Creating a TM with Fields ... 4-2
Creating a New TM ... 4-2
Defining the TM Fields ... 4-2
Adding the Client List Field ... 4-3
Adding the Project Id Text Field ... 4-4
Using TM Fields During Translation ... 4-5
Opening the Sample Document ... 4-5
Selecting the Field Values ... 4-6
Applying Fields Values During Translation ... 4-7
Filtering TUs Based on TM Field Values ... 4-8
Selecting Different Field Values ... 4-8
Setting a Filter Penalty ... 4-9
Translating a Document with a Filter Penalty ... 4-10
Summary ... 4-12
Chapter 5: TM Search Options and Penalties

About TM Search Options and Penalties ... 5-2
Modifying TM Search Options and Penalties ... 5-2
Opening the Sample Document ... 5-2
Editing the TM Language Resources ... 5-2
Changing the Minimum Match Value ... 5-4
The Formatting Penalty ... 5-5
The Auto-Localization Penalty ... 5-5
The Text Replacement Penalty ... 5-7
Multiple Translation Penalty ... 5-7
Summary ... 5-8
Chapter 6: Translating XML Files

What is XML? ... 6-2
Opening an XML Document ... 6-2
Creating an XML File Type ... 6-3
Naming the XML File Type ... 6-3
Importing the Tag List ... 6-5
Excluding Tag Content from Translation ... 6-6
Defining Character Formatting for Tags ... 6-7
Defining Context Information ... 6-10
Selecting Pre-Defined Structure Information ... 6-11
Entering Custom Structure Information ... 6-13
Making Attribute Content Translatable ... 6-15
Saving the File Type ... 6-16
Adding a Preview Stylesheet ... 6-17
Processing the XML Document with the Custom File Type ... 6-18
Previewing the Document ... 6-18
Running the Tag Verification ... 6-20
Summary ... 6-21
2013 SDL plc.
Table of Contents
Chapter 7: Custom Quality Assurance Rules

About Regular Expressions ... 7-2
Using Regular Expressions in SDL Trados Studio 2014 ... 7-2
Using Regular Expressions in QA Checker ... 7-2
Configuring QA Checker ... 7-3
Running the Regular Expression Check ... 7-4
Using Regular Expressions in the Display Filter ... 7-5
Using Regular Expressions when Searching for Strings ... 7-6
Summary ... 7-7
Chapter 8: File Type Settings

About File Type Settings ... 8-2
Customizing File Type Settings ... 8-2
Changing Microsoft PowerPoint File Type Settings ... 8-2
Changing Microsoft Word File Type Settings ... 8-4
Tweaking Microsoft Excel Files ... 8-8
Processing Adobe InDesign Files ... 8-9
Supported Adobe InDesign Versions ... 8-10
Opening an IDML File ... 8-10
Changing the Adobe InDesign File Type Settings ... 8-11
Previewing Adobe InDesign Files ... 8-12
Summary ... 8-13
Chapter 9: Pseudo-Translation
About Pseudo-Translation ... 9-2
Pseudo-Translating an Excel File ... 9-2
Creating a Pseudo-translation Project ... 9-2
Configuring the Pseudo-translate Task Settings ... 9-5
Viewing the Pseudo-translated File ... 9-6
Summary ... 9-8
Chapter 10: Reviewing Translated Files

The Review Sample Scenario ... 10-2
Opening a Project Package for Review ... 10-2
Opening a File for Review ... 10-3
Selecting your Preferred Spell Checker ... 10-4
Approving Segments ... 10-5
Making Changes ... 10-6
Using the Display Filter ... 10-7
Displaying only Segments with Tracked Changes ... 10-7
Displaying Number only Segments ... 10-8
Summary ... 10-8
Chapter 11: Segment Verification

Segment Verification Settings ... 11-2
Reviewing and Changing the Verification Settings ... 11-2
Running the Verification ... 11-5

2013 SDL plc.
Table of Contents
Correcting Errors ... 11-5

Display Filtering by Segment Status ... 11-10
Completing the Review ... 11-10
Summary ... 11-10
Chapter 12: Reviewing in Microsoft Word

The Word Review Scenario ... 12-2
Converting SDL XLIFF to DOCX ... 12-2
Reviewing in Microsoft Word ... 12-3
Importing the Changes back into SDL XLIFF ... 12-4
Accepting Changes ... 12-5
Rejecting Changes ... 12-6
Handling Comments ... 12-6
Summary ... 12-7
Chapter 13: Project Sign-Off

Creating the Reviewer Return Package ... 13-2
The Training Sign-Off Scenario ... 13-3
Loading the Project ... 13-3
Importing the Return Package ... 13-3
Accepting all Changes and Signing Off the Translation ... 13-3
Finalizing the Project ... 13-5
Summary ... 13-8
Chapter 14: SDL PerfectMatch

About PerfectMatch ... 14-2
In What Way is a PM different from CM (Context Match)? ... 14-2
Preparing an Update Project with SDL PerfectMatch ... 14-2
Loading the Previous Project ... 14-3
Project Details and Languages ... 14-4
Selecting the Project Source Files ... 14-5
Selecting TM, AutoSuggest Dictionary and Termbase ... 14-6
Selecting the Previous Files ... 14-8
Update Project or Mid-Project Update ... 14-9
Preparing the Project ... 14-10
Viewing the Project Statistics ... 14-11
Viewing the Project Files ... 14-11
Adding Another File ... 14-12
Viewing the Pre-Translated Files ... 14-13
Summary ... 14-14
Chapter 15: Integration with SDL Trados 2007-based Supply Chains

General Information ... 15-2
Opening TTX Files in SDL Trados Studio 2014 ... 15-2
Opening SDLEdit Files in SDL Trados Studio ... 15-3
SDL TTX It! ... 15-4
Scope of the App ... 15-4
Starting the App ... 15-5
2013 SDL plc.
Table of Contents
Converting Native Files to TTX ... 15-5

Bilingual Word DOCX Files ... 15-7
Processing Bilingual DOCX FileS ... 15-8
Opening the DOCX File ... 15-9
Translating and Editing the Bilingual DOCX File ... 15-10
Saving the Document ... 15-11
Summary ... 15-11
Chapter 16: OpenExchange Apps

SDL XLIFF Batch Find and Replace ... 16-2
Adding the SDL XLIFF Files ... 16-2
Running a Find Operation ... 16-3
Running a Replace Operation ... 16-5
T-Window For Clipboard ... 16-7
Configuring the App Settings ... 16-8
Translating a File Through the Clipboard ... 16-9
Summary ... 16-11
Copyright
2013 SDL plc.
All rights reserved. No part of this documentation may be duplicated in whole or in part or reproduced in any form without the express written
permission of SDL plc.
MultiTerm, SDL PhraseFinder, SDL TermBase, SDLX, Trados, TranslationZone and Translator's Workbench are registered trademarks of
and AutoSuggest, QuickPlace, TagEditor and Trados Studio are trademarks of SDL plc. All other trademarks are the property of their
respective owners. The names of other companies and products mentioned herein may be the trademarks of their respective owners. Unless
stated to the contrary, no association with any other company or product is intended or should be inferred.
Although SDL takes all reasonable measures to provide accurate and comprehensive information about the product, this documentation is
provided as-is and all warranties, conditions or other terms concerning the documentation whether express or implied by statute, common
law or otherwise (including those relating to satisfactory quality and fitness for purposes) are excluded to the extent permitted by law.
Information in this documentation, including any URL and other Internet Web site references, is subject to change without notice. Without
limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the
express written permission of SDL plc.

2013 SDL plc.
Table of Contents
2013 SDL plc.
I N T R O D U CTI O N
This introduction provides a quick overview of the topics in the

SDL Trados Studio 2014 - Advanced training course.
Chapter
Introduction
SCOPE OF THIS TRAINING COURSE

This training course was designed for the following groups of users:
C
Translators who have completed the SDL Trados Studio 2014 Getting Started (Part 1 and 2) and
Intermediate training courses and
Project managers who have completed the SDL Trados Studio 2014 for Project Managers training
courses (Part 1 and 2)
This course takes the concepts that you have learned in previous trainings to the next level by introducing
a number of features that will help you use SDL Trados Studio 2014 even more productively.
This training course focuses on the following topics:
C
Keeping your TM resources lean and efficient through effective TM maintenance
Taking your TMs to the next level by fine-tuning options, customized variable lists and attribute/text
fields
Localizing XML content effectively
Getting even more out of automated quality assurance through custom QA rules
Enhancing and customizing your localization workflows for different file types: Microsoft Word,
PowerPoint, Excel, Adobe InDesign
Pseudo-translation round-trips for identifying common localization problems before the actual
translation takes place
Further leverage SDL Trados Studio through OpenExchange Utilities, for example, run search and
replace operations over multiple files
Processing legacy files (i.e. TradosTag, ITD, bilingual MS Word documents) in SDL Trados Studio
2014
Review processes in SDL Trados Studio 2014: using the track changes feature, QA Checker and MS
Word-based review processes
Handling update projects and mid-project updates effectively with SDL PerfectMatch
The main focus of this training guide is on practical life examples, for which training sample files are
available.
We recommend that you copy the sample files to your desktop, so that you can find them more easily, i.e.:
..\Desktop\Sample Files.
1-2
2013 SDL plc.
T R A N S LA TI O N M EMORY
M A I N TENA NCE
This chapter provides practical examples of how to maintain a
translation memory. You will learn how to:
C
Browse through the content of a TM
Edit/delete translation units
Filter for specific translation units
Batch-edit and batch-delete a specific set of translation

units
Run a filtered TM export
Create a new TM based on the subset of another TM
Chapter
Translation Memory Maintenance
ABOUT MAINTAINING TRANSLATION MEMORIES

Maintaining your translation memories (TMs) can be necessary to keep your linguistic resources lean and
efficient. You can, for example, find and replace terms and expressions, when the terminology used in the
TM has become outdated and needs to be adapted to comply with new standards.
This chapter provides various practical examples of how to perform various maintenance operations on a
TM. Your sample files folder contains a small English to German sample TM with approx. 100 translation
units. The TM file can be found in your sample files folder, i.e. ..\Sample Files\01_TM_Maintenance.
VIEWING THE TM
Opening the TM
2-2
1.
Click the Translation Memories View button on the bottom of the Navigation pane to switch to the
Translation Memories view.
2.
Click the Open button on the Home tab, then select Open Translation Memory.
3.
Browse to your sample folder. Select the sample TM file Sample_EN-US_DE-DE.sdltm by

double-clicking it.
4.
The selected TM is now shown in the upper section of the Navigation pane.
2013 SDL plc.
The segment pairs (i.e. translation units or TUs for short) of this TM are now listed in a side-by-side view
as shown below:
Browsing the TM
You can, of course, scroll down in the list to view the TUs that are currently not displayed on the screen.
By default, the list contains 50 TUs. To browse to the next set of 50 TUs take the following steps:
1.
Click the Next Page button.
2.
Note that the next set of 50 TUs are now shown in the side-by-side view. Repeat the above
step to show the next set of TUs.
3.
When you press the Next Page button again, a message appears to inform you that no more
TUs have been found. Close the message by clicking OK. Note that the Next Page button is
now grayed out, as you have reached the end of the TM.
4.
To go back to the previous set of TUs click the Previous Page button.
5.
To go back to the beginning of the TM click the First Page button.

2-3
2013 SDL plc.
Viewing the TU Count

If you want to know how many TUs your TM contains, take the following steps:
1.
Right-click the TM and select Settings from the context menu.
2.
The TU count is shown in the Translation Units field of the Translation Memory Settings
dialog box. When you have ascertained the TU count click OK to close the dialog box.
EDITING TM CONTENT
Apart from viewing the TM content and properties you can also make changes, e.g. by editing and deleting
TUs.
2-4
2013 SDL plc.
Editing TUs
Let us assume that you want to make a change to TU number 3, i.e. Improved quality assurance with QA
Checker 2.0 to say Enhanced quality assurance with QA Checker 3.0:
Editing Segment Content

1.
Click inside the source segment of TU 3 and just overwrite Improved with Enhanced in the source
segment, and the number 2 with 3 both in the source and in the target segment.
2.
Note that the TU background color has changed. Also, an Edited icon has appeared next to
the TU.
Editing TM Fields
TUs can also have so-called TM fields, which are fully user-definable. TM fields contain meta data that
provide additional information on a TU, e.g. Subject, Project, etc.
NOTE
In one of the following chapters you will learn how to define and add such fields to a TM.
Let us assume that you would also like to change the value of the Type field from Technical
Documentation to Marketing. To do this take the following steps:
1.
Go to the Field Values window on the right-hand side. Click the small arrow next to the Type value.
2.
This opens the list of available field values. Uncheck the box next to the value Technical
Documentation, and check the box next to the value Marketing. Then confirm by clicking
OK.

2-5
2013 SDL plc.
3.
Click inside TU number 4 and repeat the above step. Note that changing the field value for
the next TU also changes the background color of this TU.
Deleting TUs
Let us assume that you want to delete TU number 6, i.e. Faster, more powerful and compatible with Microsoft
Word 2007. To do this take the following steps:
1.
Click inside TU 6. Then click the right mouse button and select Mark TU for Deletion from the
context menu.
2.
Note that the background color for the TU has changed, and a Deleted icon has appeared
next to the source segment.
Committing Pending Changes

Note that at this point all changes you made (i.e. editing and deleting) are not active yet. To make the
changes to all edited/deleted TUs final, click take the following steps:
1.
Click the Commit Changes button.
2.
A message box appears prompting you to confirm the changes. Click Yes to proceed.
NOTE
Committed changes cannot be undone.
Note that after committing the changes the original background color has been restored and the Edited
icons next to the modified TUs have disappeared.
FOR MORE INFORMATION

Editing and Deleting Translation Units
2-6
2013 SDL plc.
Global Find and Replace

Let us assume you want to run a find/replace operation in the TM. For example, you need to replace the
word dictionary with spelling dictionary in all source segments.
Find/replace operations can be necessary if, for example, the styleguides or other documentation
guidelines in your organization have changed.
To perform the find/replace operation take the following steps:
1.
Click the Replace button (or press Ctrl+H).
2.
This will open the Find and Replace dialog box. Here, do the following: enter the search
term, i.e. dictionary into the Find what text field. Then enter spelling dictionary into the
Replace with text field.
3.
To make sure the find/replace operation is done in the source segments, select the Source
radio button. Also check the option Match case to make certain that the find/replace
operation is case-sensitive.
TIP
In a real-life scenario you may have to run two find/replace operations, i.e. one for lower-case search
terms and another one for upper-case variants, as the search term might also occur at the beginning
of a segment, which means that the initial letter would be in upper case.

2-7
2013 SDL plc.
2-8
4.
Click the Find Next button. This will highlight the first occurrence of the search term in the
TM.
5.
Click the Replace button to replace the search expression. This will jump to the next
occurrence.
6.
You could now click Replace again to repeat this procedure and confirm the replace
operation for each occurrence of your search term. However, let us assume that you are sure
that you want to run the find/replace on the whole TM. Therefore, click the Replace All
button.
7.
Note that the changes are again not immediately applied to the TM. Each TU on which the
find/replace has been carried out has been highlighted with a changed background color
and an Edited icon has appeared next to each modified TU.
2013 SDL plc.
8.
To commit the changes to the TM click the Commit Changes toolbar button, and confirm by
clicking Yes.
Filtering for TUs that Contain a Particular Term

Let us assume that you want to display all TUs whose source segments contain the term spelling dictionary.
This can be useful, for example, if you want to verify the TUs that were modified by our find/replace
operation. To do this take the following steps:
1.
Enter the term spelling dictionary into the Source Text field above the side-by-side TU list. Then click
the Perform Search button.
2.
This filters the TU list, so that only TUs that contain your source text string are displayed.
This allows you to verify these TUs more easily and make changes if required.
3.
Now remove the search string from the Source Text field. Then click the Perform Search
button again. This will show the full list of TUs again.
Defining a Filter
In the above example you learned how to quickly show all TUs that contain a particular string. Let us
assume that you want to view only TUs that have the Subject field value Hardware. To do this take the
following steps:
1.
Click the Add Filter button.

2-9
2013 SDL plc.
2-10
2.
Enter a descriptive name for your filter into the Filter Name text field, e.g. Hardware only.
3.
To define the actual filter condition click the Add button. This will open the Add Condition
dialog box.
4.
In the Add Condition dialog box click the check box next to the value Hardware, then
confirm by clicking OK.
5.
You can now verify the condition in the Condition column, i.e. Subject=Hardware.
6.
Click the Save Filter button to save the newly defined filter.
2013 SDL plc.
7.
Now click the Perform Search button, which will display the TUs that match your filter.
Note that now the list only contains TUs with the Subject value Hardware. The field values are shown on
the right-hand side of the TU list.

Working with Filters in the TM View
PERFORMING BATCH OPERATIONS

In the previous sections you learned how to edit particular TUs. Sometimes you may have to edit a large
number of TUs. For this reason SDL Trados Studio 2014 supports batch edit operations, which allows you
to make changes to a number of TUs with a single click.
Batch Editing Specific TUs

Take the following example:
Take a look at the filtered TU list: the TUs with the Subject value Hardware do not have a Type field value.
Let us assume that you would like to apply the field value Type = Technical Documentation to each TU
that matches our previously defined filter. To do this take the following steps:
1.
Click the Batch Edit button. This opens the Batch Edit dialog box.

2-11
2013 SDL plc.
2-12
2.
In the Batch Edit dialog box select the previously-defined filter, i.e. Hardware only from the
Filter dropdown list.
3.
Then click Add -> Change Field Value. This opens the Edit Action dialog box.
4.
In the Edit Action dialog box select Type from the Field dropdown list.
5.
Then select Add from the Change mode dropdown list.
6.
Finally, activate the box next to the Technical Documentation value and confirm by clicking
OK.
2013 SDL plc.
7.
Now you are back in the Batch Edit dialog box. Click Finish to run the batch edit operation.
After the batch operation is complete, click Close.
8.
Note the specified field value has been added to each TU that matches the specified filter.
How to Batch Edit Translation Units
Batch Deleting Specific TUs

You can also carry out batch delete operations to delete a specific set of TUs from your TM. You can do
this to keep your TM lean and efficient by deleting TUs that are no longer needed. The first step is to define
a filter that matches the TUs that you want to delete, e.g.:
C
TUs that were created before a specific date (i.e. to get rid of potentially outdated content)
TUs with segments that only have one or two characters
TUs that contain only a hyperlink or an e-mail address
Example 1: Deleting very Short TUs

In the following exercise we would like to delete very small TUs, i.e. TUs with source segments that
contain less than three characters, e.g. ZN, A, B, C, etc.
Defining the Filter

To do this we first need to define a filter that singles out TUs with segments smaller than three characters.
To do this take the following steps:

2-13
2013 SDL plc.
2-14
1.
2.
Enter a name for your filter, e.g. Short segments.
3.
To define the filter condition click the Add button. This will open the Add Condition dialog
box.
4.
In the Add Condition dialog box select Source segment length from the Field dropdown list.
5.
In the Operator dropdown list change the operator to Smaller than.
6.
Then enter 3 into the Value text field, and confirm by clicking OK.
7.
The filter condition should now be: Source segment length < 3
8.
Click the Save Filter button to save the newly defined filter.
2013 SDL plc.
9.
Check whether your filter actually works. To do this click the Perform Search button. Now
only the TUs with segments such as A, B, ZH, etc. should be listed.
Running the Batch Delete Operation

Now that we have defined the filter we run the actual batch delete operation. Take the following steps:
1.
Click the Batch Delete button. This opens the Batch Delete dialog box.
2.
The Batch Delete dialog box shows all the filters you have defined and saved so far. Select the
newly defined Short segments filter and then click Finish to run the batch delete operation.
3.
After the batch delete operation has finished, click Close to close the Batch Delete dialog box.

2-15
2013 SDL plc.
4.
From the TM Filter dropdown list select <no filter>, and then click the Perform Search
button to show all TUs again.
Example 2: Deleting all TUs that Contain only a Hyperlink or an E-Mail Address
Let us assume that you want to remove all TUs that are contain only a hyperlink or an e-mail address.
To keep this exercise simple, we are going to proceed on the following assumptions:
C
All TUs with source segments that contain http:// match the hyperlink criterion
All TUs that contain .com AND the @ character match the e-mail criterion
NOTE
The above assumptions are true for our sample TM, but they may not apply to your TM in a real-life
scenario.
Defining the Filter

To define the filter take the following steps:
2-16
1.
2.
Enter a name for your filter, e.g. Hyperlinks and e-mail addresses.
3.
To define the filter condition click the Add button. This will open the Add Condition dialog
box.
4.
In the Add Condition dialog box select Source segment from the Field dropdown list.
5.
Change the Operator of the filter to Contains.
2013 SDL plc.
6.
Then enter http:// into the Value text field, and confirm by clicking OK.
7.
The filter condition should now look be: Source segment CONTAINS http://
8.
Now we need to define the e-mail criterion. Click the Add button again.
9.
In the Add Condition dialog box select Source segment from the Field dropdown list.
Change the Operator of the filter to Contains. Finally, enter .com into the Value text field, and
confirm with OK.
10. Repeat the above step, but this time enter @ into the Value text field. Your filter criteria list
should now look as shown below:
11.
The above filter is not yet correct, as it currently joins all conditions with an AND statement.
Therefore, click inside the first AND and change it to OR.
12.
Click the Save Filter button to save the filter.
13.
Check whether your filter works click the Perform Search button.

2-17
2013 SDL plc.
14.
Now only the following TUs should be listed:
Running the Batch Delete Operation

Now that we have defined the filter we run the actual batch delete operation. Take the following steps:
1.
Click the Batch Delete button. This opens the Batch Delete dialog box.
2.
In the Batch Delete dialog box you will see all the filters you have defined and saved so far.
Select the newly defined Hyperlinks and e-mail addresses filter and then click Finish to run the
batch delete operation.
3.
After the batch delete operation has finished, click Close to close the Batch Delete dialog box.
4.
From the TM Filter dropdown list select <no filter> and the click the Perform Search button
to show all TUs again.
SEARCHING FOR POTENTIAL DUPLICATES

The previous exercises provided examples of how to maintain your TM to keep it lean efficient and clutterfree.
Duplicate (or potential duplicate) TUs can also make your TM cumbersome to use. Potential duplicates
are defined as TUs that have the same source segment and different target segments. Such TUs might not
always be redundant, as some source segments require different translations depending on the context.
2-18
2013 SDL plc.
This is why SDL Trados Studio 2014 refers to these TUs only as potential duplicates. The application
offers an easy way of filtering for potential duplicate TUs. To scan your TM for potential duplicates take
the following steps:
1.
From the Search Type dropdown list select Search in potential duplicates only.
2.
Then click the Perform Search button. This will show the first potential duplicates set in the
list.
3.
Here you can see an example of two TUs with the same source segment, but with different
translations. Let us assume that you want to delete the first TU. Highlight the first TU, click
the right mouse button and then select the Mark TU for Deletion command from the
context menu.
4.
Now that the first TU has been marked for deletion click the Next Page button to view the
next potential duplicate set.
5.
Repeat step 3 to mark the first TU for deletion, then browse to the next duplicate set.
6.
Let us assume that you want to keep the different translations for the source segment
Language Support. Therefore just click the Next Page button. This time a message is shown
to inform you that no more potential duplicates have been found in the TM.

2-19
2013 SDL plc.
7.
To remove the TUs that you marked for deletion so far click the Commit Changes button
and then confirm by clicking Yes.
Now that you have finished cleaning up your TM set the Search Type back to the default Search entire TM
and click the Perform Search button to reset the TU list.
EXPORTING AND IMPORTING TM CONTENT

Example of use cases for TM exports are:
C
Backing up TMs to external files
Running a filtered export to create a new TM, which is a subset of the original TM (e.g. only TUs
related to a particular customer or subject)
Running a filtered export to provide another user with a subset of your TM
Exporting a Subset of a TM
Let us assume that you would like to export only TUs that have the Subject value Software:
1.
2-20
Click the Export button. This opens the Export dialog box.
2013 SDL plc.
2.
In the Export dialog box click Browse to select a name (e.g. Software.tmx) and a location for
your export file, e.g. your desktop.
3.
As mentioned above, let us assume that you do not want to export the entire TM, but only a
subset, e.g. all TUs related to Software. To define a filter for your export click the Edit button.
4.
In the Filter dialog box click the Add button. This opens the Add Condition dialog box.

2-21
2013 SDL plc.
5.
Note that the Subject field is already selected in the Add Condition dialog box. Click the
check box next to the Software value, and confirm by clicking OK.
6.
Click OK again to close the Filter dialog box, then click Finish to run the export.
7.
When the export is complete click Close. You can now find the export TMX file in the
previously specified location, e.g. on your desktop.
NOTE
SDL Trados Studio 2014 exports TM data in TMX (i.e. Translation Memory eXchange) format. For
more details on this format you may refer to Wikipedia.

How to Export Translation Memory Data
Importing a TMX File into a TM

Let us assume that you want to import the TMX export file into a new TM.
Creating a New TM
First, you need to create an empty TM by taking the following steps:
2-22
2013 SDL plc.
1.
Click the New button, and then select New Translation Memory.
2.
In the New Translation Memory dialog box enter the name for your TM into the Name field,
e.g. Software English-German.
3.
Click the Browse button and select a location for your TM that you can find easily later, e.g.
your desktop.
4.
Make sure that you select the language pair that matches the import file, i.e. English (United
States) -> German (Germany). Then click Finish.
5.
When the TM has been created click Close. The newly created TM should now be listed
under the first TM.
Importing the TMX File

To import the TMX file into the newly created TM take the following steps:

2-23
2013 SDL plc.
2-24
1.
Right-click the TM and select Import from the context menu. This opens the Import Files dialog
box.
2.
In the Import Files dialog box click the Add Files button and browse for the TMX export file.
Select the file (Software.tmx) by double-clicking it. When the file is shown in the dialog box
click Next to proceed.
3.
On the following screen click Next again, then click Finish to start the import.
4.
When the import has finished, click Close. The TUs of your new TM should now be shown
in the list.
2013 SDL plc.
SUMMARY
C
You can open a TM in the Translation Memories view. This will show the first 50 translation units
(TUs) in a list.
Source and/or target segments can be modified by editing the text. The corresponding TU will then
be highlighted. The changes will only be applied when you commit them by clicking the
corresponding button.
You can also change the values of TM fields (if available)
TUs can be marked for deletion. Deletions need to be committed and cannot be undone afterwards.
You can run find/replace operations on the entire TM, e.g. to replace outdated terms.
To view only TUs that correspond to certain criteria, you can define and apply filters.
You can run batch edit operations on a specific subset of a TM, e.g. add or change field values.
In the same way you can also batch delete several TUs, e.g. all TUs that have source segments that
have only one or two characters.
SDL Trados Studio 2014 offers a special type of search that allows you to single out potential
duplicates, which helps you keep your TM lean and efficient.
TM exports generate TMX files, and can be based on a filer to export only a specific subset of a TM.

2-25
2013 SDL plc.
L A N G U A G E R ES O URC E S
In this chapter you will learn how to:

C
Add abbreviations to a TM to customize the

segmentation
Add product names to your TM, so that these names are

recognized as placeable elements rather than normal
text
Chapter
Language Resources
WHAT ARE LANGUAGE RESOURCES?

A TM can be set up with, for example, custom segmentation rules, variable lists, abbreviations, etc. The
collective term for these elements is language resources.
Upon creation every TM is set up with default languages resources, i.e. default segmentation rules and a
default list of abbreviations that are common for the selected source language.
In this chapter we will focus on abbreviations and so-called variable lists. Variables are strings that are
treated as placeables during translation. This allows you to easily place them into your target segments,
for example product names (Windows Vista Business Edition, Microsoft SQL Server 2008, ...) and other
strings that are typically not translated.

About Language Resources
EDITING THE LANGUAGE RESOURCES OF A TM

In the following sections you will learn how to view and customize the language resources of a selected
TM.
Viewing the Language Resources

To view the language resources of the TM that you created in the previous chapter take the following steps:
3-2
1.
Make sure that you are still in the Translation Memories view and that you see your newly created
TM. Right-click the TM and select the Settings command from the context menu.
2.
In the Translation Memory Settings dialog box click Language Resources. This will show the
language resource types on the right-hand side, i.e. Variable List, Abbreviation List, etc.
2013 SDL plc.
Language Resources
Adding a Custom Abbreviation

1.
Double click Abbreviation List to open the list of abbreviations. Each TM contains a pre-defined list
of abbreviations that are commonly used in the source language of the TM. This ensures that, for
example, the dot after e.g. is not considered a full stop, which would split the segment in the middle.
In the Abbreviations dialog box you can view the default list of abbreviations:
2.
Let us assume that you want to add an abbreviation that is not in the default list: org. (for
organization). Scroll to the end of the list, double-click the last, empty line, and enter the
abbreviation, i.e. org.
NOTE
The abbreviation list is case-sensitive. Enter your custom abbreviations exactly as they occur in your
documents including the dot at the end.

3-3
2013 SDL plc.
Language Resources
3.
Click OK to confirm and close the Abbreviations dialog box. You should now be back in the
Translation Memory Settings dialog box. Note that the Abbreviation type is highlighted in
bold. This indicates that this language resource type has been changed, i.e. it is no longer
just the default list.
Defining a Variable List

The variable list is another language resource type. The variable list is always empty by default, i.e. you
need to add your own variables. Variables can be, for example, product names. If you enter a product name
into the variable list, the corresponding string will be treated as a placeable element. This means that
during translation you can easily insert the product name by pressing Ctrl+, instead of typing it manually.
This is especially useful for long product names, e.g. Microsoft Windows Server 2008. Whats more:
variables can be exchanged automatically by the TM, similar to the automatic number substitution.
To add variables to the list take the following steps:
3-4
1.
Double-click the Variable List type to open the Variables dialog box.
2.
In the Variables dialog box, double-click the (empty) gray line and enter the string Mac OSX.
2013 SDL plc.
Language Resources
3.
Note that this has added another empty gray line below your first variable. Repeat the above
step to add two further variables: Microsoft Windows XP Professional and Suse Linux.
4.
Then close the Variables dialog box by clicking OK.
TIP
You can press the Tab or Enter key to move to the next line.
5.
Click OK again to close the Translation Memory Settings dialog box.

About Variables

Translation Memory Settings
USING VARIABLES DURING TRANSLATION

Now that you have finished editing the language resource settings for this particular TM, we will see how
our customized language resources work during translation.
Open the following document from your sample files folder, i.e. ..\Sample Files\02_Language_Resources for
translation. To do this take the following steps:
1.
Press Ctrl+Shift+O to open a single document for translation, and then select the file Sample.docx
from the sample files folder by double-clicking it.
2.
In the Open Document dialog box make sure English (United States) is selected as your
source language.
3.
Then select your target language from the Target Language dropdown list. Note that the
target language must be the same as the one for the TM that created in the previous chapter.
4.
If there is any TM selected from another exercise in this dialog box, highlight it and click
Remove to remove it.
5.
Select the previously created TM by clicking Add -> File-based Translation Memory. Browse
to the location in which you created the new TM and select the TM file by double-clicking it.
6.
Click OK to open the document in the Editor view.

3-5
2013 SDL plc.
Language Resources
7.
Note that the first segment contains your newly added abbreviation (org). As you have added
this abbreviation to your list, it has been properly recognized, and consequently the TM did
not split the segment after the abbreviation org. Translate this segment and confirm it by
pressing Ctrl+Enter to move to the next segment.
8.
Note that the string Mac OSX has a blue underline. This means that it has been recognized
as a placeable, because it is part of your variables list. Translate the first segment and use the
Ctrl+, keyboard shortcut to insert the product name into your translation.
9.
Confirm your translation with Ctrl+Enter. After confirming your translation is autopropagated to the two following segments. Note that the product names have been replaced
automatically by the TM, as these have also been defined as variables.
10. Now you can confirm the two auto-propagated segments, save the document (Ctrl+S) and
close it (Ctrl+F4).
SUMMARY
3-6
Each TM has built-in language resources, which are comprised of e.g. abbreviation lists and
segmentation rules.
Each TM has a default list of abbreviations that are commonly used in the respective source
language. This prevents the TM from treating the dot after abbreviations (e.g. etc.) as a full stop,
thereby splitting segments in the middle.
The language resources can be customized. For example, you can add custom abbreviations to finetune the segmentation rules of your TM.
You can also enter variables into the variables list, which is by default empty. Variables can be, for
example, product names. During translation variables are treated as placeable elements. This
means that they can be easily inserted into the target segment. Moreover, they can be automatically
replaced similar to the automatic number substitution.
2013 SDL plc.
T R A N S LA TI O N M EMORY FIE L DS
This chapter provides an example of how to use translation

memory fields (TM fields). You will learn how to:
C
Add user-definable fields to a TM
Apply field values to translation units during translation
Filter for translation units with a particular field value
Chapter
Translation Memory Fields
WHAT ARE TM FIELDS?

A TM stores source segments and their translation as so-called translation units (TUs). For each TU the
TM automatically stores information such as the name of the user who translated a segment as well as the
creation/modification date and time.
Apart from that you can also store additional information in user-definable fields. Example: if you want to
know for which customer a particular segment was translated, you can add a Client field to your TM. This
allows you to track the client for whom a particular segment was translated. This can be useful when, for
example, client A requires different translations than client B.
In the following exercises you are going to translate two short sample documents for the fictitious clients
A and B. For the following exercise use the sample files stored in ..\Sample Files\03_TM_Fields.

About Translation Memory Fields
CREATING A TM WITH FIELDS

In the following section you will learn how to create a TM and add two fields to it, i.e. Client and Project Id.
This allows you to track for which client and which project a segment has been translated.
Creating a New TM
Start by creating an empty TM. To do this take the following steps:
1.
Click the New button, and then select New Translation Memory.
2.
In the New Translation Memory dialog box enter the name for your TM into the Name field,
e.g. Sample TM Fields English-German.
3.
Click the Browse button and select a location for your TM that you can find easily later, e.g.
your desktop.
4.
Make sure that English (United States) is selected as source language. You can pick any
target language, e.g. German (Germany).
5.
Then click Next.
Defining the TM Fields

On the Fields and Settings page you define the fields for your new TM.
4-2
2013 SDL plc.
Adding the Client List Field

First, you add the Client field, which is going to be associated with pre-defined list of clients. To do this
take the following steps:
1.
Click inside the empty gray field in the Name column and enter the field name, i.e. Client.
2.
Click the empty gray field in the Type column. This opens a list of available data types. Since
you want to create a pre-defined list of values for this field, select the type List.
TIP
As a rule of thumb you can say that the list data type is preferable for fields that should be associated
with a limited number of values. The text data type is recommended for fields that contain free text
information, i.e. where a virtually limitless number of values is conceivable.
3.
A list field needs to be associated with at least one list value. Click the empty gray field in the
Picklist column, then click the small black arrow icon. This opens an empty list in which you
enter the clients. Enter Client A as your first value.

4-3
2013 SDL plc.
4.
Then press Enter to move to the next line and type Client B.
5.
After you have entered the clients click OK to close the list.
6.
Let us assume that it should be possible to add more than one client to a TU. This usually
makes sense, as the same translation may be used for different clients. Therefore, active the
check box in the Allow Multiple Values column.
Adding the Project Id Text Field

Let us assume that you also want to store a project id with each TU. The project id should be a free text
field, as there can be a virtually limitless number of project ids. To add the Project Id text field take the
following steps:
4-4
1.
Click inside the empty gray field below the Client field name and type Project Id.
2.
In the Type column select Text from the list of available data types.
3.
Make sure to select the option Allow Multiple Values for the Project Id field.
4.
Click Finish and then Close, when the progress bar indicates that the TM has been created.
5.
Note that the new TM is now listed in the Translation Memories view.
2013 SDL plc.

Translation Memory Settings Dialog Box: Fields and Settings
USING TM FIELDS DURING TRANSLATION

Now that you have learned how to set up a TM with custom fields, let us take a look at how those fields
can be filled with values during translation.
Opening the Sample Document

To open the sample document for this exercise take the following steps:
1.
Press Ctrl+Shift+O to open a single document for translation, and then select the file Client_A.docx
from the sample files folder (i.e. ..\Sample Files\03_TM_Fields) by double-clicking it.
2.
In the Open Document dialog box make sure English (United States) is selected as the
source language.
3.
Then select the target language of the TM that you created in one of the previous chapters,
e.g. German (Germany).
4.
Make sure that no TMs from previous exercises are selected. If this is the case, remove them
by clicking the Remove button.
5.
Then add the TM that you created in the previous section by clicking Add -> File-based
Translation Memory.
6.
Browse for the TM file and select it by double-clicking it.

4-5
2013 SDL plc.
7.
Click OK to open the document in the Editor view.
Selecting the Field Values

Now that the document has been opened, you need to select the field values before you start the
translation. To do this take the following steps:
4-6
1.
Click the Project Settings button.
2.
In the Project Settings dialog box click Language Pairs -> All Language Pairs -> Translation
Memory and Automated Translation -> Update.
2013 SDL plc.
3.
On the right-hand side of the dialog box, you will see the two fields that you defined
previously. Click inside the Value cell next to the Client field to open the list of pre-defined
values. Select Client A from the list by clicking the check box next to it.
4.
Go to the next row to enter a Project id value. Remember that this is a free text field,
therefore no pre-defined values are available. Click inside the Value column next to the
Project Id field. This will open a field in which you enter the project id 2011_001. Then click
OK to confirm.
5.
Close the Project Settings dialog box with OK.
6.
In the Open Document dialog box click OK again to open the sample document in the Editor
view.
Applying Fields Values During Translation

Note that every segment you translate and store in the TM from now on will be associated with the two
selected field values. Take the following steps:
1.
Translate and confirm the first three segments in the document. When you get to segment 4, you
will get a high fuzzy match from the TM, as it is very similar to segment 3:
2.
Take a look at the Translation Results window. Note the information displayed next to the
target segment from the TM. It shows the field values that are associated with this TU. As
mentioned previously, the selected field values are stored with each translation that you
create.
3.
Modify the suggested translation so that it fits the current context, and confirm it by
pressing Ctrl+Enter.
4.
Translate the last segment, and confirm it too. Save the file by pressing Ctrl+S, then close it
with Ctrl+F4.

4-7
2013 SDL plc.

Translation Memory and Automated Translation > Update
Filtering TUs Based on TM Field Values

The field values that are added to TUs provide criteria for filtering within a TM. Filters are a good way of
making translators aware of the fact that a TM match that is offered might not fit the current context, as
the target segment was created, for example, for another client, project, etc.
The following exercise shows an example of how to use so-called filter penalties during translation.
Imagine that you need to translate a similar document for Client B.
Selecting Different Field Values

First, we are going to open the second document and change the TM field values. To do this take the
following steps:
4-8
1.
Open the sample document Client_B.docx, which is located in the same folder as the previous
document.
2.
In the Open Document dialog box make sure that the same language pair and TM are
selected as before. Then click OK to open the document in the Editor view.
3.
Now that the document has been opened, you need to select the field values for the current
document before you start the translation. To do this click the Project Settings button.
4.
In the Project Settings dialog box click Language Pairs -> All Language Pairs -> Translation
Memory and Automated Translation -> Update.
5.
Now select Client B from the Client list.
6.
As Project Id enter 2011_002.
2013 SDL plc.
7.
The selected values should look as shown below. Note that every translation that you create
from now on will be associated with this new set of values.
Setting a Filter Penalty

In addition to applying field values, we will also define a filter penalty. This does not mean that we will not
be offered any TUs that are associated with Client A. However, TUs that are associated with a client other
than Client B will have a slightly reduced match value, i.e. they will be penalized.
1.
Click the Filters link to display the filter options on the right-hand side of the dialog box.
2.
In the section Filter Penalties click the Add button.
3.
This opens the Add Filter dialog box. Enter a name for your filter into the Name text field,
e.g. ClientB. Then click the Add button.
NOTE
Spaces are not allowed in filter names.

4-9
2013 SDL plc.
4.
This opens the Add Condition dialog box. Click the check box next to Client B. Then confirm
by clicking OK.
5.
Click OK again to close the Add Filter dialog box.
6.
Your filter should now look as shown below. From now on each TM match that does NOT
have the field value Client B will receive a penalty of 1%. This means that, for example, a
100% match from another client will be reduced to 99%.
7.
Click OK to close the Project Settings dialog box, and then click OK again to confirm the
project settings.
Translating a Document with a Filter Penalty

Start translating the document, which is very similar to the one from the previous exercise. Take the
following steps:
4-10
1.
Translate and confirm the first segment.
2.
When you get to segment 2 you will get a high fuzzy match (99%), although this segment is
100% identical to a segment that you translated in the previous document (Client A). The
TM match has been reduced to a 99% match, because it does not match our filter. Take a
look at the TU that is shown in the Translation Results window:
2013 SDL plc.
3.
The filter gives preference to TUs with the value Client B, but the current TM match is
associated with Client A. Move the mouse pointer over the filter icon in the Translation
Results window. A tooltip shows that a penalty of 1% was applied, as the TU from the TM
does not match your filter.
4.
Filter penalties are used to alert translators to the fact that they might have to change the
suggested translation to fit the current context. However, let us assume that for this segment
it does not matter that the translation was done for a different client, i.e. the translation
created for Client A is also valid for Client B. Confirm the segment by pressing Ctrl+Enter
5.
Repeat the above steps for segments 3 and 4.
6.
Now that you have accepted the translations, you might wonder what has happened to the
field values associated with these TUs. Use the Up key on your keyboard to move back to
segment 4. Take a look at the information in the Translation Results window. Note that for
this TU both client and project id values have been stored, i.e. 2011_001, 2011_002 and Client
A, Client B.
NOTE
Storing multiple values is only possible if the fields have been configured to allow multiple values. If
multiple values are not allowed, previous values will be overwritten by the currently selected values.
7.
Use the Down key to move to segment 5. Let us assume that this time you cannot just accept
the match that has been suggested by the TM, as Client B requires a different translation.
Overwrite the suggested translation with another one.
8.
Before you commit the new translation to the TM consider the following: if you confirm the
translation by pressing Ctrl+Enter, you will overwrite the existing translation. Let us assume
that you want to make sure that BOTH translations get stored in the TM, as they are both
correct. To do this click the Add as New Translation button on the Advanced tab.

4-11
2013 SDL plc.
9.
Take a look at the Translation Results window: note that this time two different TUs have
been stored, one for Client A / Project Id 2011_001 and another one for Client B / Project Id
2011_002. Now you have two different TUs for two different clients (and projects).
NOTE
You can use the Add as New Translation button on the Advanced tab whenever you want to store a
separate TU with an alternative translation for the same source segment, regardless of whether you
use TM fields or not.
10. Confirm the last segment. Save the file with Ctrl+S and then close it with Ctrl+F4.

Filters
SUMMARY
4-12
When configuring a TM you can add user-definable fields to store meta information with each TU,
e.g. client, project, subject, etc.
TM fields can be associated with picklists. You will use the list data type for fields for which you
expect to have only a limited number of possible values, e.g. a few dozen customers.
TM fields can also be free text fields. You will use the text data type for fields for which you expect a
very large number of possible values, e.g. project ids. In the course of a year a company might have
thousands of projects with different ids.
When you select the field values before opening a document or before creating a project, these
values will be added to each TU that is created during translation.
You can set filter penalties to penalize TM matches that do not have a particular field value. Such
TUs will be shown, but the match value will be reduced, so that the translator notices that the
suggested translation might require changes to fit the requirements of the current context.
If you confirm a translation, the new field values will be added to the existing values (provided that
the fields allow multiple values).
If you choose to change the suggested translation and add it as a new TU to the TM, you will end up
having multiple TUs, each with its specific set of field values.
2013 SDL plc.
T M S EA R CH O P TI ONS AND
P E N A L TI ES
In this chapter you will learn the how to:
C
Change the minimum match value to find TU matches

that would otherwise not be offered
Configure the different kinds of penalties that can be

applied during translation
Chapter
TM Search Options and Penalties
ABOUT TM SEARCH OPTIONS AND PENALTIES

When searching in a TM the default minimum match value used is 70%. This means that any matches
lower than 70% will not be offered during translation, file analysis, etc. However, you can change the
minimum match value as required. For example, if you have the impression that you are not getting
enough matches from the TM, you might want to lower the minimum match value.
In the previous chapter you have seen how penalties work, in particular the filter penalty. Penalties are
used to penalize TM matches for not meeting certain criteria such as filters, missing formatting etc. SDL
Trados Studio 2014 has a number of penalties set by default such as the missing formatting penalty, which
reduces matches by 1% when character formatting such as bold, italics etc. is missing in the suggested TM
match.
In the following exercise you will learn how to change TM search and penalty settings.
MODIFYING TM SEARCH OPTIONS AND PENALTIES

Opening the Sample Document
To open the sample document for this exercise take the following steps:
1.
Press Ctrl+Shift+O to open a single document for translation, and then select the file Sample.docx
from the sample files folder (i.e. ..\Sample Files\04_TM_Options) by double-clicking it.
2.
In the Open Document dialog box make sure English (United States) is selected as the
source language.
3.
Then make sure that the target language, i.e. German (Germany) and the TM from the
previous exercise are used.
Editing the TM Language Resources

Before we start translating let us make a change to the TM language resources. In one of the previous
chapters you learned how to add variables to a TM. You can also do this directly when opening a document
by taking the following steps:
5-2
2013 SDL plc.
1.
Highlight the TM name and then click the Settings button.
2.
In the Translation Memory Settings dialog box click Language Resources, then double-click
Variables.
3.
In the Variables dialog box add the two values: Gerhard Schrder and Angela Merkel. Then
confirm by clicking OK.

5-3
2013 SDL plc.
4.
Click OK again to close the Translation Memory Settings dialog box.
5.
Finally, click OK to open the document in the Editor view.
Changing the Minimum Match Value

Now that the document is open note the following: for the first segment no match has been found. You
might remember that you translated a similar segment in the previous chapter, however, no match is
being offered for this segment. There is indeed a match in the TM, but it has a very low match value, i.e.
it is below the default 70%.
To lower the minimum match value take the following steps:
1.
Click the Project Settings button on the Home tab.
2.
In the Project Settings dialog box select Language Pairs -> All Language Pairs -> Translation
Memory and Automated Translation -> Search.
3.
Change the Minimum match value from 70 to 50 by entering the value into the text box.
NOTE
The minimum match value can be set to any value between 30 and 100.
5-4
4.
Confirm the change with OK.
5.
Now you should be getting a low fuzzy match, i.e. a match below the default fuzzy threshold.
This can happen especially when translating short segments, as one or two differences have
a bigger impact on the match value than in longer segments.
6.
Adapt the suggested translation as required and confirm it with Ctrl+Enter.
2013 SDL plc.
The Formatting Penalty

For the next segment you get a 99% match, as the suggested target segment is lacking bold character
formatting:
By default, the TM applies a penalty of 1% for each formatting difference. Just take the following steps:
1.
Apply bold formatting to the target term (Ordner), e.g. by selecting the word and by pressing Ctrl+B.
2.
Confirm the modified translation by pressing Ctrl+Enter.
The Auto-Localization Penalty

The next two segments are almost identical except for the number difference. Take the following steps:
1.
Translate segment 3, but do NOT confirm it yet.
NOTE
If you confirmed the segment right now, your translation will be auto-propagated to the following
segment, and the number will be automatically replaced and auto-localized. You can see that in the
above example this could lead to problems, as segment 4 requires a different translation. This is due
to the fact that the English word aircraft requires different translations for the singular and plural
form. To alert translators to such potential issues, you can set an auto-localization penalty. This
prevents users from just accepting auto-localized segments, which would normally be presented as
100% matches. The auto-localization penalty is by default zero, i.e. it is inactive.
2.
To set the auto-localization penalty click the Project Settings button again.
3.
Memory and Automated Translation -> Penalties.

5-5
2013 SDL plc.
5-6
4.
Change the Auto-localization penalty from 0 to 1 by entering the value into the text box.
5.
Confirm the change by clicking OK.
6.
Now confirm segment 3 by pressing Ctrl+Enter. Note that the number in segment 4 has
been automatically replaced and auto-localized. However, the translation is not presented as
an exact match, but as a 99% match. This is due to the auto-localization penalty that you
have set in the previous steps. In the Translation Results window the TM match is marked
with a blue underline, which signals that an auto-localization penalty has been applied.
7.
In this case the penalty is justified, as the translation really needs to be changed. For
example, in German the plural form for aircraft is Flugzeuge. Therefore, change the
translation as required.
8.
Now you need to pay attention in order to NOT confirm the modified segment, as this would
overwrite the first translation in the TM, i.e. the singular form. Instead, use the Add as New
Translation button, so that you keep both the translation with the singular and with the
plural form in the TM:
9.
Now confirm the segment by pressing Ctrl+Enter.
2013 SDL plc.
The Text Replacement Penalty

There is another, very similar type of penalty that can be applied to alert you to potential issues caused by
automatic replacement of strings in a segment. An example of this can be found in segments 5 and 6. Take
the following steps:
1.
Translate segment 5, but do NOT confirm it yet. Note that the name of the German chancellor is a
placeable, as you previously defined his name as a variable in the TM.
NOTE
If you confirmed the segment right now, your translation will be auto-propagated to the following
segment, and the name of the chancellor will be automatically replaced, as both names are in the
variable list of the TM. Because of the difference between male and female form required by the target
language, the TM should not offer a 100% match for the following segment, but apply a text
replacement penalty. The text replacement penalty is zero by default, i.e. it is inactive.
2.
To set the text replacement penalty click Project Settings button again.
3.
Memory and Automated Translation -> Penalties.
4.
Change the Text replacement penalty from 0 to 1 by entering the value into the text box.
5.
Confirm the change by clicking OK.
6.
Now confirm segment 5 by pressing Ctrl+Enter. Note that the name of the chancellor in
segment 6 has been automatically replaced. However, the translation is not presented as an
exact match, but as a 99% match. This is due to the text replacement penalty that you have
set in the previous steps. In the Translation Results window the TM match is marked with a
special icon to signal the text replacement penalty.
7.
Adapt the suggested translation to use the female form for chancellor (i.e. Kanzlerin).
8.
Now you need to pay attention in order to NOT confirm the modified segment, as this would
overwrite the first translation in the TM, i.e. the male form. Use the Add as New Translation
button, so that both the translation with the male and with the female form are stored in the
TM.
9.
Now confirm the segment by pressing Ctrl+Enter.
Multiple Translation Penalty

For the last segment you will get two 99% matches. This is because different translations have been found
for the same source segment. In this case a penalty of 1% will be applied. This penalty is active by default.

5-7
2013 SDL plc.
In the Translation Results window you see the following:
Each translation unit is marked with a green plus icon, which signals the multiple translations penalty.
Take the following steps:
1.
Let us assume that you prefer the second translation. To insert the second translation press Ctrl+2.
2.
Then press Ctrl+Enter to confirm.
3.
You can now save the document (Ctrl+S) and close it (Ctrl+F4).
NOTE
Changing settings such as the minimum match value or penalties through the Project Settings
button will only apply to the current project. If you want to change these settings globally (i.e. for all
upcoming project), you need to switch to the File tab, and then click Options.

Translation Memory Penalties
SUMMARY
5-8
By default the minimum match value is 70%. Any matches below this threshold will not be
recognized unless you lower this setting. The minimum match value can be set to any value
between 30 and 100. Lowering the value can make sense in particular for short segments in which
one small change can have a big impact on the TM leverage.
Some penalties are active by default, for example, the missing formatting or the multiple
translations penalty.
Other penalties are default by zero, i.e. inactive. One example is the auto-localization penalty. This
penalty can be useful when different translations are required, for example, when singular and
plural forms require different translations.
The text replacement penalty works the same way. It applies when variables are automatically
replaced in the target segment. In this case the penalty alerts the translator to the fact that different
variable strings might require you to make changes to the target segment.
2013 SDL plc.
T R A N S LA TI NG XML FIL E S

C
Define a custom file type for translating XML documents
Translate an XML document
Preview an XML file
Chapter
Translating XML Files
WHAT IS XML?
XML is the acronym for eXtensible Markup Language. XML is designed designed to describe and to store
content in a tagged format. Every organization can create their own type of XML with custom tags, which
can have custom names, for example:
<heading>Getting Started</heading>
The tags that a particular type of XML contains are specified in a so-called XML Schema (or XSD file). The
XSD file lists the tags and specifies the structure a document must adhere to in order to be considered a
valid XML document.

You may refer to Wikipedia for a more detailed definition of XML and XML Schemas.
In SDL Trados Studio 2014 you can open any type of XML, as the application is equipped with a generic
XML file type that allows you to process any type of XML. However, it is recommended that you create
custom file types for the XML documents that you need to translate.
NOTE
When processing XML documents, file types are the equivalent of the tag settings definitions (*.ini
files) in SDL Trados 2007. For detailed instructions on how to upgrade existing *.ini files to SDL
Trados Studio 2014, please refer to the Upgrade training workbook.
The sample file for the following exercise can be found in your sample files folder, e.g. ..\Sample
Files\05_XML.
OPENING AN XML DOCUMENT

SDL Trados Studio 2014 comes with a built-in file type that fits any XML document. When you open an
XML file for which no custom file type exists, the application will fall back to the Any XML file type. Open
the XML sample document from the sample files folder:
6-2
1.
Press Ctrl+Shift+O to open a single document for translation.
2.
Browse to your sample files folder and select Sample.xml by double-clicking the file.
3.
In the Open Document dialog box remove the TM that was used for the previous exercise by
highlighting the TM name and clicking the Remove button.
4.
Then click Add -> File-based Translation Memory, and select the sample TM that is located
in the same folder as the sample XML document (i.e. Sample_EN-US_DE-DE.sdltm).
5.
Then click OK to open the document in the Editor view, which will look as shown below:
2013 SDL plc
You could now, of course, translate this file just like any other document format. However, we would like
to show to you how to create a custom XML file type and then re-open the document with that file type. A
custom file type enables you to process custom XML files more efficiently.
Now try to generate a preview by taking the following steps:
1.
Try to generate a WYSIWYG preview. To do this switch to the File tab, then select Print and View ->
View In -> Web Browser (XML) as Target.
2.
This opens the document in your Web browser, which looks as shown below:
As you can see the browser shows the raw XML, which is not suitable for reading or printing. The preview
can be enhanced significantly by defining a custom file type that contains a stylesheet.
To sum it up, for our sample file we want to do the following:
C
Exclude untranslatable content: we want to exclude strings like PRN-1023-4350 from translation.
This means that these strings will not be offered for translation and will not be counted during file
analysis.
Show character formatting: all segments are shown in exactly the same format. The user experience
can be significantly improved if you applied character formatting, for example, to the strings that
are enclosed in the em tags (em here is short for emphasis). Moreover, you can further enhance the
user experience, for example, by displaying headings with a bigger font.
Show context information: the document structure column is empty, as the generic XML file type
does not know what information to display. To provide more information to translators and
reviewers on particular segments, we want to indicate whether a segment is, for example, a list item,
a subheading, etc.
Make attribute content translatable: Our XML sample file has translatable content stored inside socalled attributes, i.e. the caption attribute of the illustration tag. Such content is by default not offered
for translation. This is something that needs to be configured in a custom file type.
WYSIWYG preview: We want to add a stylesheet to generate document previews that can be used
for proofreading and printing.
Before we define the custom file type, close the document by pressing Ctrl+F4. (You do not need to save
the file.)
Creating an XML File Type

Now we are going to create our custom XML file type. After that we are going to open the file again based
on the new file type. Take the following steps:
Naming the XML File Type

1.
Switch to the File tab, and then click Options.
2.
On the left-hand side of the Options dialog box select File Types.

6-3
2013 SDL plc
6-4
3.
Click the New button in the top right corner of the dialog box.
4.
This opens the Select Type dialog box. Select XML, then click OK.
5.
In the Create File Type dialog box, enter a descriptive name for your custom XML file type
into the File type name text box, e.g. Training XML. Then click Next to proceed.
2013 SDL plc
Importing the Tag List

As mentioned above, each XML document type can contain its own custom set of tags. You could enter
each tag name manually in the Create File Type wizard. However, it is much easier to import the tags from
an existing file. This can be, for example, an XML schema (if available) or the actual XML file that you need
to translate. To do this take the following steps:
1.
On the XML Settings Import page select the option Define settings based on INI, ANL, XML, XSD
or ITS rule file. This will enable the Browse button, which you now need to click.
2.
Browse to the location of your sample XML file and select it by-double clicking. Then click
Next to proceed.

About Importing Parser Rules
NOTE
In this step we use the translatable XML file to generate the list of tags. It is recommended, however,
that you use the XSD (i.e. the XML schema file) if it is given to you by e.g. the customer or by the
documentation department.
TIP
If you used to process the same XML type in SDL Trados 2007 and have a tag settings definition (*.ini
file) available, you could also select the *.ini file in this step, thus upgrading your legacy tag settings
file to an SDL Trados Studio 2014 file type.

6-5
2013 SDL plc
3.
The Parser Rules page lists the tags found in the XML file that you selected in the previous
step. By default, it is assumed that all tags contain translatable content. (See the Translatable
value in the Translate column.)

Parser Rules
Excluding Tag Content from Translation

When you open the XML sample file in a text editor (e.g. Notepad) you will see that the prodcode tag
contains the strings that are not supposed to be translated.
By default, however, each tag is assumed to have translatable content. To change this default setting,
thereby excluding the tag content from translation, take the following steps:
1.
6-6
Highlight the prodcode tag in the list, and then click the Edit button.
2013 SDL plc
2.
This opens the Edit Rule dialog box. From the Translate dropdown list select Not
translatable. Then confirm by clicking OK.
3.
Note that in the tag list the prodcode tag is now marked as Not translatable.
Defining Character Formatting for Tags

Let us take a look at the em and the contact tags. These are the only tags that are listed as inline tags. All
other tags are so-called structure tags. Inline tags can occur inside a segment, whereas structure tags
enclose segments, but are never found inside a segment.
If you open the XML sample file in a text editor, and take a look at the em tags, they will look as shown
below:
In our sample document em stands for emphasis. These tags enclose specific words within a segment,
thereby emphasizing them. Let us assume that you would like any strings enclosed within these tags to be
formatted in bold. This is strictly speaking not necessary and only constitutes a cosmetic enhancement.
However, it helps enhance the user experience a lot. To do this take the following steps:
1.
Highlight the em tag in the list, and then click the Edit button.

6-7
2013 SDL plc
6-8
2.
In the Edit Rule dialog box click the Edit button next to the Formatting field.
3.
In the Font Formatting dialog box select Activate from the Bold dropdown list. Note that in
the Sample field on the bottom of the dialog box you see a preview of what text enclosed in
em tags will look like in the Editor view.
2013 SDL plc
4.
Click OK to get back to the Edit Rule dialog box. Note that the formatting information that
you defined in the previous step is shown in the Formatting field (i.e. Bold=True). Click OK
to continue.
5.
You should now again see the tag list on the Parser Rules screen. Let us assume that you
would like to specify display formatting for the contact tag as well. Highlight the contact tag
in the list and click the Edit button.
6.
In the Edit Rule dialog box click the Edit button next to the Formatting field.
7.
In our sample document the contact tag is used to define e-mail addresses. For this reason it
should be displayed with the typical hyperlink formatting in the Editor view, i.e. blue and
underlined. Therefore, select Activate from the Underline dropdown list.

6-9
2013 SDL plc
8.
Then activate the Specify color check box, click the Edit button and select the blue color from
the color palette. The Font Formatting dialog box should look as shown below.
9.
Click OK twice to return to the tag list on the Parser Rules screen.
Defining Context Information

To further enhance the user experience for translators and reviewers let us add some structure
information for the following structure tags: heading, subheading and item. This will enable users to
ascertain at a glance whether a given segment is, for example, a heading, list item, etc. Such information
can be useful, if not even vital for the translation and review process.
6-10
1.
Highlight the heading tag in the list, and then click the Edit button.
2.
In the Edit Rule dialog box click the Edit button next to the Structure info field.
2013 SDL plc
3.
This opens the Structure Information Properties window. Click the Add button to add
structure information for the selected tag.
This opens the Add Structure Information dialog box. Here, you can enter structure information for the
translator or select from a list of pre-defined values. The Standard dropdown list contains a number of
names for elements that can typically be found in a document, e.g. heading, list item, table cell, etc.
Selecting Pre-Defined Structure Information

For the currently selected tag we can just choose an item from the standard list. Take the following steps:
1.
Select Heading from the Standard dropdown list.
2.
During translation the structure information column will show whether a particular
segment is a heading. To make it even clearer and to further enhance the user experience
you can also change the character formatting for this structure element, i.e. show the
headline in a bigger font. To do this click the Edit button next to the Formatting field.

6-11
2013 SDL plc
6-12
3.
This opens the Font Formatting dialog box. Here you can freely define what the heading text
should look like in the Editor view. Activate the Specify size check box. Enter 18 into the text
field below.
4.
Then, Select Activate from the Bold dropdown list. Note that the Sample field on the bottom
of this dialog box shows an example of how the content of heading tags will be displayed in
the Editor view. Click OK to confirm.
5.
Click OK again to return the Structure Information Properties screen. Note that the
corresponding structure information has been added. Click OK twice to go back to the
Parser Rules screen.
6.
Let us assume that you would like to do the same for the item tag, which contains list item
text. Highlight the item tag in the list and click the Edit button.
2013 SDL plc
7.
8.
This opens the Structure Information Properties window. Click the Add button to add
9.
In the Add Structure Information dialog box select List Item from the Standard dropdown
list. Then click OK three times to go back to the Parser Rules screen.
Entering Custom Structure Information

Let us assume that for the subheading tag you want to enter custom structure information rather than
picking from the standard list. To do this take the following steps:

6-13
2013 SDL plc
6-14
1.
Highlight the subheading tag in the list, and then click the Edit button.
2.
3.
This opens the Structure Information Properties window. Click the Add button to add some
4.
This opens the Add Structure Information dialog box. Enter Subheading into the Name text
field.
2013 SDL plc
5.
Note that the text fields below will be filled in automatically. For example, the Code text field
contains the short form that will be displayed next to the corresponding segment. The
content of the Name field will be shown when the user moves the mouse pointer over the
structure information column. The picture below provides an example of what the structure
information column will show later during translation:
6.
Let us now define character formatting for the subheading. To do this click the Edit button
next to the Formatting field.
7.
This opens the Font Formatting dialog box. Activate the Specify size check box. Enter 14 into
the text field below.
8.
Then, Select Activate from the Bold dropdown list. Your formatting settings should look as
shown below:
9.
Click OK four times to go back to the Parser Rules screen.
Making Attribute Content Translatable

Let us now take a look at the illustration tag. In a text editor this tag looks as shown below:
The illustration tag contains translatable content in the form of the caption attribute. Some tags can have
attributes that define the tag further. In the above case there is a path attribute that contains the name and
location of the graphic file that is referenced by the tag. Let us assume that the content of this attribute is
not translatable, i.e. the path does not change in the target language. However, the caption attribute is an
example of an attribute with translatable content.
By default, attribute content is never exposed for translation. To change this behavior for the caption
attribute you need to add a new parser rule by taking the following steps:

6-15
2013 SDL plc
1.
Click the Add button in the lower left corner of the Create File Type wizard.
2.
This opens the Add Rule dialog box. First, select the Attribute from the Rule type dropdown
list, as the translatable content is inside an attribute.
3.
From the Element dropdown list select illustration, as this is the tag that contains the
attribute.
4.
Last, select caption from the Attribute dropdown list.
5.
Click OK, and note that the new rule has been added to the list.
Saving the File Type

Now finish defining the file type and save it by taking the following steps:
1.
6-16
Click Next and then Finish.
2013 SDL plc
2.
Note that your new file type is now listed in the Options dialog box.
Adding a Preview Stylesheet

Last, we are going to add a stylesheet to our new XML file type. This enables the file type to generate
readable and printable previews (both external and internal real-time previews). Note that in this section
you will only learn how to use an existing XSL stylesheet. Developing XSL stylesheets is not in the scope
of this training course.
The stylesheets might be provided by the customer or documentation department. Note that each type of
XML requires development of a custom stylesheet.
To add an existing XSL stylesheet take the following steps:
1.
Click the plus (+) icon next to the name of your newly created XML file type to expand a list of
options.
2.
Then click Preview.

6-17
2013 SDL plc
3.
On the right-hand side of the dialog box click the Select button and browse for the file
Stylesheet.xsl, which you can find in the same folder as your XML sample file. Select the XSL
stylesheet by double-clicking it.
4.
Then click OK to confirm.
PROCESSING THE XML DOCUMENT WITH THE CUSTOM

FILE TYPE
Opening the XML sample file works exactly the same way as opening with the default Any XML file type.
The application automatically assigns the correct file type to your document. When the file is open in the
Editor view it should now look as shown below:
Note the following enhancements:

C
Headings and subheadings are now shown in a bigger font size.
Strings enclosed in em tags have bold character formatting.
The structure information column contains information for the segments that are enclosed in
particular tags such as heading (H), item (LI), etc.
Tag attribute content (e.g. Corporate logo) is now exposed for translation and has been automatically
assigned the structure information code TAG(for tag content).
The strings enclosed in prodcode tags are no longer exposed for translation.
Previewing the Document

Now take the following steps:
1.
6-18
Translate the entire document. For most segments the TM will give you exact or context matches.
2013 SDL plc
2.
Once you are done translating, preview the translated document in your Web browser. To do
this switch to the File tab, and then select Print and View -> View In -> Web Browser (XML)
as Target. Owing to the stylesheet (which is part of the custom XML file type) the preview
should now look as shown below:
TIP
If you are using Mozilla Firefox, you have to set the character encoding to UTF-8 in the View menu of
your browser.
3.
Close your Web browser. To generate an interactive preview within SDL Trados Studio 2014
move your mouse pointer over the Preview tab in the top right corner.
4.
When the Preview window is shown click the Click here to generate initial preview link.

6-19
2013 SDL plc
This preview interacts with the side-by-side editor, i.e. when you click a segment in the
preview, the corresponding segment in the editor will be highlighted (and vice-versa).
5.
Running the Tag Verification

As XML is a tag-based document format, you should run the tag verification at the end of the translation.
In a worst case scenario, tag mistakes can cause corruption of the entire document. To run the tag
verification take the following steps:
1.
Switch to the Review tab, then click the Verify button (or press F8).
2.
Note that the last segment is marked with a red error icon:
Moreover, an error message is displayed in the Messages window:
The error message was raised as the target segment is missing the contact tag pair. If these
tags are missing, the e-mail link in the final target document will not work. (Note that in this
exercise you can ignore the other message that relates to the verification schema.)
3.
Go to the last target segment, highlight the e-mail address and press Ctrl+,. This will offer
the contact tag for insertion into the target segment. Press Enter to enclose the highlighted
string in a contact tag pair.
4.
Press Ctrl+Enter to reconfirm the segment. This will also remove the error icon and the
error message from the document.
Now save the XML document in SDL XLIFF format by pressing Ctrl+S. Do NOT close the file yet, as we
will need it for the exercises of the following chapter.
TIP
You can save the target XML file by using the keyboard shortcut Shift+F12. You can then open the
target XML file, for example, in Internet Explorer to check whether the target file is a valid XML
document.
6-20
2013 SDL plc
SUMMARY
C
You can open any XML document in SDL Trados Studio 2014 as the application is equipped with a
generic XML file type.
However, to optimize the processing of XML files and to enhance the user experience it is
recommended that you create a custom XML file type. This allows you, for example, to exclude
specific content from translation, define character formatting to enhance the user experiences, etc.
Tags that occur inside segments are called inline tags. All other tags are called structure tags.
Content in tag attributes is by default not offered for translation. A custom file type can also be
configured to expose attribute content for translation.
You can add structure information for particular tags to be displayed in the structure information
column to further enhance the user experience.
By adding an XSL stylesheet to the custom file type you can generate external and internal previews
for proofreading and printing.
It is recommended that you run a tag verification after translation. In a worst case scenario tag
errors can cause critical errors that prevent your document from generating a valid target XML
document.

6-21
2013 SDL plc
C U S T O M Q UA LI TY ASSURANC E
RULES
C
Define your own quality assurance rules to meet custom

quality assurance requirements
Use regular expressions for intelligent display filtering
Use regular expressions in find operations, e.g. to find all

e-mail addresses in a translation
Chapter
Custom Quality Assurance Rules
ABOUT REGULAR EXPRESSIONS

In this chapter we assume that you are already familiar with the quality assurance features of SDL Trados
Studio 2014, i.e. QA Checker 3.0. For example, you can have QA Checker point out all segments that
contain a potential number error, inconsistent end punctuation characters, etc.
In addition to the standard options you can also define your own QA rules through so-called regular
expressions. Imagine the following:
Your corporate styleguide dictates that there must always be a space between a number and each
measurement, e.g. 30 mm, 10 cm, etc. You would like to check translated documents for any segments in
which the space is missing, e.g. 30mm, 10cm.
If you try find each instance in which the space is missing using normal find functionality, you might
need dozens or even hundreds of different find operations, as there can be virtually limitless
permutations.
When you use regular expressions, you just define one expression that covers all possible permutations.
For example instead of searching for:
1mm
2mm
3mm
1cm
2cm
3cm
you just use one regular expression: [0-9]mm
In SDL Trados Studio 2014 regular expressions can be used, for example, in:
C
QA Checker
Display filter
Find/replace operations
Note that a full course on regular expressions is not within the scope of this training manual. In this
chapter we just provide a few examples of how regular expressions can be used in SDL Trados Studio 2014.
To learn more on regular expressions, you can, for example, refer to the online tutorial at
http://www.regular-expressions.info/.
USING REGULAR EXPRESSIONS IN SDL TRADOS STUDIO

2014
The following sections provide examples of how regular expressions can help you increase your
productivity.
Using Regular Expressions in QA Checker

For this exercise let us assume the following: in the XML document that you translated in the previous
chapter there are some segments that contain a number, followed by a space, followed by a measurement
(e.g. 30 mm). This is what our imaginary styleguide dictates. However, in some segments there is no space
before a measurement (e.g. 30mm). Therefore, you want to configure QA Checker to find all instances
where the space is missing between number and measurement.
7-2
2013 SDL plc.
Configuring QA Checker
To do this you first have to define a regular expression in QA Checker. Take the following steps:
1.
Click the Project Settings button on the Home tab.
2.
In the Project Settings dialog box select Verification -> QA Checker 3.0 -> Regular
Expressions.
3.
Activate the Search regular expressions check box.
4.
Regular expressions can be very cryptic (similar to shorthand). To be able to know what the
regular expression actually means you need to enter a Description into the corresponding
text field, e.g. Measurements without space.
5.
As the inconsistent use of spaces before measurements occurs within the target segments,
you only need to enter an expression into the RegEx target text field. Enter the following
expression into the RegEx target text field: [0-9]{1,}[mm|cm|m]
NOTE
The above regular expression means:
[0-9] = any number from 0 to 9
{1,} = one or more numbers
[mm|cm|m] = mm OR cm OR m
6.
From the Condition dropdown list select Report if target matches (target check only). Your
regular expression item should look as shown below:

7-3
2013 SDL plc.
7.
Click the Action button and then select Add item from the context menu. This will add the
custom QA rule to the list as shown below:
8.
Click OK to confirm and to close the Project Settings dialog box.
Running the Regular Expression Check

To run your document against your newly defined QA Check rule take the following steps:
7-4
1.
Switch to the Review tab, then click the Verify button (or press F8).
2.
QA Checker will then report several instances in which the space is missing before a
measurement. The corresponding messages will be listed in the Messages window. Each
segment concerned will be marked with a yellow warning icon.
3.
Double-click the first message in the Messages window. This opens the Verification Message
Details dialog box.
2013 SDL plc.
4.
In the Target Segment Content text field change 12cm to 12 cm. Then click the Change
button.
5.
Repeat the above step for the next segment and click Change again, which will lead you to
the next reported segment.
6.
The last reported segment contains two instances with a missing space, which need to be
corrected. After making the required corrections click Change.
7.
A message is now displayed to inform you that there are no more occurrences to be
corrected. Close this message by clicking OK. The Messages window should now be empty
and all warning icons have been removed from the corrected segments.
Using Regular Expressions in the Display Filter

The display filter allows you to focus on particular segments by showing, for example, only untranslated
segments, segments that contain a particular term, etc. However, you can also use regular expressions for
filtering the segments in the Editor view. Let us assume that you want to make certain that there are indeed
no more occurrences of missing spaces between numbers and measurements.
1.
Make sure that the Review tab is selected.

7-5
2013 SDL plc.
2.
Enter the regular expression that you defined in the QA Checker into the Search text box.
Then press Enter.
3.
This filter should come up empty, i.e. no segments are displayed. This gives you assurance
that there are no more segments in which the space is missing between figure and
measurement. Now, modify your regular expression to read: [0-9]{1,}\s[mm|cm|m]. The
added \s stands for space. Press Enter again.
4.
This will now show all segments with figures followed by a space, followed by a
measurement. Note that the segments that you corrected previously are now unconfirmed.
Therefore, confirm each segment by pressing Ctrl+Enter.
5.
Click the Reset Filters button to display all segments again.
Using Regular Expressions when Searching for Strings

Regular expressions can also be used for find operations. Let us assume that you would like to check
whether e-mail addresses have been localized. Rather than searching for all possible e-mail address
permutations (of which there might be billions), you will, of course, want to formulate a regular
expression. Take the following steps:.
7-6
1.
Press Ctrl+F to open the Find and Replace dialog box.
2.
In the Find what text field enter the following regular expression: [^\s]+@[^\s]+
3.
Make sure that the Target radio button is selected.
2013 SDL plc.
4.
Activate the Use check box and select Regular expressions from the dropdown list.
(Otherwise the find operation will not treat the string entered in Find what as a regular
expression.) The Find and Replace dialog box should now look as shown below:
5.
Click the Find Next button. This will highlight the first e-mail address in the document.
Localize the address, e.g. change it from sales@ourcompany.com to sales@ourcompany.de.
6.
Confirm the modified segment by pressing Ctrl+Enter. Raise the Find and Replace dialog
box, which has moved to the background.
7.
Click the Find Next button again, which will lead you to the second e-mail address. Localize
the e-mail address, and confirm the segment with Ctrl+Enter.
8.
You can now close the Find and Replace dialog box by clicking the Close button.
You can now save the edited document and close it.
NOTE
You might say that it would have been easier just to enter the @ instead of a regular expression. Of
course, you could do that. However, note that there is one segment that contains an @ (segment 15:
Press the @ button to get in contact with customer service.), but no e-mail address.
SUMMARY
C
Regular expressions are a powerful way of finding permutations of various strings while just using
one expression, e.g. [^\s]+@[^\s]+ stands for any e-mail address.
SDL Trados Studio 2014 supports regular expressions, for example, in QA Checker. This allows you
to define intelligent, custom QA check rules, e.g. find all segments in which the space is missing
between the figure and the measurement.
Regular expressions can also be used in the display filter as well as in the Find and Replace dialog
box.

7-7
2013 SDL plc.
F I L E TYP E SETTI NGS
This chapter provides examples of how to fine-tune your file

type settings to optimize translation processes. You will learn
how to:
C
Exclude specific text in a Microsoft Word document from

translation
Change soft break handling in Microsoft Word

documents
Exclude speaker notes from translation when processing

Microsoft PowerPoint files
Exclude content from specific columns in Microsoft Excel

files
Fine-tune settings for processing Adobe InDesign

documents
Chapter
File Type Settings
ABOUT FILE TYPE SETTINGS

SDL Trados Studio 2014 supports numerous file formats, e.g. Microsoft Office, Adobe FrameMaker,
Adobe InDesign. SDL Trados Studio 2014 uses file types to process translatable text from source
documents. The file types consider that each file format has particular features. For example, Microsoft
PowerPoint documents can contain speaker notes, which sometimes may require translating, but often
need to stay unchanged. Speaker notes are not available in other formats such as Microsoft Word.
By default, SDL Trados Studio 2014 exposes as much translatable text as possible. This also includes the
speaker notes in a Microsoft PowerPoint file. Imagine the following: you need to translate a PPTX file that
contains speaker notes, but the speaker note content needs to stay unchanged.
You can customize file type settings for specific formats to optimize your translation workflows, e.g. by
excluding non-translatable text from the very beginning. This prevents such text from being exposed for
translation, analyzed, counted, etc.
CUSTOMIZING FILE TYPE SETTINGS

This chapter provides examples of how to change file type settings for the following formats:
C
Microsoft Word
Microsoft PowerPoint
Microsoft Excel
Adobe InDesign
The sample files for the following exercises can be found in ..\Sample Files\06_FileTypes.
Changing Microsoft PowerPoint File Type Settings

From the above sample folder open the file New_Features.pptx in Microsoft PowerPoint by double-clicking
it. Take a look at the speaker note text on the bottom of the first slide:
Let us assume that this segment does not require translation, as it is an internal note to the speaker.
However, by default speaker note text is exposed for translation in SDL Trados Studio 2014, which means
that it is also counted during file analysis.
Close Microsoft PowerPoint, and take the following steps to exclude speaker notes from translation before
opening the file for translation:
1.
8-2
Press Ctrl+Shift+O to open a single document for translation.
2013 SDL plc.
File Type Settings
2.
Browse for the file New_features.pptx in your sample files folder and select it by doubleclicking it. You can continue using the TM and language pair from the previous exercises.
3.
Click the Advanced button in the lower-left corner of the Open Document dialog box.
4.
This opens the Project Template Settings dialog box. Under File Types on the left-hand side
you see a list of all document formats that are supported by SDL Trados Studio 2014. Select
File Types -> Microsoft PowerPoint 2007-2013 -> Notes and shapes.
5.
Then select Exclude notes from the Notes dropdown list. Confirm this setting change with
OK.

8-3
2013 SDL plc.
File Type Settings
6.
Now you are back in the Open Document dialog box. Click OK again to open the document
in the Editor view. Take a look at the segments. The speaker notes text should be nowhere to
be seen:
NOTE
The speaker note text will NOT be removed from the actual document. When you generate the
translation in the native file format, the speaker note will still be available in the original version. The
speaker note content is just not exposed for editing or translation in SDL Trados Studio 2014.
Now you can continue by translating the document, then save and close it.

Microsoft PowerPoint Settings
Changing Microsoft Word File Type Settings

Let us now take a look at the sample DOC file, i.e. Command.doc. When you open this document in
Microsoft Word, it looks as shown below:
Let us assume the following:

C
The text highlighted in yellow should be excluded from translation. Note that in addition to the
yellow background these segments have the custom paragraph style DoNotTranslate applied to
them.
Comment text should also be excluded from translation.
Soft returns should be treated as segment delimiters.
First, close the DOC file in Microsoft Word and open it in SDL Trados Studio 2014 without making any
changes to the file type settings. The file will look as shown below:
8-4
2013 SDL plc.
File Type Settings
Take a look at the first cell. You will note that it actually contains two segments. These two segments are
considered one segment, as they are separated by a soft return, which by default is not considered a
segment delimiter. You can display the soft return character by clicking the Show Whitespace Characters
button.
The segment will then look as shown below:
Moreover, the comment text and the segments that have the style DoNotTranslate are exposed for
translation, which we want avoid.
Close the current document by pressing Ctrl+F4. If you are prompted to save the document, click No. We
will now change the file type settings and open the same document again.
NOTE
You need to change the file type settings before opening and translating a document. Once you have
opened a document, you cannot change the file type settings on the fly.
Take the following steps to change the file type settings:

1.
Open the sample document again by pressing Ctrl+Shift+O.

8-5
2013 SDL plc.
File Type Settings
2.
In the lower-left corner of the Open Document dialog box, click the Advanced button.
3.
On the left-hand side of the Project Template Settings dialog box select File Types ->
Microsoft Word 2000-2003 -> Styles.
4.
On the right-and side enter the style name DoNotTranslate into the Styles to be converted
into structure tags text field. Then click the Add button to add the style name to the list
below.
NOTE
This will exclude any text in the DOC file from translation that has this style. For this to work,
however, you need to make certain that the text to exclude is marked with this specific style (the style
can have any name).
8-6
2013 SDL plc.
File Type Settings
5.
Now click Common. Then change the default settings on the right-hand side as shown
below:
6.
By default, comments text is exposed for translation. By deactivating the Extract comments
text for translation check box you exclude comments text.
7.
You may also activate the Process documents with non accepted or rejected changes. For the
example in this exercise this setting is not required, however, it can be useful in certain
cases. By default, SDL Trados Studio 2014 refuses to open DOC files that contain
unaccepted or unrejected changes. By activating this option you can force the application to
process such documents.
NOTE
The above setting should only be turned on in special cases. It is not recommended to activate this
setting, as this might cause you store source segments with non accepted or non rejected changes in
your TM. However, this can be a useful tip for troubleshooting issues in which you are unable to open
a Word document.
8.
Activate the Treat soft returns as structure tags check box. This will enable segmentation
after soft returns.
9.
Click OK to confirm the changed settings.
10. Click OK again to open the document in the Editor view.

Now that the document is open, you can see some notable differences:
Comments text is no longer exposed for translation.
The segments that have a yellow background have been excluded too.

8-7
2013 SDL plc.
File Type Settings
The first two segments (which are separated by a soft return) are now shown in separate cells, i.e.
they are treated as separate segments.
You can now translate the document, then save and close it.

Microsoft Word Settings
Tweaking Microsoft Excel Files

Let us take a quick look at another common format, i.e. Microsoft Excel:
Open the sample file Product_List.xlsx in Microsoft Excel. This small sample file should look as shown
below:
Let us assume that you would like to exclude the content in column A from translation, as it only contains
product codes, which should not be changed or considered during word count, analysis, etc. To do this you
actually do not have to change the file type setting in SDL Trados Studio 2014. As columns and rows are
excluded from translation by default, all you need to do is hide column A.
8-8
1.
Right-click the column header, and select Hide from the context menu.
2.
Save the file and close the document in Microsoft Excel.
3.
Open the file for translation in SDL Trados Studio 2014. Note that you do not need to
change any settings, i.e. just click OK to open the file in the Editor view.
2013 SDL plc.
File Type Settings
4.
In the Editor view, the file should look as shown below. Note the content from column A has
indeed been excluded from processing.
5.
Start by translating the first segment. Make sure that your translation is longer than 31
characters. The interactive character count in the status bar helps you ascertain how long
your translation is.
6.
Confirm the segment with Ctrl+Enter. Note the red error icon that is now shown next to
your translation. If you move the mouse pointer over the error icon, a tooltip will be
displayed that explains that Excel worksheet names must not exceed 31 characters.
7.
Take a look at the character count in the status bar: in the above example the count shows 33
characters. As a rule worksheet names must not exceed 31 characters, otherwise you cannot
generate a valid XLSX target file. Note the WSN designation in the structure information
column, which indicates that this segment occurs in a worksheet.
8.
Shorten your translation and confirm it again with Ctrl+Enter. This will remove the red
error icon.
Now you can finish translating the current document, then save and close it.

Microsoft Excel Settings
Processing Adobe InDesign Files

Let us take a look at an example from the Desktop Publishing world, i.e. Adobe InDesign.

8-9
2013 SDL plc.
File Type Settings
Supported Adobe InDesign Versions

SDL Trados Studio 2014 supports the following versions of InDesign:
C
Adobe InDesign CS2-CS4 INX (InDesign Interchange format)
Adobe InDesign CS4-CS6 IDML (InDesign Markup format)
Additionally, SDL Trados Studio 2014 also supports Adobe InCopy CS4-CS6 ICML.
Note that the native INDD format is not supported. INDD files need to be exported to either INX
(InDesign CS2-CS4) or IDML (InDesign CS5-CS6) before they can be processed in SDL Trados Studio
2014.
When the file Sample.idml is opened in Adobe InDesign proper, it looks as shown below:
Adobe InDesign implements the concepts of layers. This means that text frames can be placed on layers.
In the above example the red text frame is placed on a layer called copyright, which is locked. (Note the
padlock icon in the Layers list.) The text frames with the blue border are placed on a layer called Layer 1,
which is not locked.
Opening an IDML File

If you have the file open in InDesign, close it and take the following steps:
8-10
2013 SDL plc.
File Type Settings
1.
Open the file Sample.idml in SDL Trados Studio 2014. In the Editor view the document looks as
shown below:
2.
As you can see, the copyright text is not exposed for translation. This is because by default
any content on locked and hidden layers is excluded from translation.
3.
Let us also assume that you want to prevent SDL Trados Studio 2014 from exposing
hyperlinks for translation (see segment 18), as they do not need to be changed and you want
to avoid storing them in your TM.
Changing the Adobe InDesign File Type Settings

To change the file type settings first close the file. If prompted to save changes, click No. Then take the
following steps:
1.
Open the file Sample.idml again for translation, however, this time click the Advanced button in the
Open Document dialog box.

8-11
2013 SDL plc.
File Type Settings
2.
In the Project Template Settings dialog box select File Types -> Adobe InDesign CS4-CS5
IDML -> Common. Then change the settings as shown below:
3.
Activating the Extract content of hidden layers check box is necessary to expose content of
hidden and locked layers for translation.
4.
Selecting Do not extract localizable data from the Hyperlink extraction type dropdown list is
required to prevent hyperlinks from being exposed for translation.
5.
Click OK to confirm the changed settings.
6.
Click OK again to open the document in the Editor view.
The copyright text should now be exposed for translation, while the hyperlink is not. Translate the
document, then save it.

Adobe InDesign CS5/6 Settings
Previewing Adobe InDesign Files

Generating an external preview (by selecting the File tab and then selecting Print and View -> View In) is
only possible if Adobe InDesign is installed on your PC, which is often not the case.
If you want to generate a printable preview just for proofreading from paper, you can take the following
steps:
8-12
1.
Switch to the File tab, and then select Print and View -> Print Preview.
2.
This will open your Web browser with the source and target content in a side-by-side view.
From here, you can print the content for paper-based review.
2013 SDL plc.
File Type Settings
NOTE
You can generate this kind of print preview for any format.
You can now close the Web browser and close the document in SDL Trados Studio 2014.

Which file types are supported?
SUMMARY
C
SDL Trados Studio 2014 supports various file formats. For each file format there is a file type that
offers settings to customize the way file formats are processed. For example, you can choose to
exclude speaker notes from translation.
When processing DOC files you can choose to treat soft returns as segment delimiters.
Moreover, you can exclude certain paragraph styles from translation.
A common use case is to exclude specific rows or columns in Excel files from translation. This can
easily be done by hiding the corresponding rows or columns.
Excel worksheet names must not exceed 31 characters, otherwise you cannot generate a valid Excel
target file.
Adobe InDesign files can contain layers, which, in turn, can be locked or hidden. Such content is by
default excluded from translation. However, by changing a setting you can expose such content for
translation.
SDL Trados Studio 2014 supports INX files (Adobe InDesign CS2-C4) and IDML files (Adobe
InDesign CS4-CS6).

8-13
2013 SDL plc.
P S E U DO -TR A NS LATION

C
Run a pseudo-translation on a project to check the project

file for potential localization problems
Chapter
Pseudo-translation
ABOUT PSEUDO-TRANSLATION
SDL Trados Studio 2014 includes a pseudo-translate task sequence, which allows you to easily check
source documents for potential localization problems, e.g. violation of file-specific length restrictions.
This task sequence works as follows:
C
The source files are converted to SDL XLIFF format
The source files are then pseudo-translated, i.e. the target segments are filled with a random
sequence of target-language words
The SDL XLIFF files are then converted back to the original format
Especially the last step can be critical if during the localization phase errors are introduced that prevent
the target file from being generated in the required format. For example, when worksheet names of
Microsoft Excel files contain, for example, an asterisk (*), or if the worksheet name has more than 31
characters, the target Excel file can no longer be generated, as it violates a file-specific rule.
Using the pseudo-translate round-trip you can make certain that in principle your source files can be
processed. If problems occur during the pseudo-translate round-trip, you know about them BEFORE the
actual translation starts. This saves you from situations in which you run into problems converting fully
translated files into the original format just a few minutes before the target files need to be delivered.
PSEUDO-TRANSLATING AN EXCEL FILE

The sample file for this exercise can be found in the following folder: ..\Sample
Files\07_Pseudo_Translation.
Creating a Pseudo-translation Project

To create a pseudo-translation project take the following steps:
9-2
1.
Click the New Project button on the Welcome screen.
2.
On the Project Type screen of the New Project wizard click Next.
2013 SDL plc.
Pseudo-translation
3.
On the Project Details screen enter the name of your project into the Name field, e.g. Sample
pseudo-translation.
4.
On the Project Languages screen make sure that English is selected as the source language.
5.
As target language select, e.g. Arabic (Lebanon) from the Target Languages list by doubleclicking the language name. Then click Next.

9-3
2013 SDL plc.
Pseudo-translation
9-4
6.
On the Project Files screen click the Add Files button to add the sample file. This opens the
Add Files dialog box. Browse to the location of the sample file (SpellCheckOptions.xlsx) and
select it by double-clicking. Then click Next.
7.
On the Translation Memory and Automated Translation screen you do not need to select
anything, as no translation memories are required for pseudo-translation. Just click Next to
continue.
8.
You can also skip the Termbases and the SDL PerfectMatch screens by clicking Next.
9.
On the Project Preparation screen select Pseudo-translate Round Trip from the Task
Sequence dropdown list. Then click Next.
2013 SDL plc.
Pseudo-translation
Configuring the Pseudo-translate Task Settings

1.
On the following screen click Pseudo-translate below Batch Processing. This displays the available
task settings.
2.
The default Pseudo-translate type is Random. This means that a random sequence of targetlanguage words will be inserted into the document each time the task runs. Leaving this
option to Random means that every time you set up a pseudo-translation project, you will
get a different pseudo-translation result.
3.
By default, the pseudo-translate task adds an underscore at the beginning and end of each
segment (or paragraph if you select the Alter on paragraph unit level option). You may
change the leading and trailing characters if required. These characters are used to clearly
indicate that a segment or paragraph has been pseudo-translated and not been processed by
a human translator.

9-5
2013 SDL plc.
Pseudo-translation
4.
One important factor during localization is the length of the target text. For example, if the
target text is too long, it might not fit into a text box. By default, the pseudo-translate task
expands the target text by a factor of 1.3, i.e. the resulting pseudo-translation will be 20%
longer than the original text. This is good for target languages that typically turn out longer
than the original.
Arabic by contrast tends to be a bit shorter than e.g. English. This is why you may set this
option to a value lower than 1, e.g. 0.9.
5.
By default, the pseudo-translate tasks inserts a random sequence of target language words
from a dictionary into the target segments. However, you may also fill the pseudo target text
just with a sequence of dollar signs by selecting the corresponding option. For this exercise
let us just keep the default option selected.
6.
Now click Finish to run the tasks. If no errors have occurred during conversion of the source
file to SDL XLIFF format and conversion back to the original format, all tasks will be shown
as Completed. If this is the case, click Close to close the New Project wizard.
Viewing the Pseudo-translated File

To view the pseudo-translated SDL XLIFF file, take the following steps:
9-6
2013 SDL plc.
Pseudo-translation
1.
Make sure that you are in the Projects view, and then double-click your pseudo-translation project.
2.
Double click the (pseudo-translated) SpellCheckOptions.xlsx.sdlxliff file to open it in the

Editor view.
3.
Below you see what the pseudo-translated file looks like. The pseudo-translate task has filled
the target segments with random sequences of Arabic words, which are preceded and
followed by an underscore character. Note that the pseudo-translate task applies tags and
formatting in the approximate positions within the target text.
4.
The pseudo-translate task has also generated a target language version of the Excel file. To
view it, switch to the Files view.
5.
Right-click the (pseudo-translated) SpellCheckOptions.xlsx.sdlxliff file and select Explore

Containing Folder from the context menu.

9-7
2013 SDL plc.
Pseudo-translation
6.
This opens Explorer where you will see the SDL XLIFF file alongside the pseudo-translated
Excel file, which you can double-click to open in Excel.
7.
Below you see what the pseudo-translated target file looks like.
This result clearly proves that the original file can be converted to and from SDL XLIFF without any
problems. The pseudo-translated target file also complies with the requirements of the target format and
language, e.g. right-to-left directionality and no violation of length limitations.
This means that you can now remove and delete the pseudo-translation project and prepare your file(s) for
proper localization in another project.

About Pseudo-translation
SUMMARY
9-8
SDL Trados Studio 2014 offers a pseudo-translation task sequence when you create a project.
This allows you to check for potential localization issues by converting the native source files to SDL
XLIFF.
The pseudo-translate function fills the target column with random sequences of target language
words.
The pseudo-translate task can be customized to take into account target language-specific
requirements, e.g. if your target content tends to be longer than the source, you can select to expand
the target text by e.g. 20%.
The pseudo-translated SDL XLIFF files are immediately converted back to the native format. That
way you are made aware of potential conversion issues before the actual translation is done, i.e. not
just a few minutes before you need to deliver the translation.
2013 SDL plc.
R E V I E WI NG TR A N SL ATED FIL E S
This chapter provides examples of how to use the review

functionality of SDL Trados Studio 2014 for supporting review,
proofreading and quality assurance processes. You will learn
how to:
C
Track changes in SDL XLIFF files
Select your favorite spell checker
Use the display filter feature to focus on segments that

contain changes
Chapter
10
10
Reviewing Translated Files
THE REVIEW SAMPLE SCENARIO

During the following exercises you will learn to use the new features of SDL Trados Studio 2014 to review
translated content. Imagine the following: you have just received a package that contains two fully
translated SDL XLIFF files, which you are required to review. First, you need to open the package, which
is contained in your sample files folder, i.e. ..\Sample Files\08_Review.
Opening a Project Package for Review

To open the project package take the following steps:
10-2
1.
On the Welcome screen of the application click the Open Package button.
2.
Browse to your sample files folder and select the project package file Review Sample
Project.sdlppx by double-clicking it.
3.
The Open Package dialog box, which has now opened, provides an overview of the package
content, i.e. it shows the names of the files to review as well as the number of untranslated
and unreviewed words. Click Finish to extract the package content and add the project to
your SDL Trados Studio 2014 environment.
2013 SDL plc.
4.
After the package content has been successfully extracted to your folder, click Close.
5.
Studio has now switched to the Projects view. Note that the review project is now shown in
your projects list. Click the Confirmation Statistics tab on the bottom of the application
window. This will display the number of translated words in a bar chart representation.
While you are reviewing and approving translations, the words will be upgraded to the
Reviewed status.
10
Opening a File for Review

To open the first file for review take the following steps:

10-3
2013 SDL plc.
10
1.
Double-click the project to switch to the Files view.
2.
Right-click the first file (PhotoPrinter.doc.sdlxliff) and select the Open For Review command
from the context menu.
3.
The file to review looks as shown below:
Selecting your Preferred Spell Checker

SDL Trados Studio 2014 now supports the Microsoft Word spell checker in addition to Hunspell. Using
the Word spelling checker can have the following advantages:
C
Higher-quality spelling check, i.e. less false errors
Re-use of your spell check settings from Word including custom dictionaries
Let us assume that you prefer to use the Word spell checker rather than Hunspell. To switch the spell
checker take the following steps:
10-4
1.
Switch to the File tab, then click Options.
2.
In the Options dialog box drill down to Editor -> Spelling.
2013 SDL plc.
3.
By default, Hunspell Spell Checker is active. Select MS Word Spell Checker from the Active
Spell Checker dropdown list.
4.
If you want to configure further options (e.g. Ignore words in UPPERCASE), you need to do
this in Word proper. Also, any custom dictionaries will now be taken from Word. Click OK to
confirm your selection.
10
From this point forward the wavy underlines used to highlight unknown words and spelling mistakes are
inserted by the Word spell checker. After changing the spell checker you should see an immediate effect,
e.g. the word Papierzufhrungspfad that Hunspell flagged as an unknown word is no longer underlined,
as it is known to the Word spell checker:
Approving Segments
Opening a file for review is different from opening a file for translation in the following ways:
C
The window that contains the translation results, comments and messages is displayed below the
document.
The track changes feature is activated by default.
Pressing Ctrl+Enter sets the segments Translation Approved instead of Translated.
While you are inside the first segment press Ctrl+Enter. Note the icon that has now been placed between
the source and the target segment.

10-5
2013 SDL plc.
10
This icon indicates that the translation has been approved. Also note the status bar on the bottom of the
application window:
The status bar shows the percentage of edited, translated, approved, and rejected content. You may also
have noted the target character count, which is shown for the currently selected segment, i.e. in this case
the second segment.
Making Changes
Apply the following changes:
1.
Let us assume that you do not approve of the translation for the second segment, i.e. the word
geeigneten needs to be deleted. To do this select the word and click the Delete key on your keyboard.
2.
Note that the word has not disappeared, but is now highlighted with red strikethrough
formatting:
3.
Moreover, a Translation Rejected icon is now shown between the source and the target
segment, i.e. correcting a segment implicitly rejects the translation.
4.
Take a look at the status bar again. Note that the percentage of rejected content has
increased. At the same time the character count has decreased. Although the deleted word is
still being displayed, it is no longer being counted.
5.
Move the mouse pointer over the deleted word. Note that this will display a tooltip that
indicates when the change was made, by whom and what type of change was made, i.e.
deletion or insertion.
6.
Do NOT confirm the edited segment. Just use the Down key to move to the next segment.
NOTE
Tracked changes content is not stored in the TM, i.e. only the final versions are saved in the TM.
7.
10-6
Note that in the next segment the italics formatting is missing. Correct this by applying the
required formatting to the corresponding string in the target segment, e.g. by using the
QuickPlace shortcut key, Ctrl+,.
2013 SDL plc.
8.
Applying formatting will also cause the translation to be rejected, as it counts as a change.
This time the unformatted string has red strikethrough formatting, while the part that is
formatted is underlined.
9.
Use the Down key to go to the next segment. Let us assume that you would like to replace
the word gengend with ausreichend. After making the change, your target segment should
look as shown below:
10
10. Move the mouse pointer over the underlined (added) word. The tooltip now indicates that
this change is of the type Insertion.
11.
Go down to segment 18. Note that this segment contains a spelling mistake. Right-click the
misspelled word and select the correct version from the context menu.
TIP
For going to a particular segment number you can press Ctrl+G and enter the segment id.
12.
As you can see, changes made through the spell check are tracked as well as would be
changes made by the find and replace function.

How to Track Suggested Changes
Using the Display Filter

At this point we would like to point out some additions that have been introduced to the display filter
function. The display filter allows you to restrict the editor to show only segments of a particular category,
e.g. all segments that contain comments, all segments that are unconfirmed, etc.
Displaying only Segments with Tracked Changes

To show only segments with tracked changes take the following steps:
1.
Switch to the Review tab.
2.
From the list of available display filter options select With tracked changes.

10-7
2013 SDL plc.
10
3.
This will show only the segments that contain changes:
Displaying Number only Segments

Let us take a look at another display filter category: the document contains a few number only segments.
To display only those segments take the following steps:
1.
Select Number only from the Display dropdown list. The result will be as shown below:
2.
Of course, you can also do the opposite, i.e. display only segments that are not number only
by selecting Excluding number only from the Display dropdown list. This is especially
useful when translating e.g. technical documentation in which segments can be surrounded
by a lot of numbers.
3.
Last, switch back to the default All segments to display the entire document again.

Display Filter
SUMMARY
10-8
SDL Trados Studio 2014 can automatically track changes similar to Microsoft Word, i.e. deleted
words have red strikethrough formatting, insertions are underlined. The track changes feature is
active by default in the Review mode.
For each change you make the system records the change date/time and the change type (i.e.
deletion or insertion).
When you make a modification the segment status changes to Translation Rejected.
When confirming a segment by pressing Ctrl+Enter the segment status is upgraded to Translation
Approved.
You can switch between Hunspell and the Microsoft Word spell check, which leverages the settings
from Word including custom dictionaries.
Corrections made through the spell checker are also marked up as tracked changes.
SDL Trados Studio 2014 features new display filter categories, for example, you can show all
segments that contain tracked changes, all number-only segments, etc.
2013 SDL plc.
S E G M ENT VER I F I CATION

C
Change the pre-configured QA Checker settings
Run the segment verifiers on a translated file using a preconfigured profile
Have QA Checker quickly correct mistakes such as

multiple spaces and repeated words with a simple click
Chapter
11
11
Segment Verification
SEGMENT VERIFICATION SETTINGS

The sample project package comes with a number of pre-configured quality assurance settings, which
include a predefined QA Checker profile.
Reviewing and Changing the Verification Settings

To take a look at the verification settings of our project and to change them, take the following steps:
11-2
1.
Make sure that you are back in the Home tab, then click the Project Settings buton.
2.
In the Project Settings dialog box select Verification -> QA Checker 3.0. Let us take a look at
the verification settings that have been pre-configured for this project.
2013 SDL plc.
3.
Click Segments Verification. As you can see, the QA Checker has been configured to check
for target segments that are longer than the source by 50% or more.
4.
Now click on Inconsistencies. Here you can see that the QA Checker is set to check for
repeated words, e.g. The photo printer printer ....

11
11-3
2013 SDL plc.
11
11-4
5.
Under Punctuation you can see that the QA Checker will check for end punctuation
inconsistencies as well as for multiple spaces.
6.
Let us assume that you would like to add another verification criteria. Imagine the following:
in the past the word Hinterseite (for rear) has been used rather than Rckseite, which is the
approved translation. In order to check whether the incorrect form has been used, active the
Word List check by clicking the corresponding link.
7.
Activate the Check word list check box. Then enter the wrong form and the correct form into
the corresponding text fields.
8.
Click the Action button and select the Add item command from the dropdown list.
9.
To confirm the changed QA settings and to close the Project Settings dialog box click OK.
2013 SDL plc.
11
Running the Verification

Before we run the verification, let us deactivate the track changes function. When QA Checker corrects
mistakes, the corresponding changes would be tracked too. However, let us assume that you do not want
to track small changes such as removal of redundant spaces or repeated words. Therefore, take the
following steps:
1.
Switch to the Review tab, and switch off the track changes mode by clicking Track Changes.
2.
To start the segment verification click the Verify button (or press F8).
3.
When the verification is complete, you will find warning, notes and error icons next to the
segments in which potential problems have been found.
4.
Take a look at the Messages window below the document. This window contains the error
messages, i.e. the reason why an error was thrown as well as the origin, i.e. the verifier that
threw the error, e.g QA Checker 3.0, the Document Verifier, or the Tag verification.
Correcting Errors
Now you will want to go through the list and correct problems wherever necessary. To do this take the
following steps:
1.
Double-click the first message in the Messages window. This opens the Verification Message Details
window, which provides information on the current issue and helps you correct it.

11-5
2013 SDL plc.
11
11-6
2.
The first message points out an end punctuation difference between the source and the
target segment. While the source segment ends on a colon, the target ends on a full stop.
You can now correct this mistake directly in the Target Segment Content text field of the
window: replace the full stop at the end of the target segment with a colon. Then click
Change to apply the correction to your document.
3.
This will go directly to the following message. In this target segment a redundant space has
been detected. This is the kind of problem that QA Checker can correct itself without you
having to type anything. Just click the Change button to correct the target segment and to
proceed to the next message.
2013 SDL plc.
4.
In the next instance a repeated word has been found. This type of error can also be corrected
by QA Checker. All you have to do is click Change.
5.
The next message again points to a multiple space problem. Click Change to have the extra
blank space removed automatically.

11
11-7
2013 SDL plc.
11
6.
This message only points out that the current segment could not be verified because of the
tracked changes that it contains. Click the Ignore button to skip this message.
7.
The three following messages point to the same issue, i.e. these segments could not be
verified as they contain tracked changes. Just click the Ignore button three times to skip
those messages as well.
8.
The next error was thrown by the tag verification, as the picture tag is missing in the target
segment. This is the kind of problem that cannot be corrected in the Verification Message
Details window directly, but has to be fixed in the document itself. For this reason, click Next
to skip this error, which we are going to fix later.
NOTE
Clicking Ignore removes the corresponding message from the Messages window, while Next just
skips the current issue, but leaves the message in the list, so that you can fix the problem later in the
document proper.
11-8
2013 SDL plc.
9.
11
The next message shows that a wrong word form was found according to the word list that
you configured in QA Checker. The Problem Description field provides a recommendation
on what you need to do. Again, this is a type of mistake that can be easily corrected by
clicking Change, which will replace the wrong word with the correct one.
10. Repeat the above step for the next two messages, which point to exactly the same problem.
The last message points to the missing tag problem, which we will fix in the document itself.
Just click Close to close the Verification Message Details window.
11.
Now there should be only one error message left, i.e. the missing picture tag.
12.
Go to the segment in question (i.e. segment 14) in the editor and insert the tag at the
corresponding position using the QuickPlace feature (Ctrl+,). Note that after inserting the
missing tag, the red error icon turns gray. This is because the message is now pending.
Press Ctrl+Enter to confirm the segment.
13.
Now the segment has been set to the Translation Approved status, and the error icon has
disappeared.
NOTE
The verifier does not automatically insert the tag, because in the target segment the tag might have to
be placed in a completely different position. This is why the correction has to be made manually.

How to Specify Settings for the QA Checker

11-9
2013 SDL plc.
11
Display Filtering by Segment Status

Note that the segments that you have changed from the Verification Message Details window have been
set to Draft. This is the default behavior when the track changes feature is toggled off. When toggled on,
changed segments get the status Translation Rejected.
The display filter allows you to filter by segment status. For example, to show only approved translations
select Translation approved from the Display dropdown list, which will show only the segments that you
have approved up to now.
Now select All segments to display all segments again.
Completing the Review

Let us assume that you want to approve all segments except for those that have the Translation Rejected
status. Of course, you could do this by pressing Ctrl+Enter for each unrejected segment. However, there
is a much quicker way to do this. Just take the following steps:
1.
Close the document by pressing Ctrl+F4.
2.
When prompted to confirm, click Yes. This will set all segments that have no tracked
changes to approved.
3.
You should now be back in the Files view. Make certain that the Confirmation Statistics
window is displayed. Note that the project statistics have been updated to reflect the number
of approved/rejected words. The part of the bar chart in red indicates how many words have
been rejected during review.
SUMMARY
C
11-10
Certain kinds of issues reported by QA Checker need to be corrected manually, e.g. missing tags as
you need to decide where exactly to insert the tag in the target language. To go back to a message for
correction in the editor at a later point, just click Next. To remove a message, click Ignore.
2013 SDL plc.
11
The display filter allows you to show only segments with a particular status, e.g. all segments that
have the status Translation Approved.
You can set all segments (which do NOT have the Translation Rejected status) to Translation
Approved just by closing the document any clicking Yes, thereby completing the review and
saving/closing the current document.

11-11
2013 SDL plc.
R E V I E WI NG I N M I CROSOFT
WORD
C
Convert an SDL XLIFF file to Microsoft Word (DOCX)

format for proofreading in Word
Import changes made in Word back into the Studio

format, i.e. SDL XLIFF
Chapter
12
12
Reviewing in Microsoft Word
THE WORD REVIEW SCENARIO

For this exercise we are going to assume the following: you need to delegate the review task for the second
file (i.e. the document on the spell checker topic) to a colleague, since you are not familiar with the subject
matter. However, this colleague is not equipped with SDL Trados Studio 2014. Therefore you want to do
the following:
C
Convert the SDL XLIFF file to Word format
Have your colleague use the track changes function in Word to mark up any changes he or she
makes
Import the changes from the Word file back into the SDL XLIFF document, so that the reviewed
content can later be used to update the TM
SDL Trados Studio 2014 can convert SDL XLIFF files to DOCX, which allows you can seamlessly exchange
the following between Word and Studio:
C
Text
Comments
Tracked changes
Converting SDL XLIFF to DOCX

To convert the second document to DOCX take the following steps:
4-2
1.
Make sure that the Home tab of the application ribbon is displayed and that the second file
(SpellCheckConfiguration.doc.sdlxliff) is highlighted.
2.
Then click the Batch Tasks button. From the list of available batch tasks select Export for
External Review.
3.
On the first screen of the Batch Processing wizard, click Next.
4.
The following page shows the two files that should be exported for external review. Just click
Finish to start the export.
5.
After the export has completed, click Close.
6.
You will now be asked whether you would like to open the folder that contains the exported
file. Click Yes.
2013 SDL plc.
7.
This will open the folder that contains the exported files in Windows Explorer. Double-click
the folder name, i.e. de-DE to show the DOCX file.
8.
This is the file that you need to send to the reviewer. You can do this e.g. by e-mail or FTP
upload, i.e. no packaging in Studio is required for this.
12
The screenshot below shows that the converted files look like in Word. As you can see, the converted files
are presented in a side-by-side view, which allows for easy comparison between source and target
segments.
NOTE
The track changes feature is by default activated for the DOCX files. This allows you to see what the
reviewer actually changed when you receive back the reviewed files.

Now imagine that you are the colleague who does the review in Word, and that you have received the
DOCX file.
The converted document is presented in a similar side-by-side view as SDL XLIFF files in Studio, i.e. you
will find the following information:
C
Segment ID
Segment status
Source segment
Target segment
The Segment status column also provides the matching information, i.e. you can see whether a segment
was, for example, an exact or fuzzy match. This is also indicated by the segment background color.
NOTE
Note that character formatting is not shown. Instead you see the opening and closing pt tags around
the words and expressions to which formatting is applied. pt stands for placeholder tag. Reviewers
should be instructed to avoid editing/deleting the tags. Word - in contrast to Studio - does not offer
any tag protection features. Therefore, reviewers working in Word need to take care to only edit the
text and not delete the tags.
Make the following changes to the document:

1.
Start by making the first change: go to segment 3 and replace the target word Hinweis with
Anmerkung. (BTW: this is the expression that we used in the other document, which we reviewed in
Studio.)

12-3
2013 SDL plc.
12
2.
Now go down to segment 10, and make another change, e.g. replace Korrekturvorschlge with
Verbesserungsvorschlge.
3.
Go down to segment 11. Replace die Anwendung with Word in the target segment.
4.
Go to the last segment. Note that here the source segment contains just the application
name Word, whereas in the target segment you find Microsoft Word. Let us assume that you
do not want to make a correction, but add a comment, e.g.: Note that it is inconsistent to refer
to the application sometimes as Word, then as Microsoft Word. Select the string Microsoft Word
and add a comment as you would do in any other Word document.
TIP
To add a comment in Word switch to the Review tab and click the New Comment button.
5.
Finally, save the document and close it.
Importing the Changes back into SDL XLIFF

Let us now assume that you have received the file from the reviewer who worked in Word. Now you would
like to import any changes applied in Word to your SDL XLIFF document, so that all reviewed content can
be further processed in Studio (e.g. sign-off and update of main translation memories).
4-4
1.
Make sure that the second file (SpellCheckConfiguration.doc.sdlxliff) in the Files view is highlighted.
2.
Then click the Batch Tasks button. From the list of available batch tasks select Update from
External Review.
3.
On the first screen of the Batch Processing wizard, click Next. On the second page click Next
again.
4.
On the third page of the wizard, you need to map the SDL XLIFF file to the reviewed file.
2013 SDL plc.
5.
Then right-click the first file that is listed in the Project File column, and select Add Specific
Review Document from the context menu.
6.
Browse to the folder that contains the reviewed file (i.e.

C:\Users\UserName\Documents\Studio 2014\Projects\Review Sample Project\External
Review\de-DE\SpellCheckConfiguration.doc.review.docx), which you select by double-clicking.
7.
Note that the SDL XLIFF project file has now been matched to the corresponding review file.
Now click Finish, and then Close.
12
Accepting Changes
1.
Double-click the file SpellCheckConfiguration.doc.sdlxliff to open it in the Editor.
2.
Switch to the Review tab, then select With tracked changes from the Display dropdown list.
3.
Segment 3 contains a tracked change. Let us assume that you would like to accept this
change. To do this right-click the crossed-out (i.e. deleted) word, and select Accept Change
from the context menu.
4.
Repeat the above step with the underlined (i.e. inserted) word. Then confirm, i.e. approve
the segment with Ctrl+Enter.

12-5
2013 SDL plc.
12
Rejecting Changes
1.
Take a look at segment 10. Let us assume that you do not agree with the change made here, and
therefore want to reject it. To do this right-click the crossed-out word. Segments that contain
changes by default have the status Translation Rejected.
2.
Then select the Reject Change command from the context menu.
3.
Repeat the above step with the underlined (i.e. inserted) word. Then confirm, i.e. approve
the segment with Ctrl+Enter.
TIP
You can reject changes by pressing Alt+Shift+F9 and accept changes by pressing Ctrl+Shift+F9.
When a change consists of a deletion and an insertion, you have to accept / reject the crossed out
and the underlined expressions separately.
Handling Comments
4-6
1.
Now select With comments from the Display dropdown list. This will show only the one segment
that contains a comment.
2.
Click the Comments tab on the bottom of the application window. This will display the full
comment text and further information on the comment such as the comment date/time.
3.
Let us assume that there is no need for you to act on the comment. Therefore you would just
like to delete it. To do this click the Delete Command toolbar button in the Comments
window.
2013 SDL plc.
4.
12
Close the document by pressing Ctrl+F4. You will then be asked whether you would like to
complete the review. Click Yes, which will set to all segments that do NOT contain tracked
changes to the status Translation Approved and save and close the document.
SUMMARY
C
Reviewers can work on the DOCX file. Text, comments as well as tracked changes can be exchanged
between DOCX and SDL XLIFF.
Any changes made in the DOCX file can also be imported into the SDL XLIFF files after the
reviewer has sent back the revised DOCX file.
You can accept or reject any changes that were made in MS Word.
You can also view any comments that were added in MS Word, and edit or delete them if required.

12-7
2013 SDL plc.
P R O JECT SI G N-O FF

C
Create the return package that contains the reviewed files
Open the return package
Accept all changes and sign-off on the project files
Finalize the project
Chapter
13
13
Project Sign-Off
CREATING THE REVIEWER RETURN PACKAGE

First, let us create a return package to forward the reviewed file. This package is for the person who
ultimately signs off on the files, e.g. the project manager. To create the return package take the following
steps:
13-2
1.
Make sure that you are in the Projects view.
2.
Right-click your project, and then select Create Return Package from the context menu.
3.
In the Create Return Package dialog box the two files that will be included in the return
package are shown. Here you do not need to change anything. Just click Next to continue.
4.
On the following screen click Browse and select the storage location for the return package
and the file name. You can enter a file name of your choice. Note that return packages have
the extension *.sdlrpx, which is added automatically to the file name.
5.
Once the return package creation is complete click the Open Target Folder button. This will
launch Windows Explorer, where you can view the file, attach it to an e-mail or upload it to
an FTP server, etc.
6.
Last, click Close to close the Create Return Package dialog box.
7.
Finally, right-click your project, and then select Mark as Complete from the context menu.
2013 SDL plc.
Project Sign-Off
8.
When you are prompted to confirm completion of the project click Yes. The project should
now be marked as Completed.
9.
To remove the project from the list, right-click it again, select Remove from List from the
context menu, and then confirm with Yes.
13
THE TRAINING SIGN-OFF SCENARIO

In the next step you pretend that you are the person who has received the return package with the reviewed
files. As the person who does the sign-off, you open the return package, import the reviewed files and sign
off on the translation.
To be able to do all this you need to load the project from which the original project package was created.
Note that this is NOT something that you would do in a real-life scenario. The following steps only need
to be taken, so that you can go through the training scenario on your PC, as you are acting both as the
reviewer and the project manager (i.e. the person who signs off on the files), and this is all happening on
the same machine. In a real-life scenario review and sign-off would occur on different PCs.
Loading the Project

To load the original project take the following steps:
1.
Switch to the File tab, then select Open -> Open Project.
2.
Browse for the project files, which you will find in your sample files folder, i.e. ..\Sample
Files\08_Review\Review Sample Project. Select the file Review Sample Project.sdlproj by doubleclicking it. This will add the original project to the Projects view.
By taking the above steps you have prepared your training machine. Now you can simulate the scenario
in which you are the project manager, who does the sign-off.
Importing the Return Package

Now you can import the package with the reviewed files. To do this take the following steps:
1.
Click the Open Package button on the Welcome screen.
2.
In the Open Package dialog box browse for the return package, which you created in the
previous section and select it by double-clicking the file.
3.
In the Open Package dialog box click Finish to extract and import the package content.
4.
After the import is finished, click Close.
Accepting all Changes and Signing Off the Translation

Let us assume that you fully agree with the changes made by the reviewer. Therefore, you just want to
accept all pending changes and then sign-off on the files in one go. To do this take the following steps:
1.
Double-click the project to switch to the Files view.

13-3
2013 SDL plc.
13
Project Sign-Off
2.
Right-click the first file (PhotoPrinter.doc.sdlxliff) and select Open For Sign-off from the
context menu.
3.
This opens the selected document in the Sign-off mode of the editor. This mode is very
similar to the review mode. In this mode, too, the track changes feature is switched on by
default. The main difference is that when you press Cltr+Enter the selected segment is
marked with a Signed Off icon. While being in the first segment press Ctrl+Enter.
4.
After confirming the first segment, you will see the Signed Off icon between the source and
the target segment.
5.
Accept the change that was made in the second segment, and then press Ctrl+Enter again to
confirm it.
6.
Now, rather than going through all segments one by one, let us assume that you would like
to accept all changes in one go. To do this switch to the Review tab, and then select Accept ->
Accept All Changes in Document.
7.
Note that the remaining segments in which changes have been accepted are still marked
with the Translation Rejected icon:
8.
To sign-off on the whole document, press Ctrl+F4 to close it, and then confirm by clicking
Yes in the message box. This will set all segments to Signed Off and save and close the
document.
Apply the above steps to do the following:
13-4
Open the second document
Accept all changes
Complete sign-off
2013 SDL plc.
Project Sign-Off
13
Finalizing the Project

Finalizing the project updates the main TM and generates the target language files in the respective
original format. To finalize our project take the following steps:
1.
Switch to the Projects view.
2.
Select your project and click the right mouse button. From the context menu select Batch
Tasks -> Finalize.

13-5
2013 SDL plc.
13
Project Sign-Off
13-6
3.
This will open the Batch Processing dialog box, where you can see the individual batch tasks
that are going to be performed on the project files. Just click Next to continue.
4.
The following screen shows the project files on which the batch tasks will be performed. Just
click Next again.
5.
On the Settings screen click Translation Memory Updates. This will display what status a
translation unit from an SDL XLIFF file needs to have by default to be used for updating the
TM. For example, Draft TUs will not be used to update the TM. By default, only TUs with
the status Translated, Translation Approved and Signed Off are used for the update task.
6.
Leave these settings unchanged, and click Finish.
2013 SDL plc.
Project Sign-Off
7.
Wait a few seconds and click Close when both batch tasks have been completed.
8.
SDL Trados Studio 2014 creates a report for the update TM task. To view the report switch to
the Reports view. Then click Update Main Translation Memories to display the
corresponding report.
9.
The report highlights the number of TUs that were added, updated, or not included during
the update TM batch task.
13
10. Now switch back to the Projects view. Right-click the project, select Mark as Complete from
the context menu, and then confirm with Yes.
This concludes our sample round-trip, during which you have learned how reviewing files works in SDL
Trados Studio 2014.

13-7
2013 SDL plc.
13
Project Sign-Off
SUMMARY
13-8
The reviewer can create a return package, which includes the reviewed files with all the tracked
changes.
The project manager can open the return package to import the reviewed files.
The reviewed files can be opened in the sign-off mode, which is similar to the review mode, i.e.
changes are tracked by default.
The person responsible for the sign-off (e.g. the project manager) can make changes, reject or
accept changes. It is also possible to accept or reject all changes with a single click.
Confirming segments in sign-off mode applies the Signed Off status to the TUs.
When applying the Finalize task sequence the main TMs are updated using by default the TUs that
have the status Translated, Translation Approved or Signed Off. This task automatically generates an
update TM report.
2013 SDL plc.
S D L P E R F ECTMA TCH

C
Process update projects effectively by leveraging previous

projects for optimal, in-context re-use of existing
translations for update and mid-project update scenarios
Match a particular document to a specific bilingual

reference file
Chapter
14
14
SDL PerfectMatch
ABOUT PERFECTMATCH
SDL PerfectMatch (PM) allows you to match translated, bilingual documents against new source files for
in-context pre-translation. This is a highly reliable way of leveraging existing content, as the pre-translation
is not done by matching single segments, but by matching entire paragraphs and documents, which
provides a lot more context information. This means that the content re-use is done not on a segment level,
but on a document level.
That way you can be certain that a pre-translated segment always fits into the current context, and (in
contrast to normal 100% matches) does not require further review, proofreading, etc., as translations
inserted by SDL PerfectMatch usually come from previously translated, fully reviewed and signed-off
document.
This makes SDL PerfectMatch ideal for update projects and mid-project updates, i.e. for scenarios in
which:
C
The new project content is to a large extent identical to a previous project, e.g. the documentation
for release 2.2 of a software product has already been translated. Now the documentation needs to
be updated for release 2.3. In this kind of scenario typically only a small portion has to be translated
from scratch.
The customer sends an updated version of the source documentation while the translation is still in
progress (i.e. a mid-project update). You can then stop the translation process and use SDL
PerfectMatch to leverage the content that has already been translated before the mid-project update
occurred. This is done in a reliable and simple way. That way you can be certain to fully re-use all
existing target-language content when processing the updated source files.
In What Way is a PM different from CM (Context Match)?

SDL Trados Studio 2009 introduced the concept of CM (Context Match). A CM is given when the
following conditions are met:
C
The current segment is identical to a previously translated segment stored in the TM.
The segment above the current segment and its translation are identical to a previously translated
document, i.e. the segments occur in the same sequence as in a previous document.
While CM takes only the current and the previous segments into account, SDL PerfectMatch gives you
even more security by matching the paragraphs from a whole documents against the current source file.
CM uses a TM as translation provider, whereas PM relies on previously translated, bilingual documents,
which can be in any of the following formats:
C
SDL XLIFF
TTX (TRADOStag as used in SDL Trados 2007)
ITD (as used in SDLX)
The fact that legacy TTX and ITD files are supported by PM means that you can even leverage projects
done in previous product versions, i.e. SDL Trados 2007 and SDLX.
PREPARING AN UPDATE PROJECT WITH SDL

PERFECTMATCH
In this exercise you will learn how to effectively process an update project with SDL PerfectMatch.
The scenario is as follows:
14-2
In the past you handled version 1.0 of a documentation project with a number of files.
Now you need to translate version 2.0 of the same documentation, and you want to leverage the
existing content in the best possible way.
2013 SDL plc.
SDL PerfectMatch
14
The sample file for this exercise can be found in the following folder: ..\Sample Files\09_PerfectMatch.
Loading the Previous Project

To create your update project take the following steps:
1.
Click the New Project button on the Welcome screen.
2.
On the first the New Project wizard you first need to select the Create a project based on a
previous project radio button.
3.
Then click Browse to search for the previous project.

14-3
2013 SDL plc.
14
SDL PerfectMatch
4.
The previous project can be found in your sample files folder, i.e. ..\Sample
Files\09_PerfectMatch\Previous Project. In this sub-folder, double-click the Spell Checker
Version 1.0.sdlproj project file to select the previous project.
5.
The previous project is now shown in the list of previous projects. Now click Next to
continue.
NOTE
If your previous projects are still listed in as Completed in the Projects view of SDL Trados Studio
2014, then you do not have to browse for the *.sdlproj files to load a project. Any completed project is
shown in the dropdown list and can be picked from there.
Project Details and Languages

1.
14-4
Enter the name of your project into the Name text field, e.g. Spell Checker Version 2.0. Pick a due date
of your choice. Then click Next.
2013 SDL plc.
SDL PerfectMatch
2.
14
All settings have been taken over from the previous project, e.g. the project languages. Just
click Next to continue.
Selecting the Project Source Files

1.
On the Project Files screen click the Add Files button, then browse for the sample source files,
which are located in ..\Sample Files\09_PerfectMatch\New Source Files.
2.
Select the DOC files contained in the folder:

14-5
2013 SDL plc.
14
SDL PerfectMatch
3.
After you have selected the source files click Next to continue.
Selecting TM, AutoSuggest Dictionary and Termbase

1.
14-6
The TM already has been pre-selected, as it is also referenced in the previous project. Typically you
want to use the same TMs for the update project as for the previous project.
2013 SDL plc.
SDL PerfectMatch
2.
The same is true to the AutoSuggest dictionary. Therefore, you do not have to make any
changes on this screen. Just click Next to continue.
3.
Also, the termbase has been taken over from the previous project. Click Next to continue.
NOTE
14
TM, AutoSuggest dictionaries and termbases can, of course, only be used if they have remained in
the same location as they were when the previous project was processed.

14-7
2013 SDL plc.
14
SDL PerfectMatch
Selecting the Previous Files

On the SDL PerfectMatch screen you can see that the new source files have all been matched to the SDL
XLIFF files from the previous project except for the last document. Source files can only be matched
automatically to their previous versions if the names have stayed unchanged. This is not the case for the
last file. In this case, you need to select the SDL XLIFF file manually. To do this take the following steps:
14-8
1.
Right-click the file New_features_2.0.doc, and select Add Previous Document from the context menu.
2.
Browse to the following sub-folder of your previous project: ..\Sample

Files\09_PerfectMatch\Previous Project\de-DE and select the file New_features_1.0.doc.sdlxliff
by double-clicking it.
2013 SDL plc.
SDL PerfectMatch
3.
14
The source file and the corresponding previous file (whose name differs slightly from the
current name) have now been matched.
Update Project or Mid-Project Update

Take a quick look at the Translation transfer options. There two options available:
Apply PerfectMatch and lock: this is the default option, which is recommended for update projects.
The previous translations that are leveraged by PM will be locked (i.e. set to not editable). This is
recommended as the previous content comes from fully finished and signed-off files.
Use the original translation origin status: this option is recommended for mid-project updates, i.e.
when the source files have changed while the translation is still ongoing. You then need to create a
new project for the updated source files. For the new project you will want to re-use as much content
as possible from the previous project, which you had to stop when the updated source files arrived.
In this case you can also use PerfectMatch for in-context pre-translation. However, since the files in
the previous project have (usually) not been signed off and may still contain draft or only partially
reviewed content, you do not want to apply the PerfectMatch status an lock them. This is why this
second option applies the original status, which can be, for example, Draft, Translated, etc.
As we are processing an update project in this exercise, just leave the default Apply PerfectMatch and lock
option activated, and click Next to continue.

14-9
2013 SDL plc.
14
SDL PerfectMatch
PREPARING THE PROJECT

Note that on the Project Preparation screen the default Prepare without project TM task sequence is
selected. This task sequence includes the Apply PerfectMatch batch task, which leverages the previous
documents to pre-translate the new source files.
After that the Pre-translate Files task is executed to leverage any content from the selected TM.
NOTE
If you want a project TM to be created based on your main TM, you need to select the Prepare task
sequence.
To run the task sequence take the following steps:
14-10
1.
Click Finish to start the automatic project preparation.
2.
After all tasks have been completed click Close to close the New Project wizard.
2013 SDL plc.
SDL PerfectMatch
14
Viewing the Project Statistics

Now that the project has been created, make sure that you are in the Projects view. Both your new Spell
Checker Version 2.0 and the previous Spell Checker Version 1.0 projects should be listed.
Click the Confirmation Statistics tab on the bottom of the application window. The bar chart will then
show the following:
C
The number of words that have been have the Not Translated status.
The Translated bar shows the number of words that have been translated using the TM.
The Signed-off bar shows how many words could be leveraged through PM. Note that since content
that is pre-translated by SDL PerfectMatch is highly reliable, the corresponding segments are
automatically set to Signed-off.
Viewing the Project Files

Click the Files view button in the lower left corner of the application window. This will show the project
files with a progress bar. The progress bar indicates how much of a particular file has been pre-translated
either from a TM or from previous bilingual files.

14-11
2013 SDL plc.
14
SDL PerfectMatch
Adding Another File

Let us assume that at this point you receive an additional file that needs to be translated. Your customer
is sending you a Web page in HTML format. Of course, you will want to do the following:
C
Add the HTML file to your project.
Prepare the file the same way all other source files have been prepared, i.e. pre-translation against a
previous file and the TM.
To do the above take the following steps:
14-12
1.
Files can only be added in the source language. Therefore you need to select English (United States)
from the dropdown list in the upper left corner of the application window.
2.
Click the Add Files button.
3.
Browse for the HTML file (Web_Configuration.htm) and select it from the ..\Sample
Files\PerfectMatch\Additional file folder.
4.
The HTML file is now shown in the list of files. However, you need to run the same tasks on
this document as you did with all the other source documents. To do this right-click the file
and select Batch Tasks -> Prepare without project TM from the context menu.
5.
This will open the Batch Processing dialog box, which lists all the batch tasks of the Prepare
without project TM task sequence. Now you need to select the previous document to apply to
the new file. To do this click Next.
2013 SDL plc.
SDL PerfectMatch
6.
To add the previous document, right-click the file Web_Configuration.htm and select the Add
Previous Document command from the context menu.
7.
The previous document is located in the same folder as the HTML file, and is in TTX
format, i.e. Web_Configuration.htm.ttx. Therefore, you need to make certain that
TRADOStag Documents (*.ttx) is selected in the file type dropdown list.
8.
After matching the HTML file to the previous TTX document, click Finish to execute the
batch task sequence. After all tasks have been completed click Close.
9.
Switch back to the target language, i.e. German (Germany). The pre-translated files will
again be listed, the recently added HTML file among them.
14
Viewing the Pre-Translated Files

To see what the files look like after they have been processed by SDL PerfectMatch double the file
Configuration.doc.sdlxliff, thereby opening it in the Editor view.

14-13
2013 SDL plc.
14
SDL PerfectMatch
Below you see an example of what a file that was pre-translated with SDL PerfectMatch looks like:
The segments that were pre-translated by PM are marked as follows:

C
Source and target segments are grayed out and
they are signed-off as the PM matches were already used reviewed and signed-off in the previous
project
PM matches have a PM icon as well as a
lock icon (i.e. the target segment cannot be edited)
The translator or reviewer can focus on the delta, i.e. the segments that have not been pre-translated, while
still being able to see the PM content for reference purposes and for translating and reviewing in context.
The translator or reviewer can focus on the delta, i.e. the segments that have not been pre-translated, while
still being able to see the PM content for reference purposes and for translating and reviewing in context.
At this point we will stop the exercise, as the main point of this chapter was to familiarize you with the
SDL PerfectMatch process. In a real-life scenario you would now create project packages for the translators
to translate the new segments, send the files out for review, and then finalize the project.

About PerfectMatch
SUMMARY
14-14
SDL PerfectMatch (PM) compares previous files to new source files for in-context matching
PM matches new source files to previously translated files in the following formats: SDL XLIFF,
TTX or ITD
PM provides a highly secure way of efficiently handling update projects and mid-project updates, as
PM translations usually do not have to be proofread again. (Never proofread the same sentence
twice.)
PM segments are locked and marked as signed-off.
2013 SDL plc.
I N T E G RA TI O N WI TH SDL
T R A D OS 2007-B A SED SUPPLY
C H A I NS
This chapter provides a number of examples of how to
integrate SDL Trados Studio 2014 into SDL Trados 2007- or
SDLX 2007-based supply chains. You will learn how to:
C
Process pre-translated TTX and ITD files in SDL Trados

Studio 2014
Convert files to TTX, which enables you for processing of

documents in SDL Trados Studio 2014
Process pre-translated Word files in SDL Trados Studio
Chapter
15
15
Integration into SDL Trados 2007-based Supply Chains
GENERAL INFORMATION
For backward compatibility with previous versions such as SDL Trados 2007 or SDLX 2007, SDL Trados
Studio 2014 continues to support the formats TRADOStag (TTX) and SDL Edit (ITD). This allows SDL
Trados Studio 2014 users to process files delivered through SDL Trados 2007- or SDLX 2007-based
workflows, while benefiting from the range of new features that SDL Trados Studio offers, e.g.:
C
Fragment matching through AutoSuggest dictionaries
Multiple TM lookup
Enhanced editing and reviewing environment
Integrated, customizable user interface
NOTE
There is a range of possible scenarios in which SDL Trados Studio users need to be plugged into an
SDL Trados 2007- or SDLX 2007-based supply chain or vice versa. This training workbook can only
familiarize you with the basic principles of exchanging data between SDL Trados Studio 2014 and
SDL Trados 2007/SDLX 2007 environments. It cannot replace consulting for custom workflows.
OPENING TTX FILES IN SDL TRADOS STUDIO 2014

Continued support of TTX/ITD documents in SDL Trados Studio is the basis for exchanging files between
the new SDL Trados Studio 2014 platform and SDL Trados 2007-based systems.
Take the following steps to open a TTX file pre-translated with SDL Trados 2007 in SDL Trados Studio
2014:
1.
Press Ctrl+Shift+O, and then browse to your sample files folder, e.g. Desktop\Sample Files\10_Legacy
Bilingual Formats\TTX and ITD.
2.
Double-click the sample file Configuring_Spelling_Check.htm.ttx. This TTX file was generated
by pre-translating a HTML file in SDL Trados 2007.
NOTE
Processing files in the TTX format also ensures that the segmentation rules of SDL Trados 2007 are
applied, which also ensures that the TM leverage is consistent with SDL Trados 2007. Segmentation
rules differ slightly between SDL Trados Studio 2014 and SDL Trados 2007. For details please consult
the SDL Trados Studio 2014 Migration Guide.
15-2
3.
In SDL Trados Studio, the TTX file will look as follows:
4.
A number of segments have been pre-translated. The match values are shown between the
segment pairs.
5.
Apart from the match value icons, you will often see a green pencil icon with a check mark
between the pre-translated source and target segment pairs. This icon indicates that the
segment has been translated (and confirmed).
6.
Move the mouse pointer over the 100% match icon beside the first source segment. A
tooltip shows that this 100% match has been retrieved from a TM.
2013 SDL plc.
7.
Move the mouse pointer over the 79% match icon beside source segment 3. A tooltip shows
that this match was originally retrieved from a TM, but then edited during interactive
translation.
NOTE
15
SDL Trados Studio 2014 offers a number of status values for segments such as draft, translated,
translation approved, translation rejected, etc. These status values are not supported in SDL Trados
2007. The only status values in SDL Trados Studio 2014 that can be mapped to SDL Trados 2007 are
translated (indicated by a green pencil icon with a check mark) and not translated.
8.
Enter some target text for the untranslated segments 4, 5, and 11.
9.
Save the document by pressing Ctrl+S. This will open a Save As dialog box. A file name is
suggested in the File name text field, i.e. Configuring_Spelling_Check.htm.ttx._en-GB_deDE.sdlxiff. Note that the TTX file will be saved as SDL XLIFF, which is the successor format
to TTX and ITD.
10. Click Save to save the file in the new bilingual interchange format.
11.
Suppose you have fully translated the file. Now you need to generate the original file format
(in this case TTX), so that you can deliver it back into the SDL Trados 2007-based supply
chain. To do this press Ctrl+F12.
12.
This will open the Select File Type dialog box keep TRADOStag Document selected, and
then click OK.
13.
Overwrite the original TTX file by clicking Save.
14.
You can now open the target TTX file in TagEditor, which looks as follows:
OPENING SDLEDIT FILES IN SDL TRADOS STUDIO

SDLEdit (ITD) is the equivalent of TTX in SDLX-based workflows. A pre-translated ITD sample file can
be found in the same sample folder, e.g. ..\Sample Files\10_Legacy Bilingual Formats\TTX and ITD.
TRADOS STUDIO 2014 ADVANCED

15-3
2013 SDL plc.
15
1.
Open the sample file Configuring_Spelling_Check.itd in SDL Trados Studio 2014, which looks as
shown below:
2.
Note the following difference between ITD and TTX files: some of the segments are marked
with a green pencil icon (i.e. pencil icon without a check mark). Move the mouse pointer
over one of the pencil icons. A tooltip shows that this segment is in draft status. This status
is the equivalent of the unconfirmed status in SDLX.
3.
When you save the file by pressing Ctrl+S, an SDL XLIFF file will be generated from the ITD
document.
4.
Suppose you have fully translated the file. Now you need to generate the original file format
(in this case ITD), so that you can deliver it back into the SDL Trados 2007-based supply
chain. To do this press Ctrl+F12.
5.
This will open the Select File Type dialog box keep SDL Edit Document selected, and then
click OK.
6.
Overwrite the original ITD file by clicking Save. The ITD document that you have generated
from SDL Trados Studio 2014 can be further processed in SDLX-based workflows (e.g.
TMS).
SDL TTX IT!

SDL TTX IT! is an OpenExchange Application, which was developed to convert different file formats to
TTX so that the files can be processed in SDL Trados 2007.
Scope of the App

When you want to translate files in SDL Trados Studio 2014 and still deliver files that can be further
processed in SDL Trados 2007-based supply chains, you first need to convert the native files (e.g. DOC)
into TTX (TRADOStag). You can do this, for example, by opening the source files in TagEditor one by one
and save them in TTX format. Those TTX files can then be translated in SDL Trados Studio 2014 and
delivered back as TTX after translation.
Opening and saving a large number of files as TTX in TagEditor can take time and involve a lot of mouse
clicks. This is why we SDL Trados Studio 2014 comes with the SDL TTX It! app, which batch converts
source files to TTX.
15-4
2013 SDL plc.
15
Starting the App

First you need to start the SDL TTX It! app from the Navigation pane of the Welcome screen:
The started app looks as shown below:
Converting Native Files to TTX

In this exercise you will learn how to convert several DOC files to TTX.
The sample files for this exercise can be found in the following folder: ..\Sample
Files\10_OpenExchange\TTXit.
To convert the sample files to TTX follow the steps below:
Click the Browse for file(s) button and select the five DOC files from the above sample folder

15-5
2013 SDL plc.
15
15-6
1.
Click the Browse for file(s) button and select the five DOC files from the above sample folder
2.
Make sure to select the appropriate source language from the dropdown list, e.g. English
(United States).
3.
Click the Convert button. When the conversion process has completed successfully, you see
the Completed message on the bottom of the app window.
2013 SDL plc.
4.
In your sample folder you will now find the TTX files alongside the original DOC files. You
can now process the TTX files in SDL Trados Studio 2014 and deliver TTX target files for
further processing in an SDL Trados 2007-based workflow.
NOTE
15
When converting ML files (XML, SGML or HTML) make sure that the appropriate tag settings file
(INI) is available. To do this click the INI Files button to open the Tag Settings Manager.
BILINGUAL WORD DOCX FILES

SDL Trados Studio 2014 can process bilingual Word files just like it can process TTX and ITD files. This
allows you to plug into SDL Trados 2007-based supply chains even more effectively.
With this enhanced support for legacy bilingual formats you can, for example:
C
Open a bilingual Word file in SDL Trados Studio 2014
Make changes to the bilingual file
Generate a bilingual Word file, which can then be further processed in Microsoft Word and can be
used to update a Translators Workbench translation memory through the clean-up function
The sample file for this exercise can be found in the following folder: ..\Sample Files\10_Legacy Bilingual
Formats\Bilingual Word.

15-7
2013 SDL plc.
15
PROCESSING BILINGUAL DOCX FILES

The above folder contains a sample file named Configuring.docx, which looks as shown below in Microsoft
Word:
This is a fully translated bilingual DOCX file. Translated text colors have been applied to the segments.
For example, source segments are formatted in blue, exact matches in green. The file contains a few
untranslated segments, for which the source content has been copied into the target segment.
TIP
SDL Trados Studio 2014 only displays source segments for which there is a target segment, i.e.
source segments without the tw4win markers will not be shown in Studio. To make certain that all
segments - even the untranslated ones - are properly exposed for translation and editing in Studio,
you may pre-process the file with the pre-translation function of Translators Workbench.
When doing so, make sure that you have selected the Segment unknown sentences option.
15-8
2013 SDL plc.
15
Opening the DOCX File

To open the bilingual sample document take the following steps:
1.
First make sure that the DOCX document is no longer open in Word. Click the Translate Single
Document button on the Welcome screen, or use the keyboard shortcut Ctrl+Shift+O.
2.
Browse for the folder that contains the Configuring.docx sample file and select it by doubleclicking.
3.
The source language of the sample document is English. Therefore, make sure that English
(United States) is selected as source language. The target language should be German
(Germany). This is the language pair used by the sample TM (and the DOCX file).
NOTE
Remove any TMs from previous exercises by clicking the Remove button.
4.
To select the sample TM, which is located in the same folder, click Add -> File-based
Translation Memory.
5.
Double click the sample TM file English-German.sdltm to select it. Then click OK to open the
file in the Editor view.
NOTE
Further resources such as AutoSuggest dictionaries or termbases do not need to be select for this
exercise. But, of course, you can fully use all SDL Trados Studio 2014 features when handling bilingual
DOCX files, e.g. AutoSuggest, Auto-propagate, etc.
6.
The screenshot below shows what the bilingual DOCX file looks like in the Editor view of
Studio.
Note the following:

C
Translated text colors (if applicable) are displayed shown.
Special elements such as fields (e.g. the date and the footnote reference) are shown as inline tags.
Exact matches have the Translated status.

15-9
2013 SDL plc.
15
All other segments (i.e. fuzzy matches and source segments that have been copied into the target
field) have the Draft status.
Translating and Editing the Bilingual DOCX File

1.
With the cursor being in the first segment, click Cltr+Enter to go down to segment 2.
2.
Note that there is a problem in the second segment: the date has been entered using literals
rather than by inserting the field into the target segment. This has now become evident in
Studio, as the field tag, which acts as the placeholder for the date, is missing in the target.
To correct this, highlight the date in the target segment. Then use the shortcut key Ctrl+, and
insert the date field from the QuickPlace by pressing Enter.
3.
Now press Ctrl+Shift+Enter to confirm the segment and move to the next one.
NOTE
At this point we press Ctrl+Shift+Enter to make certain that the cursor is placed inside segment 3. If
you just pressed Ctrl+Enter, segment 3 would be skipped, as it is a confirmed segment.
4.
Segment 3 is a 100% match. Let us assume that no further editing is required. Therefore
press Ctrl+Enter to continue and go to segment 4.
5.
Segment 4 is a segment in which the source content has just been copied into the target
field using the Segment unknown sentences option in Translators Workbench. To quickly
remove the source content press Ctrl+D.
6.
Now enter your translation, e.g.:
7.
Do not forget to apply bold formatting to the corresponding words in your translation by
pressing Ctrl+B.
8.
Now press Ctrl+Alt+Enter 4 times to save segments 4-8 to your TM.
NOTE
Again, here you use Ctrl+Alt+Enter rather than Ctrl+Enter, as this shortcut key would skip all
confirmed segments. Ctrl+Alt+Enter allows you to save all confirmed segments to your TM.
15-10
2013 SDL plc.
9.
15
You should now be in segment 9. The target field for segment 9 also contains a copy of the
source segment. However, in this case a fuzzy match has been found in the TM, as you can
see in the Translation Results window. To copy the suggested translation into the target field,
press Ctrl+T.
10. After applying the translation you need to edit the translation suggestion by adding the
target language equivalent for Win95 or Q4, for example. Do not forget to apply italics
character formatting, e.g. by pressing Ctrl+I.
11.
Now save segments 9 through 13 to your TM by pressing Ctrl+Alt+Enter. Let us assume that
no more changes are required.
Saving the Document

Now that you have finished translating and editing the document take the following steps:
1.
Press Ctrl+S to save your translation.
2.
Like for all documents that you process in Studio, an SDL XLIFF file (Configuring.docx_enUS_de_DE.sdlxliff) will be generated. Click the Save button to save the SDL XLIFF file.
3.
To create the target bilingual DOCX file press Ctrl+F12. This will generate the finished
bilingual DOCX file, which can be used for further processing in a SDL Trados 2007-based
supply chain, e.g. for clean-up in Translators Workbench.
SUMMARY
C
Studio can be plugged into legacy supply chains through continued support of legacy bilingual
formats, i.e. TTX, ITD and bilingual Word files.
When opening a TTX, ITD or bilingual Word document, you can process it in Studio while
leveraging all features such as AutoSuggest. When saving the file as target you can choose to
generate the legacy bilingual format, which can be seamlessly processed in legacy supply chains.

15-11
2013 SDL plc.
O P E N E XCHA NG E APPS
In this chapter you will learn how to use the OpenExchange

apps that are set up when running the SDL Trados Studio 2014
installer. You will learn how to:
C
Find and replace strings in multiple SDL XLIFF files
Translate content that cannot be processed through the

existing file types by going through the Windows
Clipboard
Chapter
16
16
OpenExchange Apps
SDL XLIFF BATCH FIND AND REPLACE

Scope of the App
You can, of course, perform search and replace operations in Studio proper. However, the SDL XLIFF
Batch Find and Replace app is useful when you want to do the following:
C
Run search and replace operations on multiple SDL XLIFF files
Retain the status of changed segments (in Studio changed segments are by default set to draft and
need to be re-confirmed manually) or set the segment status to another value (e.g. Signed Off).
Starting the App

First you need to start the SDL Batch Find and Replace app from the Navigation pane of the Welcome
screen:
The started app looks as shown below:
Adding the SDL XLIFF Files

In this exercise you will learn how to search for and replace a particular term in multiple (fully translated)
SDL XLIFF files.
16-2
2013 SDL plc.
OpenExchange Apps
16
The sample files for this exercise can be found in the following folder: ..\Sample
Files\11_OpenExchange\Batch_Find_Replace.
To run a find or replace operation, you first need to add the SDL XLIFF files to the list of files to process.
1.
Click the Add button in the lower left corner of the app window.
2.
Now the files to process have been added as shown below:
Running a Find Operation

Let us assume the following: you are uncertain of whether the term dialog box has been translated correctly
in the selected files. In order to verify how this term has been translated, you first want to run a find
operation on all selected SDL XLIFF files. To do this take the following steps:

16-3
2013 SDL plc.
16
OpenExchange Apps
16-4
1.
Click the Find tab and enter the term dialog box into the Find what text field.
2.
Click the Find All button. This will display the source and target segments from all SDL
XLIFF files in which the search string has been found on the bottom of the app window.
Note that the search term is highlighted with a yellow background. For each segment the
segment id and the status (e.g. Translated) is displayed. From the search results you can see
that the term dialog box has been translated with Dialogfenster.
2013 SDL plc.
OpenExchange Apps
3.
16
Click the Statistics tab you to see how many occurrences of the search string have been
found and in which file(s).
Running a Replace Operation

Let us assume the following: the target term Dialogfenster is outdated and needs to be replaced with
Dialogfeld. To replace the term in all selected files take the following steps:
1.
Switch to the Replace tab.
2.
In the Find what text field enter the term to replace, i.e. Dialogfenster. Enter the new term, i.e.
Dialogfeld into the Replace with text field.
3.
Click the Replace All button to run the find and replace operation.

16-5
2013 SDL plc.
16
OpenExchange Apps
16-6
4.
On the bottom of the app window all changed occurrences will be listed and highlighted
with a yellow background.
5.
When viewing the files in Explorer note that by default the app creates backup copies of the
changed files, which contain the target segments as they were before you ran the find and
replace operation.
2013 SDL plc.
OpenExchange Apps
6.
16
When you open one of the edited files in Studio you will see that the changed segments have
retained their original status, which in this case is Translated. The changed files can now be
used e.g. for updating your translation memories.
T-WINDOW FOR CLIPBOARD

Scope of the App
T-Window for Clipboard is useful when you need to translate a file format for which no file type is available
in SDL Trados Studio 2014. Example: you need to translate text frames in a CorelDraw file. T-Window for
Clipboard works as follows:
C
You copy text from your native application into the Windows Clipboard
The app will run a search in one or several TMs and provide a match (if any)
The translation can then be pasted into the native application
T-Window for Clipboard provides segment lookup in TMs as well as concordance search.
Starting the App

First you need to start the SDL T-Window for Clipboard app from the Navigation pane of the Welcome
screen:

16-7
2013 SDL plc.
16
OpenExchange Apps
In the following exercise you will learn how to translate a small sample file with T-Window for Clipboard.
The sample file for this exercise can be found in the following folder: ..\Sample Files\11_OpenExchange\TWindow for Clipboard.
Configuring the App Settings

Before you can use the app you need to do the following:
C
Select your language pair
Select one or more TMs
16-8
1.
Click the Options button in the upper right corner of the app window.
2.
In this dialog box make sure that the language pair is set as shown below:
2013 SDL plc.
OpenExchange Apps
3.
To add the sample TM file click the Add button, then select File-based translation memory.
4.
Browse to your sample files folder, i.e. ..\11_OpenExchange\T-Window for Clipboard and select
the sample TM (e.g. Sample_EN-US_DE-DE.sdltm) by double clicking it.
5.
As in Studio proper, TMs can be used for lookup, concordance and update. Click OK to
confirm your selection. Now you can start translating using T-Window for Clipboard.
16
Translating a File Through the Clipboard

You can now close T-Window for Clipboard by clicking the Close button in the upper right corner of the
app window.
This will not actually exit T-Window for Clipboard. The app will still be running in the background. From
this point forward T-Window for Clipboard can be called simply by using the default keyboard shortcut for
copying text into the Windows Clipboard, i.e. Ctrl+C.
Now open the sample text file, i.e. sample.txt from the sample files folder by double-clicking it. This will
show the text file in Notepad.
NOTE
Note that for this exercise we chose a very simple format that can be opened in an application that is
installed on all PCs. In a real-life scenario you may have to open the file e.g. in Adobe Illustrator,
CorelDraw, etc.

16-9
2013 SDL plc.
16
OpenExchange Apps
After you have opened the sample text file take the following steps:
16-10
1.
Highlight the first segment and press Cltr+C.
2.
This will call up T-Window for Clipboard, which displays a 100% match. Press Ctrl+Enter to
confirm. By doing so you will also copy the suggested translation into the Windows
Clipboard.
3.
Switch back to Notepad. While the first segment is still highlighted, press Ctrl+V to paste the
translation into the sample file, thereby overwriting the original segment.
4.
Select the second segment and press Ctrl+C again. This time T-Window for Clipboard
presents two fuzzy matches. The translation suggestion of the first fuzzy match is shown in
the text field in the lower right corner of the app window. Adapt the translation as required
and press Ctrl+Enter.
5.
Switch back to Notepad and press Ctrl+V to overwrite the original segment.
2013 SDL plc.
OpenExchange Apps
6.
Select the third segment in Notepad and press Ctrl+C. This time no match is suggested.
Enter the corresponding translation into the text field in the lower right corner of the app
window as shown below, and confirm it by pressing Ctrl+Enter.
7.
Switch back to Notepad and press Ctrl+V to insert the target segment.
16
Now you have finished translating the small sample file. Note that T-Window for Clipboard is still running
in the background and will be called again whenever you press Ctrl+C. Once you have finished translating
the file you may want to exit T-Window for Clipboard. To do this right-click the corresponding application
icon in the Windows task tray and select Exit from the context menu.
SUMMARY
The SDL Trados Studio 2014 installer deploys four OpenExchange apps in addition to Studio proper:
C
SDL XLIFF Batch Find and Replace for performing a find or find and replace operation on multiple
SDL XLIFF documents at once. This saves you the trouble of running several find and replace
operations on several files and confirming each changed segment.
T-Window for Clipboard for translating file formats that are not supported through file types using
the Windows Clipboard. Pressing Ctrl+C triggers the TM lookup. Ctrl+V inserts the target segment
into the native file.

16-11
2013 SDL plc.
Copyright 2013 SDL plc. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.
SDL enables global businesses to enrich their customers experience through the entire customer journey. SDLs technology and services
help brands to predict what their customers want and engage with them across multiple languages, cultures, channels and devices.
SDL has over 1,500 enterprise customers, 400 partners and a global infrastructure of 70 offices in 38 countries. 42 out of the top 50
brands work with SDL. For more information, visit www.sdl.com.

SDL Trados Studio 2014 Advanced - Workbook

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SDL Trados Studio 2014 Advanced - Workbook

Uploaded by

Copyright:

Available Formats

SDL Trados Studio 2014

Chapter 2: Translation Memory Maintenance

Chapter 3: Language Resources

2013 SDL plc.

Chapter 4: Translation Memory Fields

Chapter 5: TM Search Options and Penalties

Chapter 6: Translating XML Files