Outcomes
TRANSLATE.
Change the language. Keep the meaning.
Translate executes translation workflows automatically, using configured terminology, quality rules and translation paths. These configurations can evolve with your requirements, while each run follows the rules defined for it.
- Terminology
- Translation Memory
- XLIFF
- TMX
- TBX
- Linguistic Quality
QUALITY SHOULD NOT DEPEND ON WHO HANDLES THE FILE.
The revised remedy for the Model 200 has to reach the German and the French service manual. Often that means exporting text, sending files, waiting, importing and checking by hand whether the safety terms are still right. Each round is handled a little differently: terminology drifts, checks depend on who has time, and afterwards nobody can say which step changed what. This makes time and cost hard to plan as well.
HOW THE REVISED REMEDY IS TRANSLATED
The remedy that Convert made a separate unit has been revised in English and now has to reach the German and French manuals. The eight steps below are one configuration for this manual. Other configurations use other translation paths, and translation memory, machine translation and quality checks take part as each process is configured. Terminology and quality requirements guide every run, configurations can be revised as requirements change, and a normal run needs no mandatory human translation or approval step.
Illustrative exampleNot real customer or product data
Source check
Automated checkBefore translation, the revised English remedy is checked against your terminology and writing rules. The check confirms that it uses “emergency stop”, the term your terminology prescribes.
Preparation
AutomatedThe remedy is extracted into XLIFF, the exchange format that translation tools work with. The reference to safety notice “S-14” is marked so it stays as it is.
Earlier translations
AutomatedSentences your translation memory holds unchanged are applied as they are. Close matches are recorded as candidates and not inserted, because a translation memory is only as reliable as what it contains.
Terminology for translation
AutomatedTerms from your termbase are prepared for the translation step, so “emergency stop” becomes “Not-Halt” in German and “arrêt d’urgence” in French.
Machine translation
AutomatedGerman and French are translated through the translation path configured for each language, with your terminology applied.
- ENWait until the spindle has stopped, release the emergency stop and acknowledge the message on the control panel.
- DEWarten, bis die Spindel stillsteht, den Not-Halt entriegeln und die Meldung am Bedienfeld quittieren.
- FRAttendre l’arrêt de la broche, déverrouiller l’arrêt d’urgence et acquitter le message sur le panneau de commande.
Target checks
Automated checkBoth translations are checked against your terminology and language rules, and every protected part and tag is compared with the source. A missing or changed protected part stops the run. Language findings are recorded in the run’s report.
Exceptions
ConditionalNo check found a problem in this run. When a technical validation check fails, the run stops and the report shows why.
Rebuild
AutomatedBoth languages return into the structure of the service manual, ready to be published and delivered through their configured processes like the English one.
QUALITY, TIME AND COST
Every translation weighs quality, time and cost. An automated process starts from quality: terminology, rules and checks are defined first, and each run follows them. Time and cost can benefit from that repeatability; how much depends on your content, your translation assets and your process.
- Quality
- Terminology, defined rules and automated checks before and after translation support consistent execution in every run.
- Time
- Repeatable execution reduces the dependency on manual handoffs between export, translation and import.
- Cost
- Repeatable runs, reuse of earlier translations and a report for every run help make the effort behind a translation more manageable.