In order to use a translation memory for analysis, pre-translation, or for the actual translation in the Memsource Editor, the TM must be assigned to a project first. Multiple TMs can be assigned to one project, and one TM can be assigned to multiple projects.
Translation Memories in your project
Open your project and scroll down to a section labeled Translation Memories. The assigned TMs are listed there, including the target languages and the TM's settings.
There are two options there:
- Click the Create New button to create a new translation memory that will automatically be assigned to this project.
- Or, you can click Select and assign a previously created TM. You can also use this button to unassign any TMs that is already assigned to the project.
- For project with multiple target languages, you can either choose one language or you can use "all" (only TMs containing all languages will be then listed in the TM selection)
- For projects with Workflow, you can either choose one step or all steps (see details below).
Selecting the TMs for a Project
There are several different options for each TM that you can use:
- Read: The Analysis, Pre-translate and the Editor will be able to access the content of the TM selected as Read. Unchecking the Read checkbox will unassign the TM from the project. TM with the reverse source and target languages can be assigned as Read-only (see Languages and Locales).
- Write: With this feature checked, any segments confirmed in the Memsource Editor or uploaded via "Tools > Upload job" with will be saved into the TM. There must be at least one Write TM among the selected TMs.
- Source Language: This is where the source language of your saved TMs is displayed.
- Target Langues: This section shows the all target languages each TM has, regardless of which languages are in your current project.
- Penalty (%): Here you can set the penalty percentage for TM matches for your Analysis, Pre-translate and the Memsource Editor. See the Setting Penalties section below for more information.
There are a few important things to note:
- At least one TM must be set for Write. (The maximum is two "Write" TMs per language and Workflow step in a project).
- There can be up to 10 TMs assigned to each project (per language and Workflow step).
- Relevant TMs are displayed first. Relevant TMs are determined based on the Client, Domain, Subdomain and user rights of the Project Manager.
- A filter is available as shown in the picture above. You can use it to search for TMs by name, their ID number (on the far left side), or by the client's name.
- The first selected TM will be automatically selected for Write mode. You can change this if you select a different TM to be designated for Write mode.
Languages and Locales
As mentioned above, the source and target languages of your TM must be the same as the languages in your project. However, Memsource allows the selecting of TMs that have the reverse source-target combinations. For example, a TM that has English as the source and German as the target can be used for a project with German as the source and English as the target as shown below. These TMs will be read-only in the project.
Memsource also allows you to add a TM to a project with the same language but a different locale.
Generally, all languages with the same prefix can be added (EN, EN_GB, EN_UK, etc.). For example, if you create a TM with German and English as your languages, you can assign TMs that use both DE and DE_CH as well as EN_GB and EN_US. (It also does not matter which is the source language and which is the target). However, keep in mind that all translation units will be stored as EN only with no distinction between US and GB. Therefore, using this TM for strictly GB or US projects might be inaccurate.
Note that for certain languages, the code has a different prefix. For example, Norwegian has the code "NO" and Norwegian (Bokmål) has code "nb-NO”—these two languages cannot be mixed.
TM for Workflow Steps
When selecting TMs for projects with Workflow steps, you can decide whether the same translation memories should be selected for all of the project's Workflow steps or whether each Workflow step should have its own TM set up.
Note: You can select a TM for all Workflow steps and all languages. Afterwards, you can assign one specific TM to one step and one language (if needed). However, this does not work in the reverse order; you cannot select a TM for a specific step and language, and afterwards select a TM for all of the rest of the steps and languages.
Recommendations for Workflow steps
If you are using proofreading on a regular basis, we recommended that you do the following:
- Create a TM for proofreaders only, where only reviewed translations will be stored (for example, TM_REV) and always assign it as Read for the translation step and as Write for the revision step.
- Create a TM for translation only (for example, TM_TRA) and assign it as Write for the translation step and READ in the revision step.
- You can even set a 2% penalty to TM_TRA so that the matches from TM_REV always have priority. This would mean that 101% matches from TM_TRA will be shown as 99% matches in T_REV. For more information on this, see Setting Penalties below.
- After a project is completed and all translation is reviewed and saved in TM_REV, you can then delete TM_TRA.
Setting Penalties for Translation Memories
If you assign multiple TMs to a project but want to prefer matches from only one (or a few selected TMs), you can set a penalty for any of the selected TMs, as shown below. These settings will impact the pre-translation, analysis, and the matches offered to the Linguists in the Memsource Editor.
In addition to applying penalties to an entire TM, you can also apply a 1% penalty to 101% (in-context) matches within a TM. This option is useful, for example, if you would like a Linguist to decide which 101% match from different TMs should be used in a translation. The penalty will mean that none of the in-context matches are inserted automatically into the target segment if the text is pre-translated.
If you do decide to penalize 101% matches, the penalized matches will be displayed in a new order in the CAT Pane. That is, a 101% match penalized by 2% will become a 99% match. A little arrow indicating the penalization will be shown next to the percentage number.
Articles related to Translation Memory:
Articles related to Project: