{"id":3867,"date":"2026-10-09T09:50:00","date_gmt":"2026-10-09T08:50:00","guid":{"rendered":"https:\/\/nadiapereira.pt\/?p=3867"},"modified":"2026-11-04T12:09:19","modified_gmt":"2026-11-04T11:09:19","slug":"traducao-automatica-vs-tradutor-humano-quando-vale-a-pena-cada-uma","status":"publish","type":"post","link":"https:\/\/nadiapereira.pt\/en\/traducao-automatica-vs-tradutor-humano-quando-vale-a-pena-cada-uma\/","title":{"rendered":"Machine translation vs. human translators: when is each one worth it?"},"content":{"rendered":"<div class=\"wp-block-stackable-image stk-block-image stk-block stk-6bb2ed5\" data-block-id=\"6bb2ed5\"><style>.stk-6bb2ed5 {margin-bottom:50px !important;}.stk-6bb2ed5 .stk-img-wrapper{aspect-ratio:3\/1 !important;height:380px !important;}.stk-6bb2ed5 .stk-img-wrapper img{object-position:49% 20% !important;}<\/style><figure><span class=\"stk-img-wrapper stk-image--shape-stretch\"><img loading=\"lazy\" decoding=\"async\" class=\"stk-img wp-image-4012\" src=\"https:\/\/nadiapereira.pt\/wp-content\/uploads\/2026\/10\/deepl-vs-google.jpg\" width=\"1665\" height=\"1218\" srcset=\"https:\/\/nadiapereira.pt\/wp-content\/uploads\/2026\/10\/deepl-vs-google.jpg 1665w, https:\/\/nadiapereira.pt\/wp-content\/uploads\/2026\/10\/deepl-vs-google-300x219.jpg 300w, https:\/\/nadiapereira.pt\/wp-content\/uploads\/2026\/10\/deepl-vs-google-1024x749.jpg 1024w, https:\/\/nadiapereira.pt\/wp-content\/uploads\/2026\/10\/deepl-vs-google-768x562.jpg 768w, https:\/\/nadiapereira.pt\/wp-content\/uploads\/2026\/10\/deepl-vs-google-1536x1124.jpg 1536w, https:\/\/nadiapereira.pt\/wp-content\/uploads\/2026\/10\/deepl-vs-google-16x12.jpg 16w\" sizes=\"auto, (max-width: 1665px) 100vw, 1665px\" \/><\/span><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">It\u2019s the question every translator hears time and again: isn\u2019t Google Translate or DeepL enough? The short answer is: <strong>it depends on what could go wrong<\/strong>. When it comes to understanding an email from a supplier, machine translation is an excellent tool. But when it comes to a clinical report, a contract or a machine manual, it\u2019s not quite the same. Let\u2019s see where the line is drawn.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What machine translation does well<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Today\u2019s neural network-based engines have improved immensely and produce fluent sentences. They are excellent for three things: grasping the gist of a text you don\u2019t fully understand, translating low-risk internal communications, and generating a first draft that someone will then review.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The criterion is simple. If a mistake costs, at most, a misunderstanding that can be resolved with another email, the system works. If a mistake could cost someone their health, money, a legal deadline or a company\u2019s reputation, the system is no longer fit for purpose on its own.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Where the problems begin: specialised translation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In specialist texts, the risk does not lie in the grammar \u2013 which machines usually get right \u2013 but in the meaning. Each field has its own terminology, conventions and implications:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Medical:<\/strong> The abbreviation \u2018MS\u2019 can stand for multiple sclerosis, morphine sulphate or mitral stenosis. A human translator specialising in the field makes a judgement based on the clinical context; a machine chooses the most likely option, which is not always the correct one. A missed negation or an incorrectly converted dose can have serious consequences.<\/li>\n\n\n\n<li><strong>Scientific:<\/strong> The strength of a statement is measured by the verbs used. \u2018Suggests\u2019, \u2018indicates\u2019 and \u2018demonstrates\u2019 do not carry the same weight, and swapping one for another alters what the study claims.<\/li>\n\n\n\n<li><strong>Technical:<\/strong> The same term must always be translated in the same way. If \u2018bracket\u2019 appears as \u2018support\u2019 on one page and as \u2018angle bracket\u2019 on the next, the person carrying out the maintenance will waste time or install it incorrectly.<\/li>\n\n\n\n<li><strong>Legal:<\/strong> Many terms belong to different legal systems and have no exact equivalent. In English law, \u2018consideration\u2019 refers to the consideration provided by each party, not \u2018consideration\u2019 in the general sense; and replacing \u2018shall\u2019 with \u2018may\u2019 transforms an obligation into a possibility.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">What makes this tricky is that machine translation produces fluent text even when it is incorrect. It may omit sentences or add others, and the result reads so well that nobody suspects a thing. Only those who are fluent in the source language and familiar with the subject area can spot what has been left out.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Proofreading and post-editing: where the human eye makes all the difference<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When the text is sensitive, the crucial factor is not who writes the first draft, but who reviews it. The industry calls it <strong>post-editing<\/strong> to the hybrid model in which a human translator uses the machine-translated text as a starting point and corrects it. The standard <a target=\"_blank\" rel=\"noopener\" href=\"https:\/\/atc.org.uk\/wp-content\/uploads\/ISO-Blog-18587-Machine-translation-post-editing.pdf\">ISO 18587<\/a>, which is dedicated to this process, argues that only qualified post-editors should be involved and that the final post-edited version should be of a quality comparable to that of a human translation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There is also the standard <a target=\"_blank\" rel=\"noopener\" href=\"https:\/\/www.tuvsud.com\/en-us\/services\/management-system-certification\/iso-17100\">ISO 17100<\/a>, for translation services, which requires each translation to be reviewed by a second qualified linguist before delivery. It is easy to see why: translators tend to read what they meant to say, rather than what is actually there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What a human proofreader checks, apart from grammar:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>correct and consistent terminology from start to finish;<\/li>\n\n\n\n<li>numbers, units, dates and proper names;<\/li>\n\n\n\n<li>sentences omitted or added without notice;<\/li>\n\n\n\n<li>tone, style and conventions appropriate to the reader and the target country.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">And in some cases, there\u2019s no debate at all. According to the <a target=\"_blank\" rel=\"noopener\" href=\"https:\/\/www.dges.gov.pt\/ost\/kb\/faq.php?id=242\">DGES<\/a>, when a certified translation is required in Portugal, it is certified by bodies such as notaries, solicitors, legal practitioners, consulates or chambers of commerce and industry, and the translator must declare to them that the text is an accurate translation. No machine can do that.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">So, when should you use which one?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The higher the cost of a mistake, the more human eyes the text needs. This is my rule of thumb:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Text type<\/th><th>Just machine translation?<\/th><th>What I recommend<\/th><\/tr><tr><td>To understand an email or a web page<\/td><td>Yes<\/td><td>Machine, no problem<\/td><\/tr><tr><td>Low-risk internal communication<\/td><td>Yes, carefully<\/td><td>Machine; review if text is to be circulated<\/td><\/tr><tr><td>Website, marketing and brand communication<\/td><td>No<\/td><td>Human translator, or post-editing by a professional<\/td><\/tr><tr><td>Technical documentation and manuals<\/td><td>Just as a draft<\/td><td>Post-editing by a technical translator, with a glossary<\/td><\/tr><tr><td>Scientific articles and reports<\/td><td>Just as a draft<\/td><td>Post-editing by a specialist in the field and proofreading<\/td><\/tr><tr><td>Medical documents<\/td><td>No<\/td><td>Specialist translator and proofreading by a second linguist<\/td><\/tr><tr><td>Contracts and legal or official documents<\/td><td>No<\/td><td>Legal translator; certified translation where required<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">A good translator does not compete with the machine: they use it when it makes sense and take responsibility for the final result. It is this responsibility, and not the dictionary, that the machine is still unable to assume.<\/p>","protected":false},"excerpt":{"rendered":"<p>\u00c9 a pergunta que qualquer tradutor ouve com frequ\u00eancia: n\u00e3o chega usar o Google Translate ou o DeepL? A resposta curta \u00e9: depende do que pode correr mal. Para perceber um email de um fornecedor, a tradu\u00e7\u00e3o autom\u00e1tica \u00e9 uma ferramenta excelente. Para um relat\u00f3rio cl\u00ednico, um contrato ou o manual de uma m\u00e1quina, j\u00e1 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[64,63],"tags":[],"class_list":["post-3867","post","type-post","status-publish","format-standard","hentry","category-revisao","category-traducao"],"_links":{"self":[{"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/posts\/3867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/comments?post=3867"}],"version-history":[{"count":2,"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/posts\/3867\/revisions"}],"predecessor-version":[{"id":4013,"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/posts\/3867\/revisions\/4013"}],"wp:attachment":[{"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/media?parent=3867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/categories?post=3867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nadiapereira.pt\/en\/wp-json\/wp\/v2\/tags?post=3867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}