My workflow in SDL Trados Studio 2014/2015/2017

Transcription

1 My workflow in SDL Trados Studio 2014/2015/2017 Reino Havbrandt 1 March 2018

2 Contents 1 Introduction Project Structure File structure Creating a new project Translation memories and AutoSuggest AnyTM Change language AutoSuggest Automated translation in Studio Google Translate MultiTerm and termbases Term recognition Term collection My glossaries Exchanging files with colleagues SDL Trados Studio 2009/2014/ Proofreading of sdlxliff files Import and export to other CAT tools Wordfast Classic Wordfast Professional memoq The tool SDLX Memory Maintenance Other cooperation models Project Packages Working in the Editor All these settings Formatting display style Font adaption Auto-propagation Review - Track Changes Verification Keyboard Shortcuts Merge files Translate until Fuzzy with Auto-propagation Segmentation Abbreviation list Filtration Standalone numbers and tables Word count excluding locked segments Terminology check Adding terms on the fly The Align function ABBYY Aligner Info about SDL Trados Studio 2014/2015/ List of pictures... 35

3 My workflow in SDL Trados Studio 2014/2015/ Introduction There is already a lot of instruction material for Studio, both from SDL and from third party publishers. Thus, this is not a comprehensive manual for Studio, but a collection of practical tips for people that already knows the basics of Studio. In this document I will describe my workflow, which of course is not the only possible. My version is SDL Trados Studio Freelance The screenshots come from different versions of Studio. The shots with blue header comes from Studio 2014, the ones with white header comes from Studio 2015 or Picture 1-1. My Studio. I still have use for my old printed dictionaries. 2 Project Structure Unlike the old Trados, Studio is based on the use of Projects, also when the job consists of only one file. In my opinion, it is not easier to use Open Document than to define a project. You must select the memory, dictionaries, language, AutoSuggest etc. in both cases. The advantage of defining a project instead is that the settings can be reused. A new project can be based on the settings made for a previous project. The project settings can be saved in a Project Template. 2.1 File structure I use a four-digit project number and a customer code consisting of three to five letters. In Windows Explorer I have a folder for jobs called Ajobb. There I create a subfolder named 9999 cust where I put the files to be translated and the reference material. Picture 2-1. File structure. 3

4 Picture 2-2. TM fields. In my TM I only use two system fields, a text field job where I put the project number and a list field for the customer code. Picture 2-3. Fields Jobb and Kund. 2.2 Creating a new project Go to the Projects tab, use Ctrl + N or click New Project to start a wizard. If you have a suitable project template, you just have to step through all the windows and fill in the customer and the project number in the Customer and Jobs. Picture 2-4. Project type with template. Below is my workflow to create a project if no template exists. Select a default template if you do not have created own Project Templates. Picture 2-5. Project type without template. Click on Next. 4

5 Picture 2-6. Project name and location. Here you can create the folder where the Studio files are stored. Please note that you cannot use the folder 9999 cust, because it already contains files. The project folder must be empty or created here. Enter the project name in the field Name: 9999 cust Se, and a new folder with the same name will be automatically created in the folder Jobb. Make sure that the path to the folder Jobb is stated in Location. If you always use the same main folder for the Project folders, you do not have to change Location each time you create a new project. I use two folders for each project, 9999 cust for the project files and 9999 cust Se for files created by Studio. Click on Next. Picture 2-7. Project Languages. Picture 2-8. Project files. Click the button Add Files... and then select the files to be translated from the folder 9999 cust. If you want to merge several files into one, highlight the files and click Merge Files. Note that a real Merge can only be done in the Project Wizard when the project is created. Click on Next. 5

6 Picture 2-9. Translation Memory and Automated Translation. Adding translation memories with Add. To use Google Translate as a virtual memory, you must have an agreement with Google and an API key. Studio 2014 Add Google Translate to the list of TM:s, but do not check the box Enabled. If the box is checked, Google Translate suggests full sentences when running Studio. I prefer to only use automated translation via AutoSuggest, which works even if the box is not checked. Studio 2015 and 2017 Google Translate works somewhat differently here. Add Google Translate to the list of TM:s, and check the box Enabled. If the box is checked, Google Translate gives suggestions for complete sentences in the Translation Results window, but does not copy the text to the editor. I prefer to only use automated translation via AutoSuggest. Then click on the current language pair, Swedish- >English, and then AutoSuggest Dictionaries. Picture AutoSuggest Dictionaries. Click Add and find the file with the extension.bmp. in the folder Studio 2014\AutoSuggest Dictionaries. Click on Next. 6

7 Picture Termbases. Click Add and find the termbases, with the extension sdltb. in the folder SDL\SDL MultiTerm\Termbases. At the beginning of a project, I always have an empty termbase called AAFlySourceTarget on the top of the list. When I add terms on the fly they will be added to this termbase. Click on Next. Next step is SDL PerfectMatch. This is a rather strange feature I never got to work properly. The purpose is to use a previously translated sdlxliff file as a supplement to the TM:s. Click on Next. Picture Project Preparation. I mainly use Prepare without project TM, as I mostly work directly in my main memories. Click on Next. Picture Batch Processing Settings. Here you can among other things set various parameters for the pre-translate, e.g. automated translation of empty segments. Click on Next. 7

8 Click on Project Settings... if you want to check that all settings are correct. Then click on the Finish button. When you have run through the wizard, it may be a good idea to click on Create Project Template, so that the settings are saved for the next time. In practice, it is quite easy to create a project, especially if you have project templates and file structures ready. Do not worry if you missed any of the settings. You can change everything with Project Settings after creation of the project. After creating the project, add the project number and customer in the Project settings. Note: Do not enter Jobb and Kund in All language pairs, but in the current language pair, e.g. Swedish -> English. Each project and each TU in memory can then be identified by the customer code and the project number. 3 Translation memories and AutoSuggest I translate in the language combinations English, German and Finnish into Swedish. Thus I use three main memories, one for each language combination. In most cases, I work directly in the main memory. Sometimes I use project specific memories, if I have got external memories from the customer or if the customer wants to have a project memory. Since my main memories are now quite large, I use two memories per language pair. For example, for English, I use the following: English OldBM.sdltm, my BigMama, containing all old translations, this memory is not updated during work English2017.sdltm which is an annual memory, which I update with new translations. By the end of the year, I import the annual memory to BigMama. 8

9 Picture 3-1. BigMama and annual memory. 3.1 AnyTM Studio does not permit you to use memories with language combinations other than the languages selected for the project. You cannot even use an en-us memory if the language locale is en-gb. However, there is a good workaround for this. Download and install the add-in AnyTM from SDL OpenExchange. Picture 3-2. Translation Memory and Automated Translation. Then you get a new menu branch in the menu Add (Use) named AnyTM: any file-based TM: The picture above also shows memories with other locales and language directions added with the app AnyTM. In addition, three automated translation systems are shown. 3.2 Change language If you want to change the language locale in a memory, for example, from en-us to en-gb, proceed as follows: Export the memory to a TMX file. Create a new memory with the appropriate locale Import the modified TMX file. You no longer need to do search and replace en-us to en-gb, which was necessary in previous Trados versions. But it is not necessary to change language direction. In most cases, you can use Any TM instead. 3.3 AutoSuggest AutoSuggest is a great way to leverage your termbases, TM and automated translation to avoid typing long words and phrases. Set up the providers you want to use in File/Options/AutoSuggest: 9

10 Picture 3-3. AutoSuggest. MultiTerm termbases can be utilized directly in AutoSuggest, if you have added them to your project. In earlier program versions, it was necessary to create an AutoSuggest dictionary, to use the TM content. Now, you can use data mining to find data directly in the TM, through automatic concordance search and fuzzy matches. This is not the default setting. If you want to get suggestions also from the TM, you have to check the boxes Fuzzy translation memory matches and Automated translations. Picture 3-4. Check all boxes. In Studio 2014/2015/2017, you can also use automated translation as a provider for AutoSuggest. There is a very good description of AutoSuggest on the blog multifarious. AutoSuggest Dictionaries You cannot create AutoSuggest dictionaries in the Freelance version, if you do not purchase a special addition to Freelance. However, if you get an AutoSuggest somewhere, you can add it to the project. You do this in the Project Settings / AutoSuggest Dictionaries: Picture 3-5. Choose AutoSuggest Dictionaries. Do not forget to enable AutoSuggest in File/Options/AutoSuggest, see Picture 3-3. AutoSuggest. 4 Automated translation in Studio In my opinion, automated translation is one tool among many that actually makes the translation process more effective. You can use automated translation as a virtual TM in 10

11 Studio. There are several ways to do this. I have the best experiences from using Google Translate API which is a paid service. There are also other suppliers of automated translation, but they are more or less based on Google Translate. 4.1 Google Translate Picture 4-1. Google Translate raw translation. In order to use GT in Studio you must have a Google API account. The charge is per character. Add the API number under File/Options/Translation Memory and Automated Translation, menu Add/Google Translate: Picture 4-2. Google Translate API. Google Translate can be used as a translation memory. Enable Google Translate only when you actually use it. There are different ways to use automated translation. You can pre-translate with automated translation, using it as a memory during translation or only use it as an AutoSuggest provider. I've tried all the methods in some detail, and found that the most effective method is to use Google Translate, but only via AutoSuggest. Studio 2014 Add Google Translate as a TM, but leave Enabled unchecked. Studio 2015/2017 Add Google Translate as a TM, and check Enabled. Go to File/Options/Automation and uncheck Perform automated translation lookup on translated segments: 11

12 Picture 4-3. Automation settings Studio Picture 4-4. Lookup function deactivated in Studio To turn off MT as a provider for AutoSuggest, uncheck MT provider in Files/Options/MT AutoSuggest or remove Google Translate from the list of memories above. Picture 4-5. Providers for AutoSuggest. The cost of the GT is not very high, for me it costs 1 to 4 dollars a month, and in my opinion, it is money well spent given the benefits of GT. It saves a lot of keystrokes plus, you get a number of good laughs during the day, which prolongs your life. An example from 2016: I invoiced approximately SEK , and the cost of Google Translate was SEK 625, which is about 0.15% of the revenue. The effectivity gain using Google Translate is about 5-10%. So it is very profitable to use Google Translate. Conclusion: If you want to use automated translation systems in an efficient manner, I think that a Google Translate account is the best start. If you never use the function, it doesn't cost anything. There is also a rapid development in this area, thus many of my views on automated translation may already be outdated. Read more on the blog multifarious_there is more than one way to skin a CAT. 5 MultiTerm and termbases MultiTerm is a tool that can be used to build multilingual termbases with explanations, pictures and references. It can be used completely independent, but the biggest advantage is that Multiterm databases can be used directly in Studio to automatically retrieve terms from 12

13 the project glossary. It is also possible to add terms on-the-fly during the work via Studios terminology function. Creating a termbase There is now an externally developed app, Glossary Converter, with which it is very easy to convert termbases from Excel to MultiTerm and back. Glossary Converter can be downloaded for free from SDL Open Exchange. The tool MultiTerm Convert is included in MultiTerm, but that program it is more complicated to use than the Glossary Converter. Steps to create a termbase with Glossary Converter: Make an Excel spreadsheet with optional headers and at least one term pair: Picture 5-1. Excel glossary. Save the Excel as AAFlySve_Eng.xlsx, start Glossary Converter. This window will open: Picture 5-2. The Glossary Converter window. Then drag the Excel file and drop it in the window. If you get an error that the file is busy, it's likely because you have either Studio or MultiTerm open. If it's the first time you use the headers, Glossary Converter asks which languages are to be set for the columns Se T and En T, and stores your choice for the next time. The conversion is very fast, and you get a finished termbase named AAFlySve_Eng.sdltb. 5.1 Term recognition Customers often have a company-specific terminology that it is important to follow. In order to obtain uniform terminology in a large project, especially if several translators are involved, it is useful to develop a project glossary. Picture 5-3. Term recognition. The terms found in the termbase are marked with a red bar above the word, and are shown in the Term Recognition window. 13

14 Picture 5.4. Termbase list. 5.2 Term collection During the work I collect terms in Studio on-the-fly. If there are multiple termbases in a Studio project, the terms on-the-fly are added to the termbase at the top of the list. However, it is usually necessary and convenient to use a Word table for the terms during the project, as they often need to be sent back and forth to the end user and involved translators. Select a term in the Source and the same term in Target and press Alt F12. This opens Studios Termbase Viewer. Confirm with Ctrl F12 (or Ctrl F2 if you use Studios default settings). Picture 5-4. Adding terms. In Studio 2014/2015/2017, you can edit and delete terms directly in the Termbase Viewer: Picture 5-5. Studio Termbase viewer. In Studio 2017, MultiTerm integration has been reworked, and is now much easier and better. 14

15 Picture 5-6. Studio 2017 Termbase viewer. If you want to have the glossary back to Excel format, shut down Studio, start Glossary Converter and drag AAFlySve_Eng.sdltb to the Converter window and drop it. This creates a new AAFlySve_Eng.xlsx with the new terms. Picture 5-7. Excel glossary converted from sdltb. When the project is finished and the terms approved I add my terms to a temporary termbase and empty AAFlySve_Eng.xlsx. The transfer of terms is most easily done by cutting and pasting in the Excel versions and then create new termbases with Glossary Converter. Glossary Converter can also handle multilingual termbases with abbreviations and explanations. 15

16 5.3 My glossaries I have over the past 20 years collected my terms in a term base, RHterm. My termbase is not of dictionary quality, and is not always reliable. The terms are now tagged with 45 subject areas. Short aeronautic al agri airc allm assa aud borr bridge brush brw ByggFis chemp combu const cut dent elec eng Framv grd hoch Description aero, FiEn agricultural machinery, mostly De air conditioning, mostly Fi general medical analysis, En video recorders, En Rock drilling, EnFi bridge construction, EnDeFi brushes, EnDeFi brewery, En construction, Fi chemical plants, En combustion, boilers, EnDeFi construction, EnDeFiNo cutting; En dental, De electricity, mostly En engines, mostly En front suspension settings, EnDeFi grinding, De construction H hor Short hydro Lar lemm mach measur nuc nuc2 paper prt pump rh RHtx sensor Stra sund tool tooth train turb vechi vent wld clockwork, En Description water and heat, EnDeFi construction, EnDeFiNo construction L machinery, EnDeFi metrology, De nuclear, EnDeFi nuclear, EnDeFi paper machines, EnFi printer, En pumps, En Reino s old terminology Reino s old terminology metrology, En construction S construction, EnNo metrology, EnDeFi dental technology, EnDeDa train technology, EnDe steam turbines, De vehicles, EnDeFi ventilation, De welding, En 16

17 To view the abbreviation in Studios Term Recognition Window, you need to redo the settings: Click on the third symbol in the Term Recognition Window: Picture 5-8. Settings for the Term Recognition Window. Then the window Hitlist Setting shows: Picture 5-9. Hitlist Settings. Click on Select fields. Picture Note contains the subject abbreviation. Check Note, it is the field where my subject abbreviations are shown. 17

18 6 Exchanging files with colleagues I have on a few occasions collaborated with colleagues working with different versions of Studio and other CAT tools. I have some experience of sending and receiving text from different versions of Studio, memoq, Wordfast and SDLX. 6.1 SDL Trados Studio 2009/2014/2015 If the translator has Studio I prepare the document and create a sdlxliff file. Then I send sdlxliff file for translation. I also attach TM, termbases and AutoSuggest. How to handle sdltm, sdlxliff, sdltb and bmp If you get files with different extensions from a client you have to put them in the correct folders. Start by copying all the files to your job folder, for example 9999 cust. Then move all TMs, files with the extension.sdltm, to the folder Studio 2014/Translation memories. Then move the termbases, files with the extension.sdltb, to the folder SDL/SDL MultiTerm/Termbases. Then move the AutoSuggest, the file with the extension.bmp, to the folder Studio 2014/AutoSuggest Dictionaries. The folder paths may vary depending on how you installed Studio. Then start Studio and define a project. How to create a project, see chapter 2.2 Creating a new project Proofreading of sdlxliff files The translator sends sdlxliff file to me. I load it into the Studio and make changes. Then I return the file and my comments in a separate file. The translator then loads the file into Studio, and runs Translate Until Fuzzy. Studio stops at the changed TU:s, signalling Different translation into memory, and the translator can decide whether the change should be approved or not. It is of course important that the translator does not continue to work in the same file while I proofread. It hampers the possibilities to keep track of which version is actually current. Another possibility is that the translator puts the file into Studio as above, and runs the function "Update main translation memories". Then the changes are entered in the memory, and the translator can work in the original file and pick up the changes with Translate Until fuzzy. This method works relatively good even if the translator has been working on the file in the meantime. 6.2 Import and export to other CAT tools Even if CAT systems are more or less compatible, I prefer to work with people running Studio, because everything will work so much easier for both parties. Then I can send and receive ready-prepared.sdlxliff, without conversions and segmenting problems. A colleague with Studio can also make full benefit of my reference material in the form of TM, termbases and AutoSuggest. The problems that arises are primarily connected with conversions, delivery formats, segmentation and tags. Below I will take a closer look at each tool and describe some of the practical and technical details Wordfast Classic Wordfast is similar to the old Trados-version and is not a stand-alone program, it is a collection of Word macros. 18

19 Picture 6-1. Sample of Wordfast Classic text. From the Wordfast Classic translator I got a tmx file and also an uncleaned Word. For some reason I got error messages when trying to import the uncleaned Wordfast to Studio. But I was able to import tmx to the TM, and so I could get this translation into the main file Wordfast Professional Another translator in the project worked with Wordfast Professional, and I got a file in txml format. Studio does not read txml from Wordfast, but there is an app to download from SDL Open Exchange called "File Type Definition for Wordfast txml". This app installs a new file type that shows up in the file list: Picture 6-2. Added file type for Wordfast txml. If you installed the file type but it does not appear in the list, go to Options -> File Types tab and look in the right window. It probably says "additional file types exist". Click this option and select the missing file type memoq memoq uses a bilingual file type called memoq xliff, and in the same way as for files from Wordfast Professional you must download an app from SDL Open Exchange called " File type definition for memoq xliff" to be able to process memoq files in Studio. This app installs a new file type that shows up in the file list: Use the same procedure with Options -> File types as for Wordfast if you do not see the file type in your list from start The tool SDLX One of the translators used SDLX, although he had Studio. I got a TTX file, and the import to Studio is technically unproblematic. But when I started proofing the translation in Studio duplicate translations was created of every TU, and both the old and changed version was saved in memory. I finally found the solution. Here a quote from Studio 2014 release notes: "When using bilingual file types such as ITD or TTX unwanted duplicate translation units may be created when changing existing translations in a file. If this happens consider deleting the duplicate translation using the Delete Translation Unit option on the Advanced tab in the Editor view." In my opinion, you should use keyboard shortcut Ctrl + Del instead, it goes somewhat faster. 6.3 Memory Maintenance There are some situations where Studio creates unwanted duplicates. These can be removed manually in the box Translation results by clicking on the TU and then press Ctrl + Del. It is also 19

20 possible to remove the duplicates with a little manual memory maintenance. Export the memory to a tmx file: Picture 6-3. Exporting TM to tmx. Then import to a new empty memory with the setting "Keep most recent" which clears the duplicates that has been produced. Picture 6-4. Import of tmx back to the new TM. 7 Other cooperation models 7.1 Project Packages Another possibility is to send a Project Package, but I have so far not been using this function. This is partly due to the fact that I do not like to receive Project Packages myself, as they disturb my workflow. When I start a new job I always use some of my Project Templates where I have predefined memories, AutoSuggest and termbases. If I receive a Project Package and open it in Studio I will have the sender's settings and materials. And of course it is good to get the senders reference materials, sdlxliff, project glossary and TM into the project. But the problem is, that I have to add my memories, AutoSuggest and termbases afterwards. There is now an app which helps to supplement a package with your own choices and settings. I have tested this, but in my opinion it was not so much easier, as the app has quite a few settings. Disassembling Project Packages A Project Package is actually a normal zip file. If you change the file extension sdlppx or sdlrpx to zip, you can open the package like any zip file, and access the files the sender has put in the package. You can then send back a sdlxliff, because that is actually what a Return Package 20

21 needs to contain. It is possible to disassemble the Project Package, then define my own project and add sdlxliff and other stuff in the created project. Here a disassembled Package: Picture 7-1. Contents of a Project Package. Here a disassembled Return Package: Picture 7-2. Contents of a Return Package. 8 Working in the Editor 8.1 All these settings The settings can be set on three levels: 1) The upper level is File/Options. These settings affects all new projects or templates, but not the ones that are already created. 2) The next level is Project Templates. You do not have to use templates, but it facilitates the start of new projects. A change of a template affects new projects, but not the ones already defined. 3) The lowest level is Projects. Changes in Project Settings only affects the current project. Note that the Templates and Projects has two sublevels. In Language Pairs you can make changes for All Language Pairs or for one of the language pairs used in the project. 21

22 Here a table that gives some hints on how to choose settings level: n/a = not applicable yes = may be selected new = only affects new projects or files all = affects current and coming projects Function Sublevel SubSub 1) Tools /Options 2) Project template 3) Project settings Editor Spelling all n/a n/a AutoCorrect all Trans. Res. W. all n/a n/a Conc. Search all n/a n/a Font adapt all n/a n/a Automation all n/a n/a Auto-prop all n/a n/a Languages all n/a n/a Track chng all n/a n/a Review AutoSuggest all n/a n/a TM and AT all Autotext all n/a n/a Project yes File Types new new yes Emb.Cont.Proc new new yes Verification new new yes QA checker new new yes Tag Verifier new new yes Term Verify new new yes TR. Q. Ass. new new yes Lang. Pairs All Lang P TM and AT new new yes Search new new yes Penalties new new yes Filters new new yes Update new new yes Language R new new yes Termbases new n/a yes Search set new n/a yes Batch pro new n/a yes Your Lang P TM and AT n/a new yes Search n/a new yes Penalties n/a new yes Filters n/a new yes Update n/a new yes Auto-sub n/a new yes Autos dic n/a new yes Batch pro new new yes DefTaskSeq Only in Pro ve yes yes n/a TM view all n/a n/a Colours all n/a n/a Keyb short all n/a n/a Aut updates all n/a n/a Welco. View all n/a n/a 22

23 Some changes of the default settings that I prefer. Go to Options / Editor: Formatting display style If you do not want to see the colours in the editor, change this setting to "Show all tags but do not show formatting". It may sometimes be necessary, for example, if there is white text in the document Font adaption If you want to avoid seeing all font and size changes while working in the editor, make changes as described below. Note that it is only the Studio Editor interface that changes. The document text will not be changed. Picture 8-1. Adaption of the text that is shown in the Editor Auto-propagation I check the boxes for Auto-propagate... And Confirm segment... Picture 8-2. Changes in following segments are made and confirmed automatically. 23

24 8.1.4 Review - Track Changes I have no use for this, so I uncheck this. They are used for proof reading in Studio. Picture 8-3. Disable Track Changes Verification Almost all settings for the QA are unchecked by default. I recommend to go through the lists and check (almost) everything. Then the list of errors will be long, but it is easy to browse through the notes you do not need Keyboard Shortcuts There are keyboard shortcuts for most of the common functions in Studio. Use them, it streamlines the work and you will avoid carpal tunnel syndrome from unnecessary mouse clicking. Here some keyboard shortcuts that I am using in the daily translation work in the Editor. Command SDL short My Short Add New Term Ctrl F2 Alt F12 Clear Target Segment Alt Del Alt Z Concordance Search F3 F3 Confirm and Move to Next Segment Ctrl Alt Enter Alt Q Confirm and Move to Next Unconfirmed Segment Confirm and Translate until Next Fuzzy Match Ctrl Enter Alt E Alt W Confirm All Ctrl Alt F Remove! Copy All Source to Target Alt Shift Ins Remove! Copy Source to Target Ctrl Ins Alt < Project settings (toggle MT) - Alt S Save Term Ctrl F12 Ctrl F12 Select Match 1 9 Ctrl 1-9 Ctrl 1-9 Picture 8-4. Table of keyboard shortcuts. If you have a keyboard shortcut for the Copy All Source to Target or Confirm All there is a big risk to use it by mistake, which could destroy some work if you have not saved for a while, and have Unconfirmed TU:s. Thus, it is a good idea to remove the shortcut for this command. You can change the keyboard shortcuts with the File/Options/Keyboard Shortcuts. As you can see, I've changed almost all of the keyboard shortcuts. And there is good reason to do it, even if you are not left-handed like me. I think that there is a difference between one hand shortcuts two hand shortcuts and three finger shortcuts. For all very frequent commands, like the first four in the table, you should have one hand shortcuts. Preferably placed so that you do not need to move your hands from the normal 24

25 writing position. I have put all the frequent commands on the left hand, but a right-handed person might choose to put them on the right side of the keyboard. In my opinion, SDL's default shortcuts are not very ergonomic. Especially the three-finger shortcuts. 8.2 Merge files In previous versions of Studio, it was possible to merge files, but only when the project was created. That possibility is still there in newer versions of Studio, but a new way for virtual merging files has been added. Picture 8-5. Merging of files. Select the files you want to work with simultaneously and click on Open For Translation. This opens the files in the Editor, and you can work with all files concatenated. In the left panel, you can switch between files, and the file boundaries are marked with yellow tags in the Editor. Picture 8-6. Segment Numbering. The only difference between virtual and 'real' merged files is that segment numbering starts again for each file, see the picture above. This makes it a little more difficult to search for a segment number. Copyright note: Finncont Oy has approved that these examples from their sales material published online. 8.3 Translate until Fuzzy with Auto-propagation Now I go to the top line and begin the translation with "Translate until Fuzzy", or "Confirm and Translate until Next Fuzzy Match" as the official name is. Do not forget to turn off the automated translation first. If you have it on the Translate until Fuzzy runs slower and if you use GT, it costs a bit too. Auto-propagation means that if there are several duplicates of a source TU, then the translation is copied to all TUs. After some trial and error, my settings are as below. 25

26 Files/Options/Auto-propagation: Picture 8-7. Auto-propagation. Translate until Fuzzy steps through all confirmed TU's and stops at the first that is either below 100% or is an automated translation. If you do not think the hit can be edited, delete it with the function Clear Target Segments. If you want to copy the source, use the Copy Source to Target. Use keyboard shortcuts for the above functions and any others frequently used. 8.4 Segmentation There are several ways to improve the segmentation of Studio. All such adjustments are made in the translation memory. Select Translation Memories in the left pane. If the memory does not appear in the memory listing, use Open. To change the segmentation, right-click the memory and select Settings/Language Resources, and then Segmentation Rules. Example sentence: If I translate with Studio's default settings, the segmentation becomes like this: Segmentation with tab as a delimiter It is often advantageous to let the tab character be segment breaking. 26

27 Picture 8-8. Segmentation Rules. Click Add and select Anything / Tab / Anything: Picture 8-9. Change segmentation rules. Then the segmentation becomes like this: Note: If you have several memories in a project, the segmentation will be controlled by the memory at the top of the list of memories in Project Settings Abbreviation list If an abbr. is followed by a capital letter, the CAT tool interprets it as a start of a new sentence, and segments incorrectly. To avoid this, there is an Abbreviation list initially containing a number of common abbreviations in the current source language. The list can then be supplemented. In this case I add the abbreviation frkort. in the Abbreviation List: 27

28 Picture Abbreviations that do not separate a sentence. Then I get the following segmentation: Some documents may contain line breaks in the wrong places. You can then automatically or manually search and replace line breaks against new paragraph before the document is imported into Studio. Another possibility is to add a Soft Line Break in Segmentation Rules. In this case, I would not want to have "rad1 -" in the same segment. Add in a little Regex in Segmentation Rules / New / Advanced view: Before Break: [\w\p{p}]\s?[\n]+ After break: \s? Then the segmentation becomes like this: Note: Soft Line Break can cause problems, because sentences can sometimes be broken into parts in an unwanted way. Use Soft Line Break only when really needed, for example in Excel files with long item lists in the same cell, that else would become one segment. 8.5 Filtration Standalone numbers and tables In technical documents there are often a lot of numbers and codes in standalone TUs: 28

29 Picture Standalone numbers. Autopropagation of numbers can delay the work, as Studio always autopropagates numbers. One way to avoid this is to filter and lock all numbers. In the tab Review, choose the built-in filter "Number only" in the box Display Filter. Picture Filtering on "Number only". Picture Display after filtering on "Number only". I believe that it is better to use a Regex formula like ^[\d.+]+$, which also filters numbers with dots, like The symbol ^ is written with Alt Enter the filter formula in the field beside the hopper in Display Filter: Picture Display after filtering with a regex formula. Explanation of the formula ^ starts with [\d. digits followed by a dot +] repeated + previous pattern group repeated $ only this pattern and nothing else may occur. If you omit the $ you also get segments that begin with a numerical pattern and continue with the text. 29

30 Picture Filtering with ^[\d.+]+$. The formula ^[\d.+]+[\d,+]+$ also finds numbers with dot and comma: Picture Filtering with ^[\d.+]+[\d,+]+$. If you need to localize, and change decimal or thousands delimiter, you can do it after the filtering, with Studios Search & Replace function, or manually, if only some of the punctuation marks have to be changed. When you filtered out the numbers you should lock them. Click on the TU number in the column for TU-number on the first line. Shift-click on the TU number in the last line of the selection. Then press Ctrl + L. Picture Locked rows. Translate to Fuzzy skips locked rows, and no Autopropagation takes place Word count excluding locked segments By default, Studio also counts numbers. To avoid this, you can lock the numbers according to the above section, and choose not to include the numbers in the word count. In this case, tick "Exclude locked segments from analysis". Or get them in a separate category with "Report locked segments as a separate category". 30

31 Picture Locked rows are excluded from analysis Terminology check The filter is useful also for other purposes, for example to check if a term has been translated consistently. Here I filter on the Finnish word fragment merikontt to make sure that the translation is consistently sjöcontainer: 8.6 Adding terms on the fly To get the term correct in the future, and not have to write it again, I select the term in both the Source and Target, and then press Alt F12 and then Ctrl F12 (Ctrl F2 if you have SDL settings). That adds the term in my On the fly-dictionary AAFlyFin_Sve: You can move the Termbase viewer window, to your side screen, it's not a good idea to have it in the middle of the Editor: The above image shows a suitable arrangement for running Studio. I use three monitors, a 14-inch monitor to the left for termbases and glossaries, a widescreen in the middle of the editor and a 31

32 widescreen to the right for reference material. The dictionaries are Mot-Ruteka with Talvitie for Finnish and Wordfinder including Engströms technical, which does not include Finnish. Finally, a few more examples of filtering: Contains DTD, gives this result: Starts with DTD, gives this result: Codes should be handled simultaneously. Select in the TU number column as above, copy to Target, make changes if needed and approve. 9 The Align function Studios Align function I have for many years been using the old align function in Studio, and it was not intuitive, simple and easy to use, but was actually quite efficient once I learned to master the features of it. There was a degree of intelligence in it that was useful in documents that did not align very nicely. So I looked forward to the promised new Align function in Studio I got into a pretty big job for aligning, and decided to test this feature thoroughly. Soon I realized that the new align function is not similar to the old one, but was at least as difficult to learn. In addition, the interface is bad, as the 32

33 texts are not placed side-by-side. The sentences are connected by curved lines instead of straight ones in the old align version, which makes it very hard to get a good overview and see which sentences fit together. There are two sets of different line numbers, which increases the confusion. Picture 9-1. Studio 2014 align. 9.1 ABBYY Aligner Since I have experience from ABBYY FineReader as an easy to use tool, I tested ABBYY Aligner. It proved to be a good alternative, and I worked quickly through my large align projects. Picture 9-2. ABBYY Aligner. Problem solving example Picture 9-3. Automatic merging in Studio align. Studios align discovers that Obs. is on a separate line and aligns correctly. Picture 9-4. ABBYY Aligner. ABBYY places Obs. on a separate line, but it is easy to fix. Highlight row 18 and 19, right-click and choose Merge fragments. Picture 9-5. Manual merging in ABBYY Aligner. Studios align also introduces problems not present from the beginning. For example: Picture 9-6. Studio Align works too hard. Studio tries to insert a hyperlink leading to incorrect segmentation. Picture 9-7. ABBYY does not complicate a simple thing unnecessarily. 33

34 ABBYY Align vs Studio Align function It is possible that ABBYY Align does not solve problems equally good, but it is more than compensated by the transparent interface. It is very easy to add, edit and delete rows with the functions split fragment, delete lines and merge fragments. There is also a search and replace function, which seems to be missing in Studios align. In short, if you are used to edit Excel tables and Word tables, you can use ABBYY Align without having to read and understand any extensive documentation. When the work is finished, the result may be exported to a TMX file and imported in a Studio TM. This approach is also better than Studios, where you must choose a TM first. It is quite common that an align fails completely, if the files are different formatted. Then you have to edit the files and try again, and it's fine if you do not need a lot of unnecessary steps to start a new align. 10 Info about SDL Trados Studio 2014/2015/2017 Find answers to questions about Studio A great way to quickly find information is to simply type in a few keywords about your problem and search the internet. You could then end up in a discussion list on ProZ, or in a KB-article from SDL, or perhaps in some blog or mailing list. With a little luck you will find the answer to your question directly. If you want to search a bit more systematically, you will find relevant information in the Studio help tab: Picture Studios Help tab. Help topics contains help files where the program's basic functionality is briefly explained. When it comes to more complicated problems, there is a collection of articles in the SDL Knowledgebase. The button Studio Blog will take you to the technically oriented blog multifarious, where you can learn things that are not found in other sources, such as the basics of Regex. There are also a lot of information in sources that are not directly connected to SDL. ProZ has a number of discussion forums on various themes in Studio. There is also a blog, Signs & Symptoms of Translation which is largely about SDL Trados Studio. And then there is a very active mailing list on Yahoo Groups, TW_users, where you can get answers to specific questions. Often you will find an answer by just searching the list archive. Picture list TW_Users. 34

35 Training If you want to learn how to run Studio, there are a lot of sources to choose from. The button Tutorials in Studios help tab takes you to an SDL page with videos explaining different features in the Studio. SDL also has a wide range of self-instruction trainings with study materials that can be completed with an online test that leads to certification. I liked this method of learning Studio. Picture Translationzone. Manuals If you don't feel comfortable with the structure in Studio help files, there is a very good third party manual complied by Mats Linder. It is available in electronic format for downloading and costs about 50 dollars and is well worth the money. See SDL Trados Studio 2017 The Manual. There are also versions for Studio 2011, 2014 and Picture Mats Linder The Manual. 11 List of pictures Picture 1-1. My Studio. I still have use for my old printed dictionaries Picture 2-1. File structure Picture 2-2. TM fields Picture 2-3. Fields Jobb and Kund Picture 2-4. Project type with template Picture 2-5. Project type without template Picture 2-6. Project name and location Picture 2-7. Project Languages Picture 2-8. Project files Picture 2-9. Translation Memory and Automated Translation Picture AutoSuggest Dictionaries

36 Picture Termbases Picture Project Preparation Picture Batch Processing Settings Picture 3-1. BigMama and annual memory Picture 3-2. Translation Memory and Automated Translation Picture 3-3. AutoSuggest Picture 3-4. Check all boxes Picture 3-5. Choose AutoSuggest Dictionaries Picture 4-1. Google Translate raw translation Picture 4-2. Google Translate API Picture 4-3. Automation settings Studio Picture 4-4. Lookup function deactivated in Studio Picture 4-5. Providers for AutoSuggest Picture 5-1. Excel glossary Picture 5-2. The Glossary Converter window Picture 5-3. Term recognition Picture 5-4. Adding terms Picture 5-5. Studio Termbase viewer Picture 5-6. Studio 2017 Termbase viewer Picture 5-7. Excel glossary converted from sdltb Picture 5-8. Settings for the Term Recognition Window Picture 5-9. Hitlist Settings Picture Note contains the subject abbreviation Picture 6-1. Sample of Wordfast Classic text Picture 6-2. Added file type for Wordfast txml Picture 6-3. Exporting TM to tmx Picture 6-4. Import of tmx back to the new TM Picture 7-1. Contents of a Project Package Picture 7-2. Contents of a Return Package Picture 8-1. Adaption of the text that is shown in the Editor Picture 8-2. Changes in following segments are made and confirmed automatically Picture 8-3. Disable Track Changes Picture 8-4. Table of keyboard shortcuts Picture 8-5. Merging of files Picture 8-6. Segment Numbering Picture 8-7. Auto-propagation Picture 8-8. Segmentation Rules Picture 8-9. Change segmentation rules Picture Abbreviations that do not separate a sentence Picture Standalone numbers Picture Filtering on "Number only" Picture Display after filtering on "Number only" Picture Display after filtering with a regex formula Picture Filtering with ^[\d.+]+$ Picture Filtering with ^[\d.+]+[\d,+]+$ Picture Locked rows Picture Locked rows are excluded from analysis Picture 9-1. Studio 2014 align Picture 9-2. ABBYY Aligner Picture 9-3. Automatic merging in Studio align Picture 9-4. ABBYY Aligner Picture 9-5. Manual merging in ABBYY Aligner

37 Picture 9-6. Studio Align works too hard Picture 9-7. ABBYY does not complicate a simple thing unnecessarily Picture Studios Help tab Picture list TW_Users Picture Translationzone Picture Mats Linder The Manual