{"id":12137,"date":"2018-01-18T00:00:00","date_gmt":"2018-01-17T23:00:00","guid":{"rendered":"https:\/\/www.textform.com\/tf2019\/uncategorized\/sap-translation-hubs-reference-language-feature\/"},"modified":"2020-01-17T15:02:42","modified_gmt":"2020-01-17T14:02:42","slug":"sap-translation-hubs-reference-language-feature","status":"publish","type":"post","link":"https:\/\/www.textform.com\/en\/blog-en\/sap-translation-hubs-reference-language-feature\/","title":{"rendered":"SAP Translation Hub\u2019s Reference Language Feature"},"content":{"rendered":"

This is the third installment in my blog about SAP Translation Hub so far (see here<\/a> and here<\/a>). A lot has happened since SAP introduced this product over a year ago. As it has evolved, so too, has our SAP add-on tf-externalize for SAP<\/em><\/strong>\u00ae<\/strong> Translation Hub<\/strong><\/a>, which truly connects it to the ABAP world. Today, I want to tackle one of its features in more detail: the reference language<\/em>.<\/p>\n

The Hidden Gem<\/h2>\n

The reference language feature has been there from the beginning, and it\u2019s very, very useful. In fact, I\u2019ve called it SAP Translation Hub\u2019s \u201ckiller feature\u201d on more than one occasion. The basic idea is that instead of sending one text in one language to SAP Translation Hub, you send two texts \u2014 one in the source language and one in the reference language. The reference language text helps disambiguate the text in the source language, which allows SAP Translation Hub to return a more accurate match. This means: you improve translation quality and minimize review work.<\/p>\n

\"When

In this simplified example, \u201cCancel\u201d can be translated into French in two different ways; however, only one of the possible translations is also a valid translation for \u201cStornieren.\u201d<\/p><\/div>\n

How are you able to select two texts that mean the same thing, you ask? That\u2019s easy \u2014 if a button says Cancel<\/em> when you log on in English and Stornieren<\/em> when you log on in German, they reside in the same object and have the same ID. Now what happens if we send those two texts to the SAP Translation Hub?<\/p>\n

Disambiguation is the thing<\/h2>\n

Let\u2019s say we are translating from English into French. A text like Cancel<\/em> has two possible translations in French: Interrompre<\/em>, which means \u201ccancel an action,\u201d and Annuler<\/em>, which means \u201ccancel an invoice.\u201d In German, the situation is identical to French. Abbrechen<\/em> is used for cancelling actions and Stornieren<\/em> for cancelling invoices. This three-way relationship between English, French and German helps clarify which variety of Cancel<\/em> we need. It disambiguates<\/em> the English source text.<\/p>\n

So, if you know that the English Cancel<\/em> can be correctly translated into German with Stornieren<\/em>, you know that it is much more likely that the correct French translation is Annuler<\/em> and not Interrompre<\/em>. How do you know this? Experience, you say? Well, SAP Translation Hub\u2019s multilingual text repository works much the same way.<\/p>\n

\"A

A language vector can contain translations in any number of languages, plus metadata.<\/p><\/div>\n

SAP Translation Hub Learns from Experience, Too<\/h2>\n

SAP Translation Hub stores not just a few text pairs, but a large number of so-called vectors<\/em>. Each vector consists of a text in multiple languages that was once used to translate the same text, such as the same button on a screen, plus a large amount of metadata. This means that when you feed it not just one text, but two, it can select a vector that matches both the source language text and the reference language text. As a result, it can return a much better match.<\/p>\n

Working with a Reference Language<\/h2>\n

Of course, tf-externalize<\/em> also supports this reference language feature. This is especially useful in projects where the texts are translated into more than one language and high translation quality is expected. In such a scenario, instead of pulling translations from SAP Translation Hub<\/a> for all languages at project start, we first get translation suggestions for one language only and ask translators for that language, say German, to start translation. So, in our example, we give the Germans a head start!<\/p>\n

\"Exporting

Once German is done, we get translations from SAP Translation Hub for the other languages.<\/p><\/div>\n

Once the German translators have translated the first few packages, we use tf-externalize for SAP\u00ae Translation Hub<\/em> to get translation suggestions for all other languages from SAP Translation Hub. This time using German as a reference language. Plus, we also send the newly translated German texts in addition to the English source texts. The resulting translation suggestions will be of much higher quality, which allows the review work to go much quicker.<\/p>\n

\"German

With this process, one language finishes a few packages first before the other languages start\u2026<\/p><\/div>\n

Translation as a Relay Race<\/h2>\n

The translators for the other languages now start translating the completed packages in German, and the German translators start working on the next packages. Once these packages are completed for German, translation suggestions are again pulled from SAP Translation Hub for the other languages. This process can then be repeated until the translation is complete for all languages.<\/p>\n

This process leads to a much more cost-efficient translation process overall, without compromising quality. However, for projects where speed is of the essence, it may not be possible to give one language a head start while the other translators are waiting. Apart from the initial delay, this scenario gives you lower translation costs with essentially no downside at all.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

This is the third installment in my blog about SAP Translation Hub so far (see here and here). A lot has happened since SAP introduced this product over a year ago. As it has evolved, so too, has our SAP add-on tf-externalize for SAP\u00ae Translation Hub, which truly connects it to the ABAP world. Today, […]<\/p>\n","protected":false},"author":14,"featured_media":13895,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[339,741],"tags":[745,490,361,482,484,354,746],"_links":{"self":[{"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/posts\/12137"}],"collection":[{"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/comments?post=12137"}],"version-history":[{"count":0,"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/posts\/12137\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/media\/13895"}],"wp:attachment":[{"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/media?parent=12137"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/categories?post=12137"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.textform.com\/en\/wp-json\/wp\/v2\/tags?post=12137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}