Pre-translation is the initial application of non-translatables, translation memories, machine translation and/or human translation engines against a source text before it is presented to the Linguist in an editor.
Pre-translation settings can be set in global settings, when creating or editing a project or when defining a project template.
They can also be set for individual jobs via the Pre-translate button in the job table but without options for the auto-propagation of repetitions.
If the correct settings are not applied for a selected resource (TM/NT/MT), the pre-translation will fail with an error message.
-
-
-
Use of a TM if assigned to the project and pre-translation threshold.
The pre-translation threshold specifies the minimum score required for insertion of translation memory matches.
-
-
Use of MT and/or QPS if assigned to a project.
Available MT is presented in job resources notifications in the CAT editor.
-
-
Using this option does not save confirmed 100%/101% matches into the project's TM in the write mode.
-
100% non-translatables
-
Project Manager users can define the for automated confirmation of segments pre-translated from MT based on the QPS score.
Default threshold is set to 100%. Segments confirmed after pre-translation are not saved into the project's TM in the write mode.
Note
QPS threshold customization is available for Team plans and higher. Get in touch with Sales for licensing questions.
-
-
Set job or project to 'completed' options.
-
Use Case
-
Confirm and lock translated segments
Configure pre-translation settings to prevent duplicated effort by translation providers and ensure the job analysis accurately reflects the work required:
Pseudo-translation is used to create dummy text based on the target language. Both ASCII and Non-ASCII characters are supported. The text is used to simulate how a translated text may appear inside a layout based on contraction or expansion due to the translation. Pseudo-translation can also help indicate all translatable text is exported.
Pseudo-translation options
-
:
Specified character(s) is added to source text.
-
:
Specified character(s) is added to the beginning of the segment.
-
:
Specified character(s) is added to the end of the segment.
-
:
A comma separated list of characters can be provided.
Example:
-
:
For pseudo-translations with a segment key, a pseudo-string to be prepended with a numerical hash value of the segment key can be provided.
-
:
Specify how much contraction is anticipated.
Using QPS in pre-translation reduces the amount of content requiring post-editing.
High quality matches from a TM are inserted into target segments and auto-confirmed. The rest of the job is populated from MT and segments with a QPS score above the threshold are auto-confirmed. Linguists need only focus on low quality matches that require their attention. In some cases, jobs may be fully auto-confirmed and set to completed without any human post-editing.
If set at the organization level, all projects benefit from the workflow and pre-translation can be adjusted for individual project templates or projects.
To use QPS in pre-translation, follow these steps:
-
Select the translation memories and Phrase Language AI profile for the project.
-
From the Settings
page, scroll down to the section and select Pre-translation.
The page opens.
For an individual project template or project, click Edit on the project page.
The page opens.
-
Optimize the pre-translation settings:
-
From the Settings menu, click Pre-translation.
The settings are presented.
-
Set threshold to 100%
-
Enable .
-
Enable .
-
Enable .
-
:
-
101% and 100% translation memory matches
-
100% non-translatable matches
-
Machine translation matches
Configure QPS threshold for machine translation according to quality goals. The default value is 100, but a different good enough score can be used when lower machine translation quality is acceptable.
-
-
Ideally, enable to ensure pre-translation is applied to all jobs.
-
to .
-
Click Save.
The settings are applied to the project or to the organization.
-