{"id":9562,"date":"2023-10-23T07:48:00","date_gmt":"2023-10-23T07:48:00","guid":{"rendered":"https:\/\/www.oneword.de\/artikel\/terminology-for-machine-translation\/"},"modified":"2026-08-06T06:54:39","modified_gmt":"2026-08-06T06:54:39","slug":"terminology-for-machine-translation","status":"publish","type":"post","link":"https:\/\/www.oneword.de\/en\/artikel\/terminology-for-machine-translation\/","title":{"rendered":"Terminology for machine translation: effective approaches to improve the quality of translation output"},"content":{"rendered":"\n
\n
\n

As good as the results of machine translation are, they are still far from perfect. Above all, it's the rendering of specialised terminology that plays a decisive role in the quality of the output. This is because specialised terms are often translated incorrectly, inconsistently or at least in a way that deviates from a company's corporate language. So we explain when and how terminology can be integrated into machine translation and what needs to be taken into account in the process.<\/p>\n<\/div><\/div>\n<\/div>\n\n

\n
\n

MT systems<\/a> generally translate texts and the terminology they contain "as learnt", i.e. as trained by the training material. This is because neural machine translation works on the basis of statistical probability, analysing how often a foreign-language equivalent for a word occurs in the training corpus and what other words occurred in the same sentence.<\/p>\n\n\n\n

As far as specialised terms are concerned, this means that standardised terms for which there are few or no common synonyms are usually rendered correctly and consistently by MT systems. This is because standardisation means consistent use across many sources. On the other hand, terms that occur rarely or very inconsistently in the training material will be translated freely, incorrectly or differently from one instance to the next. This is because a proliferation of different terms, either within a company or across many companies and or even industries, ultimately manifests in the form of variants in MT output. Depending on the standardisation, subject area, text content and company specifications, the translation offered by an MT system may therefore run counter to expectations.<\/p>\n\n\n\n

In a recent article on domain-specific MT systems<\/a>, we showed that there is no significant difference between the use of generic and domain-specific MT engines when it comes to the rendering of specialised terminology. Specialised terms were translated inconsistently in both types of system. However, it's precisely this inconsistency that many companies have been battling against for years or decades by undertaking systematic terminology work<\/a> and managing their terminology in the form of databases or Excel files. And since specialised vocabulary plays such an important role in the quality of the translation, when using machine translation, we have to ask: how we can get the desired terminology into the MT output?<\/p>\n\n\n\n

There are three approaches to integration and implementation: before, during and after machine translation. In the discussion below, we work through the options, starting with the last one, and take a look at the details.<\/p>\n<\/div><\/div>\n<\/div>\n\n

\n
\n

After machine translation: correcting terminology during post-editing<\/h2>\n\n\n\n

Even though correcting terminology is one of the most time-consuming aspects of post-editing machine translation output<\/a>, the integration of specified terminology in the form of glossaries or databases is a decisive factor in text quality. This is because where MT systems do not translate specialised terms or fail to translate them consistently, post-editors need the clearest possible specifications in order to correct the machine output.<\/p>\n\n\n\n

In practice, this means that all important specialised terms must be defined, preferably in a database format, and integrated into the post-editor's working environment. Integrating this information into CAT tools means that source-language terms are recognised and the target-language equivalents are suggested directly. This allows source and target terms to be clearly linked and prevents the disorganised proliferation of terminology variants in MT systems.<\/p>\n\n\n\n

Doch auch Termini, die von einer Engine bereits einheitlich \u00fcbersetzt wurden, k\u00f6nnen den Corporate-Language-Vorgaben eines Unternehmens widersprechen. In einem unserer Praxistests enthielt ein Text aus dem Automotive-Bereich im Deutschen den Terminus \u201eSpurhalteassistent\u201c. In W\u00f6rterb\u00fcchern ist der Terminus oft gar nicht zu finden und ein Blick auf die Websites verschiedener Hersteller zeigt, dass im Englischen von \u201elane keeping assist\u201c bis \u201elane guard system\u201c viele Varianten kursieren. Erwartbar ist dadurch auch ein entsprechender Variantenreichtum bei der maschinellen \u00dcbersetzung.<\/p>\n\n\n\n

Doch auch wenn ein MT-System eine der \u00dcbersetzungsm\u00f6glichkeiten konsistent umsetzen w\u00fcrde, kann diese immer noch der Vorgabe des jeweiligen Unternehmens widersprechen und muss dann beim Posteditieren im gesamten Text ersetzt werden. Bei der Umsetzung von Terminologie nach erfolgter maschineller \u00dcbersetzung kommen also sowohl den Posteditor:innen als auch der Qualit\u00e4t der Vorgaben entscheidende Rollen zu.<\/p>\n<\/div><\/div>\n<\/div>\n\n

\n
\n

During machine translation: integrating terminology by means of a glossary<\/h2>\n\n\n\n
\n
\n

Many providers of MT systems allow you to integrate specified terminology in the form of glossaries, which are made available to the MT engine during translation. The advantage of the glossary function clearly lies in its dynamic nature. If specified terms change or new ones are added, the glossary can be added to or even reduced if terms become superfluous.<\/p>\n<\/div><\/div>\n\n\n\n

\n

Providers differ in terms of the supported language pairs and the file formats in which the glossaries need to be provided. While some providers only support list formats such as .csv, others can work with the terminology database standard .tbx.<\/p>\n<\/div><\/div>\n<\/div>\n\n\n\n

However, although the entire database could theoretically be quickly exported and used as a glossary, this makes little practical sense for at least two reasons.<\/p>\n\n\n\n

Firstly, MT systems usually cannot work with additional information such as usage, i.e. information on whether a term is preferred, permitted or prohibited. Either the information is ignored and forbidden terms are interpreted as valid translations, or the system completely rejects entries that appear ambiguous. Ideally, the MT system should be provided with positive one-to-one terminology \u2013 i.e. only unambiguous equivalents and only preferred terms for the target language.<\/p>\n\n\n\n

Secondly, when creating a glossary, the number of defined terms must also be carefully considered. A large number of terms may not affect the turnaround time of the machine translation, but it does have a significant impact on its quality. The more specified terms the machine receives, the more the neural approach is cancelled out and the MT system is narrowly constrained. The result is often a stringing together of terms from the database, resulting in clumsy-sounding sentences. Best practice is therefore a "bottom-up" strategy, in which glossaries are populated with a limited number of important core terms. The machine output is then checked for terminology errors and any terms that are regularly associated with errors can be added to the glossary.<\/p>\n\n\n\n

It's important to look at the native output of translation engines. Depending on the subject area and language, many terms from a company database may not need to be included in a glossary as MT systems already use the desired terminology due to their statistical frequency. For example: a company has an entry in its terminology database for "Schraubendreher" (screwdriver) because the use of this standardised term and its synonym "Schraubenzieher" has been defined. From a terminological point of view, this entry makes perfect sense, but it is superfluous for a glossary for the German-English language direction. It can be safely assumed that every MT system will natively translate both "Schraubendreher" and "Schraubenzieher" as "screwdriver" as this is by far the most common and standardised English equivalent.<\/p>\n<\/div><\/div><\/div>\n<\/div>\n\n

\n
\n

Before machine translation: consistent terminology in the training material<\/h2>\n\n\n\n
\n
\n

MT training promises to raise the quality of machine output to a new level. Through targeted training using company data, the appropriately trained MT system should not only translate technical details correctly but also in accordance with the defined style and corporate language. This requires comprehensive but linguistically clean training material for the desired language pair, which is then used to train a customised MT engine.For the purposes of specifying terminology, this means that all training material must contain the desired terminology in a clear, consistent form.<\/p>\n<\/div><\/div>\n\n\n\n

\n

As a general principle, a source text should contain plenty of variants while the target language should be kept consistent. The above example of "Schraubendreher" (screwdriver) is a good illustration of this. The source language material must contain both German terms, i.e. "Schraubendreher" and "Schraubenzieher". If possible, both terms should be used in different inflections and in a variety of sentences. In the target language \u2013 in our example English \u2013 only "screwdriver" should be included to ensure consistent translation.<\/p>\n<\/div><\/div>\n<\/div>\n\n\n\n

As the training material is usually put together from translation data acquired over many years or decades, consistency in terminology is usually wishful thinking. This makes it all the more important to clean up the data before training so that the machine can learn the desired terminology.<\/p>\n\n\n\n

Incidentally, it would be inappropriate to simply transfer the desired terminology to the MT system in list form as training material. A simple word list lacks the context that is so important for NMT systems and which is used for statistical comparison: with what other words does the word you are looking for often occur, and how is it translated in different sentences? An NMT system cannot learn anything from the list format without context.<\/p>\n<\/div><\/div><\/div>\n<\/div>\n\n

\n
\n

In summary<\/h2>\n\n\n\n

It's imperative that machine translation has specified terminology to work with if it is to match human translations in terms of quality. Whether this is integrated into the translation output before, during or after the use of MT depends on the process and the capabilities of the systems. However, the quality and preparation of terminology play a decisive role.<\/p>\n\n\n\n

Would you like more information about the interaction between terminology and machine translation? Or would you like to know how your organisation's terminology can be integrated into machine translation? Then get in touch with us at mtpe@oneword.de<\/a> or use our contact form.<\/strong><\/p>\n\n\n\n

Get in touch with us now!<\/span><\/a><\/div>\n<\/div><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":7,"featured_media":9563,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_nectar_blocks_hide_post_title":false,"_nectar_blocks_transparent_header_effect":false,"_nectar_blocks_transparent_header_effect_color":"light","_nectar_blocks_header_animation":false,"_nectar_blocks_header_animation_delay":0,"_nectar_blocks_header_animation_effect":"fade","_nectar_blocks_page_css":"","_nectar_blocks_page_js":"","inline_featured_image":false,"footnotes":""},"categories":[69,64],"tags":[],"class_list":["post-9562","post","type-post","status-publish","format-standard","has-post-thumbnail","category-terminology","category-ai"],"_links":{"self":[{"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/posts\/9562","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/comments?post=9562"}],"version-history":[{"count":8,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/posts\/9562\/revisions"}],"predecessor-version":[{"id":12258,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/posts\/9562\/revisions\/12258"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/media\/9563"}],"wp:attachment":[{"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/media?parent=9562"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/categories?post=9562"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oneword.de\/en\/wp-json\/wp\/v2\/tags?post=9562"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}