Our international team celebrated the International Labour Day by shipping many new features last month.
We have built a website translation widget with Smart Routing and custom NMT, added initial support for detect-language intent, made our memoQ plugin work with formatted texts and integrated with a new Yandex Translate API. There are also several updates across MT providers — please read below.
Website Translation Widget
A while ago, Google provided Website Translator, a small JS snippet for web sites, to make them translated via Google Translate. It was a popular tool among many companies, with two significant limitations:
- It worked with public Google Translate engine, which provided generic translations and did not provide data confidentiality, and
- It was deprecated some time ago, with this translation feature moving into the Chrome browser.
Following client requests, we created a similar JS snippet. You may use it to translate your website with any cloud MT engine or even to perform translation by routing requests to a portfolio of custom NMT engines based on the language pair and URL.
You may check how it works by going to Intento website with a special URL parameter (look for a gray icon in the top-right corner!). For this case, requests are routed to different engines using the default Intento Smart Routing.
Reach us for pricing! 💸
Formatting support for memoQ
Thanks to the continuous support of the memoQ team, we have managed to properly implement the translation of the formatted texts (HTML and XML) via Intento plugin for memoQ.
Check out the last version (>1.2.2) and make sure you have memoQ >8.7.
Detect Language intent
We have added initial support for the Language Detection intent. Currently, it relies on a single AI provider, Microsoft. We expect to add more soon and also briefly evaluate them to understand what’s the difference.
Smart Routing and Terminology Support
Google Translate v3 was the first engine we enabled terminology support for last month. In our Web Tools, we have added convenient drop-downs so you can immediately see custom models and glossaries available on your Google account.
As our clients use more and more custom Smart Routing schemas, we added new metadata to the async job log. Now, for every job you run via Intento you see what Smart Routing table was used, where the requests were routed, and what custom model and glossary were used for this job.
Machine Translation Provider Updates
New Yandex Instance with Custom Model parameter (just in case)
We have integrated the new Yandex Translate API. You can use it in our Web Tools and plugins for Trados, memoQ and other CAT/TMS tools.
Besides the simplified authentication, we have noticed that the machine-readable API specification contains a parameter for a custom model id!
Whoa! It seems some big news are coming! We have added its support, just in case 😉
Amazon Translate adds Hindi, Malay, Norwegian and Persian
Amazon Translate quietly added support for Hindi, Malay, Norwegian and Persian. We did not see any announcement, but our API monitoring immediately noticed the change. Make sure you checked it out — Amazon ships amazing MT models lately.
This added another 177 language pairs to Amazon Translate. Interestingly, not all of them are symmetric. If you need to translate from Norwegian to Arabic, you still have to go somewhere else.
PROMT adds Dutch to German
Another thing our robots have found is that PROMT adds support for NL->DE language pair. We do not know if it is a pivotal pair or not — if not, this may be a good one.
Microsoft postpones switching off the Hub and API v2
Microsoft postponed switching off Text Translator API v2 and Microsoft Translator Hub till May 17th. Make sure you have migrated by then! Having it postponed for the third time would be too much luck!
Baidu launches vertical pre-trained engines
Baidu publishes the first three pre-trained vertical MT engines (including IT and Biomedical) for few language pairs. We’ll figure out how to support them on our side.
