![\"\"](\"https:\/\/www.textform.com\/tf2019\/wp-content\/uploads\/2020\/02\/flawed_perfection.png\")
<\/p>\n<\/p>\n
Highly praised and frowned upon, machine translation<\/a> is a hot topic for the translation industry. It causes fear of drastic changes while promising increased productivity and quality. Without predicting either scenario, it will certainly change the industry in the near future. As in so many other industries, the potential conflict resulting from such scenarios is based on the supposed superiority of machines over humans. That\u2019s why it\u2019s worth taking a look at the details to understand why machines have not yet prevailed.<\/p>\n <\/p>\n Neural Machine Translation (NMT) still has some obstacles to overcome, despite amazingly good results. An example that is commonplace for text&form<\/a> will be used here to shed light on two of these obstacles. They may seem marginal at first, but the difference between a human-like and a common machine translation is governed by details like these. First, read the following (admittedly very technical) sentence:<\/p>\n “For instance, while a healthcare monitoring service might suffice with single cellular network coverage, a trucking fleet might require more than one mobile network footprint.”<\/em><\/p>\n First of all, a little bit of context: The text is about so-called machine-to-machine communication (such as the healthcare monitoring service or the trucking fleet mentioned above) and the SIM cards required for this (paraphrased with \u201ccellular network<\/a>\u201d and \u201cmobile network footprint\u201d), which enable wireless information exchange. More precisely, the sentence draws attention to the requirements for the mobile network depending on the scope of the machine-to-machine application. At least that\u2019s how I interpret this sentence, as does our auditor. However, that is not the case when translating the sentence into German with several major NMT providers. They usually interpret the sentence as follows:<\/p>\n “W\u00e4hrend z.B. ein Gesundheits\u00fcberwachungssystem mit einem einzigen Mobilfunknetz ausreichen k\u00f6nnte, k\u00f6nnte eine LKW-Flotte mehr als ein Mobilfunknetz ben\u00f6tigen.”<\/em><\/p>\n Don\u2019t worry if you don\u2019t speak German. Translating this sentence back into English illustrates the problem perfectly fine:<\/p>\n “For example, while a healthcare monitoring system might be enough with a single cellular network, a trucking fleet might require more than one mobile network footprint.”<\/em><\/p>\n By the way, the translation is deliberately modified so that the results cannot be traced back to a specific NMT provider. The key point, however, is always the same: in the first independent clause, it is the healthcare monitoring system that is enough<\/em>, although the sufficiency in question refers to the cellular network. The sentence doesn\u2019t become completely incomprehensible, but I doubt that any auditor would be turning a blind eye on a case like that.<\/p>\n <\/p>\n The reason for that is embedded in the design of these NMT<\/a> engines. Our “test subjects” source their ability to translate from text corpora. These bilingual texts are tremendous in size and linguistically flawless. Feeding such large quantities of data to an engine enables it to understand what a specific word means \u2013 at least in another language. Thus all of our test subjects have learned that in German, the verb to suffice<\/em> always translates to ausreichen<\/em> or one of its close synonyms. We cannot blame our test subjects nor their developers: they only learned or taught to the best of their knowledge. What our digital competitors are not aware of is the use of non-standardized language. In this case the use of to suffice with<\/em> in the sense of to make do with<\/em>. The German verb ausreichen<\/em> doesn\u2019t reflect this meaning; neither do its synonyms. It\u2019s not surprising that our test subjects don\u2019t know that usage of to suffice with<\/em>, since it\u2019s not standard and generally a rare sight. And yet the author of the text has chosen this construction. And although it can be found in a freely accessible translation memory associated to one of our test subjects, it is simply not common enough for the engine to consider that translation. In other words, the design of these NMT engines is too perfect to translate such informal expressions correctly.<\/p>\n At this point, you might have questioned the usage or even the existence of the aforementioned construction. And you are not to be blamed for that. But ultimately, there are two rather disenchanting facts that you should consider: First, language works in mysterious ways, and second, both biological and digital translators eventually have to work with what\u2019s on the (metaphorical) table.<\/p>\n To sum up: Informal language usage will remain the NMT\u2019s Achilles’ heel, unless we find the right balance between correct and informal training data. Despite all that, it\u2019s worth mentioning that this problem is not limited to machines, as humans are far from perfect themselves. In the next installment of this article, we will therefore look at a very human workaround for this problem: bridging.<\/p>\n to be continued<\/em><\/p>\n About the Author<\/em><\/p>\n <\/p>\n <\/p>\n <\/p>\nA Closer Look<\/h2>\n
Flawed Perfection<\/h2>\n
\n![\"Daniel](\"https:\/\/www.textform.com\/tf2019\/wp-content\/uploads\/2020\/01\/daniel_nad_project_manager_textform-300x300.png\")
<\/p>\nOrganized sounds, manifested in abstract character strings with thousands of mutually unintelligible variants: human languages are fascinating. At least according to our author Daniel Nad. As a passionate linguist and PM at text&form<\/a>, he experiences language on a daily basis –\u00a0and enjoys sharing his passion with others.<\/div>\n
![\"Join](\"https:\/\/no-cache.hubspot.com\/cta\/default\/5306090\/087b4f07-6a28-438f-a182-3ad47941a092.png\")
<\/a><\/span>