SDL Trados Studio Getting Started Part 2 sp1
SDL Trados Studio Getting Started Part 2 sp1
TABLE OF CONTENTS
Chapter 1: Introduction
About this Training Workbook ... 1-2
Chapter
1
Introduction
1
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 easily.
For further product documentation please refer to the SDL Documentation Center.
2
User Defined Settings
2
CUSTOMIZATION
As you can customize the layout of the windows in SDL Trados Studio, you can also customize how text
is shown in the editor or how differences between a match from the TM and the segment in the editor are
marked.
2. This will open the Options window. Select Editor and click on the small plus symbol to
expand the list of options for the editor.
3. Select Font Adaptation from the list to view the available settings.
4. Activate the Adapt Font sizes checkbox and select for example the minimum font size for
text in the source column.
5. Changing the font size might become necessary, if the text in the source document is not
readily readable with a font size of 8 point.
6. Set the minimum font size to 12 for both the source and target language.
7. Set the maximum font size to 18. The maximum font size is useful when the source
document uses very large font sizes in the source text (e.g. 120 points), which would take an
unreasonable amount of space on your screen.
NOTE
D
If you change the setting in the Options dialog, SDL Trados Studio will remember this setting until
you change them again, i.e. for every project you work on after customizing you settings, this settings
will be applied.
Chapter
3
Project Packages
3
Upon opening a project package the files contained therein are automatically extracted, and added to your
SDL Trados Studio environment. The content of the package will appear as a new project in your list of
projects. A project package file carries the extension *.sdlppx.
3. In the Open Package window, browse to the sample files location and select the package file
for your source/target language combination by double-clicking it, e.g. ..\Sample
Files\Packages\Sample_Package_English-German.sdlppx.
5. This window displays, for example, project name, the due date (if any), the total and the
untranslated number of words, the source files to translate contained in the package, etc.
6. After taking a look at the information in this window, click Finish to extract and import the
package content.
TIP
E
The package content is usually extracted into the default project folder, i.e. C:\Users\<User
Name>\Documents\Studio 2019\Projects. Upon extraction of the package, the application creates a
new sub-folder that has the name of the project. If this folder already happens to exist, you will need
to select a different folder, which must be empty.
7. Once the import is complete, click the Close button at the bottom right corner of the Open
Package window.
8. After importing the package content SDL Trados Studio switches to the Projects view.
The project that you have just imported from the package is shown in the Projects list.
2. The Analyze Files report is now displayed on the right-hand side. Take a look at the table
with the heading Totals. This section of the report gives you an overview of all the files
contained in the package.
The package that you have just imported contains two files, an MS Word and an MS PowerPoint
document, which have already been saved to the Studio-internal SDL XLIFF format.
For each file the total number of words is shown in the column Words. A Progress bar indicates whether
a file has pre-translated content. In the above example, the MS PowerPoint document has been 22% pre-
translated by the person who sent you the package.
In addition to the files to translate the sample project package also contains a TM, a termbase, and an
AutoSuggest dictionary. These databases have been automatically added to the project upon opening the
package, and will be used when you translate the files.
Context Matches
Click inside the first segment, which will insert a translation from the TM. This time you get a so-called
context match, which is indicated with a green CM icon in the translation status column. You can also see
that the translation is confirmed.
A context match is better than a 100% match. To be a context match, the translation memory segment
must be a 100% match for the document segment and the two segments must have the same document
context. For the document segment and the translation memory segment to have the same context, they
must both have been preceded by the same segment.
In the example a Context Match is retrieved, as the TM ’knows’ that in a previously translated document
this segment was also found at the beginning of the document.
By default, SDL Trados Studio always suggests the highest match. You can switch between the TM
matches by clicking the Select Next Match and Select Previous Match buttons. This will highlight the
selected match in the Translation Results window and insert the corresponding target segment into the
target cell.
Modify the selected translation to fit the current source segment, then confirm it with Ctrl+Enter to move
to the next segment. For the next segment, the TM has suggested a high fuzzy match. Linguistically the
suggested translation is correct, but it lacks some character formatting. Apply the required character
formatting (bold and italics) by marking the text in the target segment that needs the formatting, pressing
the shortcut key Ctrl+, and selecting the appropriate formatting from the QuickPlace list.
Then confirm the modified translation and move to the next segment.
1. Start translating the current segment, for which no TM match has been found.
2. As soon as you start typing the first letters of the target term for photo printer, a list opens,
and suggests possible translations, e.g. Fotodrucker for photo printer.
In the above example the same translation is suggested from the AutoSuggest dictionary
(the suggestion marked by the green/yellow icon) and from the termbase (the suggestion
marked by the gray icon).
3. You can click any of the suggestions to insert the target term into your translation.
4. You may also use another way of inserting the target terms from the termbase: the second
recognized term in the current segment is color cartridge. To insert the target term into your
translation use the shortcut key combination Ctrl+Shift+L.
5. This will open a list with all termbase suggestions (and only termbase suggestions) relevant
for the current segment. Click the target term for color cartridge in the list (i.e. Farbpatrone) to
insert it into your translation.
1. In the Term Recognition window select one of the displayed source or target terms.
2. Right-click the selected term and select View term details from the context menu.
3. This will slide in the Termbase Viewer window, which displays the full entry and an
alphabetically sorted list of some other terms on the left-hand side.
4. A termbase entry can contain a lot more information than just the terms in the different
languages. Click the term ContraPLUS to view the full entry content.
6. Move the mouse pointer out of the Termbase Viewer window, which will cause it to hide
automatically.
3. While both words are highlighted click the right mouse button on one of the highlighted
terms.
5. A draft entry is now displayed in the Termbase Viewer window. Click the Save this Entry
button to save the new entry in the termbase.
Move the mouse pointer out of the Termbase Viewer window, which will cause it to auto-hide. Confirm
the finished target segment with Ctrl+Enter. When you move to the following segment note that the term
paper is now highlighted with a red bracketed line. This means that you can click the shortcut key
combination Ctrl+Shift+L to open a list of available target terms, among which you will find the translation
for the newly-added term paper.
Inserting Tags
Now we translate segment number 5, for which there is no TM match. It contains a string enclosed in a
bookmark start and end tag pair.
To insert the tags using the keyboard, take the following steps:
1. For this exercise it is useful to display the full tag text. To do this click the Full Tag Text button on the
View tab. Afterwards, go back to the Home tab.
2. Start translating the segment and stop just before you translate the English word clearance,
which is enclosed in bookmark start/end tags.
3. Press the Ctrl+, on your keyboard. This opens a list of possible tags to place at the current
cursor position.
5. Type the target equivalent for clearance, press Ctrl+, again and select the <bookmarkend
name=“clearance“/> tag from the list to insert the second tag into your translation by
pressing the Enter key.
Intentionally leave out both tags, and confirm with Ctrl+Enter to see what happens.
As soon as you confirm the translation a red Error icon will be displayed between the source and target
segment.
Move the mouse pointer over the icon. This will display the reason for the error in a tooltip. In the above
example, you are being warned that you left out both bookmark tags.
Go back to the segment (e.g. with the Up Arrow key on your keyboard) and insert the tags using the Ctrl+,
keyboard shortcut. Then confirm the segment again.
The interactive tag verification is triggered when you confirm a segment. How does SDL Trados Studio
react when you neglect to insert tags, and you do not confirm the segment? Give it a try with the next
segment, which contains a field tag:
Translate the segment without inserting the tag. Then move to the following segment without confirming
it, i.e. simply use the Down key to continue. Observe that although you left out the tag, no warning icon
appears when moving to the next segment, i.e. the interactive tag verification is only triggered when you
confirm a translation.
You can also run a tag verification on the entire document, i.e. also on unconfirmed segments. We will
have a look at this type of verification later, when you have finished translating the document.
For now, translate and confirm the next segment, which consists of a single word (i.e. ventilation). Then
go to the following segment (Connecting and turning on the power).
Adding Comments
You can add comments to particular segments or expressions/words in your translation (not to the source
language segments). This is useful e.g. when you want to:
C Flag a translation that you need to check on later
C Provide information for the reviewer, proofread, project manager, etc.
3. Right-click the highlighted word. From the context menu select Add Comment.
4. In the text area of the Add Comment window enter the comment text, e.g. Ask Dave whether
this is correct. Then click OK.
5. After adding the comment the selected word is highlighted. When you move the mouse
pointer over the highlighted string, the comment text (including the name of the user who
added the comment as well as the date/time) is displayed in a tooltip.
Confirm the segment with Ctrl+Enter, and continue translating the following segments. Let us add
another comment, this time not to a particular string, but to the segment as a whole:
1. After translating the segment, make sure that no particular word is selected.
2. Right-click anywhere inside the segment and select Add Comment from the context menu.
3. Enter the comment text into the Add Comment window, then click OK.
You can also edit existing comments by right-clicking the commented expression/word or segment. Select
Edit Comment from the context menu. In the Edit Comment window click Edit to edit an existing
comment text. With Add you can add another comment to the same segment or expression/word.
TIP
E
If a comment applies to the whole document rather than to a particular string or segment, select
Current File from the Scope dropdown list before adding the comment.
Commented segments and expression/words are highlighted and therefore easy to spot. However, if you
want to see all comments in a document (or several open documents), click the Comments tab.
For each comment you will see the comment text, the name of the document the comment was found in,
the date/time, etc.
Click this button to duplicate the source segment into the target cell. (The default keyboard shortcut is
Ctrl+Ins.) Then confirm the segment with Ctrl+Enter.
The Copy Source to Target function is highly useful for target segments that are identical or very similar
to their source-language counterparts, e.g. sentences that contain a lot of untranslatable product names.
Display Filtering
Suppose you have finished translating the entire document, and you would like to take a particular look at
all segments that have comments. To show only specific segments, take the following steps:
2. By default, the display filter is set to display all segments. Click All segments (i.e. the filter
button) to show the numerous display options.
3. From the available options select Segment Review -> With comments.
4. The Editor now displays only segments with comments, regardless of whether the
comments were added to a selection or to the whole segment. This is useful, for example, if
you want to focus on the commented segments during proofreading.
5. Note that the status bar on the bottom of the application also shows the currently selected
display filter option. Even when the Review tab of the ribbon is not selected, you can
ascertain at a glance which display filter is currently active. Clicking the display filter option
in the status bar opens the display filter list and switches to the Review tab.
When you have checked on a commented segment and found it to be correct, you will certainly want to
delete the comment:
3. This removes the comment from the list and, of course, also from the corresponding
segment.
To display all segments again, go to the display filter dropdown list (on the Review tab) and select General
-> All segments. Make sure all segments in the current document are translated and confirmed. Save the
document with Ctrl+S.
NOTE
D
Comments that were added to a document rather than a word/phrase or segment can only be viewed
in the comments window.
1. In the Review tab click the Verify button (or press F8).
2. If tag errors are found, they will be listed in the Messages window, which will be displayed
instead of Translation Results.
In the above example a missing field tag has caused an Error message.
3. Double-click the message to jump to the segment in which the problem has been found.
NOTE
D
There are three different message types:
Errors (red) are serious problems, which can in a worst-case scenario even prevent you from saving
the translation back in its native format.
Warnings (yellow) point to problems that might, for example, lead to a loss of formatting,
bookmarks, etc., however, that usually do not prevent you from saving the translation in its native
format.
Notes (white) usually point to cosmetic issues such as missing spaces around tags.
4. Insert the missing tag into the highlighted segment, and confirm it with Ctrl+Enter, which
will remove the Error message from the list.
5. Save the file again. For this you can also use the keyboard shortcut Ctrl+S.
2. Note that in the file list the progress for the Microsoft Word document is at 100%, (provided
that you translated and confirmed all segments). Double-click the file
SamplePresentation.ppt.sdlxliff to open it in the Editor view.
The sample presentation is very easy to translate, as it contains only two segments, which are both context
matches. This is because they occur in exactly the same order in the Microsoft Word document that you
previously translated.
Note that as you did not close the previous document, its name is still being shown in a tab in the Editor
view. You can quickly switch back to the first document by clicking the corresponding tab.
In SDL Trados Studio you can have several documents open at the same time. This can be useful, for
example, if you want to quickly check on the translation in a previous document.
2. Right-click the PhotoPrinter Manual project and select Create Return Package from the
context menu.
3. The Progress bars in the Create Return Package window show the translation progress for
each file. They should be at 100%. Click Next to continue.
4. Click Browse and select the location for the return package and the file name. Enter
Photo_Printer_target.sdlprx as return package name. Note that return packages have the
extension *.sdlrpx, which is added automatically to the file name. In the Comment text field
you can enter an optional message for the recipient of the package (i.e. the customer or
project manager).
5. When the return package has been created you can send the return package by clicking the
Send Package by Email button.
6. This will automatically create an email using Microsoft Outlook (if available), and add the
return package as an attachment.
7. You can also choose to click the Open Target Folder button. This will launch Windows
Explorer, where you can view the file, attach it to an email, upload it to an FTP server, etc.
For good measure, mark the project as complete. When you are dealing with multiple projects this will
help you see at a glance which projects are completed, and which ones are still in progress.
1. Right-click the project name in the Projects view, and select Mark as Complete from the context
menu.
Note that the Status column now shows Completed for the sample project.
SUMMARY
C Project packages contain the translatable files, project translation memories and possibly further
elements such as reference files, termbases, etc.
C When opening a project package in Studio the package content needs to be extracted to an empty
folder.
C The project package contains a file analysis reports, which gives an overview of the total number of
words, the repetition and the TM leverage rate, etc.
C You can view the translatable project files in the Files view. From there you can open the files for
translation by double-clicking them.
C After finishing the translation you create a return package, which contains the translated files, and
which can then, for example, be e-mailed to the customer/project manager.
Chapter
4
SDL WorldServer Packages
4
In this chapter you will see how to open a sample package, which has downloaded from SDL WorldServer.
The process of opening the package is identical to opening SDL Trados Studio packages (see previous
chapter).
3. In the Open Package window, browse to the folder that contains the sample packages, i.e.
..\Sample Files\Packages.
4. If you prefer to open a sample package that goes from English into German, then select the
file tasks_Sample_WorldServer_Project_1037_de_DE_xliff. For English into French, select
tasks_Sample_WorldServer_Project_1038_fr_FR_xliff.
6. Wait until the package has been prepared for import, and then click Next again.
7. The following screen shows an overview of the package content, e.g. the total numbers of
words, the files and their respective progress, etc. Click Finish to unpack the project files.
NOTE
D
The package content is usually extracted into the default project folder, i.e. C:\Users\<User
Name>\Documents\Studio 2019\Projects. Upon extraction of the package, the application creates a
new sub-folder that has the name of the project. If this folder already happens to exist, you will need
to select a different folder, which must be empty.
8. Once the import is complete, click the Close button at the bottom right corner of the Open
Package window.
9. After importing the package content SDL Trados Studio switches to the Projects view.
The project that you have just imported from the package is shown in the Projects list.
NOTE
D
Names of files have been downloaded from SDL WorldServer typically contain a sequence of
numbers. This ensures uniqueness of all files in the SDL WorldServer system.
PerfectMatch Segments
The sample file will look as shown below:
Note that segments 1 through 3 are marked with a PM icon, which stands for PerfectMatch. PM matches
are considered highly reliable (even more reliable than context matches), as PerfectMatch takes the context
of a segment into consideration even more than CM matches. For this reason, they are often locked, i.e.
they usually are not supposed to be edited.
However, let us assume that you would like to make a change in segment 3, for example, you would like
to exchange the word weiteres with anderes. Take the following steps:
1. Try to edit target segment 3 accordingly. Note that this is not possible, and a popup message will
inform you that the current segment is locked.
2. However, you can unlock this segment by clicking the Lock Segment - > Unlock segments
command on the Advanced tab. Note that the yellow lock icon has disappeared, and that the
segment text is no longer grayed out. The segment is now available for editing.
4. To restore the lock for the edited segment, click inside segment 3, then click the Lock
Segment -> Lock Segments command. Note that the yellow lock icon has re-appeared next to
the segment and that the segment text is grayed out.
TIP
E
You can also unlock and lock segments by pressing Ctrl+L.
Handling Tags
Continue by translating and confirming 4 and 5. Note that after confirming segment 5, segments 6 and 7
are skipped, as they are already confirmed. Now translate segments 8 through 11. This is mostly a revision
exercise from the Getting Started Part 1 training course.
The sample document contains a few tags, which you should handle as outlined below:
1. Note that segment 12 contains one placeholder tag, which has already been inserted into the target
cell. Files that are pre-processed in SDL WorldServer typically have all tags pre-inserted into the
target segment if no match has been found, as is the case for segment 12.
2. When you get inside segment 12, a translation suggestion will be inserted, and the tag will
be removed. The reason for this is the fact that you have already translated this segment
before, but without the tag. Consequently, a 99% fuzzy match will be automatically inserted.
3. However, you still need to decide where the tag needs to be placed in the target segment.
This is not done automatically, as the position of the tag can be different in the target
language. Use Ctrl+, (i.e. QuickPlace), to insert the tag where it is required to be, and then
confirm the segment.
5. Segment 14 contains a number of tags. Here, it turns out quite useful that SDL WorldServer
has populated empty target cells with the tags. All you need to do is to enter your translation
between the tags.
Finally, you can save the document (by pressing Ctrl+S) and close it (by pressing Ctrl+F4).
1. Make sure that both files in the package are selected, then click Batch Tasks -> WIP Report.
3. The Settings page lists the confirmation levels, match types, and the required type of work.
For example, untranslated segments require translation (of course), while translated
segments require review, and locked segments do not require any type of work. Just take a
look at these settings, as they cannot be changed anyway. Then click Finish.
6. Make sure WIP Report under Multiple Languages is selected. This will display the WIP
report. Scroll down to the section Total in order to view the WIP statistics for the whole
project. As you can see, 13 segments remain to be translated, while 10 translated segments
require review.
7. Let us assume that you are not the one doing the review. Your job is just to finish the
translation. Therefore, switch back to the Files view, and double-click the file
sample_answering_machine8320977215196477423.sdlxliff to open it in the Editor.
Translate the second document, which also contains a number of PerfectMatches. Again, this is largely a
revision exercise, and you can use all the features that you learned in the Getting Started Part 1 training
course.
1. Select both files, and then click the right mouse button.
3. On the first screen of the Create Return Package wizard click Next.
4. There are two ways of delivering your translated files to SDL WorldServer:
C The translations are either uploaded directly to SDL WorldServer from SDL Trados Studio, if
you have a live connection, or ...
C You create a return package file, which you then upload later to SDL WorldServer through the
Web browser.
5. Let us assume that for the moment we have no live connection to SDL WorldServer.
Therefore, we go for the latter option, and create a return package (like we did for the SDL
Trados Studio package in the previous chapter). To do this click the File radio button. This
enables the corresponding text field in which you see the return package file path and name.
NOTE
D
In this training course, we are using a generic package with no live connection to an SLD WorldServer
system. In a real-life scenario, the address of the corresponding SDL WorldServer would be visible in
the Server field, and you could upload your translation directly.
Open the folder in which the return package has been stored in Windows Explorer, i.e.
C:\Users\<UserName>\Documents\Studio 2019\Projects.
There you will find the package file to upload to SDL WorldServer.
TIP
E
The suggested return package names can also be changed.
SUMMARY
C SDL WorldServer creates project packages, which are very similar to the SDL Trados Studio project
packages, and which can be opened in exactly the same way.
C Files that have been processed in SDL WorldServer can also be translated the same way as files that
have been directly opened in SDL Trados Studio. The only difference is that SDL WorldServer
automatically copies any tags into the target cells if no TM match has been found for a particular
segment.
C To deliver your translations you can either create a return package or upload directly to SDL
WorldServer, if a live connection is available. Otherwise, you need to manually upload the return
package to SDL WorldServer using the Web browser.
C PerfectMatches are considered highly reliable translation suggestions, as they fit the current
context.
C You cannot edit locked segments unless you unlock the with the keyboard shortcut Ctrl+L or the
corresponding button.
Chapter
5
Aligning Legacy Files
5
WHAT IS ALIGNMENT?
Alignment is a process that allows you import existing translations into a TM. Imagine that you have an
English source file and the corresponding target document, but the content is not stored in a translation
memory database, as the translation was done without a TM system. Alignment allows you to pre-process
both the source and the target file(s), so that you can import the legacy content into a TM.
The main challenge during alignment is to determine whether segments or entire paragraphs were left
out during translation. Sometimes content is left out, because it is not relevant for the target audience.
Also, translators often change the segmentation, e.g. by translating two source segments with just one
target segment. SDL Trados Studio uses a sophisticated algorithm to detect such discrepancies between
the source and the target content.
The exercises in this chapter involve two scenarios in which English source documents needs to be aligned
with their translations. The sample files for this exercise can be found in your sample files folder, i.e.
..\Sample Files\Alignment.
1. On the Welcome screen of SDL Trados Studio select Align Documents -> Align Single File Pair.
1. Click the Create button, and select New File-based Translation Memory.
2. This will open the New Translation Memory wizard. Enter the name for your TM into the
Name text field, e.g. Alignment TM En-De. Note that the sample files to align are English to
German. Make certain that the correct source and target language pair is selected.
TIP
E
The TM file will be stored at the path that is shown in the Location text field. You may change the TM
location by clicking Browse and selecting another path.
3. Click Next to continue. This will lead you to the Fields and Settings page. It is possible to
store additional meta information in a TM. For example, for each segment pair you can store
the name of the project that it relates to, the customer name, etc. Let us assume that you
would like to add the name of the project to each segment pair that will later be imported
from the alignment into the new TM.
4. To enable your new TM to store the project name, click into the empty field under Name and
enter the field name, i.e. Project.
5. Fields can be of different types, e.g. free text fields, list fields, etc. Let us assume that the
project name should be a free text field. Click into the empty field under Type and select the
option Text.
6. To create the TM click Finish, then Close. The TM name and path is now shown in the Align
Documents window.
1. Click the Browse button below the Source File text field and select the English sample file, i.e.
..\Sample Files\Alignment\English.docx.
2. Repeat the above step for the target file, i.e. ..\Sample Files\Alignment\German.docx.
The column on the left-hand side shows the source segments, the column on the right-hand side lists the
corresponding target segments. The column between source and target segment visualizes the
connections that have been made between source and target content during the alignment process.
You might have noticed that some segment pairs are connected using a green dotted line, while others
show a yellow or red line. The colors indicate how reliable a particular segment pair is considered to be by
the alignment algorithm.
Move the mouse pointer over the id (i.e. 2) of the second segment pair, which has a green line. A tooltip
shows that this particular alignment pair is considered to be of good quality with a trust score of 92.
If you move your mouse pointer over the id of source segment 10, which is connected to target segment
9 with a yellow line, you will see that this segment pair is considered of average alignment quality with a
trust score of 90.
Source segment number 11, which is connected to target segment 10 using a red line, is even considered
of low alignment quality with a trust score of only 50.
NOTE
D
Alignments of average or low quality are not necessarily incorrect. The dotted line color and the trust
score are just indications of how reliable the alignment algorithm is considering a particular segment
pair alignment to be.
To confirm segment pairs that are correct, take the following steps:
1. As you can see, the first segment pair has been aligned correctly. Therefore, click the Confirm
button or press Ctrl+Shift+F.
2. Note that after confirming the first segment pair, a full green line is drawn between the
source and the target segment. Also, the tooltip shows that the segment pair is confirmed
with a trust score of 100.
3. Use the Arrow Down key to move to the second segment pair, which you confirm as well.
Repeat this procedure for segments 3 through 5.
Editing Segments
You can edit the content of source and target segments if necessary. Let us assume that in segment 6 you
would like to replace Preparing Microsoft Word with Setting Up Microsoft Word. All you have to do is
overwrite the source text as required. Make the corresponding change in the target cell, then confirm the
segment pair by pressing Ctrl+Shift+F.
n:n Alignments
Up to this point you have only had clean 1:1 alignments. However, different segmentation between source
and target segments can also lead to, for example, 2:1 alignments, which is the case for source segments
7 and 8, which have both been linked to target segment 7.
In this case, the 2:1 alignment is correct, and you can therefore confirm it. You can also confirm source
segments 9 through 24, as these are all correct alignments.
Splitting Segments
Segment 9 has been correctly linked to segment 8. The segments actually contain two sentences each, as
the semicolon is not regarded as a segment delimiter. Imagine that you would like to replace the
semicolon with a full stop in both languages.
To do this, just edit the source and target segment as required, e.g.:
After editing the segments as shown above, you should split the segments alongside the full stop character
to have the correct segmentation in the TM.
1. First, click the Disconnect button, which will remove the connection between the source and target
segment.
2. Place the cursor behind the full stop, then click the right mouse button, and select the
command Split Segment from the context menu.
4. The split segments should all be disconnected. Click on the segment number 9 of the
source segment, then click the segment number 8. Please make sure to click on the segment
numbers, not on the text.
5. Now click the Connect button to connect the segment pair. Repeat this procedure to connect
source segment 10 to target segment 9.
Most of the remaining segments (down to segment 27) should have been aligned correctly, therefore you
can simply confirm them.
Correcting Misalignments
It can happen that segment pairs are not correctly aligned. This is the case, for example, for source
segment number 28. Click inside source segment 28, which will highlight the target segments to which
it has been linked, i.e. 27 and 28. As you can see, the alignment is not entirely correct. Actually, source
segment 28 should be linked only to target segment 27.
This misalignment has caused a subsequent problem: Source segment 29 has been linked to target
segment 29. However, it should have been linked to target segments 28 and 29.
From segment 30 onwards, the alignment is again correct, see the example below:
NOTE
D
Misalignments can lead to consecutive faults, but usually these remain limited to a specific part of
the text. I.e. a single misalignment does not have an impact on the entire rest of the document.
1. Make sure that you are inside source segment 28, then click the Disconnect button or press
Ctrl+Alt+D.
2. Note that this has removed the connections between source segment 28 and target
segments 27 and 28. Disconnect source segment 29 in the same way. The segment pairs
should now look as shown below:
3. Click the segment number 28 on the source and 27 on the target side. The segments should
now be highlighted with a yellow background:
5. Note that this turns the selected segment pair into a confirmed alignment.
8. Note that the 1:2 connection has been confirmed between source segment 29 and target
segments 28 and 29.
3. As there is no target equivalent for the last source segment, you need to manually insert the
translation into the empty target segment. To do this, right-click inside segment 34. From
the context menu select the command Insert After.
4. Type the target segment into the newly-inserted empty line, then connect segment 35 on the
source side to segment 35 on the target side.
2. You will now be prompted to save the alignment result as an *.sdlalign file. Click Save to
confirm.
1. In the application ribbon select Import into Translation Memory -> Advanced Import.
NOTE
D
The Quick Import option will import the alignment result directly into the TM with a single click. The
Advanced Import allows you to set a number of options before the import is performed.
2. On the first page of the Translation Memory Import wizard click Next.
3. You will now see a few import settings that you can configure. One example is the
Alignment quality value, which is by default set to 0. If you want to have only confirmed
segment pairs to be imported into your TM, you should set this value to 100. If you want to
have segment pairs with an average or low trust score to be imported, then select a value
lower than 100. For this exercise let us keep the alignment quality value unchanged.
4. Remember that we have set up our TM with a Project text field. Let us assume that you would
like each segment pair to feature the name of the project that the aligned documents belong
to, e.g. Alignment Sample. To make sure that this piece of meta information is added to the
imported segment pairs, click the Edit button, which will open the Field Values window.
5. Click inside the empty field below Value, and enter Alignment Sample. Then confirm with
OK.
6. Finally, click Finish to start the import. After a few seconds a message box appears to inform
you how many segment pairs have been added to your TM. Click OK to close the message
box.
1. Click the Translation Memories View button in the Navigation pane to switch to the Translation
Memories view.
3. Browse to the location where you created your TM, and select the TM file by double-clicking
it.
4. The TM content (i.e. the alignment result) is now displayed as shown below:
The segment pairs are shown in a side-by-side view. Take a look at the column on the right-hand side. This
column contains the meta information that has been added to each imported translation unit, i.e.: the
alignment document name, and the Project field value.
1. Switch to the Welcome screen, and select Align Documents -> Align Multiple Files from the
application ribbon.
2. On the first page of the Align Documents wizard click Add -> File-based Translation
Memory.
3. Browse for the TM that you created in the previous section when you aligned the single
document pair, and select it by double-clicking the TM file.
NOTE
D
The alignment results will be stored in a folder, e.g. ..\Studio 2019\Alignment Results. You may select a
different folder by clicking the Browse for folder button.
2. Browse to your sample files location and select the folder ..\Sample Files\Alignment\English.
3. Now select the target folder by clicking the Add button, then select Target Files by Folder.
4. Browse to your sample files location and select the folder ..\Sample Files\Alignment\German.
5. The source and target folders contain various sub-folders. Drill down to
..\English\Desktop\Common. This will reveal the corresponding source and target files.
NOTE
D
The source and target files do not necessarily have to have identical names for the alignment to work.
7. Wait until all documents have been processed, then click Close.
8. You will now be prompted whether to open the folder that contains the alignment result
files. Choose Yes.
9. This will open the folder that contains the alignment results in the form of *.sdlalign files.
For each aligned file pair a bilingual *.sdlalign file has been created, which contains the
actual alignment result.
NOTE
D
You could review each alignment result in Studio, by double-clicking the corresponding *.sdlalign file,
and then confirm and modify the results as required. However, to keep this exercise simple, let us
assume that this time we want to import all alignment result files without reviewing them.
1. Click the Translation Memories View button in the Navigation pane to switch to the Translation
Memories view.
2. The TM from the previous exercise should still be open. Click the Import button in the
application ribbon.
3. In the Import window click Add Folder, and select that folder that contains your alignment
result. All *.sdlalign files will then be listed under Files.
5. The following pages display a number of advanced options, which we leave unchanged.
Therefore, just click Next twice to continue.
6. On the last page of the import wizard click Finish to start the import.
7. Wait a few seconds for the import to finish, then click Close.
1. Make sure that the Home tab of the application ribbon is selected. Then click the Next Page button.
2. This shows the next 50 segment pairs. Click the Next Page button two or three more times to
browse further in your TM.
3. To move back to the previous page click the Previous Page button.
4. Now move back to the first page by clicking the First Page button.
On the bottom of the Translation Memory Settings window you can see the number of translation units:
SUMMARY
C SDL Trados Studio offers an alignment feature through which you can import the content of legacy
source and target documents into a translation memory.
C You can add single file pairs as well as folder structures that contain multiple source and target
documents.
C You can review the alignment result to correct any misalignments. During review you can confirm,
disconnect, and reconnect segment pairs, edit the source and target content, split segments and
insert new, empty segments, which is useful, for example, when the source text contains segments
that are missing in the target language.
C Studio uses different colors (green, yellow and red) to visualize whether a particular segment pair
alignment is considered of good, average or low quality.
C The alignment supports one-to-one as well as one-to-many connections for cases in which, for
example, one source segment has been translated with two target segments.
C After reviewing the alignment result you can import it into the selected TM. When importing you
can choose to apply TM field values, import the alignment result as plain text, set the alignment
quality value, etc.
C You can also import the alignment result (i.e. the *.sdlalign files) directly into the TM without
reviewing it.
Chapter
6
Generating AutoSuggest Dictionaries
6
AutoSuggest dictionaries are created from existing translation memories. The TM input files can be in one
of the following formats:
C *.sdltm
C *.tmx (Translation Memory Exchange)
C *.tmx.gz (compressed TMX format)
For this exercise we provide a TMX sample file, which you can find in your sample files folder. i.e.
..\Sample Files\Generating AutoSuggest Dictionaries.
To create an AutoSuggest dictionary from an existing TMX file, take the following steps:
FREELANCE
T
AutoSuggest dictionaries can only be created with the SDL Trados Studio Professional or the
Freelance Edition with the AutoSuggest dictionary creator add-on. If you have the Freelance Edition
without the add-on, you can use AutoSuggest dictionaries, but you can only create them within the
first 30 days after installation of the product.
2. Make sure that the Home tab is selected. Then click the Create AutoSuggest Dictionary
button.
3. This opens the New AutoSuggest Dictionary window. Here, click the Browse button to select
the TMX input file.
4. In the Open File-based Translation Memory window, make sure that the file type TMX
Translation Memories (*.tmx;*.tmx.gz) is selected in the file type dropdown list.
5. Browse for the sample TMX file from which the AutoSuggest dictionary is to be created, i.e.
Sample EN-GB_DE-DE.tmx.
NOTE
D
The sample file is an English-German TM in TMX format that contains approx. 40,000 TUs.
6. Click Next and wait a few seconds for the TMX file to load.
7. On the next page you can see the language pair of the AutoSuggest dictionary
(i.e. English - > German). Just click Next to continue.
8. On the page AutoSuggest Dictionary Creation Memory Usage the total number of units to
process is displayed. The sample TMX file contains over 40,000 units. You may decide to
reduce the number of units to process. Reducing the number of units to process can be
helpful when processing very large TMs, which could help avoid memory issues. However,
for our sample input file this is not required, as it is relatively small. Therefore, just click
Next to continue.
9. On the following page click Browse and select the location in which the AutoSuggest
dictionary is to be created. Select a location that you can find easily, e.g. your desktop, and
enter a name for the AutoSuggest dictionary file, e.g. EN-DE.
NOTE
D
AutoSuggest dictionary files have the extension *.bpm (for bilingual phrase mapping).
10. Click Finish to start the creation of your AutoSuggest dictionary. Depending on the size of
the TMX file, generation of the AutoSuggest dictionary takes some time (for the sample file
about 3 minutes).
NOTE
D
The AutoSuggest dictionary can only be generated, if your input TM contains 10,000 translation units
or more. TMs with less units do not provide a sufficient basis for reliable phrase extraction.
11. When the generation process is complete, click Close. Open Windows Explorer to view the
newly-created AutoSuggest dictionary file, e.g. EN-DE.bpm.
SUMMARY
C AutoSuggest dictionaries support the translation process by interactively suggesting relevant words
and expressions while you are typing.
C AutoSuggest dictionaries can be generated from a TM or a TM in TMX export format.
C The source TM needs to contain at least 10,000 units (i.e. pairs of source and target segments) for
meaningful phrase extraction.
Chapter
7
Creating Termbases from Excel Glossaries
7
Note that this file already fits the requirements for converting into SDL MultiTerm XML format, i.e.:
C The terms for each language and the values of the descriptive field (i.e. Subject) are listed in separate
columns.
C The column headers contain the label of each language field and the descriptive field. It is
important that the column headers match the names that the fields will have in the SDL MultiTerm
termbase.
1. First, make sure that the file to convert is NOT open in Microsoft Excel.
2. Launch SDL MultiTerm Convert through Start -> All Programs -> SDL MultiTerm 2019.
Then click the SDL MultiTerm 2019 Convert application icon.
3. This will open SDL MultiTerm Convert, which is a wizard application. On the first page of
the wizard, click Next to continue. On the following page click Next again.
4. On the Available conversion options page select Microsoft Excel format from the available
input formats, then click Next.
5. On the Specify Files page you select the file to convert. Click the Browse button and select
the file glossary.xlsx from your sample files location (i.e. ..\Sample Files\Converting_Glossaries)
by double-clicking it. Then click Next.
NOTE
D
The other text fields will be filled in automatically. These contain the names of the output file paths,
most importantly the XML output file, which we will later import into a termbase.
2. Start with the Subject field. Make sure that this field is highlighted in the Available column
header fields list.
3. The Subject column contains descriptive information (i.e. no terms), therefore the
Descriptive fields radio button, which is already pre-selected, applies here. Just change the
value in the dropdown list below from Text to Picklist.
NOTE
D
The data type Text is used for fields that allow for free text, e.g. a definition, note, example, etc. When
you have a limited number of values (e.g. only a limited number of clients), then use the data type
Picklist. This is the likely data type for Subject, as a Subject is usually associated with a limited set of
values, e.g. general, politics, science, etc.
4. Continue with the other columns, i.e. English and German. Let us assume that the terms
listed in the English column should be stored as English (United Kingdom) in the termbase.
To do this make sure that English is selected in the Available column header fields list.
5. Then click the Language field radio button, as English is language, not descriptive
information.
6. From the dropdown list below Language field select English (United Kingdom).
7. Repeat the above step for German, which needs to be assigned to German (Germany).
2. Highlight Subject in the Available descriptive fields list and select Entry level in the Entry
structure box. Then click the Add button.
3. Note that the Subject field has now been added under Entry level and therefore above the
languages. Click Next to continue.
2. This will start the conversion. Wait for the progress bar to indicate that the conversion is
finished.
4. Take a quick look at the sample folder that contains your glossary.xslx file.
SDL MultiTerm Convert has created the following files:
C glossary.xdt: this is the termbase definition file from which we will create a new (empty)
termbase
C glossary.mtf.xml: this is the termbase content, which we will import into the termbase (which
we are going to create in the next step)
1. Switch to the File tab, and then select the New -> Create Termbase.
2. This opens the Save New Termbase window, in which a location and a default name for the
new termbase is already suggested, i.e. New Termbase.sdltlb.
3. Replace the suggested termbase file name with glossary.sdltb, then click Save.
1. This opens the Termbase Wizard. On the first screen of the wizard just click Next to continue.
2. We will now create the new termbase based on the glossary.xdt termbase definition, which
SDL MultiTerm Convert has created. To select this termbase definition click the Load an
existing termbase definition file radio button.
3. Click the Browse button and select the file glossary.xdt from your sample files location.
1. On the Termbase Name page, enter a name for your termbase into the Friendly Name text field, e.g.
User Interface Glossary.
2. You can also skip the next two pages, i.e. Descriptive Fields and Entry Structure by clicking
Next twice.
4. Wait a few seconds for the new termbase to be created. Note that the termbase name is
shown in the application title bar.
1. Click the Termbase Management button on the bottom of the Navigation pane.
2. Right-click Import and then select Process from the context menu.
3. On the first page of the Import Wizard click Browse and select the file glossary.mtf.xml,
which has been created by SDL MultiTerm Convert, from your sample files folder.
4. Then activate the Fast import check box and proceed by clicking Next.
6. Wait for the progress bar to reach 100%. After all entries have been processed click Next,
and then Finish.
7. Switch back to the Terms view, and the terms from the imported entries are now shown in
the Browse list.
SUMMARY
C Glossaries in Excel format can be converted to SDL MultiTerm XML through SDL MultiTerm
Convert, which is a wizard application.
C The field and language names need to be stated in the first row, i.e. in the column headers.
C SDL MultiTerm Convert generates an *.xdt file, which contains the termbase definition and from
which a termbase can be created.
C SDL MultiTerm Convert also generates an *.xml file, which contains the actual entries, and which
can be imported into the termbase.
The exercise in this chapter demonstrates how you can use the
translation memory, the termbase, and the AutoSuggest
dictionary that you created in the previous chapters to translate
a sample document.
Chapter
8
Leveraging Legacy Resources
8
This document is an updated version of one of the files that you aligned before. Moreover, it also contains
terminology that can be found in the converted glossary.
Make sure that you select the corresponding TM, termbase, and the AutoSuggest dictionary that you
created in the previous chapters.
1. Make sure that your cursor is placed inside the empty target cell of the first segment.
2. Note that you will get a translation suggestion, which is marked as a 99% fuzzy match.
Move the mouse pointer over the icon below the match value in the Translation Results
window.
3. A tooltip will appear to indicates that an alignment penalty of 1% has been applied to current
translation suggestion. Note that this penalty is by default applied to all translation units that
come from an alignment. The purpose of the alignment penalty is to alert the user that the
current translation suggestion comes from an alignment and might not be 100% reliable.
4. However, in this case, the correct translation has been suggested. Therefore, you can
confirm the current segment without making any changes.
NOTE
D
Once an aligned unit has been confirmed during translation, it will be offered as a 100% or even a
CM match the next time that the same segment comes up in a document again.
NOTE
D
The alignment penalty is also the reason why you will find a lot of 99% matches in the analysis report
when you run an analysis on the current file.
2. In the Batch Processing window click Finish, and after the process is complete click Close.
5. Note that most segments can be found in the 95%-99% range, which is due to the
alignment penalty, as most segments will be 100% matches that have a 1% alignment
penalty.
Switch back to the Editor view to translate the rest of the document. For most segments, you will get high
fuzzy matches that require very little or no editing. For the segments that have no TM match, you should
get a number of hits from the termbase and/or from the AutoSuggest dictionary, e.g.:
SUMMARY
C The resources that you generated through alignment of legacy documents and conversion of MS
Excel glossaries can be easily used for processing new documents.
C Translation suggestions that come from an alignment are automatically assigned a penalty of 1% to
alert users to the fact that the current suggestion might not be 100% trustworthy.
C Once you have confirmed a translation suggestion that originates from an alignment, the alignment
penalty will no longer be applied, i.e. the translation will be offered as a 100% or CM match the next
time that the same segment comes up.
Chapter
9
Fuzzy Match Repair
9
Now imagine the following: Studio automatically modifies the suggested target segment to fit the current
context, so that you only have minimal or even no post-editing work. This automatic adaptation of fuzzy
matches is called Fuzzy Match Repair.
The only difference between the previous and the current source segment is the fact the verb has changed
from close to open. After retrieving the suggested translation, you need to manually adapt the target
segment by manually inserting the target-language equivalent for the word open.
With Fuzzy Match Repair, the corresponding word in the target segment gets replaced automatically. This
means that you can save even more time when dealing with fuzzy matches. For this to work, of course,
Studio has to ‘know’ where the words to replace are located in source and target. Furthermore, Studio has
to ‘know’ which target-language words to insert. For this Studio can draw from the following sources:
1. Fragments from other segments stored in the TM (in our example, other segments in which the
words open and close occur)
3. Web-based machine translation systems such as SDL Language Cloud (which we will not be
using in this exercise)
1. Press the keyboard shortcut combination Ctrl+Shift+O, and browse to the folder ..\Sample
Files\Studio - Getting Started Part 2\Fuzzy match repair.
2. Select the file Sample_Document.docx. Select English (United Kingdom) as source and
German (Germany) as target language. Use the sample TM that you find in the same folder
as the sample document.
3. Then click the Advanced button in the lower-left corner of the window. In the Project
Template Settings window select Language Pairs -> All Language Pairs -> Termbases. Then
click Use -> File-based MultiTerm Termbase to select the termbase that you find under
..\Sample Files\Fuzzy match repair\Termbase.
5. Select All Language Pairs -> Translation Memory and Automated Translation -> Search.
1. For the first segment you are getting a repaired fuzzy match, which is indicated by the wrench
symbol in the match value box. In this case, the word adding has been replaced with saving. In the
Translation Results window, the changes are not only highlighted for the source segment, but also
for the target segment. This indicates that the target segment has been ‘repaired’ by inserting the
correct term.
2. You might still have to adapt the suggested translation, but you should have less editing
work than if you had to ‘repair’ the whole fuzzy match manually. Edit the segment as
required, and confirm it.
3. For the next segment you are also getting a repaired fuzzy match. The string in TagEditor has
been removed from the source, as this is an outdated product name. Studio has also
removed it from the target. Verify whether the repaired fuzzy match is correct, edit it if
necessary, then confirm it.
4. For segments 3 and 4 you should also get repaired fuzzy match suggestions. Studio has been
able to repair these matches using segment fragments from other translation units in the
same TM. Edit the suggested translations as required, and confirm them.
5. For the last segment you also get a repaired fuzzy match: the outdated product name T-
Window has been replaced with the application. Thanks to the fact that this term has been
found in the termbase, Studio was able to automatically insert the correct target term into
the target segment.
SUMMARY
C Studio can automatically adapt fuzzy matches, which means less manual editing work for you.
C Studio determines which terms have to be changed in the target segments using segment
fragments from other translation unit in the TM, terms from a terminology database, or Web-based
machine translation systems such as SDL Language Cloud.
C Repaired fuzzy matches are highlighted with a wrench symbol to distinguish them from non-
repaired matches.
C For repaired fuzzy matches, the Translation Results window also highlights the changes in the
target segment, so that you can see what automatic fuzzy match repair has changed.
Chapter
10
SDL GroupShare
10
GroupShare facilitates the handling of projects that involve distributed 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. GroupShare logs which files have been checked out by which user. That way you can
transparently trace who currently owns which files. The system thereby effectively avoids conflicts, e.g. two
users changing the same file.
3. In the Add SDL Server window 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. Click Next to proceed to the Authentication page.
5. On the Authentication page SDL Authentication should be selected as Login Provider. Then
enter your user name and password into the corresponding text fields. In order to avoid
being prompted for the password next time you connect, make sure the Remember me
check box is activated.
6. Then click Finish to connect. If you have been successfully connected, then the server
should be shown as Available. Now click Close.
1. Switch to the Welcome screen, and then click Open Trados GroupShare Project.
2. This will raise the Open GroupShare Project window. On the left-hand side you will see a list
of so-called organizations. Projects are usually stored in different organizations (e.g.
Marketing, User Guides etc.), similar to the way files on a hard disk are stored in different
folders.
3. Translators and reviewers can be given access to particular organizations. Let us assume that
the project that you would like to access is called Training Sample Project, which can be
found in the Training organization. To open this server project, select the Training
organization, and then click the corresponding project name. Finally, click Next.
4. On the following page you see that a folder has been suggested into which the project
information file will be downloaded. Leave the suggested location unchanged, and then click
Finish.
NOTE
D
In this step you will NOT download the actual files to translate, but just the project information file.
The files to process need to be downloaded in a separate step (see section below).
5. After the project information has been downloaded to your local PC click Close.
7. Note that the server project is now listed in the application. The project icon with the green
globe indicates that this is a GroupShare Server project.
2. Right-click the first file, and select Check Out from the context menu.
3. Note that after you have checked out the file it is marked with a specific icon, and the name
of the user who has checked out the file is stated in the Checked Out To column. By
checking out the file you have claimed ownership of the document. This means that no
other translator or reviewer can check out the file now. All authorized users can see who has
claimed ownership of a project file.
CHECKING IN FILES
Since checking out a file means that you have downloaded it to your local PC. You can now translate or
edit it just like any other file that you have opened in Studio. After having translated the file you will want
to upload it to the GroupShare Server, i.e. check it in.
1. Make sure that you are back in the Files view. Right-click the file, and then select Check In from the
context menu.
2. This raises the Check In window. Here you may enter an optional comment. Click Check In
to upload the file to the server.
3. Note that by checking in you have released ownership of the file, which is now available to,
for example, a reviewer, an editor, the project manager, etc.
SUMMARY
C SDL GroupShare helps distributed teams to work more effectively on projects.
C To connect to a GroupShare Server you require the server address and a login.
C Once connected to a server you can open projects that have been published and to which you have
access.
C Project files and be downloaded (check out) and uploaded (check in) from/to the server. It is
transparent to all those involved who is currently working on which file.
Chapter
11
The SDL AppStore
11
DOWNLOADING AN APP
Imagine you have heard about a useful plugin called Dictionary Plugin, which allows you to look up online
dictionaries directly from Studio. To download the plugin take the following steps:
1. Enter the name of the plugin into the search field, i.e. Dictionary Plugin, then press Enter.
2. Click the icon of the corresponding plugin that appears in the search result(s).
3. Then click Download. You will then be prompted to log in with your SDL user account, or to
sign up if you have no account with SDL. After logging in you will be able to download the
plugin to your PC.
INSTALLING A PLUGIN
To safe you the trouble of downloading, we have already placed the plugin into your sample files folder,
i.e. ..Studio - Getting Started Part 2\Apps. There you will find the *.sdlplugin file, which you need to double-
click. This will open the SDL Plugin Installer:
3. Select the version of Studio for which the plugin should be installed
4. On this screen, you can also decide in which folder the plugin should be installed. The
option All your domain machines will deploy the plugin to a roaming folder, so that you can
use it from any PC in a local network. The option Local machines will put the plugin to a
folder that is only accessible on the local PC. Select your preferred deployment option, then
click Next.
NOTE
D
If you have several versions of Studio installed, you can deploy the plugin to all Studio versions.
5. Finally click OK. If Studio is already started, please close the application, and re-start it. The
plugin will only be available after a re-start.
You can now start using the plugin. In case of our sample plugin, you will find an extra button on the
Advanced tab in the Editor view, which you can use to look up selected terms in Wiktionary.
MANAGING PLUGINS
If you download and install a lot of plugins you might want to get an overview of which plug-ins are
installed, and possibly remove a plugin you no longer need. To manage your plugins take the following
steps:
3. This will open the following window in which you can view information like: installed
plugins, version, author, and a button that allows you to uninstall the corresponding plugin.
SUMMARY
C The SDL AppStore offers a big choice of plugins that add new functionality to your Studio, e.g.
plugins that allow you to look up terms in online dictionaries.
C To download a plugin, you need to have an account with SDL.
C The plugin file can be installed by double-clicking the plugin file. Studio needs to be restarted before
you can access the plugin functionality.
C From the Welcome view you can manage and - if required - uninstall plugins.
Chapter
12
Intermediate Topics - Overview
12
Are you in the know? Find out why the top global companies work with and trust sdl.com.
Follow us on Twitter, LinkedIn and Facebook.
Copyright © 2018 SDL plc. All Rights Reserved. The SDL name and logo, and SDL product and service names are trademarks of SDL plc and/or its
subsidiaries, some of which may be registered. Other company, product or service names are the property of their respective holders.
SDL_Trados_Studio_2019_Getting Started_PT2_EN_A4_240718