SDL Trados Studio 2011 New Features

Training Course
SDL Trados Studio 2011

New Features and Concepts
Innovation Delivered.
Table of Contents
TABLE OF CONTENTS
Chapter 1: Introduction
About this Training Workbook ... 1-2
Initial Startup of the Application ... 1-2
Chapter 2: Reviewing Translated Files
Introduction ... 2-2
The Review Sample Scenario ... 2-2
Opening a Project Package for Review ... 2-2
Opening a File for Review ... 2-4
Selecting your Preferred Spell Checker ... 2-5
Approving Segments ... 2-6
Making Changes ... 2-6
Using the Display Filter ... 2-8
Displaying only Segments with Tracked Changes ... 2-8
Displaying Number only Segments ... 2-9
Summary ... 2-10
Chapter 3: Segment Verification
Enhanced Segment Verification ... 3-2
Reviewing and Changing the Verification Settings ... 3-2
Running the Verification ... 3-5
Correcting Errors ... 3-6
Display Filtering by Segment Status ... 3-10
Completing the Review ... 3-10
Summary ... 3-11
Chapter 4: Reviewing in Microsoft Word
The Word Review Scenario ... 4-2
Starting the SDL XLIFF Converter for Microsoft Office ... 4-2
Converting SDL XLIFF to DOCX ... 4-2
Configuring the Conversion Settings ... 4-3
Reviewing in Microsoft Word ... 4-5
Importing the Changes back into SDL XLIFF ... 4-7
Summary ... 4-10
Chapter 5: Project Sign-Off
Creating the Reviewer Return Package ... 5-2
The Training Sign-Off Scenario ... 5-3
Loading the Project ... 5-3
Importing the Return Package ... 5-3
Accepting all Changes and Signing Off the Translation ... 5-4
Finalizing the Project ... 5-5
Summary ... 5-8
SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

SDL plc Confidential. Copyright
2011 SDL plc.
Table of Contents
Chapter 6: SDL PerfectMatch

About PerfectMatch ... 6-2
In What Way is a PM different from CM (Context Match)? ... 6-2
Preparing an Update Project with SDL PerfectMatch ... 6-2
Loading the Previous Project ... 6-3
Project Details and Languages ... 6-4
Selecting the Project Source Files ... 6-5
Selecting TM, AutoSuggest Dictionary and Termbase ... 6-6
Selecting the Previous Files ... 6-7
Update Project or Mid-Project Update ... 6-8
Preparing the Project ... 6-9
Viewing the Project Statistics ... 6-10
Viewing the Project Files ... 6-11
Adding Another File ... 6-11
Viewing the Pre-Translated Files ... 6-13
Summary ... 6-16
Chapter 7: Pseudo-Translation
About Pseudo-Translation ... 7-2
Pseudo-Translating an Excel File ... 7-2
Creating a Pseudo-translation Project ... 7-2
Configuring the Pseudo-translate Task Settings ... 7-5
Viewing the Pseudo-translated File ... 7-6
Summary ... 7-8
Chapter 8: Support for Bilingual Word Files
General Information ... 8-2
Processing Bilingual DOCX FileS ... 8-2
Opening the DOCX File ... 8-3
Translating and Editing the Bilingual DOCX File ... 8-4
Saving the Document ... 8-6
Further Legacy Support Enhancements ... 8-7
Summary ... 8-8
Chapter 9: AutoText
About AutoText ... 9-2
Adding AutoText Entries ... 9-2
Viewing the AutoText List ... 9-4
Summary ... 9-5
Chapter 10: OpenExchange Apps
SDL XLIFF Batch Find and Replace ... 10-2
Scope of the App ... 10-2
Starting the App ... 10-2
Adding the SDL XLIFF Files ... 10-3
Running a Find Operation ... 10-3
Running a Replace Operation ... 10-5
SDL TTX It! ... 10-7
2011 SDL plc.
Table of Contents

Converting Native Files to TTX ... 10-8
T-Window For Clipboard ... 10-10
Configuring the App Settings ... 10-11
Translating a File Through the Clipboard ... 10-12
Summary ... 10-14
Chapter 11: File Type Enhancements
New and Enhanced File Types ... 11-2
SDL Trados Translators Workbench ... 11-2
Adobe FrameMaker 8-10 MIF ... 11-2
Adobe InDesign CS2-CS4 INX ... 11-2
OpenOffice ... 11-3
Java Resources ... 11-3
Chapter 12: Project Server
About Project Server ... 12-2
Logging In to a Project Server ... 12-2
Publishing a Project on the Server ... 12-3
Checking out Files ... 12-6
Summary ... 12-7
Chapter 13: Compatibility with SDL Trados Studio 2009
Compatibility of Linguistic Resources ... 13-2
Upgrading Projects ... 13-2
Copyright
2011 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.

2011 SDL plc.
INTRODUCTION
This chapter contains a quick overview of the new features in

SDL Trados Studio 2011 and explains the initial startup of the
application.
Chapter
Introduction
ABOUT THIS TRAINING WORKBOOK

This training workbook was designed for existing users of SDL Trados Studio 2009. It helps you get
quickly familiar with the new features of SDL Trados Studio 2011 quickly and efficiently.
SDL Trados Studio 2011 offers the following main advantages over the previous version:
C
Track changes for supporting review processes
Extended support for Microsoft Word-based review processes
SDL PerfectMatch for reliable in-context translation when handling update projects and mid-project
updates
Integration of MS Word spell checker and an enhanced QA Checker
Interactive character count for better adherence to length restrictions
Pseudo-translation for testing documents for common localization problems before the actual
translation takes place
Enhanced legacy format support - bilingual Microsoft Word files
Keyboard shortcut for adding AutoText entries on the fly
OpenExchange utilities: SDLXLIFF to Microsoft Word conversion app, batch find/replace

functionality for SDLXLIFF files, T-Window for Clipboard
File type enhancements: substantially improved filters for Adobe InDesign CS2-CS4 (INX), Adobe
FrameMaker MIF, Java Properties, and completely re-designed Open Office file types
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.
INITIAL STARTUP OF THE APPLICATION

After installation, start SDL Trados Studio 2011 by clicking the corresponding application icon. To do this
take the following steps:
1.
1-2
Select the program group All Programs -> SDL -> SDL Trados Studio 2011 and click the SDL Trados
Studio 2011 application icon.
2011 SDL plc.
Introduction
2.
When starting the application for the first time, you need to activate the product. To do this
click the Activate button.
3.
Enter or paste the activation code that you have received into the Activation code text field,
then click the Activate button again.

1-3
2011 SDL plc.
Introduction
NOTE
You may use alternative activation options (e.g. a license server) if applicable. If this is the case, click
the Alternative activation options link, which will open the window shown below. Select the activation
option that is relevant for you and follow the instructions on the screen.
4.
1-4
After successful activation of the product the setup wizard of SDL Trados Studio 2011 will
open. On the welcome screen just click Next.
2011 SDL plc.
Introduction
5.
On the Current User Details screen The Name text field should already be pre-filled. Enter
your e-mail address, which is mandatory information. Then click Next.
6.
You can leave the Default setting on the User Profile unchanged and click Next to continue.

1-5
2011 SDL plc.
Introduction
7.
Deselect the Load samples at initial startup option, as the sample project is not required for
this training course. Then click Finish to finish the setup process.
NOTE
The above steps are only necessary when you open the application for the first time.
You will now see the Home screen of SDL Trados Studio 2011:
1-6
2011 SDL plc.
REVIEWING TRANSLATED FILES
This chapter provides examples of how to use the enhanced

review functionality of SDL Trados Studio 2011 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 feature to focus on segments that contain

changes
Chapter
Revieweing Translated Files
INTRODUCTION
SDL Trados Studio 2011 offers the following new features for supporting review processes:
C
Track changes: changes made to a translation are immediately marked using colors and
underline/strikethrough formatting. Moreover, SDL Trados Studio 2011 automatically logs the
change date and the change user for each instance of a target text that was changed.
Enhanced display filter: the display filter has been enhanced to include additional categories, e.g.
show only segments that contain changes.
Seamless integration of Microsoft Word into the review workflow: reviewers can work either in SDL
Trados Studio 2011 or in Microsoft Word. Changes and comments can be exchanged seamlessly
between both applications using a dedicated conversion tool.
THE REVIEW SAMPLE SCENARIO

During the following exercises you will learn to use the new features of SDL Trados Studio 2011 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\01_Review.
Opening a Project Package for Review

To open the project package take the following steps:
2-2
1.
On the Home 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.
2011 SDL plc.
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 2011 environment.
4.
This will open the Browse for Folder dialog box. Note that the package content needs to be
extracted to an EMPTY folder. The best way to make certain that the target folder is empty is
to create a new one. Therefore, click the Make New Folder button and create an empty folder
e.g. on your Desktop.
5.
After the package content has been successfully extracted to your folder, click Close.

2-3
2011 SDL plc.
6.
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.
Opening a File for Review

To open the first file for review take the following steps:
2-4
1.
Click the Files button to switch to the Files view, where you will see the project files.
2.
Right-click the first file (PhotoPrinter.doc.sdlxliff) and select the Open For Review command
from the context menu.
2011 SDL plc.
3.
The file to review looks as shown below:
Selecting your Preferred Spell Checker

SDL Trados Studio 2011 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:
1.
Select the Tools -> Options menu command.
2.
In the Options dialog box drill down to Editor -> Spelling.
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.

2-5
2011 SDL plc.
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.
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:
2-6
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.
2011 SDL plc.
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.
Press Ctrl+Enter again to move to the next segment. This time you are getting a message
that prompts you to confirm whether the tracked changes should be accepted or not. If you
accepted the change, the track changes formatting would disappear and the segment will be
set to Translation Approved. Let us assume that you do NOT want to approve the segment
and want to keep the track changes formatting. Therefore click No.
TIP
Whenever a segment contains tracked changes you will be prompted with the above message. To
avoid this simply use the Down key on your keyboard to move to the next segment. That way you will
not have to deal with any warning messages.
NOTE
Tracked changes content is not stored in the TM, i.e. only the final versions are saved in the TM.
7.
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+,.
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.

2-7
2011 SDL plc.
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. 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.
FOR MORE INFORMATION

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

In SDL Trados Studio 2011 the display filter has been enhanced to include a number of new criteria. First,
make certain that the Display Filter toolbar is active. If the toolbar is not displayed, take the following steps:
2-8
1.
Select the View -> Toolbars -> Display Filter menu command.
2.
This will add the Display Filter toolbar to the application.
2011 SDL plc.
3.
Let us assume that you would like to see only those segments that contain tracked changes.
To do this select With tracked changes from the Display dropdown list. The editor now only
shows those segments that contain tracked changes.
TIP
Tracked changes are by default also applied to repetitions through the auto-propagate feature, i.e. if
you change one instance of a repeated segment, the repetitions are marked with tracked changes as
well. This behavior can sometimes be disruptive. If this is the case, then you can disable autopropagation by selecting the Tools -> Options menu command. In the Options dialog box select
Editor -> Auto-propagation, then uncheck the Enable Auto-propagation option.
Displaying Number only Segments

Let us take a look at another new 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.

2-9
2011 SDL plc.

Display Filter Toolbar - Editor View
SUMMARY
2-10
SDL Trados Studio 2011 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. If you confirm a segment that contains tracked changes you are prompted to accept the
changes.
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 2011 features new display filter categories, for example, you can show all
segments that contain tracked changes, all number-only segments, etc.
2011 SDL plc.
SEGMENT VERIFICATION
In this chapter you will learn how to:

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
Segment Verification
ENHANCED SEGMENT VERIFICATION

The sample project package comes with a number of pre-configured quality assurance settings, which
include a predefined QA Checker profile.
In SDL Trados Studio 2011 the segment verification has been enhanced to facilitate moving between the
error messages. Moreover, the segment verification has been improved to allow you to more easily correct
certain types of mistakes (e.g. redundant spaces) with only a click of a button rather than entering the
correction yourself in the editor.
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:
3-2
1.
Select the Project -> Project Settings menu command.
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.
2011 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 ....

3-3
2011 SDL plc.
3-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.
2011 SDL plc.
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.
Deactivate the track changes function by selecting the Tools -> Track Changes -> Toggle Track
Changes On/Off.
TIP
The above menu lists all available track changes-related commands and shortcut combinations, e.g.
F9 to move to the following change and Shift+F9 to move to the previous change.
2.
To start the segment verification select the Tools -> Verify menu command.
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.

3-5
2011 SDL plc.
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.
NOTE
The Document Verifier only points out that the segments with tracked changes could not be verified.
This is the default behavior, i.e. segments that contain tracked changes are not included in the
segment verification.
Correcting Errors
Now you will want to go through the list and correct problems wherever necessary. To do this take the
following steps:
3-6
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.
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.
2011 SDL plc.
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.
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.

3-7
2011 SDL plc.
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.
3-8
2011 SDL plc.
9.
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 two error messages left. The first one being 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

3-9
2011 SDL plc.
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 enhanced display filter of SDL Trados Studio 2011 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:
3-10
1.
Click the Complete Review toolbar button.
2.
When prompted to confirm this action, click Yes. This will set all segments that have no
tracked changes to approved.
3.
Now switch to the Projects View.
2011 SDL plc.
4.
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
SDL Trados Studio 2011 offers enhanced segment verification by opening a Verification Message
Details window that describes the problem found, and gives recommendations (if any).
Some types of errors, e.g. multiple spaces can be easily corrected by clicking the Change button.
Reported issues can also be ignored by clicking the Ignore button. This will take them out of the
Messages list.
Certain kinds of issues 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 later for correction in the
editor just click Next.
The enhanced 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 by clicking the Complete Review toolbar button, thereby completing the review and
saving/closing the current document.

3-11
2011 SDL plc.
REVIEWING IN MICROSOFT
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
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 2011. 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 2011 comes with the SDL XLIFF Converter for Microsoft Office app, with which you
can seamlessly exchange the following between Word and SDL XLIFF:
C
Text
Comments
Tracked changes
Starting the SDL XLIFF Converter for Microsoft Office

First you need to start the app, which can be found in the program group SDL Trados Studio 2011 - >
OpenExchange Apps:
Converting SDL XLIFF to DOCX

The app looks as shown below. To convert the SDL XLIFF file that you want to give to the reviewer, take
the following steps:
4-2
2011 SDL plc.
1.
Click the Add button in the lower left corner of the app window.
2.
The easiest way to retrieve the path of the SDL XLIFF file is to call Windows Explorer from
Studio. To do this make sure that you are in the Files view.
3.
Right-click the file SpellCheckConfiguration.doc.sdlxliff and select Explore Containing Folder

from the context menu.
4.
This will open Windows Explorer, which shows the path in which the target SDL XLIFF files
are located. Copy the file path from Windows Explorer by selecting it in the address line and
press Ctrl+C.
5.
Switch back to SDL XLIFF Converter for Microsoft Office app.
6.
In the Select *.sdlxliff file(s) dialog box browse for the SDL XLIFF file by pasting the path
into the File Name text field. Double click the file SpellCheckConfiguration.doc.sdlxliff. The file
should now be listed in the SDL XLIFF Converter for Microsoft Office app window.
Configuring the Conversion Settings

Before we do the actual conversion to DOCX, let us take a look at some settings. Take the following steps:

4-3
2011 SDL plc.
4-4
1.
Select the Settings tab.
2.
By default, the DOCX output is top-down, i.e. the target segments are shown in a table below
the source. To have a side-by-side view that is similar to the one in Studio, select Side-by-side
from the Select layout type dropdown list.
3.
Note the Prefix option on the bottom of the screen. The names of the converted DOCX files
are by default prefixed with the string Generated_. This prefix is used for automatically
matching the reviewed DOCX documents to the corresponding SDL XLIFF files when the
corrections are imported back into SDL XLIFF later.
4.
Switch back to the Convert to MS Word tab and click the Convert button in the lower right
corner of the app window.
5.
The conversion should only take a few seconds. When the conversion is finished, a message
box opens, which you close by clicking OK.
6.
Switch to Windows Explorer and go back to the folder that contains your target SDL XLIFF
files. In addition to the SDL XLIFF files you will now find a document called
Generated_SpellCheckConfiguration.doc.Preview.docx. This is the document that you send to
the reviewer.
2011 SDL plc.

Now imagine that you are the colleague who does the review in Word, and that you have received the
DOCX file. Open the file in Microsoft Word. The document looks as shown below:
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.
If you are uncertain of which color is used for which match type, then take the following steps:
1.
Go back to the SDL XLIFF Converter for Microsoft Office app.
2.
Click the Settings tab.
3.
On the left-hand side click Colors and segment locking.

4-5
2011 SDL plc.
4.
This will show the background colors used for the different segment/matching categories.
NOTE
When you are sending DOCX files that were generated through conversion from SDL XLIFF to a
reviewer, you may want to take a screenshot of the Settings page and add it as a reference. You may
also customize the background color by clicking the corresponding color on this screen and by
picking another color.
5.
Go back to Microsoft Word. 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.
NOTE
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.
6.
Make certain that the track changes feature in Word is switched on. To active track changes
in Word select the Review tab and click the Track Changes button.
TIP
Of course, you can also review and edit in Word without the track changes feature. However, the point
of this exercise is to show how tracked changes can be imported from DOCX into SDL XLIFF.
4-6
7.
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.)
8.
Now go down to segment 10, and make another change, e.g. replace Korrekturvorschlge with
Verbesserungsvorschlge.
9.
Go down to segment 11. Replace die Anwendung with Word in the target segment.
2011 SDL plc.
10. 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.
11.
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).
To do this take the following steps:
1.
Switch to the SDL XLIFF Converter for Microsoft Office app.
2.
Before we do the actual import, let us change one setting: click the Settings tab, then select
Segment update on the left-hand side.
3.
Activate the check box Update status of segment with tracked changes. By default, segments
with tracked changes keep their status during import. However, let us assume that you want
segments that were change to get the status Translation Rejected (which is what happens
when changes are tracked in Studio). Therefore select Translation Rejected from the
dropdown list.
4.
Switch to the Import from MS Word tab.

4-7
2011 SDL plc.
5.
Click the Add button in the lower left corner of the app window and browse for the SDL
XLIFF file, i.e. SpellCheckConfiguration.doc.sdlxliff. The Select original *.sdlxliff file(s) dialog
box should already point to the correct path, so all you need to do is to double-click the SDL
XLIFF file to select it.
6.
After you have added the SDL XLIFF file, click the AutoMatch button in the upper right
corner of the app window. This will match the SDL XLIFF file to the corresponding (i.e.
reviewed) DOCX file.
TIP
When matching SDL XLIFF to updated DOCX files, it is easiest to keep both types of files in the same
folder. If the DOCX files are stored in a different folder or deviate from the prefix naming convention,
then you have to manually assign the DOCX to the SDL XLIFF file by clicking the ... button and by
browsing for the reviewed DOCX document.
4-8
7.
Now click the Import button in the lower left corner of the app window. When the
conversion is finished, click OK to close the confirmation message box. You can now close
the SDL XLIFF Converter for Microsoft Office.
8.
Switch to the Files View of SDL Trados Studio 2011. Right-click the file
SpellCheckConfiguration.doc.sdlxliff and select Open For Review from the context menu.
9.
The reviewed document now looks as shown below. As you can see the tracked changes
from the DOCX file are fully reflected in Studio.
2011 SDL plc.
10. To focus on the changed segments select With tracked changes from the Display dropdown
list.
11.
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.
12.
Then select the Reject Change command from the context menu.
13.
Repeat the above step with the underlined (i.e. added) word. Then confirm, i.e. approve the
segment with Ctrl+Enter.
TIP
You can reject changes by pressing Atrl+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.
14.
Now select With comments from the Display dropdown list. This will show only the one
segment that contains a comment.
15.
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.
16.
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.

4-9
2011 SDL plc.
17.
Click the Complete Review toolbar button and confirm by clicking Yes. This will set all
segments that do NOT contain tracked changes to the status Translation Approved and save
and close the document.
SUMMARY
4-10
The SDL XLIFF Converter for Microsoft Office app can be used to convert SDL XLIFF files to
DOCX. The DOCX files present a side-by-side view similar to the one in the editor of Studio.
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 be imported into the SDL XLIFF files using the SDL XLIFF
Converter for Microsoft Office app.
2011 SDL plc.
PROJECT SIGN-OFF

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
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:
5-2
1.
Make sure that you are in the Projects view.
2.
While your project is highlighted click the Create Return Package toolbar button.
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 toolbar 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.
While your review project is still highlighted, click the Mark as Complete toolbar button.
8.
When you are prompted to confirm completion of the project click Yes. The project should
now be marked as Completed.
2011 SDL plc.
Project Sign-Off
9.
To remove the project from the list, click the Remove from List toolbar button, then confirm
by clicking Yes.
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.
Select the File -> Open -> Project menu command.
2.
Browse for the project files, which you will find in your sample files folder, i.e.
..\01_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 toolbar button.
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.

5-3
2011 SDL plc.
Project Sign-Off
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:
5-4
1.
Switch to the Files view.
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 (or use the
corresponding toolbar button).
4.
After confirming the first segment, you will see the Signed Off icon between the source and
the target segment.
5.
Press Ctrl+Enter again and then click Yes to sign off the second segment and to accept the
changes.
2011 SDL plc.
Project Sign-Off
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 select the Tools -> Track Changes -> Accept All
Changes in Document menu command.
7.
Note that the segments in which changes have been accepted are now marked with the Draft
icon:
8.
To sign-off on the whole document, click the Complete Sign-off toolbar button, 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:

C
Open the second document
Accept all changes
Complete sign-off
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:

5-5
2011 SDL plc.
Project Sign-Off
5-6
1.
Switch to the Projects view.
2.
Select your project and click the right mouse button. From the context menu select Batch
Tasks -> Finalize.
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.
2011 SDL plc.
Project Sign-Off
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.
7.
Wait a few seconds and click Close when both batch tasks have been completed.

5-7
2011 SDL plc.
Project Sign-Off
8.
SDL Trados Studio 2011 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.
10. Now switch back to the Projects View. Select your project and click the Mark as Complete
toolbar button and then confirm by clicking Yes to set the project to complete.
This concludes our sample round-trip, during which you have learned how reviewing files works in SDL
Trados Studio 2011.
SUMMARY
5-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.
2011 SDL plc.
Project Sign-Off
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.

5-9
2011 SDL plc.
SDL PERFECTMATCH

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
Focus only on the changed and new content in an update

project
Chapter
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:
6-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.
2011 SDL plc.
SDL PerfectMatch
The sample file for this exercise can be found in the following folder: ..\Sample Files\02_PerfectMatch.
Loading the Previous Project

To create your update project take the following steps:
1.
Click the New Project button in the application toolbar.
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.
4.
The previous project can be found in your sample files folder, i.e. ..\02_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.

6-3
2011 SDL plc.
SDL PerfectMatch
NOTE
If your previous projects are still listed in as Completed in the Projects view of SDL Trados Studio
2011, 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

Take the following steps:
6-4
1.
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.
2.
All settings have been taken over from the previous project, e.g. the project languages. Just
click Next to continue.
2011 SDL plc.
SDL PerfectMatch
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 ..\02_PerfectMatch\New Source Files.
2.
Select the DOC files contained in the folder:
3.
After you have selected the source files click Next to continue.

6-5
2011 SDL plc.
SDL PerfectMatch
Selecting TM, AutoSuggest Dictionary and Termbase
6-6
1.
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.
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.
2011 SDL plc.
SDL PerfectMatch
3.
Also, the termbase has been taken over from the previous project. Click Next to continue.
NOTE
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.
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:

6-7
2011 SDL plc.
SDL PerfectMatch
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: ..\05_PerfectMatch\Previous

Project\de-DE and select the file New_features_1.0.doc.sdlxliff by double-clicking it.
3.
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:
6-8
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.
2011 SDL plc.
SDL PerfectMatch
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.
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:

1.
Click Finish to start the automatic project preparation.

6-9
2011 SDL plc.
SDL PerfectMatch
2.
After all tasks have been completed click Close to close the New Project wizard.
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:
6-10
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.
2011 SDL plc.
SDL PerfectMatch
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.
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:

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 to the current project toolbar button.

6-11
2011 SDL plc.
SDL PerfectMatch
6-12
3.
Browse for the HTML file (Web_Configuration.htm) and select it from the
..\02_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.
6.
To add the previous document, right-click the file Configuration.htm and select the Add
Previous Document command from the context menu.
2011 SDL plc.
SDL PerfectMatch
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.
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.
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)

6-13
2011 SDL plc.
SDL PerfectMatch
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.
PM matches are usually skipped. If you try to edit them, a corresponding message will appear:
To translate the current file take the following steps:

1.
Press Ctrl+Enter to move to the next segment. Here you get a fuzzy match from the TM, which you
edit and then confirm.
NOTE
At this point we do not provide detailed information on how to edit fuzzy matches, as we assume that
you already know this from working with SDL Trados Studio 2009 or from previous trainings.
2.
Confirming the second segment will skip all pre-translated 100% and PM matches, which
will bring you right to segment 10, for which no match has been found. Let us assume the
following: since this document only contains very few untranslated segments, you would
like to focus on the delta and hide all pre-translated segments.
3.
To do this make sure that the Display Filter toolbar is active. If this is not the case, activate
the toolbar through the View -> Toolbars -> Display Filter menu command. Then open the
Display dropdown list.
4.
In SDL Trados Studio 2011 the display filter features a number of new options, which can be
useful for update translations. One of them is the Not translated category, which you now
select to hide all translated segments (pre-translated or manually translated and confirmed).
5.
After selecting Not translated from the dropdown list only the two untranslated segments
will be shown. Make use of the AutoSuggest feature, which should already be familiar to
you.
6.
Let us assume that after translating and confirming the new content you would like to do a
quick sanity check on the PM segments. To do this select Context matches and PerfectMatch
from the Display dropdown list.
7.
Although PM segments are locked, you can still edit them if required by unlocking them.
Take a look at segment 11. This segment contains the word da, which is the spelling that
was used before the German spelling reform.
TIP
You can use Ctrl+G and enter the segment number to quickly navigate to a particular segment.
6-14
2011 SDL plc.
SDL PerfectMatch
8.
To update this segment you have to unlock it first by clicking Ctrl+L. After unlocking the
lock icon disappears and the segment is no longer grayed out. Moreover, the word in
question has a wavy underline, which indicates a spelling mistake.
NOTE
Locked segments are by default excluded from the spelling check.

9.
Correct the word and confirm the segment. Note that the segment that you have just
unlocked and edited is no longer marked as a PM. Moreover it is no longer marked with the
icon that indicates that it is signed-off.
10. Repeat steps 8 and 9 for segment 14, which also uses outdated spelling.
11.
Save the document by pressing Ctrl+S and then close it by pressing Ctrl+F4.
12.
Switch back to the Files view and open the file Web_Configuration.htm.sdlxliff by doubleclicking it.
13.
This file looks as shown below. It contains a number of CM, PM and 100% matches. Note
that in this case you see a number of segments with inline formatting tags. This is due to the
fact that the PMs have been taken from a TTX legacy file. However, this does not make any
difference for the target file in the native format.
Now you can continue by doing the following on your own:

C
Finish translating all project files. Use the features that you know from previous courses or from
working with SDL Trados Studio 2009.
Finalize the project and set it to complete. After setting this project to complete it will be available as
a previous project for any subsequent update projects, e.g. when the documentation for the spelling
checker module version 3.0 needs to be localized.

About PerfectMatch

6-15
2011 SDL plc.
SDL PerfectMatch
SUMMARY
6-16
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.
In exceptional cases, PM segments can be unlocked if editing is required.
New display filter categories (e.g. show all not translated segments) help you focus on the parts of a
document that changed or that are new.
2011 SDL plc.
PSEUDO-TRANSLATION

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 2011 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\03_Pseudo_Translation.
Creating a Pseudo-translation Project

To create a pseudo-translation project take the following steps:
7-2
1.
Click the New Project button in the application toolbar.
2.
On the Project Type screen of the New Project wizard click Next.
2011 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.

7-3
2011 SDL plc.
Pseudo-translation
7-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.
2011 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.

7-5
2011 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:
7-6
2011 SDL plc.
Pseudo-translation
1.
Click the Files View button in the Navigation Pane to switch to the files view.
2.
Double click the (pseudo-translated) SpellCheckOptions.xsls.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 back to the Files view.

7-7
2011 SDL plc.
Pseudo-translation
5.
Right-click the (pseudo-translated) SpellCheckOptions.xsls.sdlxliff file and select Explore

Containing Folder from the context menu.
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
7-8
SDL Trados Studio 2011 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%.
2011 SDL plc.
Pseudo-translation
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.

7-9
2011 SDL plc.
SUPPORT FOR BILINGUAL

WORD FILES
C
Open a translated bilingual Microsoft Word (DOCX) file

in SDL Trados Studio 2011
Edit the bilingual DOCX file in SDL Trados Studio 2011
Use the DOCX file content to update your translation

memory
Generate a bilingual DOCX file from SDL Trados Studio

2011 for further processing in SDL Trados 2007-based
legacy supply chains
Chapter
Support for Bilingual Word Files
GENERAL INFORMATION
SDL Trados Studio 2011 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 2011
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\04_Bilingual_Word.
PROCESSING BILINGUAL DOCX FILES

The above folder contains a sample file named Configuring.docx, which looks as shown below when
opened 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 2011 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 preprocess the file with the pre-translation function of Translators Workbench.
8-2
2011 SDL plc.
When doing so, make sure that you have selected the Segment unknown sentences option.
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 Open Document
button in the application toolbar 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.

8-3
2011 SDL plc.
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 2011 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.
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.
8-4
With the cursor being in the first segment, click Cltr+Enter to go down to segment 2.
2011 SDL plc.
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.

8-5
2011 SDL plc.
9.
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 (or use the Translation -> Apply Translation menu command).
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.
Click the Save Document toolbar button 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 select the File -> Save Target As menu command.
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.
At this point we would like to draw your attention to another improvement in SDL Trados Studio 2011,
which may not evident at first glace.
Open the sample folder in Windows Explorer that contains the bilingual Word document and the
corresponding SDL XLIFF file. Note that there no longer is a sub-folder that contains the file type settings.
This sub-folder, which was generated by previous versions, is no longer required, which reduces the
number of files for each project significantly, and therefore facilitates in particular single-file jobs. A subfolder is only generated if you run a batch task, e.g. Analyze Files in order to store the related reports.
8-6
2011 SDL plc.
TIP
Of course, you can use the File -> View In -> Bilingual Word As Target menu command to view the
actual bilingual file in Word.
TIP
SDL Trados Studio 2011 features a distinct file type for bilingual Word files. To view the file type, select
the Tools -> Options menu command. In the Options dialog box go to File Types -> SDL Trados
Translators Workbench.
FURTHER LEGACY SUPPORT ENHANCEMENTS

Support for bilingual Word files is the most prominent, but not the only legacy support improvement in
SDL Trados Studio 2011.
Another enhancement is the embedded SDL Trados 2007/SDLX 2007 infrastructure. This means that
SDL Trados 2007 or SDLX 2007 no longer need to be installed separately to be able to do the following:
C
Alignment
Processing FrameMaker 7 and Interleaf/QuickSilver files
Processing TTX/ITD files
Upgrading translation memories

8-7
2011 SDL plc.
The Home screen now prominently features toolbar buttons to start S-Tagger for FrameMaker, S-Tagger
for Interleaf and WinAlign.
SUMMARY
8-8
SDL Trados Studio 2011 allows you to open bilingual Word files for further processing, thereby
offering enhanced support for legacy supply chains.
You can edit pre-translated bilingual Word files in Studio.
Bilingual Word files are also stored in SDL XLIFF format during processing in Studio.
Studio can generate target bilingual Word files, which can then be further processed in legacy
supply chains, e.g. for updating Translators Workbench TMs through the clean-up function.
2011 SDL plc.
AUTOTEXT

C
Create AutoText entries on the fly for easy insertion of

repeated phrases during translation
Chapter
AutoText
ABOUT AUTOTEXT
SDL Trados Studio 2011 allows you to add so-called AutoText entries on the fly while you are translating.
This is useful for long-winded words and expressions that occur repeatedly in a project. For example,
rather than typing a term like sustainability strategy many times during a translation, you only type it once
and then add it as an AutoText entry. After doing so the term can be automatically inserted through
AutoSuggest.
This is useful when the term is not contained in your AutoSuggest dictionary. Note that AutoSuggest
dictionaries are read-only and cannot be updated on the fly. The AutoText list, however, can be updated at
any point during translation.
The sample file for this exercise can be found in the following folder: ..\Sample Files\05_AutoText.
Adding AutoText Entries

To open the sample document for this exercise take the following steps:
1.
Click the Open Document button in the application toolbar or use the keyboard shortcut
Ctrl+Shift+O.
2.
Browse for the folder that contains the Sample.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.
4.
To select the sample TM, which is located in the same folder, click Add -> File-based
Translation Memory.
NOTE
Remove any TMs from previous exercises by clicking the Remove button.
9-2
2011 SDL plc.
AutoText
5.
Double click the sample TM file English-German.sdltm to select it. Then click OK to open the
file.
NOTE
AutoText can, of course, be used in combination with AutoSuggest dictionaries and termbases.
However, for this exercise no further AutoSuggest sources are required.
6.
The TM will give you context matches for the first two segments. For the rest of the text we
can assume that we will have to enter the translation for the English term spelling checker
quite often. Therefore, it would be helpful to add the corresponding translation to your
AutoText list. To do this highlight the target term and press Alt+F7.
7.
This will open the Add AutoText Entry dialog box. Note that the selected target term is
already shown in this dialog box. (You could still edit the term in the text field if required.)
However, let us assume that the term is ok as is. Click the Add button to add the entry to the
list field below and finally confirm by clicking OK.
8.
Move to segment 3 and start translating it. When you come to the point at which you start
typing the translation for the term spelling checker, the AutoSuggest list will open to provide
the corresponding AutoText entry. Press Enter to insert the full target term into your
translation.
9.
Finish translating this segment and confirm by pressing Ctrl+Enter.
NOTE
In contrast to suggestions from termbases and AutoSuggest dictionaries the recognition from
AutoText lists will only be triggered when you enter at least four characters. This means that AutoText
entries are only useful for long terms, i.e. terms that are considerably longer than four characters.
10. Confirming segment 3 will automatically translate and confirm segment 4, as a 100% match
has been found.

9-3
2011 SDL plc.
AutoText
11.
Before you translate segment 5, move back to segment 4. Let us assume that you want to
create an AutoText entry for the term Standard-Werkzeugleiste, which is the translation for
standard toolbar. Select the term in the target segment and press Alt+F7.
12.
In the Add AutoText Entry dialog box click Add to add the term to the AutoText list.
13.
Go down to segment 5 and translate it. The AutoText list should now suggest the required
target term when you have typed the first 4 letters. Insert the full term by pressing Enter.
14.
Now finish by translating the rest of the document.
Viewing the AutoText List

To view the entries in the AutoText list take the following steps:
9-4
1.
2.
In the Options dialog box select AutoSuggest -> AutoText.
2011 SDL plc.
AutoText
3.
This will show the previously-added entries on the right-hand side.
4.
You can, of course, also add entries in this window by typing them into the AutoText entries
text field and by pressing the Add button.
TIP
AutoText lists are linked to your user profile, i.e. they are not shared with other users. However, you
may exchange AutoText lists by exporting and importing them.

How to Add AutoText Entries
SUMMARY
C
SDL Trados Studio 2011 allows you to create AutoText entries on the fly by highlighting a string in a
target segment and by pressing Alt+F7.
AutoText entries will only be suggested when you have entered at least 4 characters. This means that
AutoText entries should only be created for terms that have more than 4 characters.

9-5
2011 SDL plc.
OPENEXCHANGE APPS
In this chapter you will learn how to use the OpenExchange

apps that are set up when running the SDL Trados Studio 2011
installer. You will learn how to:
C
Find and replace strings in multiple SDL XLIFF files
Convert files to TTX for plugging SDL Trados Studio

2011 into SDL Trados 2007-based supply chains
Translate content that cannot be processed through the

existing file types by going through the Windows
Clipboard
Chapter
10
10
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 app, which can be found in the SDL Trados Studio 2011 - > OpenExchange Apps
program group:
The started app looks as shown below:
10-2
2011 SDL plc.
OpenExchange Apps
10
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.
The sample files for this exercise can be found in the following folder: ..\Sample
Files\06_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:

10-3
2011 SDL plc.
10
OpenExchange Apps
10-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.
2011 SDL plc.
OpenExchange Apps
3.
10
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.

10-5
2011 SDL plc.
10
OpenExchange Apps
10-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.
2011 SDL plc.
OpenExchange Apps
6.
10
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.
SDL TTX IT!

Scope of the App
When you want to translate files in SDL Trados Studio 2011 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 2011 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 2011 comes with the SDL TTX It! app, which batch converts
source files to TTX.
Starting the App

program group:

10-7
2011 SDL plc.
10
OpenExchange Apps
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\06_OpenExchange\TTXit.
To convert the sample files to TTX follow the steps below:
1.
10-8
Click the Browse for file(s) button and select the five DOC files from the above sample folder.
2011 SDL plc.
OpenExchange Apps
2.
Make sure to select the appropriate source language from the dropdown list, e.g. English
(United Kingdom).
3.
Click the Convert button. When the conversion process has completed successfully, you see
the Completed message on the bottom of the app window.
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 2011 and deliver TTX target files for
further processing in an SDL Trados 2007-based workflow.

10
10-9
2011 SDL plc.
10
OpenExchange Apps
NOTE
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.
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 2011. 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 and terminology
recognition.
Starting the App

program group:
10-10
2011 SDL plc.
OpenExchange Apps
10
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\06_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

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:

10-11
2011 SDL plc.
10
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. ..\06_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.
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.
10-12
2011 SDL plc.
OpenExchange Apps
10
After you have opened the sample text file take the following steps:
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.

10-13
2011 SDL plc.
10
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.
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 2011 installer deploys four OpenExchange apps in addition to Studio proper:
10-14
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.
SDL TTX IT for converting one or several native files to TTX format, which allows you to process
the files in Studio and still deliver bilingual document that are compatible with legacy supply
chains.
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.
SDL XLIFF Converter for Microsoft Office for converting SDL XLIFF files to DOCX format, which
can then be further edited by users who do not have Studio, e.g. reviewers.
2011 SDL plc.
FILE TYPE ENHANCEMENTS
This chapter provides a quick overview of file type additions

and enhancements in SDL Trados Studio 2011:
C
SDL Trados Translators Workbench
Adobe FrameMaker 8-10
InDesign CS2-Cs4 (INX)
OpenOffice
Java Resources
Chapter
11
11
File Type Enhancements
NEW AND ENHANCED FILE TYPES

To view the file types currently supported by SDL Trados Studio 2011 take the following steps:
1.
2.
In the Options dialog box click the File Types to display all file types currently offered by SDL
Trados Studio 2011.
The file types that are highlighted in the image below have been added or have been significantly
improved:
SDL Trados Translators Workbench

This file type provides support for bilingual DOC/DOCX files. Chapter 8 provides a concrete example of
how to process bilingual Word files in SDL Trados Studio 2011.
Adobe FrameMaker 8-10 MIF

This updated file type offers substantial improvements over previous versions as well as support for
FrameMaker 10.
Adobe InDesign CS2-CS4 INX

This file type has been re-designed. It now offers better quality and stability for processing of INX files
(InDesign Interchange format). It is now independent of Java, which means that very large INX files no
longer cause problems because of Java out-of-memory exceptions.
11-2
2011 SDL plc.
File Type Enhancements
11
OpenOffice
This completely new file type offers full support of OpenOffice documents, presentations and
spreadsheets on a level that has up to now only been available for MS Office files.
For each OpenOffice file type there are a number of configuration options available, e.g. for
enabling/disabling processing of hidden text, text in conditions, etc.
Java Resources
Like the INX file type, the support for Java Resources has been re-designed for enhanced stability and is
now independent of Java Runtime Environment.
NOTE
You can open SDL XLIFF files generated e.g. from an OpenDocument presentation also in SDL
Trados Studio 2009. However, you cannot generate the target file, as this file type was not supported
in SDL Trados Studio 2009.

11-3
2011 SDL plc.
PROJECT SERVER
This chapter provides a quick overview of Project Server. You

will learn how to:
C
Connect to a Project Server
Publish a project on a server
Check out a file
Chapter
12
12
Project Server
ABOUT PROJECT SERVER

SDL Trados Studio 2011 has the capability to connect to a central Project Server. A Project Server allows
you to do the following:
C
Upload and download files to/from a central server over the Internet or an Intranet
Check in and check out files and track who is currently working on which files and/or projects
Have colleagues take over your projects while you are out of office
Project Server facilitates handling projects that involve larger teams. Rather than sending out package files
to project team members, translators can log on to the server and check out the files that they need to
process. Project Server logs which files have been checked out by which user. That way you can
transparently trace who currently owns which files. Project Server thereby effectively avoids conflicts, e.g.
two users changing the same file.
LOGGING IN TO A PROJECT SERVER

Note that the following exercise is only relevant for you if you have access to a Project Server. To connect
to a Project Server take the following steps:
12-2
1.
Select the File -> Servers menu command.
2.
In the Servers dialog box click Add to add a connection to a Project Server.
3.
In the Add SDL Server dialog box enter the server name into the Server Address text field.
4.
The default port is 80. If the port number needs to be changed, enter the value into the Port
text field.
5.
In this example we assume that SDL authentication is used, therefore make sure that the
Use SDL authentication radio button is selected.
6.
Enter the user name and password that was given to you (e.g. by your administrator).
2011 SDL plc.
Project Server
7.
If you do not want to be prompted for your credentials every time you open the application,
then activate the Do not prompt me again check box.
8.
Then click OK to connect. If you have been successfully connected, then the server should
be shown as Available. Now click Close.
NOTE
12
The above is just an example of how server connection data. This might differ from your setup, e.g.
instead of SDL authentication you might have to use Windows authentication. In that case, you do
not need to enter a user name and password, as your Windows credentials will be used.
PUBLISHING A PROJECT ON THE SERVER

Now that you are connected to the server you can publish projects. They will then become accessible to all
the users who have the required access privileges.
Take the following steps:

12-3
2011 SDL plc.
12
Project Server
12-4
1.
Make sure that you are in the Projects view.
2.
Right-click an existing project, e.g. Spell Checker Version 2.0 and select the Publish to Server
menu command.
3.
In the Publish Project dialog box click the Browse button.
2011 SDL plc.
Project Server
4.
In the Select Location dialog box select the location where you want to publish the project.
(The location or locations are assigned to you by the server administrator.) Then click OK to
confirm.
5.
You should now be back in the Publish Project dialog box. Click Finish to publish the project
on the server. This will automatically upload the project files to the central server, from
where they can be downloaded by the team members.
6.
Wait for the upload and publish process to finish, then click Close.

12
12-5
2011 SDL plc.
12
Project Server
7.
In the Projects view the published project is now marked as a Server project.
CHECKING OUT FILES

Users with the required credentials can now open the server project, e.g. by clicking the Open Server
Project button on the Home screen.
From the Files view they can smoothly check out and after translation/review check in files, which will
then be uploaded to the server. This means that there is no need to distribute files e.g. through e-mail to
team members.
To do this they just have to right-click the file(s) and select the required commands (e.g. Check Out) from
the context menu.

About Server Projects
12-6
2011 SDL plc.
Project Server
12
SUMMARY
C
Project Server helps distributed teams to work more effectively on projects.
To connect to a project server you require the server address and a login.
Once connected to a server you can publish projects, which then become accessible to all team
members with the required credentials.
Project files and be downloaded and uploaded from/to the server. You can easily track who is
currently owning which file(s)

12-7
2011 SDL plc.
COMPATIBILITY WITH SDL

TRADOS STUDIO 2009
This chapter provides a compatibility overview between SDL
Trados Studio 2009 and SDL Trados Studio 2011.
Chapter
13
13
Compatibility with SDL Trados Studio 2009
COMPATIBILITY OF LINGUISTIC RESOURCES

The following linguistic resources are fully compatible between SDL Trados Studio 2009 and SDL Trados
Studio 2011:
C
Translation memories
Termbases
SDL XLIFF files
You can continue to use the above resources in either SDL Trados Studio 2011 or SDL Trados Studio 2009
without any migration or conversion.
NOTE
SDL XLIFF files that contain tracked changes can be opened in SDL Trados Studio 2009, and the
changes can be viewed. However, since SDL Trados Studio 2009 did not support tracked changes,
you cannot process the changes any further, e.g. you cannot accept or reject changes or view
information such as change dates.
Apart from this SDL Trados Studio 2011 can connect to a TM Server 2009 (SP3).
Also note that SDL Trados Studio 2009 and SDL Trados Studio 2011 can be used side-by-side on the same
PC, e.g. for scenarios in which a customer insists that you run a project in SDL Trados Studio 2009.
UPGRADING PROJECTS
Projects that were created in SDL Trados Studio 2009 need to be upgraded for use in SDL Trados Studio
2011. This happens automatically when you open a SDL Trados Studio 2009 project in SDL Trados Studio
2011. To upgrade a project take the following steps:
1.
Select the File -> Open -> Project menu command (or press Ctrl+O) and browse to the sample files
folder that contains a SDL Trados Studio 2009 sample project, i.e. ..\Sample
Files\07_Studio2009_Project.
2.
Select the project file Sample.sdlproj by double clicking it.
3.
This will open an Upgrade Project for SDL Trados Studio 2011 dialog box. Click the Upgrade
button to upgrade the project.
NOTE
This will create an upgraded copy of the project in the location that is specified in the above dialog
box. The upgraded project can no longer be used in SDL Trados Studio 2009. However, a copy of the
original project will by default be kept at the original location.
13-2
2011 SDL plc.
Compatibility with SDL Trados Studio 2009
4.
Make sure that you are now in the Projects view.
5.
Right-click the upgraded project and take a look at the context menu commands for creating
project packages.
13
Note that there are two command for creating packages:

C
Create Project Package: creates packages for use in SDL Trados Studio 2011, which can process both
Studio 2009 and 2011 packages.
Create Studio 2009 Project Package: creates packages for use in SDL Trados Studio 2009, which
can only process Studio 2009 packages.

13-3
2011 SDL plc.

SDL Trados Studio 2011 New Features

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 2011 New Features

Uploaded by

Copyright:

Available Formats

Training Course

SDL Trados Studio 2011

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

2011 SDL plc.

Chapter 6: SDL PerfectMatch

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

SDL plc Confidential. Copyright

2011 SDL plc.

Scope of the App ... 10-7

2011 SDL plc.

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

2011 SDL plc.

This chapter contains a quick overview of the new features in

ABOUT THIS TRAINING WORKBOOK

Track changes for supporting review processes

Extended support for Microsoft Word-based review processes

Integration of MS Word spell checker and an enhanced QA Checker

Interactive character count for better adherence to length restrictions

Enhanced legacy format support - bilingual Microsoft Word files

Keyboard shortcut for adding AutoText entries on the fly

OpenExchange utilities: SDLXLIFF to Microsoft Word conversion app, batch find/replace

INITIAL STARTUP OF THE APPLICATION

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

SDL plc Confidential. Copyright

2011 SDL plc.

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

2011 SDL plc.

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

SDL plc Confidential. Copyright

2011 SDL plc.

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

2011 SDL plc.

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

SDL plc Confidential. Copyright

2011 SDL plc.

REVIEWING TRANSLATED FILES

This chapter provides examples of how to use the enhanced

Track changes in SDL XLIFF files

Select your favorite spell checker

Use the display feature to focus on segments that contain

Revieweing Translated Files

THE REVIEW SAMPLE SCENARIO

Opening a Project Package for Review

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

SDL plc Confidential. Copyright

2011 SDL plc.

Revieweing Translated Files

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

2011 SDL plc.

Revieweing Translated Files

Opening a File for Review

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

SDL plc Confidential. Copyright

2011 SDL plc.

Revieweing Translated Files

The file to review looks as shown below:

Selecting your Preferred Spell Checker

Higher-quality spelling check, i.e. less false errors

Select the Tools -> Options menu command.

In the Options dialog box drill down to Editor -> Spelling.

SDL TRADOS STUDIO 2011 NEW FEATURES AND CONCEPTS

2011 SDL plc.

Revieweing Translated Files

The track changes feature is activated by default.