/
Machine translation (MT) – most common issues & troubleshooting

Machine translation (MT) – most common issues & troubleshooting

Introduction

Below are the most common problems clients report in tickets concerning the Machine translation (MT) engines.

When submitting tickets, remember that XTM Cloud is only an intermediary between you and a particular MT service provider. We are not responsible for the quality of the returned text and can only influence the overall process in a relatively small way.

Before reading the article below, we recommend that you read the step-by-step guideline to setting up machine translation (MT): How to enable and set up machine translation (MT).

Before reading the article below, we recommend that you read the step-by-step guideline to setting up machine translation (MT): How to enable and set up machine translation (MT).


Issue description & Solution

MT engine fails during synchronization

Solution: Perform the following initial checks in your MT connection details (administrative privileges required!) before submitting a ticket:

  • Check that no additional white spaces are present.

  • Check if your credentials are correct. If you have another set of credentials, check them as well.

  • Check if your MT engine's API panel permits connections to the outside world (especially Google MT).

  • If nothing happens when you click on Synchronize, or there is an error, open the Dev Tools in your browser and check for error messages (see the following article for help: How to use browser's a developer tools (Dev Tools)?).

MT engine fails to process some of the segments

Solution: Perform the following initial checks before submitting a ticket:

  • Check that you have not hit any of the limits in your MT API. Both the character and time limits are important.

  • Check if the MT engine you are using can match the remaining segments with XTM Workbench mode (we recommend that you select the After analysis and in XTM Workbench option in your MT engine connection details).

  • Check if the affected segments have special characters or similar, which can influence the MT output.

  • The MT engine may be configured to ignore certain segments based on project settings:

    • Review the project's general information page to check if the MT engine is set to ignore specific types of TM matches.

    • Adjust settings as necessary to allow for broader translation coverage.

MT engine fails to process all segments

Solution: Perform the following initial checks before submitting a ticket:

  • Check if the MT engine is activated at project level in Project editor → General infoMachine translation.

  • Check the project's Metrics. If there are only ICE, Leveraged and other kinds of matches then your MT is probably configured to ignore such segments and not provide a translation for them. Check your project's General info page (see the screenshot from the previous bullet point).