Pre-Translating Files

You can automatically apply matching translations from a TM database, and if there are spots where you do not have matches, you can choose to have Lingo fill in those segments with matches from a machine translation provider. See Applying Translation Memory Suggestions.

Example  

Let’s say you are translating a project using a TM that has been passed along to you from a former colleague. It was assembled using translations from lots of other projects, and you're not sure exactly how accurate it will be, but you want to make a first pass through your project to see what matches there are.

You build a new project and add the TM, then tell Lingo to pre-translate the project using matches from the TM only. When it finishes, you have a few solid matches and a lot of fuzzy matches. However, you also have quite a few empty segments.

You decide to rebuild the project and add an MT provider as a backup for the pre-translation option, because you know it will fill in the gaps where you are missing translations. You also know it will provide machine translated suggestions in the TM Suggestions area for all your segments, so you can refer to these when updating your fuzzy translations later.

When the new project finishes, you have translations for most of your segments. Now you can review the MT suggestions and make any necessary adjustments, and then add new translations where needed. When you're done, you can add all the completed translations to the existing TM so you'll have a better database to work with in the future.