Yen Nguyen
Mar 26, 2019
  6545
(11 votes)

Auto Translation V2 to V3 migration


Api V3 has came out.

Microsoft has migrated auto translation service api from V2 to V3 in the beginning of this year.
Version 2 was deprecated on April 30, 2018 and will be discontinued on April 30, 2019 according to Microsoft announcement here
Episerver's Language Manager add-on was updated in response to that and released in version EPiServer.Labs.LanguageManager 3.3.0.
The upgraded auto translation service's name is changed to "Cognitive Service Translation" (was "Bing Translator" before) with new api endpoint: api.cognitive.microsofttranslator.com.
Microsoft also introduces service improvements in V3:

  • Is generally available and fully supported.
  • Is GDPR compliant as a processor and satisfies all ISO 20001 and 20018 as well as SOC 3 certification requirements.
  • Allows you to invoke the neural network translation systems you have customized with Custom Translator (Preview), the new Translator NMT customization feature.
  • Does not provide access to custom translation systems created using the Microsoft Translator Hub.

Authentication

The V3 api will accept authentication key of V2, so you don't need to get a new subscription that make it easier for you to migrate to new version without breaking anything.

How to update Episerver's Language Manager package?

These updates were released in package EPiServer.Labs.LanguageManager 3.3.0. So, all you need to do is to update this package, then go to Language Manager settings change provider to "Cognitive Service Translation".
All behaviors should remain the same.


Hope you guys find this info useful. Thanks!

Mar 26, 2019

Comments

Please login to comment.
Latest blogs
Preview multiple Visitor Groups directly while browsing your Optimizely site

Visitor groups are great - it's an easy way to add personalization towards market segments to your site. But it does come with it's own set of...

Allan Thraen | Sep 26, 2022 | Syndicated blog

The Report Center is finally back in Optimizely CMS 12

With Episerver.CMS.UI 12.12.0 the Report Center is finally re-introduced in the core product.

Tomas Hensrud Gulla | Sep 26, 2022 | Syndicated blog

Dynamic Route in ASP.NET Core When MapDynamicControllerRoute Does Not Work

Background Creating one of the add-on for Optimizely I had to deal with challenge to register dynamically route for the API controller. Dynamic rou...

valdis | Sep 25, 2022 | Syndicated blog

404 Error on Static Assets Within an Optimizely plugin

Background With the move to CMS 12 and .NET 5/6, developers are now able to build Plugins and Extensions using Razor Class Libraries (RCL).  These...

Mark Stott | Sep 23, 2022

How to bypass the content creation view in Optimizely

Something that has come up a couple of times in the last few year is feedback from content editors about the editing view that comes up when creati...

Ynze | Sep 23, 2022 | Syndicated blog

Welcome to Optimizely World's New Tech Video Portal

Optimizely, leader in the digital experience realm, has become a wealth of world class SaaS products including Web Experimentation, Full Stack, B2B...

The Developer Marketing Team of Optimizely | Sep 22, 2022