Hi and welcome to the next instalment of the SDL Trados Studio Video Help series Today I'll translate an English word document into German in SDL Trados Studio and I'll also produce a new Word document containing the translated content. To do this, I'll be using a translation memory to provide us with segment translation suggestions, a termbase which produces term recognition results and an AutoSuggest dictionary which is a resource unique to Studio which provides translation suggestions as you type. Now we've seen where these files are located, we can go over to Studio. We're going to navigate to the Home view and from there in the center of the work pane you can click the Open Document button. The Open Document dialog box will appear and you can choose the Sample Photo Printer Word document from the sample project. When you translate from one language to another you are working with a source and target language, also known as a language pair. So we will choose the translation memory with English as the source language and German as the target language. Click the Add button and select File-based Translation Memory from the drop-down list. Navigate to the sample project folder that contains the sample translation memory. Select the English to German translation memory file. Studio allows you to use more than one translation memory, so if I had another English to German translation memory I could select it as well. Studio will auto detect the source language of the document you are going to translate and it uses the translation memory we selected to determine the target language so there is no need to change anything more at this stage. The Studio Editor view is where documents are translated and reviewed. You can see in the Editor window, the document we chose has been split into segments to be translated with the source segments on the left and the target document on the right. There are several other windows which will be used as we go through the translation process. Now let's look at segment one. You can see that the heading Getting Started has already been translated and confirmed because there was a context match found in the translation memory that we are using. The context match symbol can be seen in the Segment Status column here. You can also see that we are translating a heading by looking at the Document Structure column. Studio will always use this column to give you more information about where you are in the document so you can translate more accurately. Where a document segment and a translation memory segment match exactly and also have the same document context, this is a context match. This automatically inserted translation can also be seen in the Translation Results window, where all the search results from the translation memory are displayed. As we select each translation segment, anything classed as a close match will be displayed here with a percentage to indicate how close the match is to the source segment. Now let's select segment two and well be given another translation suggestion. This time we haven't received a context match or an exact match but rather a partial match which is known as a fuzzy match. A translation with a match of 91% has been inserted to the translation segment. If we look in the Translation Results window we can see there is also an 81% match which has been found during the lookup. The 91% match was automatically used because Studio recognized it as a closer match. but if for some reason we want to use the match with a lower value because it is more appropriate we can override it by selecting it in the Translation Results window and clicking the Apply Translation button. You might not use this process very often but it shows you still have the ability to customize your translation memory results and pick the suggestion that best matches your translation context. Now you can also see in the Translation Results window, words which have been removed or added to the translation. Words which have a red line through them indicate that they have been removed and words that have a blue line under them indicated that they have been added. The fuzzy match can then be edited to complete the translation by clicking in the segment and manually adding or removing words. I'll remove the word Passenden from the proposed translation. You can also see because I have manually edited the translation the fuzzy match value is now greyed out. This can help to easily identify a translation which has been edited vs one which was a complete match from the translation memory. Now we've looked at some basic translation memory features, let's see what other resources are available to aid in the translation. Before moving onto the next segment we can add a termbase to our project translation resources. So click the Project Termbase Settings button in the Term Recognition window. The Project Settings dialog box will be displayed with the Termbase settings automatically selected. From here we can add a termbase to our project, Termbases are multilingual meaning they can hold information for multiple languages at the same time. Click Add and then browse to search for a file- based termbase. Select the sample Printer Termbase which is also included with the sample project files. Like translation memories, Studio can support using more than one termbase at a time. Click OK to close the Select Termbases dialog box and click OK to close the Project Settings dialog box. With segment two still selected the photo printer term is now highlighted with a red line above it. This indicates that the termbase we've added has automatically conducted a look up of the active segment and found a result. You can see the term Fototdrucker has been found. If you want to view more information on the term, click the View term details button and any information will be displayed in the Termbase Viewer. In the termbase entry for this term there is a picture, information on preferred terms which can be set by the user and also translations for other languages. This window is actually a component of SDL MultiTerm which is a powerful terminology management system. From this window you can fully customize your termbase and add extra terms if needed. SDL MultiTerm will be covered in more detail in a separate video but for now you can get an idea of how this window can be used by looking through the sample term entries and reviewing the information each entry contains. Now let's take a look at segment two again. In Segment two you can see there is a spelling mistake for the word Fotodrucker. This means it has not been recognized as a valid spelling by the spell checker which is standard with Studio. By right clicking it is possible to see a list of alternate spellings. If the translation spelling is correct, you can select Add to Dictionary which will add the term to your custom dictionary. So now I'm happy with the translation I can press Ctrl+Enter to confirm the segment just like segment one and this will automatically select segment three. Another translation memory result is added for use here and this time the translation has a 98% match. Looking in the Translation Results window shows that it's not a different translation causing the 2% penalty because the text is identical to the source document. So let's look at where the difference is. You can find this by hovering over the small symbol below the translation percentage. This is called a formatting penalty symbol and by hovering over it we can see that a formatting penalty is the reason for the 2% deduction. In this case the source segment uses bold and italics fonts and Studio has recognized that the translation memory result doesn't. Highlight the words in the target segment which need to have the bold formatting. Press Ctrl+Comma to display the QuickPlace drop-down list and use the Arrow keys and the Tab key to select the bold formatting. Studio gives you the options for formatting by recognizing what formatting is used in the source segment. This can be any formatting not just simple bold but the principle is always the same. Repeat the same process for the text that needs to be formatted in italics. We have now seen how to apply the correct formatting to the segment text and can move onto translating the next segment by pressing Ctrl+Enter to confirm the segment. When segment four is selected there is no translation memory result, so we can begin to type the translation. This will allow us to look at some of the more interesting features of Studio which are automatic Quality Assurance Checks and working with Placeable elements. So if we start to type the translation into segment four "Lassen Sie" and then we deliberately type the incorrect measurement of 11cm. Then we confirm the segment. We can see that a small error symbol appears indicating that Studio has found a verification error. To view the details of the error you can hover over the message, alternatively you can select the messages tab and see them listed in the window. Looking at this it is obvious that the wrong number has been used for the translation and Studio has picked this up. If we wanted we could now go and correct this by going and typing the correct number or like when we applied formatting we can highlight the incorrect number and press Ctrl+Comma to bring up the QuickPlace drop-down list. So now we have the correct measurement in the target segment, we can finish the translation and confirm the segment. Now that we've seen how termbases, spelling and the QA check work, we can take a look at the unique feature called AutoSuggest. Now this feature will allow you to boost your productivity by taking away one of the most time consuming aspects of translation, which is manually typing the same phrases again and again. Autosuggest analyzes your translation memory and extracts repetitive phrases which will then be displayed to you as you type. These extracted phrases will then be added to what is known as an AutoSuggest dictionary. Now let's take a look at how this feature works. To add an AutoSuggest dictionary we go back to the Project Settings and this time were going to select the English to German individual language pair. Underneath the language pair we're going to select AutoSuggest Dictionaries. Now AutoSuggest dictionaries are bilingual and only hold information on one language pair. So click Add and select the AutoSuggest dictionary form the sample project folder. Click OK to close the Project Settings dialog box. Select segment ten and type a capital "V". You'll see a list of suggestions appear. the suggestions can be from several sources, in this case we see phrases that have been extracted form a large translation memory. In this case we want to use the verb Verwenden. Use the Arrow keys and press Tab to insert it into the document. So instead of having to use 9 key strokes to type the translation, we have used three to insert the suggestion. Let's continue translating the segment and this time we see a suggestion we don't want to use so to ignore this just continue typing. When we type the letter "N" we get another list of suggestions. Lets select Netzeil and continue typing Das I'm, and when you type the letter "L" you actually get a suggestion which is an entire fragment, so go ahead and select Lieferumfrang des Druckers and finish translating the rest of the sentence, selecting the suggestion and confirm it. You can now see we've saved a lot of keystrokes doing this, we've use 42 keystrokes with AutoSuggest. If you didn't use AutoSuggest you would have used 90 key strokes. One final tool we will look at now which is useful during translation is the Real-Time Preview Window. Slide in the Preview window and doc it to the Studio environment by clicking the pin. This will show the window in the lower right corner. Create the preview by clicking the link. Then you can make it as big as necessary to make it legible. The window can be moved and also resized. You can also minimize the navigation pane to get more space for editing. Now let's see how the preview is going to update in real time as we confirm the translation for the current sentence. This time we have two results from AutoSuggest. Select the first suggestion and continue typing. Confirm the segment and you can see the text in the Preview window is updated. Now that we've seen this feature, let;s look at how you can produce a final document with the translated content. You can go to File, Save Target As and choose a location to save the document. I'm going to save this document into the German language folder because then I will know where to look for it when I come to open and review it. So if I go to Windows Explorer and find the file, I can open it with Word and see the translated content. Any segments that haven't been translated will still be in English but you can see the progress I have made so far and how the text has taken on the formatting of the original document. We can now start to see the results of using the translation resources during translation and start to understand how they can increase are productivity and reduce our translation costs. Thank you for watching how to translate a document in SDL Trados Studio. For any more information on some of the points covered in this video, please see the Online help and the Quick-Start guides available from the Home view.