TMs added to a project can be prioritized for relevancy and importance. Based on priority, files are pre-translated and suggestions are proposed in the CAT pane during translation.
Projects
TM sequence if manual prioritization is not set:
-
First WRITE TM added to the project.
-
Second WRITE TM (if defined) added.
-
First READ TM added followed by further READ TMs (if defined).
If manually prioritized and saved, sequencing follows the saved order.
Use cases
-
If a different configuration is set for the same TM (Translation step has TM with 1% penalty, while Review step uses a 5% penalty) and
is selected, both penalties cannot be displayed.
Fallback default values:
-
READ mode
-
not selected
-
Define priority order off (WRITE is sorted first and then according to position).
-
Penalty 0%
-
-
A project with two workflow steps, Translation and Review.
-
From the window, select Individual workflow steps then Continue. Only set TM_A in WRITE mode with a 1% penalty for the workflow step.
Save the settings.
-
Go back to the window and select All workflow steps. A message appears stating any changes will overwrite current settings as All workflow steps is selected and settings for individual languages / workflow steps will be lost.
It is recommended to configure TMs for all languages and workflow steps before configuring TMs for individual languages and individual workflow steps.
-
-
Three prioritized TMs: 1) TM_A, 2) TM_B, 3) TM_C. Segment from a job has a match in all three TMs - TM_A has 95%, TM_B 99% and TM_C 100% match. Even if TM_C has the lowest priority, the 100% match from this TM will be used for pre-translation and will be offered at the first position in the CAT pane; the highest matches are always given higher priority.
Project templates
-
Configuration from projects is maintained but also configurable in the project template page.
-
TM configuration/priority is displayed for every workflow step under the workflow column in translation memories section. If there is no workflow step mentioned, TM is then applied to all workflow steps
Shared jobs
-
Vendor can prioritize only owned TMs (Buyer TMs is not visible in Vendor prioritization window)
-
Buyer can prioritize only owned TMs (Vendor TMs are not visible in Buyer prioritization window)
-
If no prioritization defined:
-
Displayed to Buyer:
-
Buyer's WRITE (if more TMs with WRITE mode, the one added first has highest priority)
-
Buyer's READ (if more TMs with READ mode, the one added first has highest priority)
-
-
Displayed to Vendor
-
Buyer's WRITE
-
Vendor's WRITE
-
Buyer's READ
-
Vendor's READ
-
-
-
If only Buyer prioritizes:
-
Displayed to Buyer:
-
Buyer's TMs according to priority
-
-
Displayed to Vendor:
-
Buyer's TMs according to priority
-
Vendor's WRITE
-
Vendor's READ
-
-
-
If only Vendor prioritizes:
-
Displayed to Buyer:
-
Buyer's WRITE
-
Buyer's READ
-
-
Displayed to Vendor:
-
Vendor's TMs according to priority
-
Buyer's WRITE
-
Buyer's READ
-
-
-
If both prioritize:
-
What is displayed to Buyer
-
Buyer TMs according to priority
-
-
What is displayed to Vendor
-
Buyer TMs according to priority
-
Vendor TMs according to priority
-
-
Shared projects
-
Vendor can prioritize only owned TMs (Buyer TMs is not visible in Vendor prioritization window)
-
Buyer can prioritize only owned TMs (Vendor TMs are not visible in Buyer prioritization window)
-
If no prioritization defined:
-
Buyer's WRITE (if more TMs with WRITE mode, the one positioned higher has highest priority)
-
Vendor's WRITE (if more TMs with WRITE mode, the one positioned higher has highest priority)
-
Buyer's READ (if more TMs with READ mode, the one positioned higher has highest priority)
-
Vendor's READ (if more TMs with READ mode, the one positioned higher has highest priority)
-
-
If only Buyer prioritizes:
-
Buyer TMs according to priority
-
Vendor's WRITE
-
Vendor's READ
-
-
If only Vendor prioritizes:
-
Vendor TMs according to priority
-
Buyer's WRITE
-
Buyer's READ
-
-
If both prioritize:
-
Buyer TMs according to priority
-
Vendor TMs according to priority
-