Upgrade Translation Memories Wizard > Output Translation Memories settings
Use the Output Translation Memories Settings page of the Upgrading Translation Memories wizard to specify the type, location, custom fields, settings and language resources for the new translation memory.
To display this page, click Next on the Output Translation Memories page of the Upgrade Translation Memories wizard.
| Box | Description |
|---|---|
Output translation memories | This lists the translation memories that will be created from the upgrade process. The translation memories and TMX files from which the new translation memories will be created are listed under each new translation memory in this box. Select a translation memory and specify its settings on the right-hand side of the page. |
Translation Memory Settings These are the settings for the translation memories that you selected in the Output Translation Memories box. | |
Location | This is where you can choose if you want to create a file or server-based translation memory. |
Settings | This is where you specify general settings, recognition settings and import settings. |
Language Pairs | This is where the source language and target language in the translation memory are listed. |
Compatibility | This is where you specify what translation unit data is removed or retained in your translation memory to optimize the leverage from your new upgraded translation memory. |
Fields | This is where you ensure that the fields that you want to be available for each translation unit are listed. |
Language Resources | This is where you specify the language resources that the new translation memory will use. |
Click Finish to create the new upgraded translation memories and go to the Upgrading Translation Memories page of the Input Translation Memories wizard.
Location Tab
| Box | Description |
|---|---|
| File-based translation memory |
When this option is selected, the new upgraded translation memory is created locally in the specified Location. To change the default location, click Browse.
|
| Server-based translation memory | When this option is selected, the new upgraded translation memory is created on the specified server.
|
Settings Tab
| Box | Description | ||||||
|---|---|---|---|---|---|---|---|
| Description | The translation memory description is displayed in the Translation Memory Settings dialog box. | ||||||
| Copyright | To add a copyright statement to the translation memory, add the copyright text here. For example, if you are creating a translation memory that will be used by someone outside your organization you may want to add some copyright text. The copyright can be viewed in the Translation Memory Settings dialog box. | ||||||
| Enable character-based concordance search | Select this to enable character-based concordance searching.
If the this option is selected, SDL Trados Studio indexes groupings of characters within a word in addition to indexing words in a translation memory. This can result in more partial (fuzzy) matches and bigger indexes. For example, If you enable this option and you search the translation memory for the word Resource, your search results may include Resource, Resources and Sources. The search results include all three words because they each contain groupings of characters that are the same.
| ||||||
| Settings The recognition settings are used to identify elements that do not change during translation. When the recognition settings are enabled, these items are identified as recognized tokens. Recognized tokens can be transferred directly from the current source segment to the new target segment. | |||||||
| Recognize dates | If you select this option, dates in source segments are automatically converted to the correct format to be placed in target segments. If the source segment in a translation memory matches a segment in the presented text in all content apart from the value of the date that occurs in the segment, the TM still registers a 100% match. The TM returns the translation and uses the value of the date from the presented text (rather than from the TM) to complete the translation. This is also the case for matching segments that contain numbers, variables, alphanumeric strings, times, measurements and acronyms. In addition, the value of the date from the presented text will replace the value of the date in the target segment of the TM if the same date is used in both the target and source segment of the TM. If you have defined some auto-localization settings for dates, these will be applied to dates in target segments. You define auto-localization settings for a language pair in the Options dialog box under Language Pairs. | ||||||
| Recognize times | Select this to recognize a time of day occurring in a source segment and convert the time to the correct format in target segments. Times can also be automatically converted to the correct target language format. | ||||||
| Recognize numbers | Select this to recognize a number occurring in a source segment and convert it to the correct format in target segments. For example, suppose the following segment occurs in your English-German translation: Today, the DAX was down 11.98 points (= 0.55%) to 4,312.79. The numbers would appear in the German translation as: 11,98, 0,55%, and 4.312,79. | ||||||
| Recognize acronyms | If you choose to recognize acronyms, they become available interactively in the recognized tokens drop-down list in the Editor view. Acronyms are treated literally (like words) but are still recognized text; this enables you to select them from the recognized tokens drop-down list and insert the acronym quickly into the target segment. An internal regular expression in Studio identifies words as being acronyms when it detects:
Items containing a full stop are not recognized as an acronym. If acronym recognition is activated, URLs (hyperlinks) and IP addresses are also recognized as recognized tokens. | ||||||
| Recognize variables | Select this to recognize variables. Variables are items which should not be translated. You create a list of variables in the Language Resources list. This list appears in the New Translation Memory wizard, the New Server-based Translation Memory wizard, and also in language resource templates . Variables are recognized tokens and are copied verbatim into the target segment. | ||||||
| Recognize measurements | If you choose to recognize numbers (including numbers that are part of a measurement), SDL Trados will place the number in the target segment and format it correctly for the target language. | ||||||
| Recognize alphanumeric |
Select this to recognize any alphanumeric strings found in the source segments. These are codes made up of combinations of:
Instead of trying to translate such strings, Studio automatically transfers the alphanumeric string from the source segment into the target segment. Then it completes the segment translation by inserting the rest of the text from the translation unit. | ||||||
| Import | |||||||
| Import translation units as plain text | When this option is selected, all formatting in the import file is ignored and the translation unit content is imported as plain text. This may be useful if you are importing translation units from an application that handles tags differently to Studio as the imported tag information would not display correctly in Studio. | ||||||
| If target segments differ | |||||||
| Add new translation units | This imports the new translation unit as an addition to the existing ones. | ||||||
| Overwrite existing translation units | This imports the new translation units and overwrites the existing translation units in the translation memory. | ||||||
| Leave translation units unchanged | This keeps the existing translation units and does not import the new ones. For server-based TMs, this option is only available for translation memories created in SDL Studio GroupShare SP2 and later. | ||||||
| Keep most recent translation units | This keeps the most recently changed translation unit. Studio imports a translation unit whose source segment is identical to that of an existing translation unit only if the imported unit is newer than the existing one. If the change date of the translation unit for import is older than the change date of the existing one, Studio does not replace the existing translation unit. For server-based TMs, this option is only available for translation memories created in GroupShare 2014 and later. | ||||||
Server-based TMs
The options Leave existing translation units unchanged and Keep most recent translation units are only compatible with GroupShare 2014 SP2 and later. This means that these options are disabled if you are importing TUs into a server-based TM created in GroupShare 2014 SP1 and earlier. For file-based TMs, these options are always available when importing TM data from Studio 2014 SP2 and later, regardless of the version in which the TM was created.
Language Pairs Tab
| Box | Description |
|---|---|
| Source Language, Target Language | Each row indicates one language pair. Server-based translation memories in Studio are multilingual and may have multiple language pairs listed on this page. File-based translation memories in Studio are bilingual and can only contain one language pair. Therefore, if you are upgrading several translation memories that have the same language pairs but different language variants, you can select the language variants that you want the upgraded file-based translation memory to have. For example, one translation memory is English (United States) - Italian(Italy) and another is English (United States) - Italian (Switzerland). You can select Italian used in Italy or Switzerland for the new upgraded file-based translation memory. |
Compatibility Tab
This is where you specify what data associated with the translation unit is removed or retained in your translation memory in order to optimize the leverage from your new upgraded translation memory.
The legacy translation memory engines, SDL Trados Translator's Workbench and SDLX, applied and stored data associated with a translation unit differently to Studio. In addition, the file format filters worked differently. When you upgrade a translation memory, you can specify what data inside a segment pair is removed or retained in your translation memory in order to optimize the leverage from your new upgraded translation memory. This process makes the content of the translation units in your upgraded translation memory closer to what the file format filters in Studio are likely to produce.
For example, depending on your settings, Microsoft Word's heading numbers and bullet point characters are stored in an SDLX translation memory. In the SDL Trados Studio Microsoft Word filter, it does not allow you to include the heading numbers or bullet point characters in the translation memory. This means that heading information is stored but not the heading number. If you upgrade your translation memory without removing this information from the translation memory, a difference will occur when the translation unit is reused, resulting in penalty or fuzzy match. Eliminating those pieces of data associated with the translation memory should now allow it to result in an 100% match. Although in some situations you may want to retain that data.
Choose one of the following options:
| Box | Description |
|---|---|
The upgraded TM will be primarily used with new, native source files or files processed only with SDL Trados Studio | Imports a version of the translation memory that has had some formatting-related data removed. You might want to do this, for example, if you are a translator and you receive files in their original (native) format with a legacy translation memory. In this case, removing the formatting-related data associated with the translation unit will increase the leverage. |
The upgraded TM will be primarily used with presegmented legacy SDL Trados ITD files and TTX files | Imports a version of the translation memory that retains the legacy translation unit data. You might want to do this, for example, if you are a translator and you receive a pre-segmented legacy bilingual file with a legacy translation memory. In this case, retaining the data associated with the translation unit will increase leverage. |
The upgraded TM will primarily used in mixed scenarios | Imports two versions of the translation unit, one where the data associated with the translation unit will be removed and another one where it retains the data. You might want to do this if you want to permanently upgrade the translation memory, you are using legacy bilingual files and using bilingual files from Studio. Selecting this option will maximize the translation memory leverage in all situations. |
Fields Tab
The Fields tab lists the existing custom fields in the translation memories that you are upgrading. If you upgrading multiple translation memories to a new translation memory, field clashes may occur. For example, you may have a field called Project from one translation memory that has a type as Text and a field called Project from another translation memory with a type as List. Studio automatically renames one of the fields so that one is called Project and the other Project_SinglePicklist.
For more examples of field clashes that may occur, see the SDL Trados Studio 2015 Migration Guide.
To remove a field, select the field and click Remove. Removing a field deletes all corresponding fields values from the translation units as well.
To add a new field, click Add or click inside the Name box on the next row.
| Box | Description |
Name | The name of the field. |
Type | The type of field:
|
Picklist | If you selected List as the type of field, enter the values in this field. Click in the field and a popup is displayed. Enter a value on the first line. Click on the next line to enter another value. When you have entered all of your values, click OK. |
Allow Multiple Values | When this is selected, a translation unit in the translation memory can have more than one value selected for this field. This option is only available for Text and List fields. |
Language Resources Tab
Language resources control the process of segmenting source document text so that it is ready for a translation memory to be applied to the segments. Language resources are stored in the form of lists and rules. Your input translation memories are scanned and any segmentation rules are copied. Depending on the type of translation memory or TMX file you are upgrading, some or all of the segmentation rules can be upgraded. You can also choose to select the default language resources in Studio instead of upgrading your segmentation rules.
| Box | Description |
|---|---|
Language Resources | Select the language resources that you want use with this translation memory. |