Automatic translations in COYO – COYO Campus

In your COYO, you can have timeline posts and comments translated – completely automatically, without having to copy your text.

Prerequisite for activation

In order to enjoy automatic translations, two criteria need to be fulfilled:

You need our COYO Multi-Language add-on
You have a DeepL API package

Note:

This function is provided with the translation service DeepL. To be able to use the service from DeepL, you need to have a paid DeepL API package. This gives you an API key, which you insert in the Administration of your COYO.

Other translation services: Microsoft Translator

From Cloud release 31, you can connect an alternative to DeepL: The Microsoft Translator. Unlike DeepL (11), Microsoft Translator offers more languages.

Note:
Microsoft Translator is included in the Microsoft 365 license.

A translation in one click

Do you have a post or comment in your timeline that isn’t in the language that you have set in COYO? No problem, the translation feature allows you to display the post or comment in your language. Simply click on the "Translate" button and you’ll get the translation.

Available languages

DeepL currently supports 21 languages: German, English, French, Spanish, Portuguese, Polish, Russian, Italian, Dutch, Chinese, Japanese, Bulgarian, Czech, Danish, Estonian, Finnish, Greek, Hungarian, Latvian, Lithuanian, Romanian, Slovak, Slovenian, and Swedish.
Microsoft Translator supports over 100 languages. You can find an overview here.

Connect translation service

You need an API key to use one of the translation services. You can find out where to find this for DeepL and Microsoft in the following section.

To save the corresponding API key in COYO, go to "Administration" > "General settings" and add a tick next to "Activate automatic translations". The menu expands, you select the translation provider and enter the API key.

Retrieve API key from DeepL

Note:
For On-Premises installations, the service has to first be activated on the server. To do this, set the parameter COYO_ENABLE_TRANSLATION in the .env file. You then need to restart your COYO.

You can find the API key from DeepL in your DeepL account:

Costs for the DeepL API package

You can find the costs for the DeepL API package ("For developers") directly on the provider’s website and also take out a package there. You pay a basic fee and then per translated character. But don’t worry: You don’t pay for each translation performed on the same post, but for the one-time translation of the post into the respective target language.

Example:
If person A translates an English post into German, a price per translated character is paid for this. If person B also translates the same post into German later on, this has already been performed and paid for with the translation for person A. If, however, person B translates into Spanish, this would be a different target language and so a new translation would be paid for with a one-time price per translated character.

Retrieve API key from Microsoft Translator

To use the automatic translations from Microsoft Translator, you need to create a Microsoft Translator resource in your Azure Active Directory. You can find out how that works in the Microsoft documentation for Microsoft Translator.

Once you’ve completed this step, you’ll find the subpoint "Keys and Endpoints" in Resource Management. Here you will find the key that you save in the COYO Administration under the general settings (see section "Connect translation service" here in the article).

Note:
Please make sure that you also save the location. Your API key only functions for the configured location.

Costs of Microsoft Translator

Microsoft Translator is part of the Microsoft Cognitive Services Up to 2 million characters are free per month, then you can choose between various packages. You can find out more about the price structure here.

Why am I getting incorrect translations?

We often receive inquiries about incorrect automatic translations. However, this is not due to COYO or the DeepL package, but instead results from browser plugins. If users have activated a translation plugin in their browser, pages or parts of them that these translators identify as deviating from the user’s system language are automatically translated. We recommend deactivating the browser add-on so that it doesn’t cause incorrect translations.