Project Management

Pre-translation (TMS)

Content is machine translated from English by Phrase Language AI.

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 at the project level in general settings, when creating a new 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.

Pre-translation Options

If the correct settings are not applied for a selected resource (TM/NT/MT), the pre-translation will fail with an error message.

  • Translation memory (TM)

    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.

  • Non-Translatables (NT)

  • Machine translation (MT)

    Use of MT and/or QPS if assigned to a project.

    • The Use machine translation for segments with a TM match of 100% or more option is unselected by default for new organizations and pre-selected for existing organizations.

      If unselected:

      • MT is not requested until TM results are fetched and there are no 100/101% matches.

      • Autocomplete will also not trigger the MT request.

      • Resource status provides notification to users.

  • Overwrite

  • Repetitions

    Auto-propagation

  • Set segment status to confirmed for

    Using this option does not save confirmed 100%/101% matches into the project's TM in the write mode.

    • Machine translation matches

      Project Manager users can define the QPS threshold 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.

  • Pre-translate & set job to complete

  • Lock

Pre-translating with QPS

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:

  1. Select the translation memories and Phrase Language AI profile for the project.

  2. From From the Settings Setup_gear.png page, scroll down to the Project settings section and select Pre-translation.

    The Pre-translation page opens.

    For an individual project template or project, click Edit on the project page.

    The Edit page opens.

  3. Optimize the pre-translation settings:

    1. From the Settings menu, click Pre-translation.

      The Pre-translation settings are presented.

    2. Set Pre-translate from translation memory threshold to 100%

    3. Enable Pre-translation non-translatables.

    4. Enable Pre-translate from machine translation.

    5. Enable Display quality-estimated machine translation matches in Phrase CAT editor.

    6. Set segment status to confirmed for:

      • 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.

    7. Ideally, enable Pre-translate on job creation to ensure pre-translation is applied to all jobs.

    8. Set job to completed once to Pre-translated and all segments are confirmed.

    9. Click Save.

      The settings are applied to the project or to the organization.

Pseudo-translation

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

  • Pseudo-translate using:

    Specified character(s) is added to source text.

  • Add to target segment start:

    Specified character(s) is added to the beginning of the segment.

  • Add to target segment end:

    Specified character(s) is added to the end of the segment.

  • Transliterate:

    A comma separated list of characters can be provided.

    Example:

    aá,AÁ,bь,Bβ,cć,CĆ,dđ,DĎ,eé,EÉ

  • Segment key hash length (characters):

    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.

  • Target segment length (%):

    Specify how much contraction is anticipated.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question, submit a request to our Support team.
Thank you for your feedback.